[JBoss JIRA] (JBTM-2584) Failed commit during one-phase commit optimization only logs warning and lets EJB invocation succeed
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2584?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2584:
--------------------------------
Forum Reference: https://developer.jboss.org/message/947413#947413
> Failed commit during one-phase commit optimization only logs warning and lets EJB invocation succeed
> ----------------------------------------------------------------------------------------------------
>
> Key: JBTM-2584
> URL: https://issues.jboss.org/browse/JBTM-2584
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Environment: Ubuntu Linux 32Bit, Java 8, WildFly 8.2.1.Final
> Reporter: Torsten Roemer
>
> I have an entity manager (Oracle XA datasource) and a JCA resource adapter supporting LocalTransaction in one transaction.
> Following scenario:
> - An entity with values equal to those in the database is merged
> - The commit() of the local-tx resource fails and throws a ResourceException
> All that happens is a warning being logged:
> {noformat}
> 00:34:47,619 WARN [com.arjuna.ats.jta] (default task-24) ARJUNA016039: onePhaseCommit on < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000101:25752588:566c9884:209, node_name=1, branch_uid=0:ffff7f000101:25752588:566c9884:211, subordinatenodename=null, eis_name=java:/FileDataSource > (LocalXAResourceImpl@41ac4d[connectionListener=d5fa3f connectionManager=1e7041 warned=false currentXid=null productName=Generic JCA productVersion=1.0 jndiName=java:/FileDataSource]) failed with exception XAException.XA_RBROLLBACK: org.jboss.jca.core.spi.transaction.local.LocalXAException: IJ001156: Could not commit local transaction
> at org.jboss.jca.core.tx.jbossts.LocalXAResourceImpl.commit(LocalXAResourceImpl.java:180) [ironjacamar-core-impl-1.1.9.Final.jar:1.1.9.Final]
> at com.arjuna.ats.internal.jta.resources.arjunacore.XAOnePhaseResource.commit(XAOnePhaseResource.java:113)
> at com.arjuna.ats.internal.arjuna.abstractrecords.LastResourceRecord.topLevelPrepare(LastResourceRecord.java:152)
> at com.arjuna.ats.arjuna.coordinator.AbstractRecord.topLevelOnePhaseCommit(AbstractRecord.java:428)
> at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2317)
> at com.arjuna.ats.arjuna.coordinator.BasicAction.prepare(BasicAction.java:2110)
> at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1481)
> at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:96)
> at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1166)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126)
> at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:93) [wildfly-ejb3-8.2.1.Final.jar:8.2.1.Final]
> {noformat}
> and the EJB invocation succeeds.
> I would expect the EJB to receive a RollbackException since the commit failed with XAException.XA_RBROLLBACK.
> Debugging BasicAction.prepare(), I can see that because the outcome of prepare is TwoPhaseOutcome.PREPARE_READONLY, one phase commit optimization is applied and onePhaseCommit() is called where the outcome TwoPhaseOutcome.ONE_PHASE_ERROR isn't considered an error as far as I understand.
> Then TwoPhaseOutcome.PREPARE_ONE_PHASE_COMMITTED is returned from BasicAction.prepare().
> I would never expect the EJB invocation to succeed if any participant in the transaction fails to commit.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBTM-2584) Failed commit during one-phase commit optimization only logs warning and lets EJB invocation succeed
by Torsten Roemer (JIRA)
[ https://issues.jboss.org/browse/JBTM-2584?page=com.atlassian.jira.plugin.... ]
Torsten Roemer commented on JBTM-2584:
--------------------------------------
The failing commit() throwing ResourceException that I would expect to cause the transaction to fail is [https://docs.oracle.com/javaee/6/api/javax/resource/cci/LocalTransaction....]
The BasicAction.prepare() where the 1PC optimization is applied is [http://docs.jboss.org/jbosstm/5.0.0.Final/api/jts/com/arjuna/ats/arjuna/c...]
I've started a discussion as you suggested: [https://developer.jboss.org/message/947413#947413]
> Failed commit during one-phase commit optimization only logs warning and lets EJB invocation succeed
> ----------------------------------------------------------------------------------------------------
>
> Key: JBTM-2584
> URL: https://issues.jboss.org/browse/JBTM-2584
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Environment: Ubuntu Linux 32Bit, Java 8, WildFly 8.2.1.Final
> Reporter: Torsten Roemer
>
> I have an entity manager (Oracle XA datasource) and a JCA resource adapter supporting LocalTransaction in one transaction.
> Following scenario:
> - An entity with values equal to those in the database is merged
> - The commit() of the local-tx resource fails and throws a ResourceException
> All that happens is a warning being logged:
> {noformat}
> 00:34:47,619 WARN [com.arjuna.ats.jta] (default task-24) ARJUNA016039: onePhaseCommit on < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000101:25752588:566c9884:209, node_name=1, branch_uid=0:ffff7f000101:25752588:566c9884:211, subordinatenodename=null, eis_name=java:/FileDataSource > (LocalXAResourceImpl@41ac4d[connectionListener=d5fa3f connectionManager=1e7041 warned=false currentXid=null productName=Generic JCA productVersion=1.0 jndiName=java:/FileDataSource]) failed with exception XAException.XA_RBROLLBACK: org.jboss.jca.core.spi.transaction.local.LocalXAException: IJ001156: Could not commit local transaction
> at org.jboss.jca.core.tx.jbossts.LocalXAResourceImpl.commit(LocalXAResourceImpl.java:180) [ironjacamar-core-impl-1.1.9.Final.jar:1.1.9.Final]
> at com.arjuna.ats.internal.jta.resources.arjunacore.XAOnePhaseResource.commit(XAOnePhaseResource.java:113)
> at com.arjuna.ats.internal.arjuna.abstractrecords.LastResourceRecord.topLevelPrepare(LastResourceRecord.java:152)
> at com.arjuna.ats.arjuna.coordinator.AbstractRecord.topLevelOnePhaseCommit(AbstractRecord.java:428)
> at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2317)
> at com.arjuna.ats.arjuna.coordinator.BasicAction.prepare(BasicAction.java:2110)
> at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1481)
> at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:96)
> at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1166)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126)
> at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:93) [wildfly-ejb3-8.2.1.Final.jar:8.2.1.Final]
> {noformat}
> and the EJB invocation succeeds.
> I would expect the EJB to receive a RollbackException since the commit failed with XAException.XA_RBROLLBACK.
> Debugging BasicAction.prepare(), I can see that because the outcome of prepare is TwoPhaseOutcome.PREPARE_READONLY, one phase commit optimization is applied and onePhaseCommit() is called where the outcome TwoPhaseOutcome.ONE_PHASE_ERROR isn't considered an error as far as I understand.
> Then TwoPhaseOutcome.PREPARE_ONE_PHASE_COMMITTED is returned from BasicAction.prepare().
> I would never expect the EJB invocation to succeed if any participant in the transaction fails to commit.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBTM-2495) Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate)
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2495?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2495:
--------------------------------
Issue Type: Task (was: Bug)
> Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate)
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-2495
> URL: https://issues.jboss.org/browse/JBTM-2495
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: BlackTie, Documentation
> Affects Versions: 5.0.0.M2
> Environment: RHEL 6.3
> Reporter: Joice Joy
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.next
>
>
> I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1 but the Wildfly server fails to start the Blacktie service
> But the server does not start the blacktie service:
> This is from quickstart quickstart/blacktie
>
>
>
> =========================================================================
>
>
> JBoss Bootstrap Environment
>
>
> JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final
>
>
> JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java
>
>
> JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE
>
>
> =========================================================================
>
>
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
> 07:35:52,490 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final
> 07:35:52,892 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
> 07:35:53,007 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting
> 07:35:55,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 07:35:55,055 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 07:35:55,121 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear
> 07:35:55,361 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content
> 07:35:55,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
> 07:35:55,422 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final
> 07:35:55,438 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final
> 07:35:55,482 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final
> 07:35:55,548 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem.
> 07:35:55,554 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
> 07:35:55,557 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem
> 07:35:55,602 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final)
> 07:35:55,615 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main]
> 07:35:55,652 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> 07:35:55,661 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem
> 07:35:55,670 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2
> 07:35:55,827 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem
> 07:35:55,829 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final
> 07:35:55,849 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
> 07:35:55,849 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension
> 07:35:55,998 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting
> 07:35:56,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting
> 07:35:56,095 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
> 07:35:56,119 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
> 07:35:56,352 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content
> 07:35:56,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.
> 07:35:56,437 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
> 07:35:56,589 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080
> 07:35:56,945 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started
> 07:35:56,969 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
> 07:35:57,030 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments
> 07:35:57,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear")
> 07:35:57,187 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging)
> 07:35:57,193 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock
> 07:35:57,287 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal
> 07:35:57,387 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE
> 07:35:57,414 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final
> 07:35:57,439 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP
> 07:35:57,443 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP
> 07:35:57,502 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock
> 07:35:57,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock
> 07:35:58,108 INFO [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor
> 07:35:58,112 INFO [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor
> 07:35:58,206 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live
> 07:35:58,207 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561]
> 07:35:58,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue
> 07:35:58,514 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory
> 07:35:58,519 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
> 07:35:58,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ
> 07:35:58,623 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA
> 07:35:58,721 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started
> 07:35:58,721 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra
> 07:35:58,733 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
> 07:35:58,733 INFO [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
> 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference.
> 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference.
> 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference.
> 07:35:58,763 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference.
> 07:35:58,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar")
> 07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml
> at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
> ... 5 more
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml
> at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95)
> ... 6 more
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1]
> Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
> at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89)
> ... 6 more
>
>
> 07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1]
> Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}}
> 07:35:58,980 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear")
> 07:35:58,982 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear"
>
>
> 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand)
> 07:35:59,243 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms
> 07:35:59,332 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms
> 07:35:59,413 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content
> 07:35:59,414 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear")
> 07:35:59,414 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2498:
--------------------------------
Issue Type: Task (was: Bug)
> Incomplete BlackTie quickstart documentation
> --------------------------------------------
>
> Key: JBTM-2498
> URL: https://issues.jboss.org/browse/JBTM-2498
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: BlackTie, Demonstrator, Documentation
> Affects Versions: 5.2.2
> Reporter: Michael Musgrove
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.next
>
>
> The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly.
> Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly.
> My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBTM-2568) Add config options to enable fine grained control of what's tested in a PR
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2568?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2568:
--------------------------------
Issue Type: Task (was: Feature Request)
> Add config options to enable fine grained control of what's tested in a PR
> --------------------------------------------------------------------------
>
> Key: JBTM-2568
> URL: https://issues.jboss.org/browse/JBTM-2568
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Affects Versions: 5.2.8.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Optional
> Fix For: 5.next
>
>
> Currently we have a fixed set of Jenkins CI config profiles when testing PRs (QA_JTS_JDKORB, QA_JTA, XTS, MAIN, BLACKTIE and PERF) and we are allowed to selectively disable one or more of them.
> It would be handy to be able to control other things such as running QA tests using the journal store (which none of the above QA profiles allow). It would also be a handy shortcut to explicitly set which profile to run (as opposed to which ones to disable).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months