[ openjms-Bugs-831535 ] Cannot connect to DB after idle several hours

Bugs item #831535, was opened at 2003-10-28 15:19
Message generated for change (Comment added) made by tanderson
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=831535&group_id=54559

Category: persistence
Group: v0.7.6-rc2
Status: Open
Resolution: None
Priority: 5
Submitted By: Tim Anderson (tanderson)
Assigned to: Tim Anderson (tanderson)
Summary: Cannot connect to DB after idle several hours

Initial Comment:
From https://sourceforge.net/forum/message.php?
msg_id=2258507

By: dantetang

Hi,

I got a problem... after idle for several hours, when I use 
the sample program
to send presistent message, PersistenceException 
thrown. The root cause of it
is a SQLException, Communication link failure.

The problem remains until I restart OpenJMS server.

Does anyone knows how to tackle this? Is it possible to 
restart OpenJMS
programmatically?

Many Many Thanks in advance.

Best Regards,
Dante


Here are the exceptions for your reference:


javax.jms.JMSException: Failed to make message 
persistent:
org.exolab.jms.persistence.PersistenceException:
        Failed to add message=ID:193095ea-b867-1004-
88f4-6a8c0867c808,
destination=MM1InQueue (1)
        at 
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFr
omServer(Stream
RemoteCall.java:245)
        at sun.rmi.transport.StreamRemoteCall.executeCall
(StreamRemoteCall.java:
220)
        at sun.rmi.server.UnicastRef.invoke
(UnicastRef.java:122)
        at 
org.exolab.jms.server.rmi.RmiJmsServerSession_Stub.send
Message(Unknown
Source)
        at 
org.exolab.jms.client.rmi.RmiJmsSessionStub.sendMessage
(RmiJmsSession
Stub.java:174)
        at org.exolab.jms.client.JmsSession.sendMessage
(JmsSession.java:676)
        at 
org.exolab.jms.client.JmsMessageProducer.sendMessage
(JmsMessageProduc
er.java:238)
        at org.exolab.jms.client.JmsQueueSender.send
(JmsQueueSender.java:156)
        at org.exolab.jms.client.JmsQueueSender.send
(JmsQueueSender.java:113)
        at 
openjms.examples.client.console.SimpleSender.main
(SimpleSender.java:1
41)

org.exolab.jms.persistence.PersistenceException:
java.sql.SQLException: Communication link failure: 
java.io.IOException
        at org.gjt.mm.mysql.MysqlIO.clearAllReceive
(Unknown Source)
        at org.gjt.mm.mysql.MysqlIO.sqlQueryDirect
(Unknown Source)
        at org.gjt.mm.mysql.Connection.execSQL(Unknown 
Source)
        at 
org.gjt.mm.mysql.PreparedStatement.executeUpdate
(Unknown Source)
        at 
org.gjt.mm.mysql.PreparedStatement.executeUpdate
(Unknown Source)
        at 
org.apache.commons.dbcp.DelegatingPreparedStatement.
executeUpdate(Del
egatingPreparedStatement.java:207)
        at 
org.apache.commons.dbcp.DelegatingPreparedStatement.
executeUpdate(Del
egatingPreparedStatement.java:207)
        at org.exolab.jms.persistence.Messages.add
(Messages.java:190)
        at 
org.exolab.jms.persistence.RDBMSAdapter.addMessage
(RDBMSAdapter.java:
365)
        at 
org.exolab.jms.messagemgr.MessageMgr.addPersistentMe
ssage(MessageMgr.
java:369)
        at org.exolab.jms.messagemgr.MessageMgr.add
(MessageMgr.java:281)
        at 
org.exolab.jms.server.JmsServerSession.sendMessage
(JmsServerSession.j
ava:350)
        at 
org.exolab.jms.server.rmi.RmiJmsServerSession.sendMess
age(RmiJmsServe
rSession.java:174)
        at java.lang.reflect.Method.invoke(Native Method)
        at sun.rmi.server.UnicastServerRef.dispatch
(UnicastServerRef.java:241)
        at sun.rmi.transport.Transport$1.run
(Transport.java:152)
        at java.security.AccessController.doPrivileged
(Native Method)
        at sun.rmi.transport.Transport.serviceCall
(Transport.java:148)
        at 
sun.rmi.transport.tcp.TCPTransport.handleMessages
(TCPTransport.java:4
65)
        at 
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.ru
n(TCPTransport
.java:706)
        at java.lang.Thread.run(Thread.java:484)



----------------------------------------------------------------------

>Comment By: Tim Anderson (tanderson)
Date: 2003-10-28 15:22

Message:
Logged In: YES 
user_id=557161

MySQL appears to be reclaiming the connection because it 
has been inactive for too long. 
Support needs to be added to configure the connection pool 
to periodically check if connections are valid.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=831535&group_id=54559


-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/