[jboss-jira] [JBoss JIRA] (AS7-6450) Missing <recovery> element. XA recovery disabled for: java:/JmsXA
RH Bugzilla Integration (JIRA)
jira-events at lists.jboss.org
Wed Mar 6 11:45:56 EST 2013
[ https://issues.jboss.org/browse/AS7-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759100#comment-12759100 ]
RH Bugzilla Integration commented on AS7-6450:
----------------------------------------------
Brian Stansberry <brian.stansberry at redhat.com> changed the Status of [bug 907901|https://bugzilla.redhat.com/show_bug.cgi?id=907901] from NEW to ON_QA
> Missing <recovery> element. XA recovery disabled for: java:/JmsXA
> -----------------------------------------------------------------
>
> Key: AS7-6450
> URL: https://issues.jboss.org/browse/AS7-6450
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 7.2.0.Alpha1
>
>
> With latest version of HornetQ and IronJacamar, when AS7 is started with the standalone-full.xml, it logs a WARN message:
> {noformat}
> 11:23:11,152 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221001: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messagingjournal,bindingsDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messagingbindings,largeMessagesDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messaginglargemessages,pagingDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messagingpaging)
> 11:23:11,154 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221008: Waiting to obtain live lock
> 11:23:11,175 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221017: Using NIO Journal
> 11:23:11,235 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221039: Waiting to obtain live lock
> 11:23:11,235 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221040: Live Server Obtained live lock
> 11:23:11,489 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221024: Started Netty Acceptor version 3.6.2.Final-c0d783c 127.0.0.1:5455 for CORE protocol
> 11:23:11,490 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221024: Started Netty Acceptor version 3.6.2.Final-c0d783c 127.0.0.1:5445 for CORE protocol
> 11:23:11,492 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221009: Server is now live
> 11:23:11,492 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221003: HornetQ Server version 2.3.0.CR1 (buzzzzz!, 122) [0ac0dcd4-6f7e-11e2-9c21-f566250843f7]
> 11:23:11,507 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
> 11:23:11,508 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
> 11:23:11,543 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-10) JBAS010406: Registered connection factory java:/JmsXA
> 11:23:11,545 WARN [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-10) IJ020016: Missing <recovery> element. XA recovery disabled for: java:/JmsXA
> 11:23:11,568 INFO [org.hornetq.ra] (MSC service thread 1-10) HornetQ resource adaptor started
> 11:23:11,569 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-10) IJ020002: Deployed: file://RaActivatorhornetq-ra
> 11:23:11,570 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
> {noformat}
> This WARN was not present in AS7 7.1.2.Final
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list