|
From: Mayes, R. <Reb...@G1...> - 2007-11-02 15:25:35
|
I have the same problem many others seem to have- the wrapper sometimes doesn't get a response from the JVM within the timeout period, so it shuts it down: JVM appears hung: Timed out waiting for signal from JVM. JVM did not exit on request, terminated >From everything I've read on the web, the solutions are: 1. Extend the timeout period (risking a longer hang when there's a "real" problem) 2. Do what you can to make sure the JVM is not overburdened. My questions are: 1. We predominantly see this on AIX. Is there some special problem with IBM's JVM and the wrapper? We have Java 1.5 SR4 on our test machine and I am going to try updating it to the latest (SR6) today. 2. Will reducing the memory allocated to Java help? Currently, we're using wrapper.java.initmemory=1024 and wrapper.java.maxmemory=1024 on a box with 1.8 GB of RAM. 3. Any other suggestions? Thanks! Rebecca Mayes Manager of CDQ/DI Quality Assurance Pitney Bowes Software NOTICE: This E-mail may contain confidential information. If you are not the addressee or the intended recipient please do not read this E-mail and please immediately delete this e-mail message and any attachments from your workstation or network mail system. If you are the addressee or the intended recipient and you save or print a copy of this E-mail, please place it in an appropriate file, depending on whether confidential information is contained in the message. |