April 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS subsystem and module

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?page=com.atlassian.jira.plugin.... ] Work on JBTM-1365 started by Gytis Trikleris. > Deploy REST-AT support as a JBossAS subsystem and module > -------------------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Original Estimate: 3 weeks > Time Spent: 2 days, 4 hours > Remaining Estimate: 2 weeks, 2 days, 4 hours > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. > h3. Open Issues > Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1405) idlj issue when building on Raspberry Pi

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1405?page=com.atlassian.jira.plugin.... ] Gytis Trikleris resolved JBTM-1405. ----------------------------------- Resolution: Done > idlj issue when building on Raspberry Pi > ---------------------------------------- > > Key: JBTM-1405 > URL: https://issues.jboss.org/browse/JBTM-1405 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS > Affects Versions: 4.17.3 > Environment: Raspberry Pi with stock distribution installed and openjdk 6. > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Early in the build we get ... > [INFO] Processing 3 grammar files to /home/pi/narayana/ArjunaJTS/idl/idlj/target/generated-sources/idl > [INFO] [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl > #include <orb.idl> > ^ > [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl > #include <orb.idl> > ^ > [INFO] [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl > #include <orb.idl> > ^ > [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl > #include <orb.idl> > ^ > [INFO] [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl > #include <orb.idl> > ^ > [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl > #include <orb.idl> > ^ > And eventually this results in ... > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 4:03:24.556s > [INFO] Finished at: Sat Dec 22 20:32:47 UTC 2012 > [INFO] Final Memory: 38M/105M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.9:test (surefire-idlj) on project jts: Execution surefire-idlj of goal org.apache.maven.plugins:maven-surefire-plugin:2.9:test failed: java.lang.reflect.InvocationTargetException; nested exception is java.lang.reflect.InvocationTargetException: null: org/omg/CosTransactions/ResourceOperations: org.omg.CosTransactions.ResourceOperations -> [Help 1] > It would also be good if there was a build-time switch to disable using idlj. Building with the idlj option at the start (as mentioned in the README) would imply that this is the way to go and that building just using jts therefore only uses jacorb, but it seems that the jts rule builds with both orbs. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1479) Create a quickstart to show how to use IronJacamar and JBTM inside tomcat

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1479?focusedWorklogId=12429103&page=... ] Gytis Trikleris logged work on JBTM-1479: ----------------------------------------- Author: Gytis Trikleris Created on: 22/Apr/13 8:27 AM Start Date: 22/Apr/13 8:27 AM Worklog Time Spent: 1 hour, 20 minutes Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 30 minutes) Time Spent: 1 week, 1 day, 3 hours, 20 minutes (was: 1 week, 1 day, 2 hours) Worklog Id: (was: 12429103) > Create a quickstart to show how to use IronJacamar and JBTM inside tomcat > ------------------------------------------------------------------------- > > Key: JBTM-1479 > URL: https://issues.jboss.org/browse/JBTM-1479 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Attachments: test-ds.xml, transaction.xml > > Original Estimate: 3 days > Time Spent: 1 week, 1 day, 3 hours, 20 minutes > Remaining Estimate: 0 minutes > > See JBTM-809 for the algorithm > You might want to put the startup in the context listener: > public class MyServletContextListener implements ServletContextListener { > public void contextInitialized(ServletContextEvent sce) { > // Initialize RecoveryManager > // Initialize TransactionManager > // Initialize IronJacamar > } > > @Override > public void contextDestroyed(ServletContextEvent sce) { > // Clean IronJacamar > // Clean TransactionManager > // Clean RecoveryManager > } > } > Quickstart application should connect to the database (say PostgreSQL), dummy XA resource and coordinate the transaction. The PostgreSQL data source needs to be accessed via IronJacamar. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1479) Create a quickstart to show how to use IronJacamar and JBTM inside tomcat

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1479?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1479: ---------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/jbosstm/quickstart/pull/74 > Create a quickstart to show how to use IronJacamar and JBTM inside tomcat > ------------------------------------------------------------------------- > > Key: JBTM-1479 > URL: https://issues.jboss.org/browse/JBTM-1479 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Attachments: test-ds.xml, transaction.xml > > Original Estimate: 3 days > Time Spent: 1 week, 1 day, 2 hours > Remaining Estimate: 30 minutes > > See JBTM-809 for the algorithm > You might want to put the startup in the context listener: > public class MyServletContextListener implements ServletContextListener { > public void contextInitialized(ServletContextEvent sce) { > // Initialize RecoveryManager > // Initialize TransactionManager > // Initialize IronJacamar > } > > @Override > public void contextDestroyed(ServletContextEvent sce) { > // Clean IronJacamar > // Clean TransactionManager > // Clean RecoveryManager > } > } > Quickstart application should connect to the database (say PostgreSQL), dummy XA resource and coordinate the transaction. The PostgreSQL data source needs to be accessed via IronJacamar. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1526) Add a EAP profile that contains the components required by EAP

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1526?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1526: -------------------------------- Fix Version/s: 4.17.5 (was: 4.17.4) > Add a EAP profile that contains the components required by EAP > -------------------------------------------------------------- > > Key: JBTM-1526 > URL: https://issues.jboss.org/browse/JBTM-1526 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.3 > Reporter: Weinan Li > Assignee: Tom Jenkinson > Fix For: 4.17.5, 5.0.0.Final > > > Currently narayana has too many dependencies that is disallowed in EAP repo. We could create a profile for EAP6 that just have the necessary modules. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1501) Create a Hudson job to build AS 7.2.0 branch

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1501?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1501: -------------------------------- Fix Version/s: 4.17.5 (was: 4.17.4) > Create a Hudson job to build AS 7.2.0 branch > -------------------------------------------- > > Key: JBTM-1501 > URL: https://issues.jboss.org/browse/JBTM-1501 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Fix For: 4.17.5 > > > Similar to the AS800 job. > We (incl hudson) need access to the private AS720 branch first. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1487) TXBridge 4.17 branch quickstart has 5.0.0.M2-SNAPSHOT dependencies

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1487?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1487: -------------------------------- Fix Version/s: 4.17.5 (was: 4.17.4) > TXBridge 4.17 branch quickstart has 5.0.0.M2-SNAPSHOT dependencies > ------------------------------------------------------------------ > > Key: JBTM-1487 > URL: https://issues.jboss.org/browse/JBTM-1487 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator, TxBridge, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 4.17.5 > > Original Estimate: 1 hour > Time Spent: 10 minutes > Remaining Estimate: 0 minutes > > See: > https://github.com/jbosstm/quickstart/blob/4.17/TXBridge/wsat-jta-multi_h... > Check for others. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1216) XTS Rec test fail with NPE when start service jboss.ws.endpoint-publish.ws-t11-client during booting the jboss-as

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1216?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1216: -------------------------------- Fix Version/s: 4.17.5 (was: 4.17.4) > XTS Rec test fail with NPE when start service jboss.ws.endpoint-publish.ws-t11-client during booting the jboss-as > ------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-1216 > URL: https://issues.jboss.org/browse/JBTM-1216 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Amos Feng > Assignee: Paul Robinson > Priority: Trivial > Labels: assign > Fix For: 4.17.5, 5.0.0.Final > > Original Estimate: 1 hour > Time Spent: 5 minutes > Remaining Estimate: 1 day > > see http://172.17.131.2/job/narayana-java6/1285/artifact/XTS/localjunit/crash... > {code} > 13:26:49,610 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.ws.endpoint-publish.ws-t11-client: org.jboss.msc.service.StartException in service jboss.ws.endpoint-publish.ws-t11-client: javax.xml.ws.WebServiceException: java.lang.NullPointerException > at org.jboss.as.webservices.service.EndpointPublishService.start(EndpointPublishService.java:95) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26] > Caused by: javax.xml.ws.WebServiceException: java.lang.NullPointerException > at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:357) > at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:70) > at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:246) > at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:525) > at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:119) > at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:129) > at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:68) > at org.jboss.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:134) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:112) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:95) > at org.jboss.as.webservices.service.EndpointPublishService.start(EndpointPublishService.java:93) > ... 5 more > Caused by: java.lang.NullPointerException > at org.apache.cxf.common.jaxb.JAXBUtils.generateJaxbSchemas(JAXBUtils.java:765) > at org.apache.cxf.jaxb.JAXBDataBinding.generateJaxbSchemas(JAXBDataBinding.java:431) > at org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:354) > at org.apache.cxf.service.factory.AbstractServiceFactoryBean.initializeDataBindings(AbstractServiceFactoryBean.java:86) > at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:474) > at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFromClass(JaxWsServiceFactoryBean.java:685) > at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:536) > at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:248) > at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:205) > at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:101) > at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:159) > at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:207) > at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:442) > at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:329) > ... 15 more > {code} > and the service failed > {code} > 13:26:57,492 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014777: Services which failed to start: service jboss.ws.endpoint-publish.ws-t11-client: org.jboss.msc.service.StartException in service jboss.ws.endpoint-publish.ws-t11-client: javax.xml.ws.WebServiceException: java.lang.NullPointerException > {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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1633) Add a check before http://172.17.131.2/view/Narayana+BlackTie-pulls/job/btny-pulls-* to make sure pull request is open

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1633?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1633: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 4.17.5 Resolution: Done > Add a check before http://172.17.131.2/view/Narayana+BlackTie-pulls/job/btny-pulls-* to make sure pull request is open > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1633 > URL: https://issues.jboss.org/browse/JBTM-1633 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.5, 5.0.0.M3 > > > Use the rest api, no need to run if the pull has been merged -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1556) provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1556?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1556: -------------------------------- Fix Version/s: 4.17.5 (was: 4.17.4) > provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling > ---------------------------------------------------------------------------------------------- > > Key: JBTM-1556 > URL: https://issues.jboss.org/browse/JBTM-1556 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.17.3 > Reporter: Scott Marlow > Assignee: Tom Jenkinson > Fix For: 4.17.5, 5.0.0.M3 > > > When the Synchronization.afterCompletion is invoked for EE JPA containers, knowledge of whether the current thread is the Reaper thread (cancelling the transaction from a background thread). > The fix to this jira will help with handling the [JPA 2.1 container concurrency requirements|http://java.net/projects/jpa-spec/lists/jsr338-experts/archi...]. > Please implement the solution makes the most sense to you, as this will introduce an additional dependency between other systems and JBossTM/JBossTS that depend on the solution, that will likely be around for a long time. -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues April 2013