Re: [Wrapper-user] Application Stopped Unexpected and amazingly

[jawad b. <bok...@ya...>]

Dear Leif,

Yes, I was using version 3.1.0. 
I didn't review updates on the site for newer version
because this old version was even working perfectly
for me.

Can I find some more information about this timing
bug?

However, I'll upgrade to version 3.1.2 now and see if
it happens again.

I set log-level to ERROR because I am using my own
written logging application similar to log4j and that
is configured my application internally.
If application crashes due to any reason, my logging
module informs me of that.

But through logs I noticed that application was
stopped  normally and application didn't notice any
severity inside. It just received a stop signal just
like a normal application-stop.

Thanks a lot for your quick attention and I'll apply
the latest updates now.

I would appreciate if you can give me some more
information on timing-bug problem that caused this.


Regards,

Jawad










--- Leif Mortenson <le...@ta...> wrote:
> Jawad,
>     What version are you using? The only thing that
> I am aware of that could
> have possibly caused that is a timing bug in bug in
> 3.1.0 and 3.1.1.  It was
> fixed in 3.1.2.  From the release notes:
> 
> * Fix a problem where the JVM would restart at
> certain times when using the
>   system time based timer due to an overflow error. 
> This problem was
>   introduced in 3.1.0.  Due to a separate bug in
> 3.1.0, the Wrapper would
>   shutdown rather than simply restarting the JVM as
> was happening in 3.1.1.
>   The last restart happened on Aug 21, 2004.  It
> will next occur Oct 10, 
> 2004
>   and repeat at regular intervals.  There are no
> problems when using the new
>   Tick based timer.  Bug #1014405.
> 
>     Also, what is the reason that you are setting
> your log level to ERROR?
> The way I designed the Wrapper, that is in general a
> bad idea as it 
> hides all
> of the output that you will need to recover from a
> problem.   If the problem
> is that your Java application is sending too much
> output to its console, 
> then
> I would suggest using a Java side logging system
> like log4j or LogKit to
> reduce or redirect that output.
>     Depending on your answer here, I may be able to
> come up with a change
> to the Wrapper to resolve whatever problem you had
> been having as well.
> 
> Cheers,
> Leif
> 
> jawad bokhari wrote:
> 
> >I recently noticed an amazingly strange problem in
> >using wrapper for my applicaiton.
> >
> >Application stopped working at 5 different servers
> at
> >sametime. 
> >I couldnt' see any wrapper.log having my log level
> set
> >to ERROR. I dont' see any error in my application's
> >log.
> >
> >But it suddenly happenend so. 
> >I wonder if there's some ping like application that
> >keep monitoring the service and stops the service
> >externally.
> >
> >Anything I should investigate in wrapper
> >configurations?
> >
> >
> >Regards,
> >
> >Jawad
> >  
> >
> 
> 
> 
>
-------------------------------------------------------
> SF.Net email is sponsored by: Tell us your software
> development plans!
> Take this survey and enter to win a one-year sub to
> SourceForge.net
> Plus IDC's 2005 look-ahead and a copy of this survey
> Click here to start! 
> http://www.idcswdc.com/cgi-bin/survey?id=105hix
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
>
https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com