Menu

#34 Connection.close() behaviour not compliant

v0.7.4
closed-fixed
client (26)
5
2003-06-29
2003-02-07
No

From section 4.3.5 of the spec:
"A close terminates all pending message receives
on the connection’s session’s consumers. The
receives may return with a message or null
depending on whether or not there was a message
available at the time of the close."

At the moment, Connection.close() blocks until the
receive() completes. If the receive() uses unlimited
timeout, and doesn't receive any message,
Connection.close() blocks indefinitely.

Discussion

  • Tim Anderson

    Tim Anderson - 2003-02-14

    Logged In: YES
    user_id=557161

    Also, the SimpleConsumer example closes the session
    and connection within MessageListener.onMessage() -
    this should not be possible as this violates section
    4.3.5 of the specification.

     
  • Tim Anderson

    Tim Anderson - 2003-06-29

    Logged In: YES
    user_id=557161

    Fixed in CVS. The fix will be available in the 0.7.6 release.

     
  • Tim Anderson

    Tim Anderson - 2003-06-29
    • assigned_to: jalateras --> tanderson
    • status: open --> closed-fixed
     

Log in to post a comment.

MongoDB Logo MongoDB