[
https://issues.jboss.org/browse/WFLY-5275?page=com.atlassian.jira.plugin....
]
Brad Maxwell updated WFLY-5275:
-------------------------------
Workaround Description:
Configure min-pool-size as a child element of xa-pool to a value other than the default 0.
For example:
{code}
<connection-definitions>
<connection-definition
class-name="org.apache.activemq.ra.ActiveMQManagedConnectionFactory"
jndi-name="java:/ConnectionFactory"
enabled="true"
pool-name="ConnectionFactory">
<xa-pool>
<min-pool-size>1</min-pool-size>
...
</xa-pool>
...
</connection-definition>
</connection-definitions>
{code}
was:
Configure min-pool-size as a child element of xa-pool to a value other than the default 0.
For example:
<connection-definitions>
<connection-definition
class-name="org.apache.activemq.ra.ActiveMQManagedConnectionFactory"
jndi-name="java:/ConnectionFactory"
enabled="true"
pool-name="ConnectionFactory">
<xa-pool>
<min-pool-size>1</min-pool-size>
...
</xa-pool>
...
</connection-definition>
</connection-definitions>
Connection Factory parameter disappears after code deployment
-------------------------------------------------------------
Key: WFLY-5275
URL:
https://issues.jboss.org/browse/WFLY-5275
Project: WildFly
Issue Type: Bug
Reporter: Mike Millson
Assignee: Jason Greene
The min-pool-size setting in the following connection Factory disappears from domain.xml
after any code deployments or change made in the console to the queues for the connection
factory:
<connection-definition
class-name="org.apache.activemq.ra.ActiveMQManagedConnectionFactory"
jndi-name="java:jboss/activemq/XAConnectionFactory" enabled="true"
use-java-context="true" pool-name="ConnectionFactory"
min-pool-size="0"></connection>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)