-
Bug
-
Resolution: Done
-
Major
-
7.3.0.GA
-
None
The problem is that the RA creates two connections instead of one for each connection to TIBCO broker.
Have repeated the problem and I can clearly see the issue: (simple example with two MDBs each with maxSession=1 - should be two connections only)
[tomr@aza java]$ netstat -pantu | grep /tibemsd64 | grep "ESTABLISHED" | grep ":7222"
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 192.168.1.106:7222 192.168.1.109:35812 ESTABLISHED 2182/tibemsd64
tcp 0 0 192.168.1.106:7222 192.168.1.109:35822 ESTABLISHED 2182/tibemsd64
tcp 0 0 192.168.1.106:7222 192.168.1.109:35820 ESTABLISHED 2182/tibemsd64
tcp 0 0 192.168.1.106:7222 192.168.1.109:35810 ESTABLISHED 2182/tibemsd64
This is due to the fact that the ManagedConnection creates a Connection and a JMSContext
- is cloned by
-
JBEAP-18191 [GSS](7.2.z) Generic RA ManagedConnection opens 2 connections to the broker
- Closed
- is incorporated by
-
JBEAP-19117 [GSS](7.3.z) Upgrade org.jboss.genericjms from 2.0.2.Final-redhat-00001 to 2.0.4.Final-redhat-00001
- Closed
-
JBEAP-19585 [GSS](7.3.z) Upgrade org.jboss.genericjms from 2.0.4 to 2.0.6
- Closed
- is related to
-
JBEAP-19465 [GSS](7.3.z) WFLY-13457 - Generic JMS RA leaks memory when using JMS 2.0 API with TIBCO EMS
- Closed
- relates to
-
JBEAP-18192 [GSS](7.3.z) Generic RA does not support JMS 1.1 in EAP 7.x
- Closed
- links to