[daisy] [JIRA] Commented: (DSY-659) SEVERE: Error with the JMS connection.

[RJ Singh (JIRA)]

    [ http://issues.cocoondev.org//browse/DSY-659?page=comments#action_13661 ] 

RJ Singh commented on DSY-659:
------------------------------

Karel Vervaeke: 
Thanks for all your suggestions on this issue. After several hours of back tracking through the logs and comparing log entries it seems that this problem only occured once. So at this time I would like to ask you to stop investigating this issue as we are going to close out this issue on our side as a random hichup on our system. We will monitor this the logs more closely to see if this happens again. 
Thank you
RJ

> SEVERE: Error with the JMS connection.
> --------------------------------------
>
>          Key: DSY-659
>          URL: http://issues.cocoondev.org//browse/DSY-659
>      Project: Daisy
>         Type: Bug
>   Components: JMS
>     Versions: 2.1
>  Environment: Red Hat Enterprise Linux ES release 4. This is all running on a Physical Server Dell
> MySQL 5.0- This is a separate Dell Physical Server
> Daisy CMS 2.1
>     Reporter: RJ Singh

>
> This morning we started receiving the following error message from 4 of our Daisy instances. The message recorded in the daisy-wiki-service.log is as follows: Pay close attention to the YEAR in the log. 
> INFO   | wrapper  | 2017/03/10 07:49:00 | The system clock fell behind the timer by -528886964ms.
> INFO   | jvm 1    | 2017/03/10 07:49:00 | The system clock fell behind the timer by -528886964ms.
> INFO   | jvm 1    | 2017/03/10 08:49:01 | Mar 10, 2017 8:49:01 AM org.outerj.daisy.jms.impl.JmsClientImpl$MyJmsExceptionListener onException
> INFO   | jvm 1    | 2017/03/10 08:49:01 | SEVERE: Error with the JMS connection. Will automatically try to re-establish connection every 10000 ms.
> INFO   | jvm 1    | 2017/03/10 08:49:01 | javax.jms.JMSException: java.io.EOFException
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:46)
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1513)
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1529)
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:96)
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:114)
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:96)
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:96)
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:147)
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       at org.apache.activemq.transport.InactivityMonitor.onException(InactivityMonitor.java:150)
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:97)
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:150)
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       at java.lang.Thread.run(Thread.java:595)
> INFO   | jvm 1    | 2017/03/10 08:49:01 | Caused by: java.io.EOFException
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       at java.io.DataInputStream.readInt(DataInputStream.java:358)
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267)
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:156)
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:136)
> INFO   | jvm 1    | 2017/03/10 08:49:01 |       ... 1 more
> We verified that the time is set correctly on our server. Eventually the JMS Service reconnected. Do you know what could be causing this issue, or what we can do to resolve this problem.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira