[JBoss JIRA] (JBTM-1825) Error starting XTS Services
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1825?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1825:
--------------------------------
Assignee: Amos Feng (was: Paul Robinson)
> Error starting XTS Services
> ---------------------------
>
> Key: JBTM-1825
> URL: https://issues.jboss.org/browse/JBTM-1825
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Application Server Integration, XTS
> Reporter: Paul Robinson
> Assignee: Amos Feng
> Priority: Critical
> Fix For: 5.0.0.M4
>
>
> On Wildfly master as of today, booting with standalone-xts.xml produces these errors:
> {code}
> 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService
> 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-8) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService
> 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-11) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService
> 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService
> 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService
> 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService
> 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-5) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService
> 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-1) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=BusinessAgreementWithCoordinatorCompletionCoordinatorService
> 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-8) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=CoordinatorService
> 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-11) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=CompletionCoordinatorService
> 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-4) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=TerminationCoordinatorRPCService
> 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-3) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=TerminationCoordinatorService
> 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-2) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=BusinessAgreementWithParticipantCompletionCoordinatorService
> 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-5) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=CompletionCoordinatorRPCService
> {code}
> The XTS integration tests in the WildFly codebase under 'testsuite/integration/xts' pass on my box, but are failing in CI (sometimes). I don't know how any of the XTS tests could be passing if those services really haven't started up.
> Note that the wsdl is available at http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService?wsdl, despite TerminationCoordinatorService claiming not to have started.
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1816) JavaIDL test wrongly excluded?
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1816?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1816:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
The JTS units should run with a clean object store. I have added the relevant code to the base class (TestBase.java)
> JavaIDL test wrongly excluded?
> ------------------------------
>
> Key: JBTM-1816
> URL: https://issues.jboss.org/browse/JBTM-1816
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System, JTS, Testing
> Affects Versions: 5.0.0.M3
> Reporter: Mark Little
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.0.0.M4
>
> Attachments: jacorb-rc-in-object-store.tgz
>
>
> In the JTS pom.xml within the IDLJ excludes section there is:
> <exclude>**/JavaIdlRecoveryUnitTest.java</exclude>
> Surely we shouldn't be excluding JavaIdl tests in the JavaIdl run? Should this refer to the JacORB tests instead?
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1825) Error starting XTS Services
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1825?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1825:
--------------------------------
Description:
On Wildfly master as of today, booting with standalone-xts.xml produces these errors:
{code}
14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService
14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-8) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService
14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-11) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService
14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService
14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService
14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService
14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-5) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService
14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-1) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=BusinessAgreementWithCoordinatorCompletionCoordinatorService
14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-8) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=CoordinatorService
14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-11) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=CompletionCoordinatorService
14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-4) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=TerminationCoordinatorRPCService
14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-3) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=TerminationCoordinatorService
14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-2) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=BusinessAgreementWithParticipantCompletionCoordinatorService
14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-5) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=CompletionCoordinatorRPCService
{code}
The XTS integration tests in the WildFly codebase under 'testsuite/integration/xts' pass on my box, but are failing in CI (sometimes). I don't know how any of the XTS tests could be passing if those services really haven't started up.
Note that the wsdl is available at http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService?wsdl, despite TerminationCoordinatorService claiming not to have started.
> Error starting XTS Services
> ---------------------------
>
> Key: JBTM-1825
> URL: https://issues.jboss.org/browse/JBTM-1825
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Application Server Integration, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Critical
> Fix For: 5.0.0.M4
>
>
> On Wildfly master as of today, booting with standalone-xts.xml produces these errors:
> {code}
> 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService
> 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-8) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService
> 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-11) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService
> 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService
> 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService
> 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService
> 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-5) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService
> 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-1) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=BusinessAgreementWithCoordinatorCompletionCoordinatorService
> 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-8) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=CoordinatorService
> 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-11) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=CompletionCoordinatorService
> 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-4) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=TerminationCoordinatorRPCService
> 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-3) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=TerminationCoordinatorService
> 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-2) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=BusinessAgreementWithParticipantCompletionCoordinatorService
> 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-5) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=CompletionCoordinatorRPCService
> {code}
> The XTS integration tests in the WildFly codebase under 'testsuite/integration/xts' pass on my box, but are failing in CI (sometimes). I don't know how any of the XTS tests could be passing if those services really haven't started up.
> Note that the wsdl is available at http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService?wsdl, despite TerminationCoordinatorService claiming not to have started.
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1825) Error starting XTS Services
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1825:
-----------------------------------
Summary: Error starting XTS Services
Key: JBTM-1825
URL: https://issues.jboss.org/browse/JBTM-1825
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Application Server Integration, XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Priority: Critical
Fix For: 5.0.0.M4
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1171) improve XAResource preparefailed logging
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBTM-1171?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBTM-1171:
-----------------------------------------------
Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 959462|https://bugzilla.redhat.com/show_bug.cgi?id=959462] from ASSIGNED to MODIFIED
> improve XAResource preparefailed logging
> ----------------------------------------
>
> Key: JBTM-1171
> URL: https://issues.jboss.org/browse/JBTM-1171
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: JTA
> Affects Versions: 4.6.1.CP12
> Reporter: Jonathan Halliday
> Assignee: Michael Musgrove
> Fix For: 4.6.1.CP13, 4.17.5, 5.0.0.M4
>
>
> com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed does not log the underlying XA exception. In cases where e.g. db constraints are deferred to tx commit time, such errors can contain useful information.
> Note that non-deferred constraints are covered by JBTM-575 as the problem manifests at the earlier beforeCompletion (i.e. sql flush) stage.
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1790) If xaNodeName is not set then a nullpointerexception is raised rather than an informative exception
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1790?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-1790:
----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstm/narayana/pull/368
I've added simple checking or exceptions in the places where null pointer exception can be thrown by using TxControl.getXANodeName(). It works for all JTS tests which throw NullPointerException after setting node name to null.
However, there are other places which utilise node names as null, but they do the checking for that, so I didn't touch them.
> If xaNodeName is not set then a nullpointerexception is raised rather than an informative exception
> ---------------------------------------------------------------------------------------------------
>
> Key: JBTM-1790
> URL: https://issues.jboss.org/browse/JBTM-1790
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTA, JTS
> Affects Versions: 5.0.0.M3
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M4
>
> Original Estimate: 30 minutes
> Time Spent: 30 minutes
> Remaining Estimate: 0 minutes
>
> TxControl needs a static initialization block reintroducing/similar such that if CoordinatorEnvironmentBean::getNodeIdentifier() returns null it should log a fatal error and fail to initialize.
> Currently for JTS an obscure stack trace is printed:
> [INFO] --- exec-maven-plugin:1.2.1:java (default-cli) @ iiop-jts-client ---
> Jun 21, 2013 6:08:11 PM com.arjuna.orbportability.internal.utils.InitLoader createInstance
> INFO: ARJUNA021027: Loading PreInitLoader class - com.arjuna.ats.internal.jts.context.ContextPropagationManager
> Jun 21, 2013 6:08:11 PM org.jacorb.config.JacORBConfiguration init
> WARNING: jacorb.home unset! Will use '.'
> Jun 21, 2013 6:08:11 PM org.jacorb.config.JacORBConfiguration init
> WARNING: File ./jacorb.properties for configuration jacorb not found
> Jun 21, 2013 6:08:11 PM org.jacorb.config.JacORBConfiguration init
> INFO: configuration jacorb loaded from classpath
> Jun 21, 2013 6:08:11 PM com.arjuna.orbportability.internal.utils.InitLoader createInstance
> INFO: ARJUNA021027: Loading PostInitLoader class - com.arjuna.ats.internal.jts.recovery.RecoveryInit
> Jun 21, 2013 6:08:11 PM com.arjuna.orbportability.internal.utils.InitLoader createInstance
> INFO: ARJUNA021027: Loading PostInitLoader class - com.arjuna.ats.jts.utils.ORBSetup
> Jun 21, 2013 6:08:11 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService
> INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 43728
> Jun 21, 2013 6:08:11 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem <init>
> INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 43728
> Jun 21, 2013 6:08:11 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start
> INFO: ARJUNA012170: TransactionStatusManager started on port 43728 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
> java.rmi.RemoteException: CORBA UNKNOWN 30001 No; nested exception is:
> org.omg.CORBA.UNKNOWN: java.lang.NullPointerException vmcid: 0x7000 minor code: 1329 completed: No
> at com.sun.corba.se.impl.javax.rmi.CORBA.Util.mapSystemException(Util.java:315)
> at javax.rmi.CORBA.Util.mapSystemException(Util.java:83)
> at com.sun.corba.se.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:164)
> at com.sun.corba.se.spi.orbutil.proxy.CompositeInvocationHandlerImpl.invoke(CompositeInvocationHandlerImpl.java:79)
> at com.sun.proxy.$Proxy7.hello(Unknown Source)
> at org.jboss.qa.IIOPTesting.main(IIOPTesting.java:27)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: org.omg.CORBA.UNKNOWN: java.lang.NullPointerException vmcid: 0x7000 minor code: 1329 completed: No
> at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.get_txcontext(ArjunaTransactionImple.java:1300)
> at com.arjuna.ArjunaOTS.ArjunaTransactionPOATie.get_txcontext(ArjunaTransactionPOATie.java:129)
> at com.arjuna.ArjunaOTS._ArjunaTransactionStub.get_txcontext(_ArjunaTransactionStub.java:788)
> at com.arjuna.ats.jts.orbspecific.jacorb.interceptors.interposition.InterpositionClientRequestInterceptorImpl.send_request(InterpositionClientRequestInterceptorImpl.java:196)
> at org.jacorb.orb.portableInterceptor.ClientInterceptorIterator.invoke(ClientInterceptorIterator.java:95)
> at org.jacorb.orb.portableInterceptor.AbstractInterceptorIterator.iterate(AbstractInterceptorIterator.java:67)
> at org.jacorb.orb.portableInterceptor.ClientInterceptorIterator.iterate(ClientInterceptorIterator.java:68)
> at org.jacorb.orb.ClientInterceptorHandler.invokeInterceptors(ClientInterceptorHandler.java:265)
> at org.jacorb.orb.ClientInterceptorHandler.handle_send_request(ClientInterceptorHandler.java:99)
> at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:996)
> at org.jacorb.orb.Delegate.invoke(Delegate.java:957)
> at com.sun.corba.se.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:151)
> ... 9 more
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1790) If xaNodeName is not set then a nullpointerexception is raised rather than an informative exception
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1790?focusedWorklogId=12429443&page=... ]
Gytis Trikleris logged work on JBTM-1790:
-----------------------------------------
Author: Gytis Trikleris
Created on: 05/Jul/13 8:29 AM
Start Date: 05/Jul/13 8:28 AM
Worklog Time Spent: 30 minutes
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 30 minutes)
Time Spent: 30 minutes
Worklog Id: (was: 12429443)
> If xaNodeName is not set then a nullpointerexception is raised rather than an informative exception
> ---------------------------------------------------------------------------------------------------
>
> Key: JBTM-1790
> URL: https://issues.jboss.org/browse/JBTM-1790
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTA, JTS
> Affects Versions: 5.0.0.M3
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M4
>
> Original Estimate: 30 minutes
> Time Spent: 30 minutes
> Remaining Estimate: 0 minutes
>
> TxControl needs a static initialization block reintroducing/similar such that if CoordinatorEnvironmentBean::getNodeIdentifier() returns null it should log a fatal error and fail to initialize.
> Currently for JTS an obscure stack trace is printed:
> [INFO] --- exec-maven-plugin:1.2.1:java (default-cli) @ iiop-jts-client ---
> Jun 21, 2013 6:08:11 PM com.arjuna.orbportability.internal.utils.InitLoader createInstance
> INFO: ARJUNA021027: Loading PreInitLoader class - com.arjuna.ats.internal.jts.context.ContextPropagationManager
> Jun 21, 2013 6:08:11 PM org.jacorb.config.JacORBConfiguration init
> WARNING: jacorb.home unset! Will use '.'
> Jun 21, 2013 6:08:11 PM org.jacorb.config.JacORBConfiguration init
> WARNING: File ./jacorb.properties for configuration jacorb not found
> Jun 21, 2013 6:08:11 PM org.jacorb.config.JacORBConfiguration init
> INFO: configuration jacorb loaded from classpath
> Jun 21, 2013 6:08:11 PM com.arjuna.orbportability.internal.utils.InitLoader createInstance
> INFO: ARJUNA021027: Loading PostInitLoader class - com.arjuna.ats.internal.jts.recovery.RecoveryInit
> Jun 21, 2013 6:08:11 PM com.arjuna.orbportability.internal.utils.InitLoader createInstance
> INFO: ARJUNA021027: Loading PostInitLoader class - com.arjuna.ats.jts.utils.ORBSetup
> Jun 21, 2013 6:08:11 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService
> INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 43728
> Jun 21, 2013 6:08:11 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem <init>
> INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 43728
> Jun 21, 2013 6:08:11 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start
> INFO: ARJUNA012170: TransactionStatusManager started on port 43728 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
> java.rmi.RemoteException: CORBA UNKNOWN 30001 No; nested exception is:
> org.omg.CORBA.UNKNOWN: java.lang.NullPointerException vmcid: 0x7000 minor code: 1329 completed: No
> at com.sun.corba.se.impl.javax.rmi.CORBA.Util.mapSystemException(Util.java:315)
> at javax.rmi.CORBA.Util.mapSystemException(Util.java:83)
> at com.sun.corba.se.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:164)
> at com.sun.corba.se.spi.orbutil.proxy.CompositeInvocationHandlerImpl.invoke(CompositeInvocationHandlerImpl.java:79)
> at com.sun.proxy.$Proxy7.hello(Unknown Source)
> at org.jboss.qa.IIOPTesting.main(IIOPTesting.java:27)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: org.omg.CORBA.UNKNOWN: java.lang.NullPointerException vmcid: 0x7000 minor code: 1329 completed: No
> at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.get_txcontext(ArjunaTransactionImple.java:1300)
> at com.arjuna.ArjunaOTS.ArjunaTransactionPOATie.get_txcontext(ArjunaTransactionPOATie.java:129)
> at com.arjuna.ArjunaOTS._ArjunaTransactionStub.get_txcontext(_ArjunaTransactionStub.java:788)
> at com.arjuna.ats.jts.orbspecific.jacorb.interceptors.interposition.InterpositionClientRequestInterceptorImpl.send_request(InterpositionClientRequestInterceptorImpl.java:196)
> at org.jacorb.orb.portableInterceptor.ClientInterceptorIterator.invoke(ClientInterceptorIterator.java:95)
> at org.jacorb.orb.portableInterceptor.AbstractInterceptorIterator.iterate(AbstractInterceptorIterator.java:67)
> at org.jacorb.orb.portableInterceptor.ClientInterceptorIterator.iterate(ClientInterceptorIterator.java:68)
> at org.jacorb.orb.ClientInterceptorHandler.invokeInterceptors(ClientInterceptorHandler.java:265)
> at org.jacorb.orb.ClientInterceptorHandler.handle_send_request(ClientInterceptorHandler.java:99)
> at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:996)
> at org.jacorb.orb.Delegate.invoke(Delegate.java:957)
> at com.sun.corba.se.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:151)
> ... 9 more
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1791) xts-demo-core quickstart cannot find com.arjuna.ats.arjuna.common package
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1791?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-1791:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> xts-demo-core quickstart cannot find com.arjuna.ats.arjuna.common package
> -------------------------------------------------------------------------
>
> Key: JBTM-1791
> URL: https://issues.jboss.org/browse/JBTM-1791
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Demonstrator
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M4
>
> Original Estimate: 2 hours
> Time Spent: 30 minutes
> Remaining Estimate: 0 minutes
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-quickstarts-windo...
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-quickstarts-windo...
> {code}
> [INFO] ------------------------------------------------------------------------
> [INFO] Building xts-demo-core 5.0.0.M4-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ xts-demo-core ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ xts-demo-core ---
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
> [INFO] Copying 7 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ xts-demo-core ---
> [WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. build is platform dependent!
> [INFO] Compiling 42 source files to C:\hudson\workspace\narayana-quickstarts-windows2008-taconic\XTS\legacy-api-quickstarts\demo\core\target\classes
> [INFO] -------------------------------------------------------------
> [ERROR] COMPILATION ERROR :
> [INFO] -------------------------------------------------------------
> [ERROR] \hudson\workspace\narayana-quickstarts-windows2008-taconic\XTS\legacy-api-quickstarts\demo\core\src\main\java\com\jboss\jbosstm\xts\demo\services\theatre\TheatreServiceAT.java:[32,35] error: package com.arjuna.ats.arjuna.common does not exist
> [ERROR] \hudson\workspace\narayana-quickstarts-windows2008-taconic\XTS\legacy-api-quickstarts\demo\core\src\main\java\com\jboss\jbosstm\xts\demo\services\theatre\TheatreServiceAT.java:[91,154] error: cannot find symbol
> [ERROR] \hudson\workspace\narayana-quickstarts-windows2008-taconic\XTS\legacy-api-quickstarts\demo\core\src\main\java\com\jboss\jbosstm\xts\demo\services\theatre\TheatreServiceBA.java:[110,171] error: cannot find symbol
> [ERROR] \hudson\workspace\narayana-quickstarts-windows2008-taconic\XTS\legacy-api-quickstarts\demo\core\src\main\java\com\jboss\jbosstm\xts\demo\services\taxi\TaxiServiceBA.java:[114,161] error: cannot find symbol
> [ERROR] \hudson\workspace\narayana-quickstarts-windows2008-taconic\XTS\legacy-api-quickstarts\demo\core\src\main\java\com\jboss\jbosstm\xts\demo\services\restaurant\RestaurantServiceBA.java:[115,173] error: cannot find symbol
> [ERROR] \hudson\workspace\narayana-quickstarts-windows2008-taconic\XTS\legacy-api-quickstarts\demo\core\src\main\java\com\jboss\jbosstm\xts\demo\services\taxi\TaxiServiceAT.java:[79,148] error: cannot find symbol
> [ERROR] \hudson\workspace\narayana-quickstarts-windows2008-taconic\XTS\legacy-api-quickstarts\demo\core\src\main\java\com\jboss\jbosstm\xts\demo\services\restaurant\RestaurantServiceAT.java:[98,156] error: cannot find symbol
> {code}
--
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
10 years, 11 months