Connection Factory parameter disappears after code deployment on JBoss EAP

Solution Unverified - Updated -

Issue

  • The min-pool-size setting in the following Connection Factory disappears from domain.xml after any code deployments or changes made in the console to the queue 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>

Environment

  • Red Hat JBoss Enterprise Application Platform 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.