September 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1925) Enable remote debugger in JBossAS/WildFly for all tests

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1925?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1925: ------------------------------------- [~paul.robinson] I think this is resolved? At least, I managed to debug the XTS issue we were having so I presume it is? > Enable remote debugger in JBossAS/WildFly for all tests > ------------------------------------------------------- > > Key: JBTM-1925 > URL: https://issues.jboss.org/browse/JBTM-1925 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 4.17.11, 5.0.0.M5 > > > This allows us to attach to hung AS instances and see what they are doing. > Adding this to narayana.sh should do the trick: > {code} > echo JAVA_OPTS='"$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"' >> ./bin/standalone.conf > {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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1809) At trace logging to facilitate discovery of the transaction hierarchy

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1809?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1809: -------------------------------- Issue Type: Enhancement (was: Feature Request) > At trace logging to facilitate discovery of the transaction hierarchy > --------------------------------------------------------------------- > > Key: JBTM-1809 > URL: https://issues.jboss.org/browse/JBTM-1809 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JTS > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 4.17.11, 5.0.0.M4 > > > In a distributed JTS transaction there is insufficient information in the logs to facilitate the construction of the transaction hierarchy. > For example when a transaction propagates between 3 servers the logs on server 3 do not indicate which of the two other servers has the parent transaction. This feature is required by the [https://community.jboss.org/wiki/TransactionMonitoringAndVisualization] tool. > A possible solution is to print out the TM node identifier and the CORBA request id in the CORBA Client and Server Request Interceptors (in methods send_request and receive_request_service_contexts respectively). -- 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

12 years, 10 months

1
0
0 / 0

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

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1917?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1917: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/466 > 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.M5 > > > 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1936) Cannot start managed container after JMX upgrade

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1936?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1936: ---------------------------------- Status: Closed (was: Pull Request Sent) Resolution: Done > Cannot start managed container after JMX upgrade > ------------------------------------------------ > > Key: JBTM-1936 > URL: https://issues.jboss.org/browse/JBTM-1936 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.0.0.M5 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/TESTS=MAIN,jdk=jd... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/264/TESTS=XTS,jdk... > Based on [~paul.robinson] research, this was caused by https://github.com/wildfly/wildfly/commit/c400b512be5fae6c02ef0a11886ac77... -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1809) At trace logging to facilitate discovery of the transaction hierarchy

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1809?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1809: ------------------------------------- Did this get resolved? I saw some commits on the 4.17 branch > At trace logging to facilitate discovery of the transaction hierarchy > --------------------------------------------------------------------- > > Key: JBTM-1809 > URL: https://issues.jboss.org/browse/JBTM-1809 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTS > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 4.17.11, 5.0.0.M4 > > > In a distributed JTS transaction there is insufficient information in the logs to facilitate the construction of the transaction hierarchy. > For example when a transaction propagates between 3 servers the logs on server 3 do not indicate which of the two other servers has the parent transaction. This feature is required by the [https://community.jboss.org/wiki/TransactionMonitoringAndVisualization] tool. > A possible solution is to print out the TM node identifier and the CORBA request id in the CORBA Client and Server Request Interceptors (in methods send_request and receive_request_service_contexts respectively). -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1942) Additional trace logging to enable TxProf to obtain record id of XAResourceRecords.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1942?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1942: ------------------------------------- Is this issues resolved now? /cc [~paul.robinson] > Additional trace logging to enable TxProf to obtain record id of XAResourceRecords. > ----------------------------------------------------------------------------------- > > Key: JBTM-1942 > URL: https://issues.jboss.org/browse/JBTM-1942 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Alex Creasy > Assignee: Alex Creasy > Fix For: 4.17.11, 5.0.0.M5 > > > Additional logging added in JBTM-1915 can only be utilised by TxProf for JTS transactions. This is because TxProf identifies resources in JTS transactions by their record uid, whereas in JTA transactions they are identified by the resource manager's JNDI name. Affixing the record UID to trace logging statements in XAResourceRecord will enable TxProf to provide the enhanced data for both JTA and JTS transactions -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1915) Enhancement to logging to output the status of prepare, commit and abort for each resource after they complete and the result of the transaction

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1915?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1915: -------------------------------- Fix Version/s: 4.17.11 > Enhancement to logging to output the status of prepare, commit and abort for each resource after they complete and the result of the transaction > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-1915 > URL: https://issues.jboss.org/browse/JBTM-1915 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Alex Creasy > Assignee: Alex Creasy > Fix For: 4.17.11, 5.0.0.M5 > > > Presently the transaction manager only outputs logging when beginning to prepare, commit or abort. Additional logging that shows the result of each resource asked to prepare / commit / abort and the result of the transaction is necessary for the txprof tool to diagnose common transactional problems. The proposal is to add an additional line of trace logging to the End, doPrepare, doCommit and doAbort methods in BasicAction.java. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1809) At trace logging to facilitate discovery of the transaction hierarchy

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1809?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1809: -------------------------------- Fix Version/s: 4.17.11 > At trace logging to facilitate discovery of the transaction hierarchy > --------------------------------------------------------------------- > > Key: JBTM-1809 > URL: https://issues.jboss.org/browse/JBTM-1809 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTS > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 4.17.11, 5.0.0.M4 > > > In a distributed JTS transaction there is insufficient information in the logs to facilitate the construction of the transaction hierarchy. > For example when a transaction propagates between 3 servers the logs on server 3 do not indicate which of the two other servers has the parent transaction. This feature is required by the [https://community.jboss.org/wiki/TransactionMonitoringAndVisualization] tool. > A possible solution is to print out the TM node identifier and the CORBA request id in the CORBA Client and Server Request Interceptors (in methods send_request and receive_request_service_contexts respectively). -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1942) Additional trace logging to enable TxProf to obtain record id of XAResourceRecords.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1942?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1942: -------------------------------- Fix Version/s: 4.17.11 5.0.0.M5 > Additional trace logging to enable TxProf to obtain record id of XAResourceRecords. > ----------------------------------------------------------------------------------- > > Key: JBTM-1942 > URL: https://issues.jboss.org/browse/JBTM-1942 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Alex Creasy > Assignee: Alex Creasy > Fix For: 4.17.11, 5.0.0.M5 > > > Additional logging added in JBTM-1915 can only be utilised by TxProf for JTS transactions. This is because TxProf identifies resources in JTS transactions by their record uid, whereas in JTA transactions they are identified by the resource manager's JNDI name. Affixing the record UID to trace logging statements in XAResourceRecord will enable TxProf to provide the enhanced data for both JTA and JTS transactions -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1941) When an orb is recreated the JacOrbRCServiceInit class uses a cached poa rather than a new poa linked to the new orb reference

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1941?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1941: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > When an orb is recreated the JacOrbRCServiceInit class uses a cached poa rather than a new poa linked to the new orb reference > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-1941 > URL: https://issues.jboss.org/browse/JBTM-1941 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.11, 5.0.0.M5 > > > See the upstream BZ for more details. Effectively you can't start/stop/start the JacOrbRCServiceInit within WildFly. > There are a couple of tweaks needed to achieve this. I will link a pull request but I will add some comments and delete this comment when I have the pull request finalized. -- 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

12 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2013