[
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