Hi All,
I am testing version 2.6
it looks like the JMS methods are not properly shielded
agains runtime exception. I am currently running the
latest version and under special scenarios of
deconneciton/reconnection of a message publisher to
JMS service, I can occasionally recieve the following
error, normally I should only recieve a JMSEXception.
I have found a workaround by trapping all exception
around the send method of a publisher and re-throwing
JMS exception.
Stack trace follow.
java.lang.NullPointerException
at
com.ubermq.jms.client.proc.ClientProc.toString
(ClientProc.java:391)
at java.lang.String.valueOf(String.java:2131)
at java.lang.StringBuffer.append
(StringBuffer.java:370)
at
com.ubermq.jms.client.impl.AbstractProducer.send
(AbstractProducer.java:331)
at
com.ubermq.jms.client.impl.AbstractProducer.send
(AbstractProducer.java:248)
at
com.ubermq.jms.client.impl.AbstractProducer.send
(AbstractProducer.java:192)
at
com.ubermq.jms.client.impl.AbstractProducer.send
(AbstractProducer.java:214)
...