We've got sporadically (about one time in a week) the following exception:
2007-04-24 16:47:36,676 DEBUG
[org.springframework.context.support.ClassPathXmlApplicationContext] Publishing
event in context
[org.springframework.context.support.ClassPathXmlApplicationContext;hashCode=19142683]:
org.acegisecurity.event.authorization.AuthorizedEvent[source=invocation:
method 'getPropertyValues', arguments [bd6cb20a715e128e50af, errorCode]; target
is of class [com.gide.gdcams.serviceimpl.AlertServiceImpl]]2007-04-24
16:47:42,032 INFO [STDOUT] 2024102 [UIL2.SocketManager.ReadTask#5
client=10.4.100.238:8093] - Connection failure, use
javax.jms.Connection.setExceptionListener() 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:78)
at org.jboss.mq.Connection.asynchFailure(Connection.java:420)
at
org.jboss.mq.il.uil2.UILClientILService.asynchFailure(UILClientILService.java:174)
at
org.jboss.mq.il.uil2.SocketManager$ReadTask.handleStop(SocketManager.java:440)
at
org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:372)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at
org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBufferedInputStream.java:79)
at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source)
at
java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.refill(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.read(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.readByte(Unknown
Source)
at java.io.ObjectInputStream.readByte(Unknown Source)
at
org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:317)
... 1 more
After this exception occurs, the JMS server cannot recover. Server restart
helps to solve the problem. JMS Queues are not persistent. We have 5 Queues.
Each MessageListener allows (via Spring Message Listener POJO) max threads. We
controll the length of the queue: max 100 messages are allowed per queue. So,
it shouldn't be a performance problem.
Does anybody has experience with the problem?
Thank you for any help!
Vladimir Rabkin
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041410#4041410
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041410
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
