February 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1498) Update all quickstarts to use new APIs provided by TXFramework

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1498: ----------------------------------- Summary: Update all quickstarts to use new APIs provided by TXFramework Key: JBTM-1498 URL: https://issues.jboss.org/browse/JBTM-1498 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Demonstrator, REST, TXFramework, XTS Reporter: Paul Robinson Assignee: Michael Musgrove -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1497) Implement JTA 1.2 (when complete)

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1497: ----------------------------------- Summary: Implement JTA 1.2 (when complete) Key: JBTM-1497 URL: https://issues.jboss.org/browse/JBTM-1497 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.0.Final -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1496) Transaction Monitoring and Analysis

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1496: ----------------------------------- Summary: Transaction Monitoring and Analysis Key: JBTM-1496 URL: https://issues.jboss.org/browse/JBTM-1496 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Reporter: Paul Robinson Assignee: Michael Musgrove Details here: https://community.jboss.org/wiki/TransactionMonitoringAndVisualization First step is to create a simple prototype to demonstrate the potential. This will help justify resource to do it properly. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1009) Ensure that the Object Store header for action records is the first item to be packed

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1009?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1009: -------------------------------- Component/s: Transaction Core > Ensure that the Object Store header for action records is the first item to be packed > ------------------------------------------------------------------------------------- > > Key: JBTM-1009 > URL: https://issues.jboss.org/browse/JBTM-1009 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.16.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.Final > > > Clone of https://issues.jboss.org/browse/JBTM-1008 but targeted at trunk: > Some action classes call super.save_state after save their own state which results in the record header being packed at arbitrary locations within the record. Ideally the tooling (ObjStoreBrowser) would like to read the header without having to know the specific class responsible for the record. > The equivalent fix for 4.16.0.Final was a quick fix to force offending classes to save/restore the parent classes state before the specific state. A more versatile solution is desirable for trunk, for example change the extension point (for saving state) from say save_state to save_state_impl and provide a final implementation of save_state in StateManager that calls out the classes implementation of save_state_impl after packing the header. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1188) Support override of CheckedAction

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1188?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1188: -------------------------------- Fix Version/s: (was: 5.0.0.Final) > Support override of CheckedAction > --------------------------------- > > Key: JBTM-1188 > URL: https://issues.jboss.org/browse/JBTM-1188 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Tom Jenkinson > Assignee: Mark Little > > Hi Mark, > Assigned to you initially to confirm whether this is behavior we want. Please assign back to me with a comment if we do need this and I will implement it. Otherwise please do reject it. > BasicAction::setCheckedAction is protected so cannot be called by user code (4.16.x and above). > The suggestion given at: > https://community.jboss.org/message/742293#742293 > Would therefore not work with current versions of Narayana. > Thanks, > Tom -- 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, 1 month

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: 5.0.0.M3 > 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 > Fix For: 5.0.0.M3 > > > 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, 1 month

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: -------------------------------- Priority: Minor (was: Major) > 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.M3 > > > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS subsystem and module

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1365: -------------------------------- Priority: Major (was: Minor) > Deploy REST-AT support as a JBossAS subsystem and module > -------------------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Fix For: 5.0.0.Final > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. > h3. Open Issues > Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. -- 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, 1 month

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 Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1045?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1045: -------------------------------- Priority: Minor (was: Major) > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1485) Change reaper to dump the resources that are stuck and stacks of stuck threads

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1485?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1485: -------------------------------- Priority: Minor (was: Major) > Change reaper to dump the resources that are stuck and stacks of stuck threads > ------------------------------------------------------------------------------ > > Key: JBTM-1485 > URL: https://issues.jboss.org/browse/JBTM-1485 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JTA, JTS, Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M3 > > -- 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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2013