Menu
▾
▴
wrapper-user
|
From: Earnie D. <ed...@vr...> - 2005-06-03 14:01:00
|
Could it be a memory issue? Why do you need to start your proxies as = individual wrapper instances? Could they not just be threads started by = the "main" wrapper class? Earnie! -----Original Message----- From: wra...@li... [mailto:wra...@li...]On Behalf Of Ralph Schreyer Sent: Friday, June 03, 2005 9:58 AM To: wra...@li... Subject: [Wrapper-user] Problems while starting multiple wrappers 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 __________________________________________________________ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=3D021201 ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit = http://developer.yahoo.net/?fr=3Doffad-ysdn-ostg-q22005 _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Ralph S. <ral...@we...> - 2005-06-05 20:02:21
|
Hi Earnie, thank you very much for your reply. As I stated in my description of the p= roblem, memory is no issue. The Java Proxies I've been talking about are v= arious distributed JINI services which are all uniformely wrapped by a Jav= a Service Wrapper, such that our main Jave Process can easily start, stop = and control the JINI services in a generic fashion. Well, that's just our = architecture, and it was nice if we could keep an using the Java Service W= rapper, because until now it did a great job. Cheers, Ralph wra...@li... schrieb am 03.06.05 16:02:14: >=20 > Could it be a memory issue=3F Why do you need to start your proxies as ind= ividual wrapper instances=3F Could they not just be threads started by the "= main" wrapper class=3F >=20 > Earnie! >=20 > -----Original Message----- > From: wra...@li... > [mailto:wra...@li...]On Behalf Of Ralph > Schreyer > Sent: Friday, June 03, 2005 9:58 AM > To: wra...@li... > Subject: [Wrapper-user] Problems while starting multiple wrappers >=20 >=20 > Hello, >=20 > 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 t= iny Java Proxies, where each is wrapped in its own Java Service Wrapper. >=20 > 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 ti= ny Java Proxies. >=20 > Now, the problem is that after the startup of some 20 or 30 Java Servic= e Wrappers we obtain error messages shown below and no more wrappers can s= tart. CPU or memory are not problematic. >=20 > Any ideas=3F >=20 >=20 > Thank you very much and best regards >=20 > Ralph >=20 > ------------------------------------------------------------------------= --------------------------------------------- > 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\pri= nce\releases\1.0.1\shared\jre\1.4.2=5F04\bin\client\jvm.dll > ERROR | wrapper | 2005/06/02 16:43:10 | JVM exited while loading the a= pplication. > 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\pri= nce\releases\1.0.1\shared\jre\1.4.2=5F04\bin\client\jvm.dll > ERROR | wrapper | 2005/06/02 16:43:14 | JVM exited while loading the a= pplication. > 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\pri= nce\releases\1.0.1\shared\jre\1.4.2=5F04\bin\client\jvm.dll > ERROR | wrapper | 2005/06/02 16:43:19 | JVM exited while loading the a= pplication. > 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\pri= nce\releases\1.0.1\shared\jre\1.4.2=5F04\bin\client\jvm.dll > ERROR | wrapper | 2005/06/02 16:43:23 | JVM exited while loading the a= pplication. > 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\pri= nce\releases\1.0.1\shared\jre\1.4.2=5F04\bin\client\jvm.dll > ERROR | wrapper | 2005/06/02 16:43:27 | JVM exited while loading the a= pplication. > FATAL | wrapper | 2005/06/02 16:43:27 | There were 5 failed launches i= n 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 >=20 > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. > weltweit telefonieren! http://freephone.web.de/=3Fmc=3D021201 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by Yahoo. > Introducing Yahoo! Search Developer Network - Create apps using Yahoo! > Search APIs Find out how you can build Yahoo! directly into your own > Applications - visit http://developer.yahoo.net/=3Ffr=3Doffad-ysdn-ostg-q220= 05 > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by Yahoo. > Introducing Yahoo! Search Developer Network - Create apps using Yahoo! > Search APIs Find out how you can build Yahoo! directly into your own > Applications - visit http://developer.yahoo.net/=3Ffr=FFfad-ysdn-ostg-q22005= > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/=3Fmc=3D021201 |
|
From: Ralph S. <ral...@we...> - 2005-06-05 20:08:50
|
Hi, thank you very much for your answer. Ports could be a problem, if the wrapper uses them, but 1. I did not find any clue which points to a port problem 2. ports should not be a problem, because we do not need more than a hundred Cheers Ralph wra...@li... schrieb am 03.06.05 16:35:08: > > I believe that the wrapper uses a port to communicate with the JVM. > Maybe you are running out of ports? > > I'm sure Leif will weigh in with a much more informed answer, but this > might be something to look at. > > 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 > > > >__________________________________________________________ > >Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. > >weltweit telefonieren! http://freephone.web.de/?mc=021201 > > > > > > > >------------------------------------------------------- > >This SF.Net email is sponsored by Yahoo. > >Introducing Yahoo! Search Developer Network - Create apps using Yahoo! > >Search APIs Find out how you can build Yahoo! directly into your own > >Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 > >_______________________________________________ > >Wrapper-user mailing list > >Wra...@li... > >https://lists.sourceforge.net/lists/listinfo/wrapper-user > >--- > >[This E-mail scanned for viruses by Declude Virus] > > > > > > > > > > > --- > [This E-mail scanned for viruses by Declude Virus] > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Yahoo. > Introducing Yahoo! Search Developer Network - Create apps using Yahoo! > Search APIs Find out how you can build Yahoo! directly into your own > Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 |
|
From: Ralph S. <ral...@we...> - 2005-06-07 08:42:18
|
Hello Leif, thank you very much for your answer. I turned on wrapper.debug=true and generated the output shown below, i.e. the JVM exits with code 6 (SIGABRT, afaik) In a test run, I started more than a hundred JVMs (each starting my Java service) on my PC without any problems. As soon as I wrap the calls into the Java Service Wrapper, the JVMs crash when starting more than ~ 30. Cheers Ralph STATUS | wrapper | 2005/06/06 16:49:57 | --> Wrapper Started as Console DEBUG | wrapper | 2005/06/06 16:49:57 | Using system timer. DEBUG | wrapperp | 2005/06/06 16:49:58 | server listening on port 32030. STATUS | wrapper | 2005/06/06 16:49:58 | Launching a JVM... DEBUG | wrapper | 2005/06/06 16:49:58 | command: "C:\Progra~1\prince\releases\1.0.1\shared\jre\1.4.2_04\bin\jav4tstProxy" -DUFS_HOME=C:/Progra~1/prince/releases/1.0.1/ -Djava.security.policy=C:/Progra~1/prince/releases/1.0.1/shared/policy.all -Djava.rmi.server.codebase="http://localhost:8080/prince_stubs_and_jini.jar" -Dwrapper.asport=30178 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Xms1M -Xmx2M -Xms1m -Xmx2m -Djava.library.path="C:/Progra~1/prince/releases/1.0.1/shared/lib/" -classpath "C:/Progra~1/prince/releases/1.0.1/shared/lib/prince_common.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jakarta-log4j.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/share! d/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/prince_tstproxy.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/antlr.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jini-core.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jini-ext.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jsc.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jug.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/util.concurrent.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/xmlrpc-1.2-b1.jar" -Dwrapper.key="L_8OgXHlgP5qQr5c" -Dwrapper.port=32030 -Dwrapper.debug="TRUE" -Dwrapper.use_system_time="TRUE" -Dwrapper.version="3.1.2" -Dwrapper.native_library="wrapper" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp prince.middleware.tstproxy.TstProxyService ../shared/TT_4/bin test.! exe DEBUG | wrapper | 2005/06/06 16:49:58 | JVM started (PID=4628) INFO | jvm 1 | 2005/06/06 16:49:58 | Error loading: C:\Progra~1\prince\releases\1.0.1\shared\jre\1.4.2_04\bin\client\jvm.dll DEBUG | wrapper | 2005/06/06 16:49:58 | JVM process exited with a code of 6, setting the wrapper exit code to 6. ERROR | wrapper | 2005/06/06 16:49:58 | JVM exited while loading the application. DEBUG | wrapper | 2005/06/06 16:49:58 | JVM was only running for 0 seconds leading to a failed restart count of 1. DEBUG | wrapper | 2005/06/06 16:49:58 | Waiting 5 seconds before launching another JVM. STATUS | wrapper | 2005/06/06 16:50:02 | Launching a JVM... DEBUG | wrapper | 2005/06/06 16:50:03 | command: "C:\Progra~1\prince\releases\1.0.1\shared\jre\1.4.2_04\bin\jav4tstProxy" -DUFS_HOME=C:/Progra~1/prince/releases/1.0.1/ -Djava.security.policy=C:/Progra~1/prince/releases/1.0.1/shared/policy.all -Djava.rmi.server.codebase="http://localhost:8080/prince_stubs_and_jini.jar" -Dwrapper.asport=30178 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Xms1M -Xmx2M -Xms1m -Xmx2m -Djava.library.path="C:/Progra~1/prince/releases/1.0.1/shared/lib/" -classpath "C:/Progra~1/prince/releases/1.0.1/shared/lib/prince_common.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jakarta-log4j.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/share! d/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/prince_tstproxy.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/antlr.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jini-core.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jini-ext.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jsc.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jug.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/util.concurrent.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/xmlrpc-1.2-b1.jar" -Dwrapper.key="Pj2tkNgNfVYtTsbA" -Dwrapper.port=32030 -Dwrapper.debug="TRUE" -Dwrapper.use_system_time="TRUE" -Dwrapper.version="3.1.2" -Dwrapper.native_library="wrapper" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=2 org.tanukisoftware.wrapper.WrapperSimpleApp prince.middleware.tstproxy.TstProxyService ../shared/TT_4/bin test.! exe DEBUG | wrapper | 2005/06/06 16:50:03 | JVM started (PID=4688) INFO | jvm 2 | 2005/06/06 16:50:03 | Error loading: C:\Progra~1\prince\releases\1.0.1\shared\jre\1.4.2_04\bin\client\jvm.dll DEBUG | wrapper | 2005/06/06 16:50:03 | JVM process exited with a code of 6, setting the wrapper exit code to 6. ERROR | wrapper | 2005/06/06 16:50:03 | JVM exited while loading the application. DEBUG | wrapper | 2005/06/06 16:50:03 | JVM was only running for 0 seconds leading to a failed restart count of 2. DEBUG | wrapper | 2005/06/06 16:50:03 | Waiting 5 seconds before launching another JVM. STATUS | wrapper | 2005/06/06 16:50:07 | Launching a JVM... DEBUG | wrapper | 2005/06/06 16:50:07 | command: "C:\Progra~1\prince\releases\1.0.1\shared\jre\1.4.2_04\bin\jav4tstProxy" -DUFS_HOME=C:/Progra~1/prince/releases/1.0.1/ -Djava.security.policy=C:/Progra~1/prince/releases/1.0.1/shared/policy.all -Djava.rmi.server.codebase="http://localhost:8080/prince_stubs_and_jini.jar" -Dwrapper.asport=30178 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Xms1M -Xmx2M -Xms1m -Xmx2m -Djava.library.path="C:/Progra~1/prince/releases/1.0.1/shared/lib/" -classpath "C:/Progra~1/prince/releases/1.0.1/shared/lib/prince_common.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jakarta-log4j.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/share! d/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/prince_tstproxy.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/antlr.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jini-core.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jini-ext.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jsc.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jug.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/util.concurrent.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/xmlrpc-1.2-b1.jar" -Dwrapper.key="L_t8ai3B9ul_ExPb" -Dwrapper.port=32030 -Dwrapper.debug="TRUE" -Dwrapper.use_system_time="TRUE" -Dwrapper.version="3.1.2" -Dwrapper.native_library="wrapper" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=3 org.tanukisoftware.wrapper.WrapperSimpleApp prince.middleware.tstproxy.TstProxyService ../shared/TT_4/bin test.! exe DEBUG | wrapper | 2005/06/06 16:50:07 | JVM started (PID=4748) INFO | jvm 3 | 2005/06/06 16:50:07 | Error loading: C:\Progra~1\prince\releases\1.0.1\shared\jre\1.4.2_04\bin\client\jvm.dll DEBUG | wrapper | 2005/06/06 16:50:07 | JVM process exited with a code of 6, setting the wrapper exit code to 6. ERROR | wrapper | 2005/06/06 16:50:07 | JVM exited while loading the application. DEBUG | wrapper | 2005/06/06 16:50:07 | JVM was only running for 0 seconds leading to a failed restart count of 3. DEBUG | wrapper | 2005/06/06 16:50:07 | Waiting 5 seconds before launching another JVM. STATUS | wrapper | 2005/06/06 16:50:11 | Launching a JVM... DEBUG | wrapper | 2005/06/06 16:50:12 | command: "C:\Progra~1\prince\releases\1.0.1\shared\jre\1.4.2_04\bin\jav4tstProxy" -DUFS_HOME=C:/Progra~1/prince/releases/1.0.1/ -Djava.security.policy=C:/Progra~1/prince/releases/1.0.1/shared/policy.all -Djava.rmi.server.codebase="http://localhost:8080/prince_stubs_and_jini.jar" -Dwrapper.asport=30178 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Xms1M -Xmx2M -Xms1m -Xmx2m -Djava.library.path="C:/Progra~1/prince/releases/1.0.1/shared/lib/" -classpath "C:/Progra~1/prince/releases/1.0.1/shared/lib/prince_common.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jakarta-log4j.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/share! d/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/prince_tstproxy.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/antlr.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jini-core.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jini-ext.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jsc.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jug.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/util.concurrent.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/xmlrpc-1.2-b1.jar" -Dwrapper.key="RyIlMWfaCDdZzrC5" -Dwrapper.port=32030 -Dwrapper.debug="TRUE" -Dwrapper.use_system_time="TRUE" -Dwrapper.version="3.1.2" -Dwrapper.native_library="wrapper" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=4 org.tanukisoftware.wrapper.WrapperSimpleApp prince.middleware.tstproxy.TstProxyService ../shared/TT_4/bin test.! exe DEBUG | wrapper | 2005/06/06 16:50:12 | JVM started (PID=3112) INFO | jvm 4 | 2005/06/06 16:50:12 | Error loading: C:\Progra~1\prince\releases\1.0.1\shared\jre\1.4.2_04\bin\client\jvm.dll DEBUG | wrapper | 2005/06/06 16:50:12 | JVM process exited with a code of 6, setting the wrapper exit code to 6. ERROR | wrapper | 2005/06/06 16:50:12 | JVM exited while loading the application. DEBUG | wrapper | 2005/06/06 16:50:12 | JVM was only running for 0 seconds leading to a failed restart count of 4. DEBUG | wrapper | 2005/06/06 16:50:12 | Waiting 5 seconds before launching another JVM. STATUS | wrapper | 2005/06/06 16:50:16 | Launching a JVM... DEBUG | wrapper | 2005/06/06 16:50:16 | command: "C:\Progra~1\prince\releases\1.0.1\shared\jre\1.4.2_04\bin\jav4tstProxy" -DUFS_HOME=C:/Progra~1/prince/releases/1.0.1/ -Djava.security.policy=C:/Progra~1/prince/releases/1.0.1/shared/policy.all -Djava.rmi.server.codebase="http://localhost:8080/prince_stubs_and_jini.jar" -Dwrapper.asport=30178 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Dnet.jini.discovery.interface=dusw1d06 -Xms1M -Xmx2M -Xms1m -Xmx2m -Djava.library.path="C:/Progra~1/prince/releases/1.0.1/shared/lib/" -classpath "C:/Progra~1/prince/releases/1.0.1/shared/lib/prince_common.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jakarta-log4j.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/share! d/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/wrapper.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/prince_tstproxy.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/antlr.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jini-core.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jini-ext.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jsc.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/jug.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/util.concurrent.jar;C:/Progra~1/prince/releases/1.0.1/shared/lib/xmlrpc-1.2-b1.jar" -Dwrapper.key="blr2877lahzjkFQq" -Dwrapper.port=32030 -Dwrapper.debug="TRUE" -Dwrapper.use_system_time="TRUE" -Dwrapper.version="3.1.2" -Dwrapper.native_library="wrapper" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=5 org.tanukisoftware.wrapper.WrapperSimpleApp prince.middleware.tstproxy.TstProxyService ../shared/TT_4/bin test.! exe DEBUG | wrapper | 2005/06/06 16:50:16 | JVM started (PID=4864) INFO | jvm 5 | 2005/06/06 16:50:16 | Error loading: C:\Progra~1\prince\releases\1.0.1\shared\jre\1.4.2_04\bin\client\jvm.dll DEBUG | wrapper | 2005/06/06 16:50:16 | JVM process exited with a code of 6, setting the wrapper exit code to 6. ERROR | wrapper | 2005/06/06 16:50:16 | JVM exited while loading the application. DEBUG | wrapper | 2005/06/06 16:50:16 | JVM was only running for 0 seconds leading to a failed restart count of 5. FATAL | wrapper | 2005/06/06 16:50:16 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. FATAL | wrapper | 2005/06/06 16:50:16 | There may be a configuration problem: please check the logs. STATUS | wrapper | 2005/06/06 16:50:16 | <-- Wrapper Stopped wra...@li... schrieb am 05.06.05 23:41:45: > > 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 > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput > a projector? How fast can you ride your desk chair down the office luge track? > If you want to score the big prize, get to know the little guy. > Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 |
|
From: Leif M. <le...@ta...> - 2005-06-07 13:05:03
|
Ralph, were those 100 JVMs each launched from their own console or were they all launched as child processes of a single JVM like you are trying to do with your real applications? I have never tried exactly what you are trying. It sounds like a resource issue of some kind. A single JVM uses quite a few file handles. I am wondering if the parent Wrapper process is simply running out? I can't think of anything about the Wrapper itself which would be causing this directly... Leif Ralph Schreyer wrote: >Hello Leif, > >thank you very much for your answer. I turned on wrapper.debug=true and generated the output shown below, i.e. the JVM exits with code 6 (SIGABRT, afaik) > >In a test run, I started more than a hundred JVMs (each starting my Java service) on my PC without any problems. As soon as I wrap the calls into the Java Service Wrapper, the JVMs crash when starting more than ~ 30. > > >Cheers > >Ralph > > |
|
From: Ralph S. <ral...@we...> - 2005-06-07 14:14:09
|
Hello Leif, thank you again. Good point, in my test I launched 100 JVMs each from their own console, whereas in our application the service wrappers, and therefore the service JVMs are started as child processes of a single JVM. I'll write a test to mimic this behaviour. Cheers Ralph wra...@li... schrieb am 07.06.05 15:06:06: > > Ralph, were those 100 JVMs each launched from their own console or were > they all > launched as child processes of a single JVM like you are trying to do > with your real > applications? I have never tried exactly what you are trying. It > sounds like a resource > issue of some kind. A single JVM uses quite a few file handles. I am > wondering if the > parent Wrapper process is simply running out? I can't think of anything > about the > Wrapper itself which would be causing this directly... > > Leif > > Ralph Schreyer wrote: > > >Hello Leif, > > > >thank you very much for your answer. I turned on wrapper.debug=true and generated the output shown below, i.e. the JVM exits with code 6 (SIGABRT, afaik) > > > >In a test run, I started more than a hundred JVMs (each starting my Java service) on my PC without any problems. As soon as I wrap the calls into the Java Service Wrapper, the JVMs crash when starting more than ~ 30. > > > > > >Cheers > > > >Ralph > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput > a projector? How fast can you ride your desk chair down the office luge track? > If you want to score the big prize, get to know the little guy. > Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user __________________________________________________________ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201 |
|
From: Ralph S. <ral...@we...> - 2005-06-07 14:32:43
|
Hi Leif, even when the 100 JVMs are launched as child processes from a single JVM via Runtime.exec, I encounter no problems. Could it be that the pings of the JVM by the wrappers are problematic when starting more and more wrappers? Just a guess ... Cheers Ralph wra...@li... schrieb am 07.06.05 15:06:06: > > Ralph, were those 100 JVMs each launched from their own console or were > they all > launched as child processes of a single JVM like you are trying to do > with your real > applications? I have never tried exactly what you are trying. It > sounds like a resource > issue of some kind. A single JVM uses quite a few file handles. I am > wondering if the > parent Wrapper process is simply running out? I can't think of anything > about the > Wrapper itself which would be causing this directly... > > Leif > > Ralph Schreyer wrote: > > >Hello Leif, > > > >thank you very much for your answer. I turned on wrapper.debug=true and generated the output shown below, i.e. the JVM exits with code 6 (SIGABRT, afaik) > > > >In a test run, I started more than a hundred JVMs (each starting my Java service) on my PC without any problems. As soon as I wrap the calls into the Java Service Wrapper, the JVMs crash when starting more than ~ 30. > > > > > >Cheers > > > >Ralph > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput > a projector? How fast can you ride your desk chair down the office luge track? > If you want to score the big prize, get to know the little guy. > Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 |
|
From: Leif M. <le...@ta...> - 2005-06-07 14:39:29
|
Ralph, I can't rule anything out at this point, but the error is that the java.exe is not able to load the jvm.dll for some reason. The first several times it works, so it can't be a file permissions problem. That leaves a handle problem. All sockets, files, etc require handles to be opened on Windows. Not sure why that would be much different if you are using the Wrapper vs not. The Wrapper process uses far fewer handles than the java processes. ??? I'll give this some thought. Leif Ralph Schreyer wrote: >Hi Leif, > >even when the 100 JVMs are launched as child processes from a single JVM via Runtime.exec, >I encounter no problems. > >Could it be that the pings of the JVM by the wrappers are problematic when starting more and more wrappers? Just a guess ... > > >Cheers > >Ralph > > |
