April 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1558) Prune redundant code from jboss-transaction-spi

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1558?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1558: ------------------------------------- I have revised the description to apply more accurately to the statement of work > Prune redundant code from jboss-transaction-spi > ----------------------------------------------- > > Key: JBTM-1558 > URL: https://issues.jboss.org/browse/JBTM-1558 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.Final > > Attachments: as8.zip, ij-tx-spi.txt > > > We can use jboss-transaction-spi to get started > There is much old code in jboss-transaction-spi that does not get used in AS7 and does not apply to Narayana. > Run tattletale over AS8, identify redundant methods and add new SPI functions if necessary -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1558) Prune redundant code from jboss-transaction-spi

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1558?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1558: -------------------------------- Description: We can use jboss-transaction-spi to get started There is much old code in jboss-transaction-spi that does not get used in AS7 and does not apply to Narayana. Run tattletale over AS8, identify redundant methods and add new SPI functions if necessary was:We can use jboss-transaction-spi to get started > Prune redundant code from jboss-transaction-spi > ----------------------------------------------- > > Key: JBTM-1558 > URL: https://issues.jboss.org/browse/JBTM-1558 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.Final > > Attachments: as8.zip, ij-tx-spi.txt > > > We can use jboss-transaction-spi to get started > There is much old code in jboss-transaction-spi that does not get used in AS7 and does not apply to Narayana. > Run tattletale over AS8, identify redundant methods and add new SPI functions if necessary -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1558) Prune redundant code from jboss-transaction-spi

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1558?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1558: -------------------------------- Summary: Prune redundant code from jboss-transaction-spi (was: Provide an SPI for the AS) > Prune redundant code from jboss-transaction-spi > ----------------------------------------------- > > Key: JBTM-1558 > URL: https://issues.jboss.org/browse/JBTM-1558 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.Final > > Attachments: as8.zip, ij-tx-spi.txt > > > We can use jboss-transaction-spi to get started -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1556) provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1556?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1556: ----------------------------------- A less invasive approach would be to put the transaction being cancelled on to some globally searchable list. Since each participant (2PC or Synchronisation) can only be registered with one transaction, the participant could search this list if needed and base its actions on the result obtained. > provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling > ---------------------------------------------------------------------------------------------- > > Key: JBTM-1556 > URL: https://issues.jboss.org/browse/JBTM-1556 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.17.3 > Reporter: Scott Marlow > Assignee: Tom Jenkinson > Fix For: 4.17.4, 5.0.0.M3 > > > When the Synchronization.afterCompletion is invoked for EE JPA containers, knowledge of whether the current thread is the Reaper thread (cancelling the transaction from a background thread). > The fix to this jira will help with handling the [JPA 2.1 container concurrency requirements|http://java.net/projects/jpa-spec/lists/jsr338-experts/archi...]. > Please implement the solution makes the most sense to you, as this will introduce an additional dependency between other systems and JBossTM/JBossTS that depend on the solution, that will likely be around for a long time. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1556) provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1556?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1556: ----------------------------------- What do you mean by a remote thread? We should be using interposition in all distributed cases, which means the Synchronisation will be registered with a subordinate coordinator. > provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling > ---------------------------------------------------------------------------------------------- > > Key: JBTM-1556 > URL: https://issues.jboss.org/browse/JBTM-1556 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.17.3 > Reporter: Scott Marlow > Assignee: Tom Jenkinson > Fix For: 4.17.4, 5.0.0.M3 > > > When the Synchronization.afterCompletion is invoked for EE JPA containers, knowledge of whether the current thread is the Reaper thread (cancelling the transaction from a background thread). > The fix to this jira will help with handling the [JPA 2.1 container concurrency requirements|http://java.net/projects/jpa-spec/lists/jsr338-experts/archi...]. > Please implement the solution makes the most sense to you, as this will introduce an additional dependency between other systems and JBossTM/JBossTS that depend on the solution, that will likely be around for a long time. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1556) provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/JBTM-1556?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on JBTM-1556: ------------------------------------ If we could have a thread-local that tells the Synchronization.afterCompletion callee, that they are called from the reaper or a remote thread, that would cover more cases I think than just the (reaper) thread name check. > provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling > ---------------------------------------------------------------------------------------------- > > Key: JBTM-1556 > URL: https://issues.jboss.org/browse/JBTM-1556 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.17.3 > Reporter: Scott Marlow > Assignee: Tom Jenkinson > Fix For: 4.17.4, 5.0.0.M3 > > > When the Synchronization.afterCompletion is invoked for EE JPA containers, knowledge of whether the current thread is the Reaper thread (cancelling the transaction from a background thread). > The fix to this jira will help with handling the [JPA 2.1 container concurrency requirements|http://java.net/projects/jpa-spec/lists/jsr338-experts/archi...]. > Please implement the solution makes the most sense to you, as this will introduce an additional dependency between other systems and JBossTM/JBossTS that depend on the solution, that will likely be around for a long time. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1045) Add a persistent object into the recovery manager that we can talk to in the event of ONE after a resource has completed

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1045?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1045: ----------------------------------- There's one already there. > Add a persistent object into the recovery manager that we can talk to in the event of ONE after a resource has completed > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-1045 > URL: https://issues.jboss.org/browse/JBTM-1045 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.Final > > > add a persistent IOR into the RecoveryManager and that's used in the event we get the ONE for a basic resource. Kind of like a reverse RecoveryCoordinator (top-down RecoveryCoordinator) > You can embed lots of information into an IOR, so we can do this without changing any interfaces. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1556) provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1556?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1556: ----------------------------------- If using the name works for you then it's probably the least invasive approach anyway. Otherwise we might have to look at API changes, thread-local data or some such approach, since the reaper only has a handle on the transaction and not any specific resources that may be registered with the transaction. > provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling > ---------------------------------------------------------------------------------------------- > > Key: JBTM-1556 > URL: https://issues.jboss.org/browse/JBTM-1556 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.17.3 > Reporter: Scott Marlow > Assignee: Tom Jenkinson > Fix For: 4.17.4, 5.0.0.M3 > > > When the Synchronization.afterCompletion is invoked for EE JPA containers, knowledge of whether the current thread is the Reaper thread (cancelling the transaction from a background thread). > The fix to this jira will help with handling the [JPA 2.1 container concurrency requirements|http://java.net/projects/jpa-spec/lists/jsr338-experts/archi...]. > Please implement the solution makes the most sense to you, as this will introduce an additional dependency between other systems and JBossTM/JBossTS that depend on the solution, that will likely be around for a long time. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1558) Provide an SPI for the AS

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1558?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1558: ----------------------------------- Can you provide more detail to this task, since I thought we already had an SPI. > Provide an SPI for the AS > ------------------------- > > Key: JBTM-1558 > URL: https://issues.jboss.org/browse/JBTM-1558 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.Final > > Attachments: as8.zip, ij-tx-spi.txt > > > We can use jboss-transaction-spi to get started -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1558) Provide an SPI for the AS

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1558?page=com.atlassian.jira.plugin.... ] Mark Little edited comment on JBTM-1558 at 4/3/13 1:15 PM: ----------------------------------------------------------- Can you provide more detail to this task, since I thought we already had an SPI? was (Author: marklittle): Can you provide more detail to this task, since I thought we already had an SPI. > Provide an SPI for the AS > ------------------------- > > Key: JBTM-1558 > URL: https://issues.jboss.org/browse/JBTM-1558 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.Final > > Attachments: as8.zip, ij-tx-spi.txt > > > We can use jboss-transaction-spi to get started -- 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, 9 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 April 2013