September 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1871) Automatically add the "org.jboss.xts" dependency for XTS applications

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1871?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1871: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/430, https://github.com/jbosstm/jboss-as/pull/23 > Automatically add the "org.jboss.xts" dependency for XTS applications > --------------------------------------------------------------------- > > Key: JBTM-1871 > URL: https://issues.jboss.org/browse/JBTM-1871 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: TxBridge, TXFramework, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M5 > > > At deployment time we should automatically add the org.jboss.xts dependency for applications that need it. > We should be able to detect deployments that use XTS annotations (i.e those provided by the Compensations API) through Jandex. I'm not sure how we would detect those that don't use annotations; something to investigate. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1561) Do not force the definition of services in the blacktie-admin-services

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1561?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1561: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.0.0.M5 (was: 6.0.0.Final) Resolution: Done Thanks for the contribution :) > Do not force the definition of services in the blacktie-admin-services > ---------------------------------------------------------------------- > > Key: JBTM-1561 > URL: https://issues.jboss.org/browse/JBTM-1561 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M1 > Reporter: Michael Musgrove > Assignee: Crispin Boylan > Fix For: 5.0.0.M5 > > > It is inconvenient to have to specify the list of services in the blacktie-admin-services. Although it is still necessary to configure the queue security on the hornetq server itself if the defaults are not acceptable, in the common case of acceptable default queue/topic permissions it would be best to not have to update the btconfig.xml in the admin service to allow new servers/services to be added easily. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1561) Do not force the definition of services in the blacktie-admin-services

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1561?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1561: -------------------------------- Assignee: Crispin Boylan (was: Amos Feng) > Do not force the definition of services in the blacktie-admin-services > ---------------------------------------------------------------------- > > Key: JBTM-1561 > URL: https://issues.jboss.org/browse/JBTM-1561 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M1 > Reporter: Michael Musgrove > Assignee: Crispin Boylan > Fix For: 6.0.0.Final > > > It is inconvenient to have to specify the list of services in the blacktie-admin-services. Although it is still necessary to configure the queue security on the hornetq server itself if the defaults are not acceptable, in the common case of acceptable default queue/topic permissions it would be best to not have to update the btconfig.xml in the admin service to allow new servers/services to be added easily. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1561) Do not force the definition of services in the blacktie-admin-services

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1561?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1561: -------------------------------- Summary: Do not force the definition of services in the blacktie-admin-services (was: Cannot create a user defined XATMI service) Description: It is inconvenient to have to specify the list of services in the blacktie-admin-services. Although it is still necessary to configure the queue security on the hornetq server itself if the defaults are not acceptable, in the common case of acceptable default queue/topic permissions it would be best to not have to update the btconfig.xml in the admin service to allow new servers/services to be added easily. (was: The administrative interface, btadmin, does not support the definition of user defined services. Perhaps this functionality was present in the old RHQ interface and was not ported to btadmin when RHQ support was dropped. The documentation set does not describe how to configure user defined services.) > Do not force the definition of services in the blacktie-admin-services > ---------------------------------------------------------------------- > > Key: JBTM-1561 > URL: https://issues.jboss.org/browse/JBTM-1561 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M1 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 6.0.0.Final > > > It is inconvenient to have to specify the list of services in the blacktie-admin-services. Although it is still necessary to configure the queue security on the hornetq server itself if the defaults are not acceptable, in the common case of acceptable default queue/topic permissions it would be best to not have to update the btconfig.xml in the admin service to allow new servers/services to be added easily. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1721) REST-AT participant support framework should support synchronizations

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1721?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1721: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > REST-AT participant support framework should support synchronizations > --------------------------------------------------------------------- > > Key: JBTM-1721 > URL: https://issues.jboss.org/browse/JBTM-1721 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: REST > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.0.0.M5 > > > JBTM-1365 introduced an interface for simplifying participant registration into a REST-AT transaction by providing a callback for prepare/commit/rollback support. Please can we also have a similar mechanism for synchronizations. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1721) REST-AT participant support framework should support synchronizations

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1721?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed JBTM-1721. --------------------------------- > REST-AT participant support framework should support synchronizations > --------------------------------------------------------------------- > > Key: JBTM-1721 > URL: https://issues.jboss.org/browse/JBTM-1721 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: REST > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.0.0.M5 > > > JBTM-1365 introduced an interface for simplifying participant registration into a REST-AT transaction by providing a callback for prepare/commit/rollback support. Please can we also have a similar mechanism for synchronizations. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1561) Cannot create a user defined XATMI service

by Crispin Boylan (JIRA)

[ https://issues.jboss.org/browse/JBTM-1561?page=com.atlassian.jira.plugin.... ] Crispin Boylan commented on JBTM-1561: -------------------------------------- Can close now. > Cannot create a user defined XATMI service > ------------------------------------------ > > Key: JBTM-1561 > URL: https://issues.jboss.org/browse/JBTM-1561 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M1 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 6.0.0.Final > > > The administrative interface, btadmin, does not support the definition of user defined services. Perhaps this functionality was present in the old RHQ interface and was not ported to btadmin when RHQ support was dropped. > The documentation set does not describe how to configure user defined services. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1914) Connection failed in Blacktie quickstart

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1914?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1914: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Connection failed in Blacktie quickstart > ---------------------------------------- > > Key: JBTM-1914 > URL: https://issues.jboss.org/browse/JBTM-1914 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Demonstrator > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.M5 > > > http://172.17.131.2/job/narayana-quickstarts-windows2008-taconic/448/cons... > {code} > [exec] 19:27:56,677 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Beta1-SNAPSHOT "WildFly" started in 19136ms - Started 427 of 462 services (84 services are lazy, passive or on-demand) > [exec] Buildfile: C:\hudson\workspace\narayana-quickstarts-windows2008-taconic\blacktie\test\initializeBlackTie.xml > [exec] > [exec] tweak-txfooapp-for-environment: > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 0 seconds > [exec] calling generated setenv - error 0 > [exec] "Running all quickstarts" > [exec] "Quickstart: Running XATMI admin quickstart" > [exec] [cc] cl : Command line warning D9035 : option 'GZ' has been deprecated and will be removed in a future release > [exec] [cc] cl : Command line warning D9036 : use 'RTC1' instead of 'GZ' > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] Checking for host: WIN-5GKPEREVUOO or ip: 172.17.131.21 > [exec] 2013-09-09 19:28:04,224 [0x00001384] ERROR (HybridConnectionImpl :108 ) - Connection failed: WIN-5GKPEREVUOO, 61613 > [exec] > [exec] 2013-09-09 19:28:04,224 [0x00001384] ERROR (HybridConnectionImpl :111 ) - APR Error was: 730061: No connection could be made because the target machine actively refused it. > [exec] > [exec] 2013-09-09 19:28:04,224 [0x00001384] ERROR (HybridSocketSessionImpl :445 ) - Could not send frame > [exec] > [exec] 2013-09-09 19:28:04,224 [0x00001384] ERROR (HybridSocketSessionImpl :449 ) - APR Error was: 20011: No socket was provided and one was required. > [exec] > [exec] 2013-09-09 19:28:04,224 [0x00001384] ERROR (AtmiBrokerServer :1095) - Could not advertise service with command: tpadvertise,fooapp,.fooapp1,5.0.0.M5-SNAPSHOT, > [exec] > [exec] 2013-09-09 19:28:04,240 [0x00001384] FATAL (AtmiBrokerServer :437 ) - advertise admin service failed > [exec] > [exec] 2013-09-09 19:28:04,256 [0x00001384] FATAL (AtmiBrokerServer :218 ) - serverinit failed > [exec] "Could not start server" > {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

1
0
0 / 0

[JBoss JIRA] (JBTM-1914) Connection failed in Blacktie quickstart

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1914?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1914: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/92 > Connection failed in Blacktie quickstart > ---------------------------------------- > > Key: JBTM-1914 > URL: https://issues.jboss.org/browse/JBTM-1914 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Demonstrator > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.M5 > > > http://172.17.131.2/job/narayana-quickstarts-windows2008-taconic/448/cons... > {code} > [exec] 19:27:56,677 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Beta1-SNAPSHOT "WildFly" started in 19136ms - Started 427 of 462 services (84 services are lazy, passive or on-demand) > [exec] Buildfile: C:\hudson\workspace\narayana-quickstarts-windows2008-taconic\blacktie\test\initializeBlackTie.xml > [exec] > [exec] tweak-txfooapp-for-environment: > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 0 seconds > [exec] calling generated setenv - error 0 > [exec] "Running all quickstarts" > [exec] "Quickstart: Running XATMI admin quickstart" > [exec] [cc] cl : Command line warning D9035 : option 'GZ' has been deprecated and will be removed in a future release > [exec] [cc] cl : Command line warning D9036 : use 'RTC1' instead of 'GZ' > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] Checking for host: WIN-5GKPEREVUOO or ip: 172.17.131.21 > [exec] 2013-09-09 19:28:04,224 [0x00001384] ERROR (HybridConnectionImpl :108 ) - Connection failed: WIN-5GKPEREVUOO, 61613 > [exec] > [exec] 2013-09-09 19:28:04,224 [0x00001384] ERROR (HybridConnectionImpl :111 ) - APR Error was: 730061: No connection could be made because the target machine actively refused it. > [exec] > [exec] 2013-09-09 19:28:04,224 [0x00001384] ERROR (HybridSocketSessionImpl :445 ) - Could not send frame > [exec] > [exec] 2013-09-09 19:28:04,224 [0x00001384] ERROR (HybridSocketSessionImpl :449 ) - APR Error was: 20011: No socket was provided and one was required. > [exec] > [exec] 2013-09-09 19:28:04,224 [0x00001384] ERROR (AtmiBrokerServer :1095) - Could not advertise service with command: tpadvertise,fooapp,.fooapp1,5.0.0.M5-SNAPSHOT, > [exec] > [exec] 2013-09-09 19:28:04,240 [0x00001384] FATAL (AtmiBrokerServer :437 ) - advertise admin service failed > [exec] > [exec] 2013-09-09 19:28:04,256 [0x00001384] FATAL (AtmiBrokerServer :218 ) - serverinit failed > [exec] "Could not start server" > {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

1
0
0 / 0

[JBoss JIRA] (JBTM-1917) XTS*RecoveryManager.getRecoveryManager() can return null if application deployed before XTS starts

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1917: ----------------------------------- Summary: XTS*RecoveryManager.getRecoveryManager() can return null if application deployed before XTS starts Key: JBTM-1917 URL: https://issues.jboss.org/browse/JBTM-1917 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: XTS Reporter: Paul Robinson Assignee: Gytis Trikleris Priority: Minor Fix For: 5.0.0.Final The problem is that there is currently no way of specifying that an application depends on XTS. Therefore it's possible that when the server starts, that the application can be deployed before XTS is started, thus a call to XTSBARecoveryManager.getRecoveryManager() or XTSATRecoveryManager.getRecoveryManager() will return null. The workaround is to poll for the RecoveryManager until it is not null. The fix is to have the RecoveryManager injected into the application via a Deployment Unit Processor that has a dependency on the XTS service. -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2013