-
Dobes,
I will give this some thought about how we can work something into the released product
As is, you will want to look at the Javadocs for the WrapperSimpleApp class. It is designed to work with all user Main classes. Some of which do not return. So it does not wait for the main method to return by default. You can change this by setting the...
2009-12-19 03:33:20 UTC in Java Service Wrapper
-
Ajmal,
What version of the Wrapper are you using? This is actually not a "crash of the Wrapper". The problem is that Wrapper is failing to launch your configured JVM. This is usually caused by the JVM path being incorrect.
Please set the wrapper.java.command.loglevel=INFO property to see more information on the Java command that the Wrapper is attempting to run. If the Wrapper is quite...
2009-12-11 16:57:56 UTC in Java Service Wrapper
-
Oh!. I see the problem. If you look carefully, you have added two ConsoleAppenders to the Root logger. One in the main method, and then again in the start method.
Because of this, when you log something, anything, you will get two lines of output.
I have not tested this, but it looks like the problem. Try removing the addAppender method from the start method.
Let me know how this...
2009-12-10 08:52:02 UTC in Java Service Wrapper
-
I ran some tests calling a WrapperListener from a WrapperSimpleApp helper class as I described, and the Wrapper actually handles that case correctly by reporting the following error:
---
WrapperSimpleApp:
WrapperSimpleApp: Encountered an error running main:
WrapperSimpleApp: java.lang.IllegalStateException: WrapperManager has already been started with a WrapperListener.
WrapperSimpleApp:
2009-12-10 08:45:31 UTC in Java Service Wrapper
-
The code you wrote looks correct. My first guess is that you are using one of the Wrapper's helper classes to launch your code. When you implement your own WrapperListener, you will be using Integration Method #3.
http://wrapper.tanukisoftware.org/doc/english/integrate.html#method3
If you were to use Method #1 for example, then the WrapperSimpleApp helper class would initialize the Wrapper...
2009-12-10 06:13:25 UTC in Java Service Wrapper
-
Robert,
We were able to resolve another unrelated problem that was forcing us to use an old compiler. The next release, 3.4.0, will be made using a newer compiler. Our tests against the Symantec tool show that when the wrapper is built with the new compiler it passes their scans.
Cheers,
Leif.
2009-12-01 23:15:57 UTC in Java Service Wrapper
-
mortenson committed revision 1508 to the Java Service Wrapper SVN repository, changing 9 files.
2009-12-01 15:31:50 UTC in Java Service Wrapper
-
mortenson committed revision 1507 to the Java Service Wrapper SVN repository, changing 1 files.
2009-12-01 15:28:30 UTC in Java Service Wrapper
-
Vinay,
Currently we do not support this directly. For a near future version, what is the behavior you would like to see?
For example, send an email when JVM memory usage crosses a specific level. What if it drops back below the memory warning level and crosses back up again?
As I think about how to implement this, please let me know what exactly you would like to see in a perfect world.
2009-11-30 07:39:28 UTC in Java Service Wrapper
-
Rob,
This has been an issue that a few people have reported over the years. We have never been able to reproduce it however. I have run 50 Wrappers at once in the past without problems while trying to track this down.
We will take a look at it again. Could you answer a few questions?
1) What is the Wrapper version you are using?
2) What is your total system memory?
3) What is the in...
2009-11-25 03:15:44 UTC in Java Service Wrapper
