Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5275

Connection Factory parameter disappears after code deployment

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 10.0.0.CR1
    • None
    • JCA
    • None
    • Hide

      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>
      Show
      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>

    Description

      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>

      Attachments

        Activity

          People

            chaowan@redhat.com Chao Wang
            rhn-support-mmillson Michael Millson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: