Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-24688

[GSS](7.4.z) JBoss EAP does not log exceptions thrown during a failed deployment of a resource adapter module

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.4.12.CR1, 7.4.12.GA
    • 7.4.11.GA
    • JCA
    • None
    • False
    • None
    • False
    • ?
    • Hide

      To reproduce the issue try deploy CICS RA with the ra.xml attached to the JIRA.
      The try to start EAP with CICS RA configured in hte following way:

      <subsystem xmlns="urn:jboss:domain:resource-adapters:6.0">
           <resource-adapters> 
             <resource-adapter id="com.ibm.cicseci.rar">
                    <module slot="main" id="com.ibm.cicseci"/>
                                            
                    <transaction-support>NoTransaction</transaction-support>
                    <connection-definitions>
                        <connection-definition class-name="com.ibm.connector2.cics.ECIManagedConnectionFactory" jndi-name="java:/jboss/MyCICS" use-java-context="true" pool-name="MFECIConnectionFactory">
                            <pool>
                                <min-pool-size>2</min-pool-size>
                                <max-pool-size>10</max-pool-size>
                            </pool>
                            <security>
                                <application/>
                            </security>
                        </connection-definition>
                    </connection-definitions>
            </resource-adapter>        
         </resource-adapters>
      Show
      To reproduce the issue try deploy CICS RA with the ra.xml attached to the JIRA. The try to start EAP with CICS RA configured in hte following way: <subsystem xmlns="urn:jboss:domain:resource-adapters:6.0"> <resource-adapters> <resource-adapter id="com.ibm.cicseci.rar"> <module slot="main" id="com.ibm.cicseci"/> <transaction-support>NoTransaction</transaction-support> <connection-definitions> <connection-definition class-name="com.ibm.connector2.cics.ECIManagedConnectionFactory" jndi-name="java:/jboss/MyCICS" use-java-context="true" pool-name="MFECIConnectionFactory"> <pool> <min-pool-size>2</min-pool-size> <max-pool-size>10</max-pool-size> </pool> <security> <application/> </security> </connection-definition> </connection-definitions> </resource-adapter> </resource-adapters>

    Description

      A deployment of IBM CICS resource adapter as a module fails with exception

      14:35:51,185 ERROR [stderr] (ServerService Thread Pool -- 70) org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.jca.common.api.validator.ValidateException: IJ010075: The resource adapter metadata must contain either an outbound or inbound configuration
14:35:51,187 ERROR [stderr] (ServerService Thread Pool -- 70) 	at org.jboss.as.connector@7.4.9.GA-redhat-SNAPSHOT//org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor.process(ParsedRaDeploymentProcessor.java:235)
14:35:51,187 ERROR [stderr] (ServerService Thread Pool -- 70) 	at org.jboss.as.connector@7.4.9.GA-redhat-SNAPSHOT//org.jboss.as.connector.subsystems.resourceadapters.RaOperationUtil.installRaServicesAndDeployFromModule(RaOperationUtil.java:528)
14:35:51,188 ERROR [stderr] (ServerService Thread Pool -- 70) 	at org.jboss.as.connector@7.4.9.GA-redhat-SNAPSHOT//org.jboss.as.connector.subsystems.resourceadapters.RaAdd.performRuntime(RaAdd.java:126)

      but that exception is never logged even at TRACE level. This makes it very difficult to debug the issue. The deployment of the CICS RAR file does work without any issues. Only deployment of a module fails.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-17814 JBoss EAP does not log exceptions thrown during a failed deployment of a resource adapter module

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-engineering-lgao Lin Gao
              rhn-support-toross Tom Ross
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: