July 2007 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBTM-50) Open source WS-Context implementation

by Jonathan Halliday (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-50?page=comments#action_12369553 ] Jonathan Halliday commented on JBTM-50: --------------------------------------- Hmm, this seems to be built on axis1 and a JAXM API so ancient I've not been able to find it anywhere on the web. I probably need to go back to JBoss 3.x. It's also implementing an obsolete version of the protocol. Looks like a lot of fun work ahead here. > Open source WS-Context implementation > ------------------------------------- > > Key: JBTM-50 > URL: http://jira.jboss.com/jira/browse/JBTM-50 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Reporter: Mark Little > Assigned To: Jonathan Halliday > Fix For: 4.4 > > Time Spent: 1 hour > Remaining Estimate: 0 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Work started: (JBTM-121) Check XTS recovery

by Jonathan Halliday (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-121?page=all ] Work on JBTM-121 started by Jonathan Halliday. > Check XTS recovery > ------------------ > > Key: JBTM-121 > URL: http://jira.jboss.com/jira/browse/JBTM-121 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Affects Versions: 4.2.1 > Reporter: Mark Little > Assigned To: Jonathan Halliday > Priority: Critical > Fix For: 4.4 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBTM-121) Check XTS recovery

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-121?page=comments#action_12369475 ] Mark Little commented on JBTM-121: ---------------------------------- The lack of an XARecoveryModule in XTS indicates that automatic top-down recovery isn't in place. The WS-AT transactions are instances of ACCoordinator and that saves its logs in /StateManager/BasicAction/AtomicAction/TwoPhaseCoordinator/TwoPhase/ACCoordinator so a specific RecoveryModule was required to do top-down recovery. > Check XTS recovery > ------------------ > > Key: JBTM-121 > URL: http://jira.jboss.com/jira/browse/JBTM-121 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Affects Versions: 4.2.1 > Reporter: Mark Little > Assigned To: Jonathan Halliday > Priority: Critical > Fix For: 4.4 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Work logged: (JBTM-217) Contention on SychronizedMap in TransactionLocalDelegateImpl.java

by Andrew Dinn (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-217?page=worklog#action_12369414 ] Andrew Dinn logged work on JBTM-217: ------------------------------------ Time Spent: 1 day Remaining Estimate: 0 minutes Time Spent: 1 day verified need for current version and investigated fix -- depends on addition of synchronization ordering to JTS > Contention on SychronizedMap in TransactionLocalDelegateImpl.java > ----------------------------------------------------------------- > > Key: JBTM-217 > URL: http://jira.jboss.com/jira/browse/JBTM-217 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA Implementation > Affects Versions: 4.2.3 > Reporter: Phillip Thurmond > Assigned To: Andrew Dinn > Fix For: 4.4 > > Time Spent: 1 day > Remaining Estimate: 0 minutes > > Under heavy loads, I'm seeing contention on the object map in TransactionLocalDelegateImpl.java. Can this variable be changed to use ConcurrentHashMap? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBTM-217) Contention on SychronizedMap in TransactionLocalDelegateImpl.java

by Andrew Dinn (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-217?page=comments#action_12369410 ] Andrew Dinn commented on JBTM-217: ---------------------------------- The current(WeakHashMap) implementation works round a problem with synchronization execution order dependencies. It is required until synchronization ordering can be implemented in both the local JTA and JTS. > Contention on SychronizedMap in TransactionLocalDelegateImpl.java > ----------------------------------------------------------------- > > Key: JBTM-217 > URL: http://jira.jboss.com/jira/browse/JBTM-217 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA Implementation > Affects Versions: 4.2.3 > Reporter: Phillip Thurmond > Assigned To: Andrew Dinn > Fix For: 4.4 > > > Under heavy loads, I'm seeing contention on the object map in TransactionLocalDelegateImpl.java. Can this variable be changed to use ConcurrentHashMap? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBTM-97) Remove XAConnectionRecovery support

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-97?page=all ] Mark Little closed JBTM-97. --------------------------- Resolution: Done Updated documentation too. > Remove XAConnectionRecovery support > ----------------------------------- > > Key: JBTM-97 > URL: http://jira.jboss.com/jira/browse/JBTM-97 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTA Implementation > Affects Versions: 4.2 > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.4 > > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Work logged: (JBTM-97) Remove XAConnectionRecovery support

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-97?page=worklog#action_12369266 ] Mark Little logged work on JBTM-97: ----------------------------------- Time Spent: 30 minutes Remaining Estimate: 0 minutes Time Spent: 30 minutes Removed interface and use. > Remove XAConnectionRecovery support > ----------------------------------- > > Key: JBTM-97 > URL: http://jira.jboss.com/jira/browse/JBTM-97 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTA Implementation > Affects Versions: 4.2 > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.4 > > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBTM-217) Contention on SychronizedMap in TransactionLocalDelegateImpl.java

by Andrew Dinn (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-217?page=comments#action_12369175 ] Andrew Dinn commented on JBTM-217: ---------------------------------- The short answer is no you cannot replace the map with a ConcurrentHashMap. The map in question is implemented by wrapping a WeakHashMap with a SynchronizedMap. This has different semantics to a ConcurrentHashMap -- changing it would trade off a contention problem against a garbage problem. The long answer is that thecontention is happening because of an inefficiency in the way the AS/TM code is implementing reclamation of map entries for dead transactions. A WeakHashMap works in conjunction with the GC to remove entries keyed by objects to which there are no other references (in this case the Transaction instance is the map key). So, your problem will manifest under load immediately after GC when a new local transaction is started and an update of the WeakHashMap occurs. The updating thread will lock the table and then find that a whole load of dead Transaction instances have been notified by the GC. Before it can do the update the thread has to remove the dead entries and, possibly, downsize the map table. This can take a long time and explains why the getSynchronization call in your trace is stalled The solution is for the AS/TM to make sure that the information maintained in this map is cleared out as transactions are resolved rather than relying upon the GC. I am working on a fix. > Contention on SychronizedMap in TransactionLocalDelegateImpl.java > ----------------------------------------------------------------- > > Key: JBTM-217 > URL: http://jira.jboss.com/jira/browse/JBTM-217 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA Implementation > Affects Versions: 4.2.3 > Reporter: Phillip Thurmond > Assigned To: Andrew Dinn > Fix For: 4.4 > > > Under heavy loads, I'm seeing contention on the object map in TransactionLocalDelegateImpl.java. Can this variable be changed to use ConcurrentHashMap? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Work started: (JBTM-217) Contention on SychronizedMap in TransactionLocalDelegateImpl.java

by Andrew Dinn (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-217?page=all ] Work on JBTM-217 started by Andrew Dinn. > Contention on SychronizedMap in TransactionLocalDelegateImpl.java > ----------------------------------------------------------------- > > Key: JBTM-217 > URL: http://jira.jboss.com/jira/browse/JBTM-217 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA Implementation > Affects Versions: 4.2.3 > Reporter: Phillip Thurmond > Assigned To: Andrew Dinn > Fix For: 4.4 > > > Under heavy loads, I'm seeing contention on the object map in TransactionLocalDelegateImpl.java. Can this variable be changed to use ConcurrentHashMap? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBTM-191) Update CORBA examples

by Jonathan Halliday (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-191?page=all ] Jonathan Halliday reassigned JBTM-191: -------------------------------------- Assignee: Andrew Dinn (was: Jonathan Halliday) > Update CORBA examples > --------------------- > > Key: JBTM-191 > URL: http://jira.jboss.com/jira/browse/JBTM-191 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS Implementation, Demonstrator > Affects Versions: 4.2.2 > Reporter: Mark Little > Assigned To: Andrew Dinn > Priority: Minor > Fix For: 4.4 > > > The CORBA examples are out-of-date, referring to BOA classes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 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 July 2007