[ openjms-Bugs-682160 ] Connection.close() behaviour not compliant
"SourceForge.net" <[email protected]>
| Newsgroups | gmane.comp.java.openjms.devel |
|---|---|
| Message-ID | <[email protected]> |
Bugs item #682160, was opened at 2003-02-07 07:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474136&aid=682160&group_id=54559 Category: client Group: v0.7.4 Status: Open Resolution: None Priority: 5 Submitted By: Tim Anderson (tanderson) Assigned to: Jim Alateras (jalateras) Summary: Connection.close() behaviour not compliant Initial Comment: From section 4.3.5 of the spec: "A close terminates all pending message receives on the connections sessions 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. ---------------------------------------------------------------------- >Comment By: Tim Anderson (tanderson) Date: 2003-02-14 13:17 Message: 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474136&aid=682160&group_id=54559