JMS ResourceAdapter makes unnecessary temporary delete requests
---------------------------------------------------------------
Key: JBAS-1485
URL: http://jira.jboss.com/jira/browse/JBAS-1485
Project: JBoss Application Server
Type: Bug
Components: JMS service
Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final
Reporter: Adrian Brock
Priority: Optional
The JMS ResourceAdaptor keeps track of temporaries created on a connection
(org.jboss.resource.adapter.jms.JMSSessionFactoryImpl)
and deletes them.
This is because we cannot expect the real JMS implementation to do this
because the connection is pooled and not closed.
However, if the user is deleting the temporaries themselves
(good practice in terms of resource usage),
the JMS ResourceAdapter does not know about this
and tries to repeat the delete at connection.close();
Solution:
Add some wrapping processing for the temporary queues and topics
so we can trap temporary.delete(). That way we will know we don't
need to do it on close()
IMPORTANT: Invocations like send() or JMSMessage.setJMSReplyTo will
also need to trap these destinations to do the necessary wrapping/unwrapping.
It is also possible to retrieve a temporary destination with
Session.createQueue/Topic.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
