August 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2236) Remove / from ConfigurationInfo

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2236?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2236: ------------------------------------- Hi Mark, All the tests pass with that, I am happy to merge it if you like? Tom > Remove / from ConfigurationInfo > ------------------------------- > > Key: JBTM-2236 > URL: https://issues.jboss.org/browse/JBTM-2236 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Common > Affects Versions: 5.0.2 > Reporter: Mark Little > Assignee: Tom Jenkinson > > I've been working on compiling Java using the Avian project (http://oss.readytalk.com/avian/) and have eventually had success in running some of our hammer tests. However, there was a blocker which was to do with the way in which we locate the property file within the jar using the manifest. We can argue as to whether the issue resides within Avian or the way in which we do things, but the solution was to simply remove the / from: > int suffixLength = ("/"+ConfigurationInfo.class.getCanonicalName()+".class").length(); > Rebuilding and rerunning the tests made everything work. > I don't want to check in this change until I am sure that it is right, so would appreciate someone looking at it and at least running all of the QE tests to be sure nothing else breaks. > I've included a reference to the Avian forum article where I discussed this with their team. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2237) Ensure that narayana-jts-idlj is uploaded to nexus as part of the release

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2237: ----------------------------------- Summary: Ensure that narayana-jts-idlj is uploaded to nexus as part of the release Key: JBTM-2237 URL: https://issues.jboss.org/browse/JBTM-2237 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.3 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2231) Detailed TRACE logging for Synchronization

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2231?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2231: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Detailed TRACE logging for Synchronization > ------------------------------------------ > > Key: JBTM-2231 > URL: https://issues.jboss.org/browse/JBTM-2231 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Jesper Pedersen > Assignee: Tom Jenkinson > > Provide TRACE logging of Synchronization interactions. > * Adding Synchronization through registerSynchronization > * Adding Synchronization through registerInterposedSynchronization > * Call of beforeCompletion > * Call of afterCompletion > Each TRACE statement needs > * Class name > * Identity hash code > * toString -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2236) Remove / from ConfigurationInfo

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2236?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2236: ------------------------------------- Hi Mark, I updated the PR and will let you know how it works out. Tom > Remove / from ConfigurationInfo > ------------------------------- > > Key: JBTM-2236 > URL: https://issues.jboss.org/browse/JBTM-2236 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Common > Affects Versions: 5.0.2 > Reporter: Mark Little > Assignee: Tom Jenkinson > > I've been working on compiling Java using the Avian project (http://oss.readytalk.com/avian/) and have eventually had success in running some of our hammer tests. However, there was a blocker which was to do with the way in which we locate the property file within the jar using the manifest. We can argue as to whether the issue resides within Avian or the way in which we do things, but the solution was to simply remove the / from: > int suffixLength = ("/"+ConfigurationInfo.class.getCanonicalName()+".class").length(); > Rebuilding and rerunning the tests made everything work. > I don't want to check in this change until I am sure that it is right, so would appreciate someone looking at it and at least running all of the QE tests to be sure nothing else breaks. > I've included a reference to the Avian forum article where I discussed this with their team. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2229) Issue with issue recovering AA with CMR, recovers OK but via orphan detection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2229?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2229: ----------------------------------------------- tom.jenkinson(a)redhat.com changed the Status of [bug 1129025|https://bugzilla.redhat.com/show_bug.cgi?id=1129025] from NEW to POST > Issue with issue recovering AA with CMR, recovers OK but via orphan detection > ----------------------------------------------------------------------------- > > Key: JBTM-2229 > URL: https://issues.jboss.org/browse/JBTM-2229 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.21, 5.0.2 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.22, 5.0.3 > > > The issue is with the CMR recovery module when it needs to update the underlying AA to modify it with the correct value from the CMR XIDS table. > If this AA does not have Serializable XARs, it will lead to the Xid being removed from XARM during getNewXAResource (via restore_state of the XARR). When the later AARM tries to recover the AA, it means a corresponding XAR for the XID cannot be located in the XARM by the XARR and an error message is reported. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2229) Issue with issue recovering AA with CMR, recovers OK but via orphan detection

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2229?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2229. ------------------------------- > Issue with issue recovering AA with CMR, recovers OK but via orphan detection > ----------------------------------------------------------------------------- > > Key: JBTM-2229 > URL: https://issues.jboss.org/browse/JBTM-2229 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.21, 5.0.2 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.22, 5.0.3 > > > The issue is with the CMR recovery module when it needs to update the underlying AA to modify it with the correct value from the CMR XIDS table. > If this AA does not have Serializable XARs, it will lead to the Xid being removed from XARM during getNewXAResource (via restore_state of the XARR). When the later AARM tries to recover the AA, it means a corresponding XAR for the XID cannot be located in the XARM by the XARR and an error message is reported. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2236) Remove / from ConfigurationInfo

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2236?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2236: ----------------------------------- Stick with removing the / Then after basePath is first created, try this: if (basePath.endsWith("/")) basePath = basePath.substring(0, basePath.length()-1); > Remove / from ConfigurationInfo > ------------------------------- > > Key: JBTM-2236 > URL: https://issues.jboss.org/browse/JBTM-2236 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Common > Affects Versions: 5.0.2 > Reporter: Mark Little > Assignee: Tom Jenkinson > > I've been working on compiling Java using the Avian project (http://oss.readytalk.com/avian/) and have eventually had success in running some of our hammer tests. However, there was a blocker which was to do with the way in which we locate the property file within the jar using the manifest. We can argue as to whether the issue resides within Avian or the way in which we do things, but the solution was to simply remove the / from: > int suffixLength = ("/"+ConfigurationInfo.class.getCanonicalName()+".class").length(); > Rebuilding and rerunning the tests made everything work. > I don't want to check in this change until I am sure that it is right, so would appreciate someone looking at it and at least running all of the QE tests to be sure nothing else breaks. > I've included a reference to the Avian forum article where I discussed this with their team. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2236) Remove / from ConfigurationInfo

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2236?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2236: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/704 Hi Mark, I have made the modification as you describe and created a pull request to test it. I will let you know what the outcome is. Thanks, Tom > Remove / from ConfigurationInfo > ------------------------------- > > Key: JBTM-2236 > URL: https://issues.jboss.org/browse/JBTM-2236 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Common > Affects Versions: 5.0.2 > Reporter: Mark Little > Assignee: Tom Jenkinson > > I've been working on compiling Java using the Avian project (http://oss.readytalk.com/avian/) and have eventually had success in running some of our hammer tests. However, there was a blocker which was to do with the way in which we locate the property file within the jar using the manifest. We can argue as to whether the issue resides within Avian or the way in which we do things, but the solution was to simply remove the / from: > int suffixLength = ("/"+ConfigurationInfo.class.getCanonicalName()+".class").length(); > Rebuilding and rerunning the tests made everything work. > I don't want to check in this change until I am sure that it is right, so would appreciate someone looking at it and at least running all of the QE tests to be sure nothing else breaks. > I've included a reference to the Avian forum article where I discussed this with their team. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2236) Remove / from ConfigurationInfo

by Mark Little (JIRA)

Mark Little created JBTM-2236: --------------------------------- Summary: Remove / from ConfigurationInfo Key: JBTM-2236 URL: https://issues.jboss.org/browse/JBTM-2236 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Common Affects Versions: 5.0.2 Reporter: Mark Little Assignee: Tom Jenkinson I've been working on compiling Java using the Avian project (http://oss.readytalk.com/avian/) and have eventually had success in running some of our hammer tests. However, there was a blocker which was to do with the way in which we locate the property file within the jar using the manifest. We can argue as to whether the issue resides within Avian or the way in which we do things, but the solution was to simply remove the / from: int suffixLength = ("/"+ConfigurationInfo.class.getCanonicalName()+".class").length(); Rebuilding and rerunning the tests made everything work. I don't want to check in this change until I am sure that it is right, so would appreciate someone looking at it and at least running all of the QE tests to be sure nothing else breaks. I've included a reference to the Avian forum article where I discussed this with their team. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2229) Issue with issue recovering AA with CMR, recovers OK but via orphan detection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2229?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTM-2229: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1124861, https://bugzilla.redhat.com/show_bug.cgi?id=1129025 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1124861) > Issue with issue recovering AA with CMR, recovers OK but via orphan detection > ----------------------------------------------------------------------------- > > Key: JBTM-2229 > URL: https://issues.jboss.org/browse/JBTM-2229 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.21, 5.0.2 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.22, 5.0.3 > > > The issue is with the CMR recovery module when it needs to update the underlying AA to modify it with the correct value from the CMR XIDS table. > If this AA does not have Serializable XARs, it will lead to the Xid being removed from XARM during getNewXAResource (via restore_state of the XARR). When the later AARM tries to recover the AA, it means a corresponding XAR for the XID cannot be located in the XARM by the XARR and an error message is reported. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 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 August 2014