[
https://issues.redhat.com/browse/WFLY-13457?page=com.atlassian.jira.plugi...
]
Emmanuel Hugonnet moved JBEAP-19470 to WFLY-13457:
--------------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-13457 (was: JBEAP-19470)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JCA
JMS
(was: Generic JMS RA)
[GSS](7.3.z) Generic JMS RA leaks memory when using JMS 2.0 API with
TIBCO EMS
------------------------------------------------------------------------------
Key: WFLY-13457
URL:
https://issues.redhat.com/browse/WFLY-13457
Project: WildFly
Issue Type: Bug
Components: JCA, JMS
Reporter: Emmanuel Hugonnet
Assignee: Emmanuel Hugonnet
Priority: Major
There is a memory leak when using JBoss EAP Generic JMS Resource Adapter with TIBCO EMS
JMS 2.0 API. This is due to the way TIBCO decided to implement their JMS 2.0 API.
When using JMSContext JMSProducers are only closed when JMSContext is closed which never
happens in a life time of an application since that would negates any benefits of having
JCA pool.
This could be easily observed when examining memory dump. It is possible to see a large
accumulation of JMSProducer objects in memory.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)