[
http://jira.jboss.com/jira/browse/JBAS-2492?page=all ]
Adrian Brock closed JBAS-2492.
------------------------------
Resolution: Deferred
Closing features that are (or will be) implemented in JBoss Messaging.
http://jira.jboss.com/jira/browse/JBMESSAGING
If anybody wants to provide a patch that implements these,
the issue can be reopened.
Duplicates of these issues will be closed
unless they provide an implementation/patch.
Patches should first be discussed in the
development forum:
http://www.jboss.com/index.html?module=bb&op=viewforum&f=153
if there isn't already a forum link attached to this issue.
Add an removeReceiver() to the receive(long timeout) processing
---------------------------------------------------------------
Key: JBAS-2492
URL:
http://jira.jboss.com/jira/browse/JBAS-2492
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.0.3 SP1
Reporter: Adrian Brock
Currently if the receive(long) times out, the receiver is left as waiting for a message
on the server.
This doesn't cause any semantic problems, but it can lead to an unnecessary
deliver/nack lifecyle if there is no subsequent receive() request and the receiver is not
closed.
It would be better to have the option for receive(long) to issue an removeReceiver
when it stops waiting.
However, this requires an incompatible change to the IL - there is currently no such
method in the interface.
It would also need to be implementated carefully to avoid a race condition with
connection.start/stop().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira