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: ------------------------------------- I connected to a hung JBTM-1919 job to debug it and add my comments so it was working in that branch > 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

11 years, 2 months

1
0
0 / 0

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

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1809?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-1809. ------------------------------------ Resolution: Done changes pushed to both target branches > 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

11 years, 2 months

1
0
0 / 0

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

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1925?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1925: ------------------------------------- JBTM-1919 job is using my branch. I was waiting to make sure this worked before applying to all our arquillian.xml files. If someone else has time to do this before me, then you can see the change I made by looking at my branch, pulled in by the CI job. > 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

11 years, 2 months

1
0
0 / 0

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

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1809?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1809: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/360, https://github.com/jbosstm/narayana/pull/359, https://github.com/jbosstm/narayana/pull/449, https://github.com/jbosstm/narayana/pull/455 (was: https://github.com/jbosstm/narayana/pull/360, https://github.com/jbosstm/narayana/pull/359, https://github.com/jbosstm/narayana/pull/449) > 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

11 years, 2 months

1
0
0 / 0

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

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1809?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1809: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/360, https://github.com/jbosstm/narayana/pull/359, https://github.com/jbosstm/narayana/pull/449 (was: https://github.com/jbosstm/narayana/pull/360, https://github.com/jbosstm/narayana/pull/359) > 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1482) If a naughty afterCompletion sync throws an exception, log the exception call stack

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1482?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1482: ------------------------------------- The fix was in the original import from svn: https://github.com/jbosstm/narayana/blob/4.17/ArjunaJTA/jta/classes/com/a... > If a naughty afterCompletion sync throws an exception, log the exception call stack > ----------------------------------------------------------------------------------- > > Key: JBTM-1482 > URL: https://issues.jboss.org/browse/JBTM-1482 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Scott Marlow > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 4.17.11, 5.0.0.M5 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Currently, when this happens with AS, I see: > {quote} > 2013-02-18 16:24:43,837|WARN |[com.arjuna.ats.jta]|(ThreadId: Transaction Reaper Worker 221)|ARJUNA016029: SynchronizationImple.afterCompletion - failed for org.jboss.as.jpa.transaction.TransactionUtil$SessionSynchronization@634ef5a7 with exception: java.lang.NullPointerException > {quote} > From a related email conversation: > {quote} > Here's our Logger code: > @Message(id = 16029, value = "SynchronizationImple.afterCompletion - failed for {0} with exception", format = MESSAGE_FORMAT) > @LogMessage(level = WARN) > public void warn_resources_arjunacore_SynchronizationImple(String arg0, @Cause() Throwable arg1); > Here is where we call our logger: > jtaLogger.i18NLogger.warn_resources_arjunacore_SynchronizationImple(_theSynch.toString(), e); > Maybe the message should have the {1} in it, i.e. it change it like so: > "SynchronizationImple.afterCompletion - failed for {0} with exception {1}" > {quote} -- 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-1482) If a naughty afterCompletion sync throws an exception, log the exception call stack

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1482?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1482: -------------------------------- Fix Version/s: 4.17.0 5.0.0.M1 (was: 5.0.0.M5) (was: 4.17.11) > If a naughty afterCompletion sync throws an exception, log the exception call stack > ----------------------------------------------------------------------------------- > > Key: JBTM-1482 > URL: https://issues.jboss.org/browse/JBTM-1482 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Scott Marlow > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M1, 4.17.0 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Currently, when this happens with AS, I see: > {quote} > 2013-02-18 16:24:43,837|WARN |[com.arjuna.ats.jta]|(ThreadId: Transaction Reaper Worker 221)|ARJUNA016029: SynchronizationImple.afterCompletion - failed for org.jboss.as.jpa.transaction.TransactionUtil$SessionSynchronization@634ef5a7 with exception: java.lang.NullPointerException > {quote} > From a related email conversation: > {quote} > Here's our Logger code: > @Message(id = 16029, value = "SynchronizationImple.afterCompletion - failed for {0} with exception", format = MESSAGE_FORMAT) > @LogMessage(level = WARN) > public void warn_resources_arjunacore_SynchronizationImple(String arg0, @Cause() Throwable arg1); > Here is where we call our logger: > jtaLogger.i18NLogger.warn_resources_arjunacore_SynchronizationImple(_theSynch.toString(), e); > Maybe the message should have the {1} in it, i.e. it change it like so: > "SynchronizationImple.afterCompletion - failed for {0} with exception {1}" > {quote} -- 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-1942) Additional trace logging to enable TxProf to obtain record id of XAResourceRecords.

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1942?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1942: ------------------------------------- It is done for 4.17, but I still need to apply the following to master: https://github.com/jbosstm/narayana/commit/dd4f1fb93352570f74b8c391ab92eb... > 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1938) Caching of datasource for JDBC store incompatible with WildFly :reload operation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-1938?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-1938: ----------------------------------------------- tom.jenkinson(a)redhat.com made a comment on [bug 1009931|https://bugzilla.redhat.com/show_bug.cgi?id=1009931] For information: this has the same severity as 1011379, both are fixed in 4.17.11. > Caching of datasource for JDBC store incompatible with WildFly :reload operation > -------------------------------------------------------------------------------- > > Key: JBTM-1938 > URL: https://issues.jboss.org/browse/JBTM-1938 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.11, 5.0.0.M5 > > > The JDBC object store makes a performance optimization to cache the datasource it obtains connections from. Unfortunately this is not compatible with WildFly :reload (see linked bugzilla for stack trace). > Without further performance constraints I have moved to obtaining a reference each time. If there are performance issues we might need to provide a way for the subsystem to invalidate the cached reference when :reload is called. -- 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-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 RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-1941?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-1941: ----------------------------------------------- tom.jenkinson(a)redhat.com made a comment on [bug 1011379|https://bugzilla.redhat.com/show_bug.cgi?id=1011379] For information: this has the same severity as 1009931, both are fixed in 4.17.11. > 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

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