Hi!
In short: YES :))
I think this is something to do with the SwiftMQ's router code not with the
JMS spec.
Andreas said this will be fixed in the next release.
Best regards,
Kovi
At 10:29 26.6.01 +0200, you wrote:
> > At 10:44 25.6.01 +0200, Michal Jacykiewicz wrote:
> >>After some time running AsyncQueueReceiver (in samples directory)
> >>
> >>java.lang.NullPointerException
> >> at com.swiftmq.jms.SessionImpl.cancel(SessionImpl.java:495)
> >> at com.swiftmq.jms.ConnectionImpl.cancel(ConnectionImpl.java:595)
> >> at com.swiftmq.jms.ConnectionImpl.run(ConnectionImpl.java:455)
> >> at java.lang.Thread.run(Thread.java:498)
>
>On Tuesday, June 26, 2001, Gregor Kovač wrote:
> > I got the same exception on the receiver when I shutdown the router. This
> > means that the session is closed.
> > Maybe sessions have a timeout after which they are closed ?
>
>Maybe. But shouldn't they throw JMSException instead of
>NullPointerException?
>
>
>------------------------------------------------------
>SwiftMQ developers mailing list * http://www.swiftmq.com
>To unsubscribe from this list, send an eMail to
>[EMAIL PROTECTED] and write in the body of your message:
>UNSUBSCRIBE developers <your-email-address>
>Archive: http://www.mail-archive.com/developers@mail.iit.de/
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
