[JBoss JIRA] (JBTM-1475) TXBridge InboundCrashRecoveryTests failure - could not start container
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1475?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1475:
-------------------------------------
I don't see how it could be related, but this appears in the log:
{code}
[0m[31m04:13:40,182 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."restat-web-5.0.0.M2-SNAPSHOT.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."restat-web-5.0.0.M2-SNAPSHOT.war".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "restat-web-5.0.0.M2-SNAPSHOT.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
Caused by: java.lang.NullPointerException
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1412) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceControllerImpl.access$2700(ServiceControllerImpl.java:49) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1954) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceControllerImpl.commitInstallation(ServiceControllerImpl.java:255) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:564) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.as.ee.beanvalidation.BeanValidationFactoryDeployer.bindServices(BeanValidationFactoryDeployer.java:100)
at org.jboss.as.ee.beanvalidation.BeanValidationFactoryDeployer.bindFactoryToJndi(BeanValidationFactoryDeployer.java:78)
at org.jboss.as.ee.beanvalidation.BeanValidationFactoryDeployer.deploy(BeanValidationFactoryDeployer.java:64)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
{code}
> TXBridge InboundCrashRecoveryTests failure - could not start container
> ----------------------------------------------------------------------
>
> Key: JBTM-1475
> URL: https://issues.jboss.org/browse/JBTM-1475
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: TxBridge
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.M2
>
>
> See: http://172.17.131.2/job/narayana-dualstack/83
> {noformat}
> Tests in error:
> testCrashOneLog(org.jboss.jbossts.txbridge.tests.inbound.junit.InboundCrashRecoveryTests): Could not start container
> testCrashOneLog(org.jboss.jbossts.txbridge.tests.inbound.junit.InboundCrashRecoveryTests): Deployment with name txbridge-inbound-tests-client could not be undeployed. Container jboss must be still running.
> {noformat}
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1143) Narayana with Maven Central
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1143?focusedWorklogId=12428706&page=... ]
Paul Robinson logged work on JBTM-1143:
---------------------------------------
Author: Paul Robinson
Created on: 18/Feb/13 10:25 AM
Start Date: 18/Feb/13 10:24 AM
Worklog Time Spent: 4 hours
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 4 hours)
Time Spent: 4 hours
Worklog Id: (was: 12428706)
> Narayana with Maven Central
> ---------------------------
>
> Key: JBTM-1143
> URL: https://issues.jboss.org/browse/JBTM-1143
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 4 hours
> Time Spent: 4 hours
> Remaining Estimate: 0 minutes
>
> Try syncing from M1 onwards, so that it will be synced immediately after M2 is released.
> We should also take a look at what things we depend on that are not in maven central. I said that I would take steps to reduce the number of these.
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1143) Narayana with Maven Central
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1143?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1143:
-------------------------------------
I've checked 4.17.3.Final and it seems that all the things we depend on are now in maven central.
I don't think we can sync 5.0.0.M1 as there where some dependency issues fixed as part of M2. I can look into this further, but I'm not sure it would be worth the effort.
I've sent an email off to Joel Orlina to ask him to sync 5.0.0.M2 onwards.
> Narayana with Maven Central
> ---------------------------
>
> Key: JBTM-1143
> URL: https://issues.jboss.org/browse/JBTM-1143
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Try syncing from M1 onwards, so that it will be synced immediately after M2 is released.
> We should also take a look at what things we depend on that are not in maven central. I said that I would take steps to reduce the number of these.
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1475) TXBridge InboundCrashRecoveryTests failure - could not start container
by Gytis Trikleris (JIRA)
Gytis Trikleris created JBTM-1475:
-------------------------------------
Summary: TXBridge InboundCrashRecoveryTests failure - could not start container
Key: JBTM-1475
URL: https://issues.jboss.org/browse/JBTM-1475
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: TxBridge
Reporter: Gytis Trikleris
Assignee: Paul Robinson
Priority: Minor
Fix For: 5.0.0.M2
See: http://172.17.131.2/job/narayana-dualstack/83
{noformat}
Tests in error:
testCrashOneLog(org.jboss.jbossts.txbridge.tests.inbound.junit.InboundCrashRecoveryTests): Could not start container
testCrashOneLog(org.jboss.jbossts.txbridge.tests.inbound.junit.InboundCrashRecoveryTests): Deployment with name txbridge-inbound-tests-client could not be undeployed. Container jboss must be still running.
{noformat}
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-986) Automatically setup the client side handler chain
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-986?focusedWorklogId=12428705&page=c... ]
Gytis Trikleris logged work on JBTM-986:
----------------------------------------
Author: Gytis Trikleris
Created on: 18/Feb/13 7:15 AM
Start Date: 17/Feb/13 3:15 PM
Worklog Time Spent: 4 hours
Issue Time Tracking
-------------------
Remaining Estimate: 1 day (was: 4 hours)
Time Spent: 1 week, 1 day, 6 hours (was: 1 week, 1 day, 2 hours)
Worklog Id: (was: 12428705)
> Automatically setup the client side handler chain
> -------------------------------------------------
>
> Key: JBTM-986
> URL: https://issues.jboss.org/browse/JBTM-986
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> Labels: assign
> Fix For: 5.0.0.M2
>
> Original Estimate: 4 days
> Time Spent: 1 week, 1 day, 6 hours
> Remaining Estimate: 1 day
>
> When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows:
> {code}
> BindingProvider bindingProvider = (BindingProvider) client;
> List<Handler> handlers = new ArrayList<Handler>(1);
> handlers.add(new JaxWSHeaderContextProcessor());
> bindingProvider.getBinding().setHandlerChain(handlers);
> {code}
> This is not very user friendly.
> This could be done using a JAX-WS feature passed to the Client-side port.
> We also need to support client stubs created using @WebServiceRef. Here's some examples of its use:
> http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s...
> http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s...
> http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s...
> The feature should be "enabled" by default providing the feature is enabled in the XTS server config.
> The quickstarts also need updated to use this.
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1446) Prepare Quickstarts for Release
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1446?focusedWorklogId=12428704&page=... ]
Paul Robinson logged work on JBTM-1446:
---------------------------------------
Author: Paul Robinson
Created on: 18/Feb/13 5:52 AM
Start Date: 18/Feb/13 5:52 AM
Worklog Time Spent: 5 minutes
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 4 hours)
Time Spent: 5 minutes
Worklog Id: (was: 12428704)
> Prepare Quickstarts for Release
> -------------------------------
>
> Key: JBTM-1446
> URL: https://issues.jboss.org/browse/JBTM-1446
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Demonstrator
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 4 hours
> Time Spent: 5 minutes
> Remaining Estimate: 0 minutes
>
> * The tag should reference the latest release, rather than a snapshot
> * General check over looking for things that won't work with a tagged/released AS7+Narayana.
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1446) Prepare Quickstarts for Release
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1446?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1446:
--------------------------------
Description:
* The tag should reference the latest release, rather than a snapshot
* General check over looking for things that won't work with a tagged/released AS7+Narayana.
was:
* The tag should reference the latest release, rather than a snapshot
* Check the TXFramework/readme.md to make sure it is current and to remove the link to the old pre-built AS7+TS.
* General check over looking for things that won't work with a tagged/released AS7+Narayana.
> Prepare Quickstarts for Release
> -------------------------------
>
> Key: JBTM-1446
> URL: https://issues.jboss.org/browse/JBTM-1446
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Demonstrator
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> * The tag should reference the latest release, rather than a snapshot
> * General check over looking for things that won't work with a tagged/released AS7+Narayana.
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1471) Apply 'TXFramework Repositioning' to the Quickstarts
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1471?focusedWorklogId=12428703&page=... ]
Paul Robinson logged work on JBTM-1471:
---------------------------------------
Author: Paul Robinson
Created on: 18/Feb/13 5:17 AM
Start Date: 18/Feb/13 5:17 AM
Worklog Time Spent: 2 hours
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 6 hours)
Time Spent: 1 day (was: 6 hours)
Worklog Id: (was: 12428703)
> Apply 'TXFramework Repositioning' to the Quickstarts
> ----------------------------------------------------
>
> Key: JBTM-1471
> URL: https://issues.jboss.org/browse/JBTM-1471
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Demonstrator, TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 1 day, 4 hours
> Time Spent: 1 day
> Remaining Estimate: 0 minutes
>
> * Move quickstarts into XTS, REST or TXBridge. [DONE]
> * Move quickstarts that use old APIs into a legacy folder. [Done for XTS, do REST-TX when we apply API changes]
> * Update the docs to simplify and remove TXFramework description. [DONE]
> * Add entry-point readmes [Done for XTS, do REST-TX when we apply API changes]
> * Jira tasks to upgrade legacy quickstarts [DONE]
> * Update pom descriptions to remove txf [DONE]
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1471) Apply 'TXFramework Repositioning' to the Quickstarts
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1471?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1471:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstm/quickstart/pull/64
> Apply 'TXFramework Repositioning' to the Quickstarts
> ----------------------------------------------------
>
> Key: JBTM-1471
> URL: https://issues.jboss.org/browse/JBTM-1471
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Demonstrator, TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 1 day, 4 hours
> Time Spent: 6 hours
> Remaining Estimate: 6 hours
>
> * Move quickstarts into XTS, REST or TXBridge. [DONE]
> * Move quickstarts that use old APIs into a legacy folder. [Done for XTS, do REST-TX when we apply API changes]
> * Update the docs to simplify and remove TXFramework description. [DONE]
> * Add entry-point readmes [Done for XTS, do REST-TX when we apply API changes]
> * Jira tasks to upgrade legacy quickstarts [DONE]
> * Update pom descriptions to remove txf [DONE]
--
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
13 years, 1 month