|
From: Leif M. <le...@ta...> - 2005-06-05 21:36:58
|
Ralph,
Could you try turning on wrapper.debug=true in the those child
processes? From
the log, it looks like the Wrapper is successfully launching the JVM
process. But that
Java process is having a hard time loading its jvm.dll. That is just
about the first thing
the Java executable does so this is a pretty low level problem.
I can't think of anything that the Wrapper would be doing that would
affect this.
The Wrapper does open a socket to communicate with the JVM, but that
does not
look like the problem. Unless you specify different port values, the
Wrapper will
default to using a port in the range 32000-32999. If those are all full
then you would
get an error, but you are not seeing that. Turning on debug output will
show the port
that is being used.
Out of curiosity, have you tried running all of those JVMs without
the Wrapper?
Cheers,
Leif
Ralph Schreyer wrote:
>Hello,
>
>we use the Java Service Wrapper to put a Java Process under the control of a Windows Service. This Java Process in turn controls up to, say, 100 tiny Java Proxies, where each is wrapped in its own Java Service Wrapper.
>
>In other words: E.g. after a reboot of the machine, one Windows Service starts the Java Service wrapper which starts the main Java Process, which in turn starts up to 100 Java Service Wrappers which again start their tiny Java Proxies.
>
>Now, the problem is that after the startup of some 20 or 30 Java Service Wrappers we obtain error messages shown below and no more wrappers can start. CPU or memory are not problematic.
>
>Any ideas?
>
>
>Thank you very much and best regards
>
>Ralph
>
>---------------------------------------------------------------------------------------------------------------------
>STATUS | wrapper | 2005/06/02 16:43:10 | --> Wrapper Started as Console
>STATUS | wrapper | 2005/06/02 16:43:10 | Launching a JVM...
>INFO | jvm 1 | 2005/06/02 16:43:10 | Error loading: C:\Progra~1\prince\releases\1.0.1\shared\jre\1.4.2_04\bin\client\jvm.dll
>ERROR | wrapper | 2005/06/02 16:43:10 | JVM exited while loading the application.
>STATUS | wrapper | 2005/06/02 16:43:14 | Launching a JVM...
>INFO | jvm 2 | 2005/06/02 16:43:14 | Error loading: C:\Progra~1\prince\releases\1.0.1\shared\jre\1.4.2_04\bin\client\jvm.dll
>ERROR | wrapper | 2005/06/02 16:43:14 | JVM exited while loading the application.
>STATUS | wrapper | 2005/06/02 16:43:18 | Launching a JVM...
>INFO | jvm 3 | 2005/06/02 16:43:19 | Error loading: C:\Progra~1\prince\releases\1.0.1\shared\jre\1.4.2_04\bin\client\jvm.dll
>ERROR | wrapper | 2005/06/02 16:43:19 | JVM exited while loading the application.
>STATUS | wrapper | 2005/06/02 16:43:23 | Launching a JVM...
>INFO | jvm 4 | 2005/06/02 16:43:23 | Error loading: C:\Progra~1\prince\releases\1.0.1\shared\jre\1.4.2_04\bin\client\jvm.dll
>ERROR | wrapper | 2005/06/02 16:43:23 | JVM exited while loading the application.
>STATUS | wrapper | 2005/06/02 16:43:27 | Launching a JVM...
>INFO | jvm 5 | 2005/06/02 16:43:27 | Error loading: C:\Progra~1\prince\releases\1.0.1\shared\jre\1.4.2_04\bin\client\jvm.dll
>ERROR | wrapper | 2005/06/02 16:43:27 | JVM exited while loading the application.
>FATAL | wrapper | 2005/06/02 16:43:27 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
>FATAL | wrapper | 2005/06/02 16:43:27 | There may be a configuration problem: please check the logs.
>STATUS | wrapper | 2005/06/02 16:43:28 | <-- Wrapper Stopped
>
>
|