RE: [Wrapper-user] Timed out waiting for a signal from the JVM.

[Victor K. <Vic...@se...>]

Leif,

This worked for me.  I also got it working the way it was
before.  I noticed one of my classes still refered to a 
debug utility which uses swing, I removed that and it
worked!  Maybe the awt event handler clashed with that for
the wrapper.

Thanks for the help, it's certainly apperciated.

Regards,

Vic
--
Victor Kirk
Analyst
Serco Integrated Transport
Tel: +44 (0)1642 636894
Fax: +44 (0)1642 636701
--



> -----Original Message-----
> From: Leif Mortenson [mailto:le...@ta...]
> Sent: 30 September 2004 10:54
> To: wra...@li...
> Subject: Re: [Wrapper-user] Timed out waiting for a signal 
> from the JVM.
> 
> 
> Victor,
>     I see the problem now.   If you look closely t the 
> command generated 
> by the Wrapper, you
> will that your main class is showing up before the classpath or 
> anything.   I was not paying
> close enough attention to the right things.
> 
> Change:
> wrapper.java.additional.1=uk.co.mooed.calllogger.Logger
> wrapper.java.additional.2=call-logger.properties
> 
> To:
> wrapper.app.parameter.1=uk.co.mooed.calllogger.Logger
> wrapper.app.parameter.2=call-logger.properties
> 
> The way Java was being launched, your Logger class was the 
> direct main 
> class, and
> everything else was being passed to your main method as 
> arguments.   I 
> will try to think
> of a way that the Wrapper could have caught this for a future 
> version.  
> May just be
> as simple as making sure that the wrapper.java.additional.n 
> properties 
> always start
> with a "-" character.
> 
> Cheers,
> Leif
> 
> 
> Victor Kirk wrote:
> 
> >Thanks for the quick reply :-)
> >
> >  
> >
> >>    I do not see the Java side startup banner which shows that the 
> >>WrapperManager class is being correctly initialized.   In every case
> >>I have seen to date, this was caused by the user setting the main
> >>class directly to their application's main class.   
> >>    
> >>
> >My config definitaly uses WrapperSimpleApp.
> >
> >  
> >
> >>When this happens, the app will start normally, but the Java side
> >>of the Wrapper does not get initialized correctly and you get a
> >>timeout.
> >>    
> >>
> >
> >Are there any conditions that my app must obey which qould otherwise
> >prevent WrapperSimpleApp from replying to the ping? Would it be worth
> >making my app reply to the pings and use my main class as the
> >mainclass?
> >
> >  
> >
> >>could you please add the wrapper.debug=TRUE
> >>    
> >>
> >Heres my new config
> >
> >wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
> >wrapper.java.classpath.1=wrapper.jar
> >wrapper.java.classpath.2=call-logger.jar
> >wrapper.java.command=java.exe
> >wrapper.java.library.path.1=.
> >wrapper.java.additional.1=uk.co.mooed.calllogger.Logger
> >wrapper.java.additional.2=call-logger.properties
> >wrapper.ntservice.displayname=FROG Call Logger
> >wrapper.ntservice.name=FROGCallLogger
> >wrapper.ntservice.description=Logs calls
> >wrapper.ntservice.starttype=AUTO_START
> >wrapper.ntservice.interactive=false
> >wrapper.debug=TRUE
> >
> >
> >and heres the new output:
> >
> >wrapper  | --> Wrapper Started as Console
> >wrapper  | Using system timer.
> >wrapperp | server listening on port 32000.
> >wrapper  | Launching a JVM...
> >wrapper  | command: "c:\products\j2sdk\bin\java.exe"
> >uk.co.mooed.calllogger.Logger ca
> >ll-logger.properties -Djava.library.path="." -classpath
> >"wrapper.jar;call-logger.jar"
> > -Dwrapper.key="QZqr731c447p4Jlx" -Dwrapper.port=32000
> >-Dwrapper.debug="TRUE" -Dwrapp
> >er.use_system_time="TRUE" -Dwrapper.version="3.1.1"
> >-Dwrapper.native_library="wrapper
> >" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1
> >org.tanukisoftware.wrapper.WrapperSimp
> >leApp
> >wrapper  | JVM started (PID=3928)
> >jvm 1    | localhost: Logging in localhost:23 (attempt 1)
> >jvm 1    | localhost: Logged in
> >jvm 1    | localhost: Connecting to localhost:4001 (attempt 1)
> >jvm 1    | localhost: Connected
> >jvm 1    | localhost: Logging started
> >wrapper  | Startup failed: Timed out waiting for a signal 
> from the JVM.
> >wrapper  | JVM did not exit on request, terminated
> >wrapper  | JVM was only running for 29 seconds leading to a 
> failed restart
> >count of 1
> >.
> >wrapper  | Waiting 5 seconds before launching another JVM.
> >wrapper  | Launching a JVM...
> >...
> >  
> >
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on 
> ITManagersJournal
> Use IT products in your business? Tell us what you think of 
> them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to 
> find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 
  This message, including attachments, is intended only for the use by the
person(s) to whom it is addressed. It may contain information which is
privileged and confidential. Copying or use by anybody else is not
authorised. If you are not the intended recipient, please contact the sender
as soon as possible. The views expressed in this communication may not
necessarily be the views held by Serco Integrated Transport.