2:58 p.m.
Justin Bertram created AS7-6055:
-----------------------------------
Summary: Support multiple <entry> elements for
<pooled-connection-factory>
Key: AS7-6055
URL: https://issues.jboss.org/browse/AS7-6055
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.1.Final
Reporter: Justin Bertram
Assignee: Jeff Mesnil
Currently a <pooled-connection-factory> can only be bound to a single JNDI location
because it only supports one <entry> despite the fact that the schema allows
multiple <entry> elements.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:04 p.m.
[
https://issues.jboss.org/browse/AS7-6055?page=com.atlassian.jira.plugin.s...
]
Justin Bertram updated AS7-6055:
--------------------------------
Steps to Reproduce:
1) Change the default standalone-full.xml to use this:
{noformat}
<pooled-connection-factory name="hornetq-ra">
<transaction mode="xa"/>
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
<entry name="java:/MyJmsXA"/>
</entries>
</pooled-connection-factory>
{noformat}
2) Start the server.
3) Observe in the log that the connection factory is only bound to "java:/JmsXA"
and not "java:/MyJmsXA":
{noformat}INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010401:
Bound JCA ConnectionFactory [java:/JmsXA]{noformat}
was:
1) Change the default standalone-full.xml to use this:
<pooled-connection-factory name="hornetq-ra">
<transaction mode="xa"/>
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
<entry name="java:/MyJmsXA"/>
</entries>
</pooled-connection-factory>
2) Start the server.
3) Observe in the log that the connection factory is only bound to "java:/JmsXA"
and not "java:/MyJmsXA":
INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010401: Bound JCA
ConnectionFactory [java:/JmsXA]
Support multiple <entry> elements for
<pooled-connection-factory>
-----------------------------------------------------------------
Key: AS7-6055
URL: https://issues.jboss.org/browse/AS7-6055
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.1.Final
Reporter: Justin Bertram
Assignee: Jeff Mesnil
Currently a <pooled-connection-factory> can only be bound to a single JNDI location
because it only supports one <entry> despite the fact that the schema allows
multiple <entry> elements.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:33 a.m.
[
https://issues.jboss.org/browse/AS7-6055?page=com.atlassian.jira.plugin.s...
]
Jeff Mesnil commented on AS7-6055:
----------------------------------
Please note that the workaround add significant overhead. Instead of having the CF
available under another JNDI name, it creates a wholly different CF with its own pool,
threads, etc. consuming more memory resources
Support multiple <entry> elements for
<pooled-connection-factory>
-----------------------------------------------------------------
Key: AS7-6055
URL: https://issues.jboss.org/browse/AS7-6055
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.1.Final
Reporter: Justin Bertram
Assignee: Jeff Mesnil
Currently a <pooled-connection-factory> can only be bound to a single JNDI location
because it only supports one <entry> despite the fact that the schema allows
multiple <entry> elements.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:35 a.m.
[
https://issues.jboss.org/browse/AS7-6055?page=com.atlassian.jira.plugin.s...
]
Jeff Mesnil updated AS7-6055:
-----------------------------
Fix Version/s: 7.2.0.Alpha1
7.1.4.Final (EAP)
Support multiple <entry> elements for
<pooled-connection-factory>
-----------------------------------------------------------------
Key: AS7-6055
URL: https://issues.jboss.org/browse/AS7-6055
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.1.Final
Reporter: Justin Bertram
Assignee: Jeff Mesnil
Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
Currently a <pooled-connection-factory> can only be bound to a single JNDI location
because it only supports one <entry> despite the fact that the schema allows
multiple <entry> elements.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4401
days inactive
4406
days old
3 comments
2 participants
participants (2)
-
Jeff Mesnil (JIRA) -
Justin Bertram (JIRA)