Thank you. I am using method #3. I was pointed out by my leader, that
there is no evidence of pinging during listener.start(). There is a
critical issue, which listener.start() is waiting about 5 minutes to finish.
This is due to listener.start() awaiting for a particular host to connect
and initialize. We just don't want to send "STARTED" packet before all of
the initialization have finished. I set the ping and ping interval to
default and wrapper.startup.timeout=0, so far working good for us.
Thanks
Taikei Matsushita
> Taikei,
> What integration method are you using? Both the WrapperSimpleApp and
> WrapperStartStopApp helper classes launch the user program in the
background
> so the Wrapper will be notified that the application is started even if
> the user's
> main method has not completed.
>
> It sounds like you are using method #3, implementing your own
> WrapperListener?
> In this case, the pings do not start until after the
> WrapperListener.start method has
> completed.
>
> If your start method is going to take longer than 30 seconds to complete
> then you
> will need to set the wrapper.startup.timeout to a larger value.
>
> There was a bug fixed in 3.1.0 in which the very first ping timeout was
> hardcoded
> at 30 seconds. It is possible that you are encountering problems
> related to this
> as it was still a bug in 3.0.5. (If you upgrade, I suggest 3.1.1 over
> 3.1.0. There
> were a couple significant bugs fixed in 3.1.1.)
>
> If you could post your debug output either on list or to me directly, I
> would be able
> to better explain what is happening with your application and how best
> to resolve it.
> Delete your existing wrapper.log file. Set wrapper.debug=true. Then
> run your
> application a single time all the way to shutdown. I should then be
> able to tell you
> exactly what is happening. Send your wrapper.conf as well so I can see
your
> timeout values. If it is larger than 40Kb or contains sensitive
> information, then
> sent it to me off list.
>
> Cheers,
> Leif
>
>
> v103 wrote:
>
> >On JSW 3.0.5, Does ping between wrapper and Java Side WrapperManager
start
> >after listener.start() completion.
> >In another words, is ping thrown to Java side while listener.start() is
in
> >process.
> >
> >I am having difficulty with this, the startup(listenter.start()) takes
more
> >than 5 minutes to complete, and before this completion.
> >
> >I set
> >wrapper.startup.timeout=0
> >wrapper.ping.interval=3600
> >wrapper.ping.timeout=7200
> >
> >I know this is an extreme amount of settings, however I don't want any
> >timeout and JVM shutdowns during listener.start().
> >
> >The wrapper.log at the end tells "JVM appears hung: TImed out waiting for
> >signal from JVM."
> >"JVM did not exit on request, terminated".
> >
> >Taikei Matsushita
> >
> >
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
|
