[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjms-developer
Subject:    [openjms-developer] [ openjms-Bugs-1298864 ] Operation createReceiver failed / Empty packet was retu
From:       "SourceForge.net" <noreply () sourceforge ! net>
Date:       2005-10-10 13:47:15
Message-ID: E1EOxzn-0002p3-Qd () sc8-sf-web2 ! sourceforge ! net
[Download RAW message or body]

Bugs item #1298864, was opened at 2005-09-23 01:43
Message generated for change (Comment added) made by tanderson
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1298864&group_id=54559

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: client
>Group: v0.7.6.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Franck Schmidlin (schmidlinf)
>Assigned to: Tim Anderson (tanderson)
Summary: Operation createReceiver failed / Empty packet was returned

Initial Comment:
Could someone let me know what are the possible 
causes of the following exception?

My customer environment is openJMS 7.6.1.

Knowing the cause will help me decide if it worth trying 
to reconnect, or to kill my process altogether and get 
someone to check the openJMS server.

Thanks.

java.io.InterruptedIOException: Empty packet was 
returned
 at 
com.anite.connect.jms.ConnectionMonitoringThread.set
MessageListeners(ConnectionMonitoringThread.java:460)
 at 
com.anite.connect.jms.ConnectionMonitoringThread.run
(ConnectionMonitoringThread.java:78)
Caused by: javax.jms.JMSException: Operation 
createReceiver failed:
java.io.InterruptedIOException: Empty packet was 
returned
 at 
org.exolab.jms.client.mipc.IpcJmsSessionStub.checkRe
ply(IpcJmsSessionStub.java:844)
 at 
org.exolab.jms.client.mipc.IpcJmsSessionStub.createRe
ceiver(IpcJmsSessionStub.java:338)
 at org.exolab.jms.client.JmsQueueSession.addReceiver
(JmsQueueSession.java:244)
 at 
org.exolab.jms.client.JmsQueueSession.createReceiver
(JmsQueueSession.java:149)
 at 
org.exolab.jms.client.JmsQueueSession.createReceiver
(JmsQueueSession.java:114)
 at 
com.anite.connect.jms.ConnectionMonitoringThread.set
MessageListeners(ConnectionMonitoringThread.java:456)
 ... 1 more


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

>Comment By: Tim Anderson (tanderson)
Date: 2005-10-10 23:47

Message:
Logged In: YES 
user_id=557161

It typically indicates that the physical connection to the server 
has been lost.

You can verify this by registering an ExceptionListener with the 
Connection instance e.g:
  connection.setExceptionListener(new ExceptionListener() {
      public void onException(JMSException exception) {
         exception.printStackTrace();
      }
  };



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

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


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
openjms-developer mailing list
openjms-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openjms-developer
[prev in list] [next in list] [prev in thread] [next in thread]