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

RJ Singh (JIRA) issues at cocoondev.org
Tue Jun 17 17:45:27 CEST 2008 

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

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

Karel: Thanks for taking a look at this issue for me. I don't know how the system time would have been changed especially, because according to our syslogs no one is logging into the server during that time. This server is running the ntp client. It seems that the time got changed at 7:49pm EST on March 10 2017 and then started working again at 9:13pm EST on April 6, 2008. This really does not make any sense. I placed a copy of the entire section of the logs where this change in time occured for you to take a look at.

We have 4 daisy instances running on one machine(dev, tst, stg, and prd). They all run with their own ip address and different port numbers. Each instance also have their own databases, repository server, and their own wiki repository as well.

Let me know if there is anything else that you need to know.

Logs for the change of date & Time are below.
====================================
INFO   | jvm 1    | 2008/02/19 19:29:06 | INFO: JMS connection established.
INFO   | jvm 1    | 2008/02/19 19:29:17 | 2008-02-19 19:29:17.102::INFO:  Started SelectChannelConnector @ daisy-prd-01.ny.dds.net:7001
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
INFO   | jvm 1    | 2017/03/10 08:49:01 | Mar 10, 2017 8:49:01 AM org.outerj.daisy.jms.impl.JmsClientImpl initializeJmsConnection
INFO   | jvm 1    | 2017/03/10 08:49:01 | INFO: JMS connection established.
INFO   | jvm 1    | 2017/03/10 08:49:01 | Mar 10, 2017 8:49:01 AM org.outerj.daisy.jms.impl.JmsClientImpl$ConnectionEstablisherThread end
INFO   | jvm 1    | 2017/03/10 08:49:01 | INFO: JMS connection re-establish thread ended.
INFO   | wrapper  | 2014/03/10 09:28:00 | The system clock fell behind the timer by 205053088ms.
INFO   | wrapper  | 2008/03/10 09:32:00 | The system clock fell behind the timer by 323846176ms.
STATUS | wrapper  | 2008/04/06 00:50:15 | TERM trapped.  Shutting down.
INFO   | jvm 1    | 2008/04/06 00:50:16 | 2008-04-06 01:50:16.565::INFO:  Shutdown hook executing
INFO   | jvm 1    | 2008/04/06 00:50:17 | 2008-04-06 01:50:17.393::INFO:  Shutdown hook complete
STATUS | wrapper  | 2008/04/06 00:50:18 | <-- Wrapper Stopped
STATUS | wrapper  | 2008/04/06 21:13:39 | --> Wrapper Started as Daemon
STATUS | wrapper  | 2008/04/06 21:13:40 | Launching a JVM...
INFO   | jvm 1    | 2008/04/06 21:13:40 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2008/04/06 21:13:40 |   Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.
INFO   | jvm 1    | 2008/04/06 21:13:40 |
INFO   | jvm 1    | 2008/04/06 21:13:41 | 2008-04-06 21:13:41.328::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog
INFO   | jvm 1    | 2008/04/06 21:13:41 | 2008-04-06 21:13:41.671::INFO:  Statistics on = false for SelectChannelConnector @ daisy-prd-01.ny.dds.net:7001
INFO   | jvm 1    | 2008/04/06 21:13:41 | 2008-04-06 21:13:41.866::INFO:  jetty-6.1.3
INFO   | jvm 1    | 2008/04/06 21:13:48 | Apr 6, 2008 9:13:48 PM org.outerj.daisy.jms.impl.JmsClientImpl initializeJmsConnection
INFO   | jvm 1    | 2008/04/06 21:13:48 | INFO: JMS connection established.
INFO   | jvm 1    | 2008/04/06 21:13:56 | 2008-04-06 21:13:56.230::INFO:  Started SelectChannelConnector @ daisy-prd-01.ny.dds.net:7001




> 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

More information about the daisy mailing list