[JBoss JIRA] (JBTM-1728) Use a global environment variable in CI for version numbers of Narayana and WildFly
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1728?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-1728:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Use a global environment variable in CI for version numbers of Narayana and WildFly
> -----------------------------------------------------------------------------------
>
> Key: JBTM-1728
> URL: https://issues.jboss.org/browse/JBTM-1728
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Build System, Testing
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M4
>
> Original Estimate: 2 hours
> Time Spent: 55 minutes
> Remaining Estimate: 0 minutes
>
> We have "8.0.0.Alpha2-SNAPSHOT" scattered over many jobs. This is a pain to change every time we have a new release of Wildfly. We also have the same issue with jboss-as-7.2.0.Final.
> We should use global env variables instead. See the following for how to do it. Notice that I have already added one for Narayana.
> http://172.17.131.2/configure
> Call the variables:
> WILDFLY_MASTER_VERSION=8.0.0.Alpha2-SNAPSHOT
> JBOSS_7_2_VERSION=7.2.0.Final
> Ask paul to update the sanity check job before this is done. This will blacklist the usage of hardcoded wildfly/jboss version numbers. It will make it a lot easier to find all the places it is used.
--
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
11 years, 2 months
[JBoss JIRA] (JBTM-1747) CNFE when invoking a plain Web service with standalone-xts.xml config
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1747?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-1747:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> CNFE when invoking a plain Web service with standalone-xts.xml config
> ---------------------------------------------------------------------
>
> Key: JBTM-1747
> URL: https://issues.jboss.org/browse/JBTM-1747
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M4
>
> Original Estimate: 2 days
> Time Spent: 1 day, 1 hour
> Remaining Estimate: 0 minutes
>
> I've not had chance to reproduce this, but this is what I think I did:
> 1. Start Wildfly with the standalone-xts.xml configuration
> 2. Deploy a plain (non-XTS) web service to the server
> 3. Invoke the web service from inside this server, ensuring that org.jboss.xts is not in the dependencies. Which it shouldn't be if you are just invoking a plain WS.
> 4. Observe the CNFE on one of the TXBridge interceptors (I don't remember which).
> I think the problem is that XTS is adding the handler chain for doing default context propagation to all web services, rather than just those that have the XTS dependency.
--
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
11 years, 2 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 commented on JBTM-1825:
-------------------------------------
This method seems to do the actual starting of the service. Therefore it fails if the service is already started. Given that XTS seems to be functioning correctly, I'd guess that the bug is this method being called twice. The first time it succeeds, the second it fails, producing the error.
> 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
11 years, 2 months
[JBoss JIRA] (JBTM-1829) Recovery creator service fails to start in JacORBGenericRecoveryCreatorUnitTest
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1829?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris commented on JBTM-1829:
---------------------------------------
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/178/TESTS=MAIN,jd...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/51/
> Recovery creator service fails to start in JacORBGenericRecoveryCreatorUnitTest
> -------------------------------------------------------------------------------
>
> Key: JBTM-1829
> URL: https://issues.jboss.org/browse/JBTM-1829
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTS
> Reporter: Gytis Trikleris
> Assignee: Tom Jenkinson
> Priority: Minor
> Fix For: 5.0.0.M4
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/177/TESTS=MAIN,jd...
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/50
> {code}
> Emptying /home/hudson/workspace/narayana/TESTS/MAIN/jdk/jdk7.latest/label/linux/ArjunaJTS/jts/target/test-classes/ObjectStore
> 1 [main] WARN jacorb.config - jacorb.home unset! Will use '.'
> 1 [main] WARN jacorb.config - File ./jacorb.properties for configuration jacorb not found
> 2 [main] WARN jacorb.config - no properties found for configuration jacorb
> 5 [main] INFO jacorb.orb.print_version -
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> JacORB V 2.3.1 (JBoss patch01), www.jacorb.org
> (C) The JacORB project 29-Jul-2009
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 40 [main] INFO jacorb.orb - Property "jacorb.hashtable_class" is set to: java.util.HashMap
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCServiceInit initORBandOA
> INFO: ARJUNA022087: RecoveryServer using existing ORB
> 201 [main] WARN jacorb.config - jacorb.home unset! Will use '.'
> 201 [main] WARN jacorb.config - File ./jacorb.properties for configuration jacorb not found
> 202 [main] WARN jacorb.config - no properties found for configuration jacorb
> 202 [main] INFO jacorb.orb.singleton - created ORBSingleton
> 313 [main] INFO jacorb.poa - oid:
> 00 17 4C 48 03 47 41 4C 02 05 32 ..LH.GAL..2
> object is activated
> 314 [main] INFO jacorb.poa - Using server ID (4426315968) for transient POA
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.jts.recovery.recoverycoordinators.GenericRecoveryCreator create
> WARN: ARJUNA022156: GenericRecoveryCreator: Missing params to create
> 318 [Thread-3] INFO jacorb.orb - ORB run
> 321 [POADestructor] INFO jacorb.poa - POA RcvCo-RecCoService_jaimerecovery_coordinator destroyed
> 322 [POADestructor] INFO jacorb.poa - POA RootPOA destroyed
> 322 [main] INFO jacorb.orb - prepare ORB for shutdown...
> 322 [main] INFO jacorb.orb - ORB going down...
> 323 [ServerSocketListener] INFO jacorb.orb.iiop - Listener exited
> 323 [main] INFO jacorb.orb - ORB shutdown complete
> Emptying /home/hudson/workspace/narayana/TESTS/MAIN/jdk/jdk7.latest/label/linux/ArjunaJTS/jts/target/test-classes/ObjectStore
> Emptying /home/hudson/workspace/narayana/TESTS/MAIN/jdk/jdk7.latest/label/linux/ArjunaJTS/jts/target/test-classes/ObjectStore
> 328 [main] WARN jacorb.config - jacorb.home unset! Will use '.'
> 328 [main] WARN jacorb.config - File ./jacorb.properties for configuration jacorb not found
> 329 [main] WARN jacorb.config - no properties found for configuration jacorb
> 329 [main] INFO jacorb.orb.print_version -
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> JacORB V 2.3.1 (JBoss patch01), www.jacorb.org
> (C) The JacORB project 29-Jul-2009
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 329 [main] INFO jacorb.orb - Property "jacorb.hashtable_class" is set to: java.util.HashMap
> 330 [Thread-3] INFO jacorb.orb - ORB run, exit
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCServiceInit initORBandOA
> INFO: ARJUNA022087: RecoveryServer using existing ORB
> 333 [POADestructor] INFO jacorb.poa - POA RcvCo-RecCoService_jaimerecovery_coordinator destroyed
> 333 [POADestructor] INFO jacorb.poa - POA RootPOA destroyed
> 333 [Thread-3] INFO jacorb.orb - prepare ORB for shutdown...
> 333 [Thread-3] INFO jacorb.orb - ORB going down...
> 333 [Thread-3] INFO jacorb.orb - ORB shutdown complete
> 334 [ServerSocketListener] INFO jacorb.orb.iiop - Listener exited
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCServiceInit startRCservice
> WARN: ARJUNA022083: JacOrbRCServiceInit - Failed to start RC service
> org.omg.CORBA.OBJECT_NOT_EXIST: POA destroyed vmcid: 0x0 minor code: 0 completed: No
> at org.jacorb.poa.POA.checkDestructionApparent(Unknown Source)
> at org.jacorb.poa.POA.the_POAManager(Unknown Source)
> at com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCServiceInit.startRCservice(JacOrbRCServiceInit.java:225)
> at com.hp.mwtests.ts.jts.recovery.JacORBGenericRecoveryCreatorUnitTest.testSuccess(JacORBGenericRecoveryCreatorUnitTest.java:95)
> 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Jul 07, 2013 5:55:53 PM com.arjuna.orbportability.RootOA objectIsReady
> WARN: ARJUNA021004: objectIsReady - invalid POA: rootPOA
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService
> INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 48098
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem <init>
> INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 48098
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start
> INFO: ARJUNA012170: TransactionStatusManager started on port 48098 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCManager makeRC
> WARN: ARJUNA022077: RCManager.makeRC did not make rcvco reference
> org.omg.CORBA.BAD_INV_ORDER: vmcid: 0x0 minor code: 4 completed: No
> at org.jacorb.orb.ORB.work_pending(Unknown Source)
> at org.jacorb.orb.ORB.perform_work(Unknown Source)
> at org.jacorb.orb.ORB.string_to_object(Unknown Source)
> at com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCManager.makeRC(JacOrbRCManager.java:102)
> at com.arjuna.ats.internal.jts.recovery.recoverycoordinators.GenericRecoveryCreator.create(GenericRecoveryCreator.java:121)
> at com.hp.mwtests.ts.jts.recovery.JacORBGenericRecoveryCreatorUnitTest.testSuccess(JacORBGenericRecoveryCreatorUnitTest.java:111)
> 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Emptying /home/hudson/workspace/narayana/TESTS/MAIN/jdk/jdk7.latest/label/linux/ArjunaJTS/jts/target/test-classes/ObjectStore
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore remove_state
> WARN: ARJUNA012284: ShadowingStore::remove_state() - access problems on 0:ffffac118321:8b3f:51d99d99:3 and /Recovery/TransactionStatusManager
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore remove_state
> WARN: ARJUNA012265: ShadowingStore::remove_state() - state 0:ffffac118321:8b3f:51d99d99:3 does not exist for type /Recovery/TransactionStatusManager
> {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
11 years, 2 months
[JBoss JIRA] (JBTM-1829) Recovery creator service fails to start in JacORBGenericRecoveryCreatorUnitTest
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1829?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris reopened JBTM-1829:
-----------------------------------
> Recovery creator service fails to start in JacORBGenericRecoveryCreatorUnitTest
> -------------------------------------------------------------------------------
>
> Key: JBTM-1829
> URL: https://issues.jboss.org/browse/JBTM-1829
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTS
> Reporter: Gytis Trikleris
> Assignee: Tom Jenkinson
> Priority: Minor
> Fix For: 5.0.0.M4
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/177/TESTS=MAIN,jd...
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/50
> {code}
> Emptying /home/hudson/workspace/narayana/TESTS/MAIN/jdk/jdk7.latest/label/linux/ArjunaJTS/jts/target/test-classes/ObjectStore
> 1 [main] WARN jacorb.config - jacorb.home unset! Will use '.'
> 1 [main] WARN jacorb.config - File ./jacorb.properties for configuration jacorb not found
> 2 [main] WARN jacorb.config - no properties found for configuration jacorb
> 5 [main] INFO jacorb.orb.print_version -
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> JacORB V 2.3.1 (JBoss patch01), www.jacorb.org
> (C) The JacORB project 29-Jul-2009
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 40 [main] INFO jacorb.orb - Property "jacorb.hashtable_class" is set to: java.util.HashMap
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCServiceInit initORBandOA
> INFO: ARJUNA022087: RecoveryServer using existing ORB
> 201 [main] WARN jacorb.config - jacorb.home unset! Will use '.'
> 201 [main] WARN jacorb.config - File ./jacorb.properties for configuration jacorb not found
> 202 [main] WARN jacorb.config - no properties found for configuration jacorb
> 202 [main] INFO jacorb.orb.singleton - created ORBSingleton
> 313 [main] INFO jacorb.poa - oid:
> 00 17 4C 48 03 47 41 4C 02 05 32 ..LH.GAL..2
> object is activated
> 314 [main] INFO jacorb.poa - Using server ID (4426315968) for transient POA
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.jts.recovery.recoverycoordinators.GenericRecoveryCreator create
> WARN: ARJUNA022156: GenericRecoveryCreator: Missing params to create
> 318 [Thread-3] INFO jacorb.orb - ORB run
> 321 [POADestructor] INFO jacorb.poa - POA RcvCo-RecCoService_jaimerecovery_coordinator destroyed
> 322 [POADestructor] INFO jacorb.poa - POA RootPOA destroyed
> 322 [main] INFO jacorb.orb - prepare ORB for shutdown...
> 322 [main] INFO jacorb.orb - ORB going down...
> 323 [ServerSocketListener] INFO jacorb.orb.iiop - Listener exited
> 323 [main] INFO jacorb.orb - ORB shutdown complete
> Emptying /home/hudson/workspace/narayana/TESTS/MAIN/jdk/jdk7.latest/label/linux/ArjunaJTS/jts/target/test-classes/ObjectStore
> Emptying /home/hudson/workspace/narayana/TESTS/MAIN/jdk/jdk7.latest/label/linux/ArjunaJTS/jts/target/test-classes/ObjectStore
> 328 [main] WARN jacorb.config - jacorb.home unset! Will use '.'
> 328 [main] WARN jacorb.config - File ./jacorb.properties for configuration jacorb not found
> 329 [main] WARN jacorb.config - no properties found for configuration jacorb
> 329 [main] INFO jacorb.orb.print_version -
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> JacORB V 2.3.1 (JBoss patch01), www.jacorb.org
> (C) The JacORB project 29-Jul-2009
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 329 [main] INFO jacorb.orb - Property "jacorb.hashtable_class" is set to: java.util.HashMap
> 330 [Thread-3] INFO jacorb.orb - ORB run, exit
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCServiceInit initORBandOA
> INFO: ARJUNA022087: RecoveryServer using existing ORB
> 333 [POADestructor] INFO jacorb.poa - POA RcvCo-RecCoService_jaimerecovery_coordinator destroyed
> 333 [POADestructor] INFO jacorb.poa - POA RootPOA destroyed
> 333 [Thread-3] INFO jacorb.orb - prepare ORB for shutdown...
> 333 [Thread-3] INFO jacorb.orb - ORB going down...
> 333 [Thread-3] INFO jacorb.orb - ORB shutdown complete
> 334 [ServerSocketListener] INFO jacorb.orb.iiop - Listener exited
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCServiceInit startRCservice
> WARN: ARJUNA022083: JacOrbRCServiceInit - Failed to start RC service
> org.omg.CORBA.OBJECT_NOT_EXIST: POA destroyed vmcid: 0x0 minor code: 0 completed: No
> at org.jacorb.poa.POA.checkDestructionApparent(Unknown Source)
> at org.jacorb.poa.POA.the_POAManager(Unknown Source)
> at com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCServiceInit.startRCservice(JacOrbRCServiceInit.java:225)
> at com.hp.mwtests.ts.jts.recovery.JacORBGenericRecoveryCreatorUnitTest.testSuccess(JacORBGenericRecoveryCreatorUnitTest.java:95)
> 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Jul 07, 2013 5:55:53 PM com.arjuna.orbportability.RootOA objectIsReady
> WARN: ARJUNA021004: objectIsReady - invalid POA: rootPOA
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService
> INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 48098
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem <init>
> INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 48098
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start
> INFO: ARJUNA012170: TransactionStatusManager started on port 48098 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCManager makeRC
> WARN: ARJUNA022077: RCManager.makeRC did not make rcvco reference
> org.omg.CORBA.BAD_INV_ORDER: vmcid: 0x0 minor code: 4 completed: No
> at org.jacorb.orb.ORB.work_pending(Unknown Source)
> at org.jacorb.orb.ORB.perform_work(Unknown Source)
> at org.jacorb.orb.ORB.string_to_object(Unknown Source)
> at com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCManager.makeRC(JacOrbRCManager.java:102)
> at com.arjuna.ats.internal.jts.recovery.recoverycoordinators.GenericRecoveryCreator.create(GenericRecoveryCreator.java:121)
> at com.hp.mwtests.ts.jts.recovery.JacORBGenericRecoveryCreatorUnitTest.testSuccess(JacORBGenericRecoveryCreatorUnitTest.java:111)
> 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Emptying /home/hudson/workspace/narayana/TESTS/MAIN/jdk/jdk7.latest/label/linux/ArjunaJTS/jts/target/test-classes/ObjectStore
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore remove_state
> WARN: ARJUNA012284: ShadowingStore::remove_state() - access problems on 0:ffffac118321:8b3f:51d99d99:3 and /Recovery/TransactionStatusManager
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore remove_state
> WARN: ARJUNA012265: ShadowingStore::remove_state() - state 0:ffffac118321:8b3f:51d99d99:3 does not exist for type /Recovery/TransactionStatusManager
> {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
11 years, 2 months
[JBoss JIRA] (JBTM-1825) Error starting XTS Services
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1825?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1825:
---------------------------------
The error happens in the jbossws-common org.jboss.ws.common.deployment.DefaultLifecycleHandler
{code}
public void start(Endpoint ep)
{
EndpointState state = ep.getState();
if (state != EndpointState.UNDEFINED)
{
Loggers.DEPLOYMENT_LOGGER.cannotStartEndpoint(state, ep.getName());
}
...
}
{code}
> 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
11 years, 2 months
[JBoss JIRA] (JBTM-1828) doc build fails due to missing dependencies
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1828?page=com.atlassian.jira.plugin.... ]
Michael Musgrove edited comment on JBTM-1828 at 7/8/13 11:26 AM:
-----------------------------------------------------------------
Adding a repositories section to the pom and specifying the JBoss Release and Thirdparty release repositories (and removing JBoss Release Repository from the distributionManagement section) seems more reliable, as in:
{code}
<repositories>
<repository>
<id>jboss-thirdparty-releases-repository</id>
<name>JBoss Thirdparty Release Repository</name>
<url>https://repository.jboss.org/nexus/content/repositories/thirdparty-releases</url>
</repository>
<repository>
<id>jboss-releases-repository</id>
<name>JBoss Release Repository</name>
<url>https://repository.jboss.org/nexus/content/repositories/releases/</url>
</repository>
</repositories>
{code}
I don't know why we have been using the staging repository so I am reluctant to commit the fix until someone can explain why we might need staging?
was (Author: mmusgrov):
Adding a repositories section to the pom and specifying the JBoss Release and Thirdparty release repositories (and removing JBoss Release Repository from the distributionManagement section) seems more reliable, as in:
<repositories>
<repository>
<id>jboss-thirdparty-releases-repository</id>
<name>JBoss Thirdparty Release Repository</name>
<url>https://repository.jboss.org/nexus/content/repositories/thirdparty-releases</url>
</repository>
<repository>
<id>jboss-releases-repository</id>
<name>JBoss Release Repository</name>
<url>https://repository.jboss.org/nexus/content/repositories/releases/</url>
</repository>
</repositories>
I don't know why we have been using the staging repository so I am reluctant to commit the fix until someone can explain why we might need staging?
> doc build fails due to missing dependencies
> -------------------------------------------
>
> Key: JBTM-1828
> URL: https://issues.jboss.org/browse/JBTM-1828
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 5.0.0.M3
> Reporter: Michael Musgrove
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.M4
>
>
> The build depends on the staging repository for jdocbook dependencies but when this is down the build fails. We should be relying on a more accessible repository. See the workaround on how to manually install the dependencies.
--
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
11 years, 2 months
[JBoss JIRA] (JBTM-1828) doc build fails due to missing dependencies
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1828?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on JBTM-1828:
----------------------------------------
Adding a repositories section to the pom and specifying the JBoss Release and Thirdparty release repositories (and removing JBoss Release Repository from the distributionManagement section) seems more reliable, as in:
<repositories>
<repository>
<id>jboss-thirdparty-releases-repository</id>
<name>JBoss Thirdparty Release Repository</name>
<url>https://repository.jboss.org/nexus/content/repositories/thirdparty-releases</url>
</repository>
<repository>
<id>jboss-releases-repository</id>
<name>JBoss Release Repository</name>
<url>https://repository.jboss.org/nexus/content/repositories/releases/</url>
</repository>
</repositories>
I don't know why we have been using the staging repository so I am reluctant to commit the fix until someone can explain why we might need staging?
> doc build fails due to missing dependencies
> -------------------------------------------
>
> Key: JBTM-1828
> URL: https://issues.jboss.org/browse/JBTM-1828
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 5.0.0.M3
> Reporter: Michael Musgrove
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.M4
>
>
> The build depends on the staging repository for jdocbook dependencies but when this is down the build fails. We should be relying on a more accessible repository. See the workaround on how to manually install the dependencies.
--
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
11 years, 2 months