Download Word - dcm4che

[ARR-34] Stop accepting messages after org.jboss.mq.SpyJMSException:
Exiting on IOE; - nested throwable: (java.net.SocketTimeoutException: Read
timed out) Created: 24/Jan/07 Updated: 24/Jan/07 Resolved: 24/Jan/07
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Resolved
dcm4chee-arr
Receiver
dcm4chee-arr-3.0.0
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Bug
David Smith (Inactive)
Fixed
None
Not Specified
dcm4chee-arr-3.0.0
Priority:
Assignee:
Votes:
Critical
Gunter Zeilinger
0
Not Specified
Not Specified
Description
2007-01-16 15:39:08,669 WARN -> (UIL2.SocketManager.ReadTask#1 client=10.242.0.120:8093)
[org.jboss.mq.Connection] Connection failure, use javax.jms.Connection.setExceptionListene
to handle this error and reconnect
org.jboss.mq.SpyJMSException: Exiting on IOE; - nested throwable:
(java.net.SocketTimeoutException: Read timed out)
at org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:72)
at org.jboss.mq.Connection.asynchFailure(Connection.java:421)
at org.jboss.mq.il.uil2.UILClientILService.asynchFailure(UILClientILService.java:1
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleStop(SocketManager.java:439)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:371)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
at
org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBufferedInputStream.java:
at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2196)
at
java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2376
at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:24
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2515
at
java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2664)
at java.io.ObjectInputStream.readByte(ObjectInputStream.java:875)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:316)
... 1 more
2007-01-16 15:39:08,825 ERROR -> (Thread-5) [org.dcm4chee.arr.jmx.UDPServerMBean] Failed t
schedule processing of AuditMessage[433]:<46>Jan 16 03:37:20 DREAM [1980] <?xml version="1
encoding="utf-8"?>
<IHEYr4 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLS..tamp>
</IHEYr4> received from /10.242.3.240
org.jboss.mq.SpyJMSException: Cannot send a message to the JMS server; - nested throwable:
(java.io.IOException: Client is not connected)
at org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:72)
at org.jboss.mq.SpyJMSException.rethrowAsJMSException(SpyJMSException.java:57)
at org.jboss.mq.Connection.sendToServer(Connection.java:922)
at org.jboss.mq.SpySession.sendMessage(SpySession.java:924)
at org.jboss.mq.SpyMessageProducer.send(SpyMessageProducer.java:272)
at org.jboss.mq.SpyMessageProducer.send(SpyMessageProducer.java:206)
at org.dcm4chee.arr.jmx.UDPServerMBean.sendMessage(UDPServerMBean.java:285)
at org.dcm4chee.arr.jmx.UDPServerMBean.onMessage(UDPServerMBean.java:265)
at org.dcm4chee.arr.jmx.UDPServerMBean.access$400(UDPServerMBean.java:74)
at org.dcm4chee.arr.jmx.UDPServerMBean$1.run(UDPServerMBean.java:212)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.IOException: Client is not connected
at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:264)
at org.jboss.mq.il.uil2.SocketManager.sendMessage(SocketManager.java:220)
at org.jboss.mq.il.uil2.UILServerIL.addMessage(UILServerIL.java:245)
at org.jboss.mq.Connection.sendToServer(Connection.java:918)
... 8 more
Comments
Comment by Gunter Zeilinger [ 24/Jan/07 ]
(Probable) caused by read time-out of Unified version 2 Invocation Layer JMS connection,
which usage was not intended
-> use "java:ConnectionFactory" instead "ConnectionFactory" for JNDI lookup for the JMS
Connection Factory, to use the Java Virtual Machine (JVM) Invocation Layer instead UIL2,
which never time outs.
Generated at Sat May 06 07:13:48 CEST 2017 using JIRA 6.3.6#6336sha1:cf1622c62a612607f341bda9491a04918e09ebfd.