I'm running wrapper inside OpenVZ virtual server (Debian 4 distro). I have previously used wrapper 3.2.3 which has worked perfectly. Now after upgrading to wrapper 3.3.0 pro, wrapper.daemonize=TRUE (wrapper start) does not work, only wrapper console mode works.
With daemonize, it seems like the java process is not started, only the wrapper process remains running. With wrapper.debug=TRUE, this is all that gets logged:
DEBUG | wrapper | 2008/06/10 00:44:35 | Using tick timer.
DEBUG | wrapper | 2008/06/10 00:44:35 | Enqueue Event 'wrapper_start'
DEBUG | wrapperp | 2008/06/10 00:44:35 | server listening on port 32000.
With console mode, the command line is logged next like it should be.
If I switch back to wrapper 3.2.3, using the same wrapper.conf, everything works like a charm also with daemonize.
Logged In: YES
user_id=614736
Originator: NO
I'm having the same problem on a SLES10 64-bit system. Wrapper 3.3.0 pro doesn't start the application when daemonize is TRUE. Wrapper 3.3.0 Community edition works correctly.
Logged In: YES
user_id=228081
Originator: NO
I was able to reproduce this on one of our test machines in house. It appears to be a problem only with the Professional edition and is being caused by the internal event queue thread. I am working on this tonight and will post back shortly.
Cheers,
Leif
Logged In: YES
user_id=228081
Originator: NO
I was unable to post here immediately because the SF system was not accepting logins for a while.
I managed to get this fixed late that night and released a temporary version which fixes this. You can get it here:
http://wrapper.tanukisoftware.org/downloads/3.3.1-a/
I only released the Linux and Windows versions for both 32 and 64-bit. The Windows was released so both could be used. Please let me know if you need other platforms in the short term, but we will try to get an official release out soon.
Cheers,
Leif
Logged In: YES
user_id=614736
Originator: NO
3.3.1-a works for me (SLES10 64-bit)