-
Tested 3.3.7 Logfile handling using WRAPPER_PID.
Works perfectly.
I now use:
wrapper.logfile=%TEMP%/MyAppName-%WRAPPER_PID%.log
wrapper.logfile.rollmode=WRAPPER.
2009-10-28 19:09:08 UTC in Java Service Wrapper
-
Hmm, thanks for that hint. But as you already pointed out, this would make it impossible to find out the logfile's name at runtime from my app.
Therefore I either need a way to find out the actual logfile's name or (and ;-) as you mentionned the PID as a ENV variable.
Do you have any plans when to release a next version of the wrapper?.
2009-09-30 13:16:25 UTC in Java Service Wrapper
-
sorry, I entered this as a FeatureRequest accidentially. It really is a BUG.
2009-09-30 06:08:56 UTC in Java Service Wrapper
-
I am using wrapper as a launcher for my GUI-Application. This Application can be started multiple times. There is currently no way of separating the log output for multiple invocations of the same application.
Should have the possibility to either have a PID or some sort of invocation count to be part of the logfile name like we can do it in java's logging api.
2009-09-29 21:34:26 UTC in Java Service Wrapper
-
This has been requested some while ago in ID: 973781 already.
I am able to read out the wrapper.logfile property through WrapperManager.getProperties().
However, when some rollmode is enabled, the current Logfile name is not obvious. I can't see any way of getting out the current logfile name with the existing API other than by guessing the name.
Something like...
2009-09-29 21:29:24 UTC in Java Service Wrapper
-
On WIndows 32-bit, each process may use a maximum of 2GB Ram theoretically.
However, the Shadowing of PCI-Adresses consumes some parts of the Adress-Space and therefore, not the full 2GB of Ram are available for the Processes.
Therefore, if you have a system with for example 4 GB Ram installed using Win32, Launch4J fails to start if using "90". Our internal...
2009-08-05 11:35:35 UTC in Launch4j Executable Wrapper
-
I would also very like this feature implemented.
We have now had several bugs now because the settings for RBE were not correct on some workspaces.
2008-11-05 12:18:01 UTC in Eclipse ResourceBundle Editor
-
Does this patch also work on x64 ?.
2007-09-17 06:23:21 UTC in Launch4j Executable Wrapper
-
Launcher works with 32-bit-VM on Win XP 32-Bit and Win XP 64-bit. SO far so good.
But it does not work when it should launch the AMD64 VM.
Guess this is, because the launcher tries to laounch the VM In-Process from within a 32-bit Process.
In that case, WinRun4J.exe should be compiled for amd64.
Other launchers are able to launch even 64-bit VM's, because it doesn't launch it...
2007-08-13 11:51:34 UTC in WinRun4J
-
You may take a look at the implementation of "WinRun4J" (http://winrun4j.sourceforge.net/) which implements this for Windows.
What you would have to look at is, that a 32-bit System has at max. 2GB available for an Application. Also not the full 2GB might be available for the Heap, because the VM needs a contiguous Address Space. WinRun4J does a very good job with that (but is not suitable for...
2007-08-13 11:02:00 UTC in Java Service Wrapper
