[ openjms-Bugs-753216 ] Null pointer in connection.close()

Bugs item #753216, was opened at 2003-06-12 21:37
Message generated for change (Settings changed) made by tanderson
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=753216&group_id=54559

>Category: client
Group: v0.7.5
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Paul Anderson (pbanderson)
>Assigned to: Tim Anderson (tanderson)
Summary: Null pointer in connection.close()

Initial Comment:
When clientPingInterval in the RmiConfiguration element
is set to "0", SimpleSender and SimpleReceiver get null
pointer exceptions when they attempt to close the
connection.  Setting clientPingInterval to a value of
"15" made this go away.

java.lang.NullPointerException
        at
org.exolab.jms.client.rmi.RmiJmsConnectionStub.close(Unknown
Source)
        at
org.exolab.jms.client.JmsConnection.close(Unknown Source)
        at
openjms.examples.client.console.SimpleSender.main(SimpleSender.java:2
95)

and

java.lang.NullPointerException
        at
org.exolab.jms.client.rmi.RmiJmsConnectionStub.close(Unknown
Source)
        at
org.exolab.jms.client.JmsConnection.close(Unknown Source)
        at
openjms.examples.client.console.SimpleReceiver.main(SimpleReceiver.ja
va:339)


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

>Comment By: Tim Anderson (tanderson)
Date: 2003-06-25 00:09

Message:
Logged In: YES 
user_id=557161

Fixed in CVS. Will be available in the 0.7.6 release.

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

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