It's in the latest version and in the linux "bin\testwrapper" on
line 130. I guess the same script is used for other *nix
systems.
Heres the line:
exec $CMDNICE $WRAPPER_CMD $WRAPPER_CONF
wrapper.pidfile=$PIDFILE wrapper.debug=true
wrapper.java.additional.1="-DFOO=This is a test"
As you see it seems to have some debug data there. I've
took the testwrapper script to use for a app at work and I
got confused why it debuged to console when I have ERROR
as log level in the config file. And the java additional broke
the settings to the app aswell. It worked fine in win32 but on
unix it didn't work at all. :-)
Anyway, is that stuff needed to be there, I think it's some
what confusing.
Cheers,
Spocke
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ooops. Not sure how I managed that. It was a mistake when
I made the release. That is not in CVS and it is not in
the src/bin/sh.script.in file. I must have been doing some
testing just before that release. I checked it is only a
problem in the linux distribution. I'll rework that part of
the build to make sure that it does not happen again.
In general, it is a good idea to copy the
src/bin/sh.script.in file and use that for your
applications. That is the official template file.
Thanks for pointing this out.
Cheers,
Leif
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=228081
Hey Spocke. Good to hear from you.
What debug output are you referring to? Are you sure that
you do not have any debug output enabled? I just tried it
out and see no problems.
If you are still seeing a problem, what version of the
Wrapper are you using? What are you seeing etc.
Cheers,
Leif
Logged In: YES
user_id=196697
Ok, sorry for my "not so good" description. :-)
It's in the latest version and in the linux "bin\testwrapper" on
line 130. I guess the same script is used for other *nix
systems.
Heres the line:
exec $CMDNICE $WRAPPER_CMD $WRAPPER_CONF
wrapper.pidfile=$PIDFILE wrapper.debug=true
wrapper.java.additional.1="-DFOO=This is a test"
As you see it seems to have some debug data there. I've
took the testwrapper script to use for a app at work and I
got confused why it debuged to console when I have ERROR
as log level in the config file. And the java additional broke
the settings to the app aswell. It worked fine in win32 but on
unix it didn't work at all. :-)
Anyway, is that stuff needed to be there, I think it's some
what confusing.
Cheers,
Spocke
Logged In: YES
user_id=228081
Ooops. Not sure how I managed that. It was a mistake when
I made the release. That is not in CVS and it is not in
the src/bin/sh.script.in file. I must have been doing some
testing just before that release. I checked it is only a
problem in the linux distribution. I'll rework that part of
the build to make sure that it does not happen again.
In general, it is a good idea to copy the
src/bin/sh.script.in file and use that for your
applications. That is the official template file.
Thanks for pointing this out.
Cheers,
Leif
Logged In: YES
user_id=196697
Excelent that you fixed it. I will use the source script in the
future. It's just so convinient to use the one disted in bin. :-)
Cheers,
Spocke