You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by walidito <wa...@sgcib.com> on 2007/05/17 16:10:08 UTC
[s2] unexpected Tomcat shutdown everyday
Hi all,
I have a a very strange and critical pb with my struts 2.0.1 application
that makes my tomcat server shutdown everyday between 5:40pm and 6:30pm
approx. I'm sure that this come from my application since the pb does not
occur when I remove it.
tomcat is a 5.5.20, my jdk is 1.5-009.
When my app is deployed and the server's up, here the "normal logs :
17:29:30,281 DEBUG ManagerBase:676 - Start expire sessions StandardManager
at 1179264570281 sessioncount 0
17:29:30,281 DEBUG ManagerBase:684 - End expire sessions StandardManager
processingTime 0 expired sessions: 0
17:30:30,319 DEBUG ManagerBase:676 - Start expire sessions StandardManager
at 1179264630319 sessioncount 0
17:30:30,319 DEBUG ManagerBase:684 - End expire sessions StandardManager
processingTime 0 expired sessions: 0
17:31:30,356 DEBUG ManagerBase:676 - Start expire sessions StandardManager
at 1179264690356 sessioncount 0
17:31:30,356 DEBUG ManagerBase:684 - End expire sessions StandardManager
processingTime 0 expired sessions: 0
17:32:30,394 DEBUG ManagerBase:676 - Start expire sessions StandardManager
at 1179264750394 sessioncount 0
But when the problem happens, here are the logs that I get :
17:49:31,092 DEBUG ManagerBase:676 - Start expire sessions StandardManager
at 1179265771092 sessioncount 0
17:49:31,092 DEBUG ManagerBase:684 - End expire sessions StandardManager
processingTime 0 expired sessions: 0
17:49:32,424 DEBUG JspServlet:279 - JspServlet.destroy()
17:49:32,424 DEBUG TableTag:1618 - [null] release() called
17:49:32,424 DEBUG TableTag:1618 - [null] release() called
17:49:32,424 DEBUG TableTag:1618 - [null] release() called
17:49:32,424 DEBUG TableTag:1618 - [null] release() called
17:49:32,424 DEBUG TableTag:1618 - [null] release() called
17:49:32,434 DEBUG [/dev]:3658 - Stopping filters
17:49:32,434 DEBUG [/dev]:3666 - Stopping filter 'struts2'
17:49:32,484 INFO [/dev]:646 - Closing Spring root WebApplicationContext
17:49:32,484 INFO XmlWebApplicationContext:500 - Closing application
context [Root WebApplicationContext]
17:49:32,484 DEBUG XmlWebApplicationContext:215 - Publishing event in
context [Root WebApplicationContext]:
org.springframework.context.event.ContextClosedEvent[source=org.springframework.web.context.support.XmlWebApplicationContext:
display name [Root WebApplicationContext]; startup date [Tue May 15 09:32:32
EDT 2007]; root of context hierarchy; config locations
[/WEB-INF/applicationContext.xml]]
17:49:32,484 INFO DefaultListableBeanFactory:555 - Destroying singletons in
factory
{org.springframework.beans.factory.support.DefaultListableBeanFactory
defining beans []; root of BeanFactory hierarchy}
17:49:32,484 DEBUG ManagerBase:655 - Stopping
17:49:32,494 DEBUG ManagerBase:477 - Unloading persisted sessions
17:49:32,494 DEBUG ManagerBase:484 - Saving persisted sessions to
SESSIONS.ser
17:49:32,494 DEBUG ManagerBase:507 - Unloading 0 sessions
17:49:32,504 DEBUG ManagerBase:551 - Expiring 0 persisted sessions
17:49:32,504 DEBUG ManagerBase:565 - Unloading complete
17:49:34,006 INFO DriverManagerConnectionProvider:147 - cleaning up
connection pool: jdbc:oracle:thin:@xxxxxx:xxxx:wwww
17:49:34,026 WARN DriverManagerConnectionProvider:155 - problem closing
pooled connection
java.sql.SQLException: Io exception: Socket closed
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
thanks a lot for your help.
--
View this message in context: http://www.nabble.com/-s2--unexpected-Tomcat-shutdown-everyday-tf3772115.html#a10664842
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: [s2] unexpected Tomcat shutdown everyday
Posted by Roger Varley <ro...@googlemail.com>.
> Unfortonutalely,
> I don't have any class that invokes System.exit() nor Spring scheduler.
> Nothing particular happens before tomcat shutdown (see logs).
> And No database is backed up or restarted during this time.
> This is really strange (and critical) and I suspect that it comes from
> Struts.
>
Tomcat listens on port 8009 (I think) for a shutdown command. Try
changing the port in your Tomcat configuration and see if the problems
goes away. I have read of weird situations where there are multiple
installations of Tomcat and one incorrectly configured installation
would take down another installation when the shutdown command was
issued because the port number wasn't unique to each installation.
HTH
Roger
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: [s2] unexpected Tomcat shutdown everyday
Posted by walidito <wa...@sgcib.com>.
Unfortonutalely,
I don't have any class that invokes System.exit() nor Spring scheduler.
Nothing particular happens before tomcat shutdown (see logs).
And No database is backed up or restarted during this time.
This is really strange (and critical) and I suspect that it comes from
Struts.
Tan Mook Kuen wrote:
>
> Hi,
> Do you have any classes which invoke System.exit()?
> or do u have any spring scheduler which will terminate tomcat?
> or any error occurred before tomcat shutdown?
>
> Best regards,
> MK Tan
>
> On 5/17/07, walidito <wa...@sgcib.com> wrote:
>>
>>
>> Hi all,
>> I have a a very strange and critical pb with my struts 2.0.1 application
>> that makes my tomcat server shutdown everyday between 5:40pm and 6:30pm
>> approx. I'm sure that this come from my application since the pb does not
>> occur when I remove it.
>> tomcat is a 5.5.20, my jdk is 1.5-009.
>> When my app is deployed and the server's up, here the "normal logs :
>> 17:29:30,281 DEBUG ManagerBase:676 - Start expire sessions
>> StandardManager
>> at 1179264570281 sessioncount 0
>> 17:29:30,281 DEBUG ManagerBase:684 - End expire sessions StandardManager
>> processingTime 0 expired sessions: 0
>> 17:30:30,319 DEBUG ManagerBase:676 - Start expire sessions
>> StandardManager
>> at 1179264630319 sessioncount 0
>> 17:30:30,319 DEBUG ManagerBase:684 - End expire sessions StandardManager
>> processingTime 0 expired sessions: 0
>> 17:31:30,356 DEBUG ManagerBase:676 - Start expire sessions
>> StandardManager
>> at 1179264690356 sessioncount 0
>> 17:31:30,356 DEBUG ManagerBase:684 - End expire sessions StandardManager
>> processingTime 0 expired sessions: 0
>> 17:32:30,394 DEBUG ManagerBase:676 - Start expire sessions
>> StandardManager
>> at 1179264750394 sessioncount 0
>>
>> But when the problem happens, here are the logs that I get :
>> 17:49:31,092 DEBUG ManagerBase:676 - Start expire sessions
>> StandardManager
>> at 1179265771092 sessioncount 0
>> 17:49:31,092 DEBUG ManagerBase:684 - End expire sessions StandardManager
>> processingTime 0 expired sessions: 0
>> 17:49:32,424 DEBUG JspServlet:279 - JspServlet.destroy()
>> 17:49:32,424 DEBUG TableTag:1618 - [null] release() called
>> 17:49:32,424 DEBUG TableTag:1618 - [null] release() called
>> 17:49:32,424 DEBUG TableTag:1618 - [null] release() called
>> 17:49:32,424 DEBUG TableTag:1618 - [null] release() called
>> 17:49:32,424 DEBUG TableTag:1618 - [null] release() called
>> 17:49:32,434 DEBUG [/dev]:3658 - Stopping filters
>> 17:49:32,434 DEBUG [/dev]:3666 - Stopping filter 'struts2'
>> 17:49:32,484 INFO [/dev]:646 - Closing Spring root WebApplicationContext
>> 17:49:32,484 INFO XmlWebApplicationContext:500 - Closing application
>> context [Root WebApplicationContext]
>> 17:49:32,484 DEBUG XmlWebApplicationContext:215 - Publishing event in
>> context [Root WebApplicationContext]:
>> org.springframework.context.event.ContextClosedEvent[source=
>> org.springframework.web.context.support.XmlWebApplicationContext:
>> display name [Root WebApplicationContext]; startup date [Tue May 15
>> 09:32:32
>> EDT 2007]; root of context hierarchy; config locations
>> [/WEB-INF/applicationContext.xml]]
>> 17:49:32,484 INFO DefaultListableBeanFactory:555 - Destroying singletons
>> in
>> factory
>> {org.springframework.beans.factory.support.DefaultListableBeanFactory
>> defining beans []; root of BeanFactory hierarchy}
>> 17:49:32,484 DEBUG ManagerBase:655 - Stopping
>> 17:49:32,494 DEBUG ManagerBase:477 - Unloading persisted sessions
>> 17:49:32,494 DEBUG ManagerBase:484 - Saving persisted sessions to
>> SESSIONS.ser
>> 17:49:32,494 DEBUG ManagerBase:507 - Unloading 0 sessions
>> 17:49:32,504 DEBUG ManagerBase:551 - Expiring 0 persisted sessions
>> 17:49:32,504 DEBUG ManagerBase:565 - Unloading complete
>> 17:49:34,006 INFO DriverManagerConnectionProvider:147 - cleaning up
>> connection pool: jdbc:oracle:thin:@xxxxxx:xxxx:wwww
>> 17:49:34,026 WARN DriverManagerConnectionProvider:155 - problem closing
>> pooled connection
>> java.sql.SQLException: Io exception: Socket closed
>> at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java
>> :134)
>> at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java
>> :179)
>>
>> thanks a lot for your help.
>> --
>> View this message in context:
>> http://www.nabble.com/-s2--unexpected-Tomcat-shutdown-everyday-tf3772115.html#a10664842
>> Sent from the Struts - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>> For additional commands, e-mail: user-help@struts.apache.org
>>
>>
>
>
--
View this message in context: http://www.nabble.com/-s2--unexpected-Tomcat-shutdown-everyday-tf3772115.html#a10744819
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: [s2] unexpected Tomcat shutdown everyday
Posted by MK Tan <mk...@gmail.com>.
Hi,
Do you have any classes which invoke System.exit()?
or do u have any spring scheduler which will terminate tomcat?
or any error occurred before tomcat shutdown?
Best regards,
MK Tan
On 5/17/07, walidito <wa...@sgcib.com> wrote:
>
>
> Hi all,
> I have a a very strange and critical pb with my struts 2.0.1 application
> that makes my tomcat server shutdown everyday between 5:40pm and 6:30pm
> approx. I'm sure that this come from my application since the pb does not
> occur when I remove it.
> tomcat is a 5.5.20, my jdk is 1.5-009.
> When my app is deployed and the server's up, here the "normal logs :
> 17:29:30,281 DEBUG ManagerBase:676 - Start expire sessions StandardManager
> at 1179264570281 sessioncount 0
> 17:29:30,281 DEBUG ManagerBase:684 - End expire sessions StandardManager
> processingTime 0 expired sessions: 0
> 17:30:30,319 DEBUG ManagerBase:676 - Start expire sessions StandardManager
> at 1179264630319 sessioncount 0
> 17:30:30,319 DEBUG ManagerBase:684 - End expire sessions StandardManager
> processingTime 0 expired sessions: 0
> 17:31:30,356 DEBUG ManagerBase:676 - Start expire sessions StandardManager
> at 1179264690356 sessioncount 0
> 17:31:30,356 DEBUG ManagerBase:684 - End expire sessions StandardManager
> processingTime 0 expired sessions: 0
> 17:32:30,394 DEBUG ManagerBase:676 - Start expire sessions StandardManager
> at 1179264750394 sessioncount 0
>
> But when the problem happens, here are the logs that I get :
> 17:49:31,092 DEBUG ManagerBase:676 - Start expire sessions StandardManager
> at 1179265771092 sessioncount 0
> 17:49:31,092 DEBUG ManagerBase:684 - End expire sessions StandardManager
> processingTime 0 expired sessions: 0
> 17:49:32,424 DEBUG JspServlet:279 - JspServlet.destroy()
> 17:49:32,424 DEBUG TableTag:1618 - [null] release() called
> 17:49:32,424 DEBUG TableTag:1618 - [null] release() called
> 17:49:32,424 DEBUG TableTag:1618 - [null] release() called
> 17:49:32,424 DEBUG TableTag:1618 - [null] release() called
> 17:49:32,424 DEBUG TableTag:1618 - [null] release() called
> 17:49:32,434 DEBUG [/dev]:3658 - Stopping filters
> 17:49:32,434 DEBUG [/dev]:3666 - Stopping filter 'struts2'
> 17:49:32,484 INFO [/dev]:646 - Closing Spring root WebApplicationContext
> 17:49:32,484 INFO XmlWebApplicationContext:500 - Closing application
> context [Root WebApplicationContext]
> 17:49:32,484 DEBUG XmlWebApplicationContext:215 - Publishing event in
> context [Root WebApplicationContext]:
> org.springframework.context.event.ContextClosedEvent[source=
> org.springframework.web.context.support.XmlWebApplicationContext:
> display name [Root WebApplicationContext]; startup date [Tue May 15
> 09:32:32
> EDT 2007]; root of context hierarchy; config locations
> [/WEB-INF/applicationContext.xml]]
> 17:49:32,484 INFO DefaultListableBeanFactory:555 - Destroying singletons
> in
> factory
> {org.springframework.beans.factory.support.DefaultListableBeanFactory
> defining beans []; root of BeanFactory hierarchy}
> 17:49:32,484 DEBUG ManagerBase:655 - Stopping
> 17:49:32,494 DEBUG ManagerBase:477 - Unloading persisted sessions
> 17:49:32,494 DEBUG ManagerBase:484 - Saving persisted sessions to
> SESSIONS.ser
> 17:49:32,494 DEBUG ManagerBase:507 - Unloading 0 sessions
> 17:49:32,504 DEBUG ManagerBase:551 - Expiring 0 persisted sessions
> 17:49:32,504 DEBUG ManagerBase:565 - Unloading complete
> 17:49:34,006 INFO DriverManagerConnectionProvider:147 - cleaning up
> connection pool: jdbc:oracle:thin:@xxxxxx:xxxx:wwww
> 17:49:34,026 WARN DriverManagerConnectionProvider:155 - problem closing
> pooled connection
> java.sql.SQLException: Io exception: Socket closed
> at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java
> :134)
> at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java
> :179)
>
> thanks a lot for your help.
> --
> View this message in context:
> http://www.nabble.com/-s2--unexpected-Tomcat-shutdown-everyday-tf3772115.html#a10664842
> Sent from the Struts - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>