I originally posted this on the SpyderMQ list but got no response. Hence
I'll chew up a little JBoss dev bandwidth.
The concise description is that Sending a message with an invalid destination
results in the onException handler for the QueueReceiver being called with
a JMSException with the message "Cannot send a message to the JMS provider".
As stated below, I would have thought that the InvalidDestinationException
would have been returned.
Is this a bug?
Upon first blush it looks like SpyConnection.sendToServer() or
SpyConnection.failureHandler() should do a bit of examination.
I have an application the uses the setExceptionHandler/onException method of
detecting problems with the connections to the JMSService.
If I send a message with an invalid destination, I would expect the onException
method to receive an InvalidDestinationException.
What I do see when the sender sends a message to an invalid destination is:
First to stdout (or maybe stderr)
java.rmi.RemoteException: ; nested exception is:
javax.jms.JMSException: This destination does not exist !
javax.jms.JMSException: This destination does not exist !
<<no stack trace available>>
Then my onException is called with a JMSException that looks like:
onException javax.jms.JMSException: Cannot send a message to the JMS provider
at
com.rational.clearquest.cqweb.jtltransport.JTLConnectionManager.onException(JTLConnectionManager.java:404)
at org.jbossmq.SpyConnection.failureHandler(SpyConnection.java:323)
at org.jbossmq.SpyConnection.sendToServer(SpyConnection.java:390)
at org.jbossmq.SpySession.sendMessage(SpySession.java:383)
at org.jbossmq.SpyQueueSender.send(SpyQueueSender.java:95)
at org.jbossmq.SpyQueueSender.send(SpyQueueSender.java:59)
at
com.rational.clearquest.cqweb.jtltransport.JTLService$ResponseSender.run(JTLService.java:445)
at java.lang.Thread.run(Unknown Source)
regards,
-jb
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
