[jboss-jira] [JBoss JIRA] (WFLY-12227) IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml

[Ondrej Kotek (Jira)]

Ondrej Kotek created WFLY-12227:
-----------------------------------

             Summary: IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml
                 Key: WFLY-12227
                 URL: https://issues.jboss.org/browse/WFLY-12227
             Project: WildFly
          Issue Type: Bug
          Components: JCA
    Affects Versions: 18.0.0.Beta1
            Reporter: Ondrej Kotek
            Assignee: Stefano Maestri


There is a warning during start with standalone-full*.xml:

{noformat}
12:19:04,432 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA
12:19:04,440 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
12:19:04,441 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 83) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
12:19:04,441 WARN  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020017: Invalid archive: file://RaActivatoractivemq-ra
12:19:04,486 INFO  [org.apache.activemq.artemis.ra] (MSC service thread 1-3) AMQ151007: Resource adaptor started
12:19:04,486 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra
12:19:04,492 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
12:19:04,493 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
{noformat}

For an automation checking the server log for issues, this WARN causes false positive. Hence, I set the Priority to Critical.




--
This message was sent by Atlassian Jira
(v7.12.1#712002)