Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-6606

Specifying mdb-client-id in jboss.xml causes mdb deployments to fail

XMLWordPrintable

    • Low

      Deploying MDBs with jboss.xml descriptor specifying the mdb-client-id causes the deployment to fail with an IntrospectionException. The problem is that line 87 in
      server/src/main/org/jboss/ejb/plugins/inflow/JBossJMSMessageEndpointFactory.java specifies the clientId property as clientID. Changing it to clientId fixes it.

      Caused by: java.beans.IntrospectionException: No property found for: clientID on JavaBean: org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@d8c235(ra=null destination=null destinationType=null tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
      at org.jboss.util.propertyeditor.PropertyEditors.mapJavaBeanProperties(PropertyEditors.java:354)
      at org.jboss.util.propertyeditor.PropertyEditors.mapJavaBeanProperties(PropertyEditors.java:285)
      at org.jboss.resource.deployment.ActivationSpecFactory.createActivationSpec(ActivationSpecFactory.java:129)
      ... 137 more

        1. destinations-service.xml
          1 kB
        2. JBAS-6606.patch
          0.8 kB
        3. jbas-6606-test.jar
          2 kB
        4. JBAS-6606-Test-src.zip
          3 kB

              olubyans@redhat.com Alexey Loubyansky
              brent.atkinson Brent Atkinson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: