]
Jesper Pedersen resolved JBAS-6276.
-----------------------------------
Fix Version/s: JBossAS-5.1.0.Beta1
JBossAS-4.2.4.GA
JBossAS-5.0.2.GA
JBossAS-6.0.0.Alpha1
(was: JBossAS-5.1.0.CR1)
Resolution: Done
JmsConnectionRequestInfo needs have defaults set before doing
allocateConnection()
----------------------------------------------------------------------------------
Key: JBAS-6276
URL:
https://jira.jboss.org/jira/browse/JBAS-6276
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR2
Reporter: Adrian Brock
Assignee: Jesper Pedersen
Fix For: JBossAS-5.1.0.Beta1, JBossAS-4.2.4.GA, JBossAS-5.0.2.GA,
JBossAS-6.0.0.Alpha1
The default values for the JmsConnectionRequestInfo are being setup too late
for the subpooling to work properly.
The call to JmsConnectionRequestInfo.setDefaults(...)
needs to be moved to JmsSessionFactoryImpl::allocateConnection()
something like:
JmsConnectionRequestInfo info = new JmsConnectionRequestInfo(transacted,
acknowledgeMode, sessionType);
info.setUserName(userName);
info.setPassword(password);
info.setClientID(clientID);
+ info.setDefaults(mcf.mcfProperties);
This shows up if you try to configure the clientID property on the jms resource adapter,
e.g.
<config-property name="ClientID"
type="java.lang.String">xxx</config-property>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: