June 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1495) Merge in BlackTie

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1495?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1495: ------------------------------------- Website merged, forums remain. I might leave the forums as it would make sense for them to be discussed somewhat separate given the nature of the C++ vs Java. tbd... > Merge in BlackTie > ----------------- > > Key: JBTM-1495 > URL: https://issues.jboss.org/browse/JBTM-1495 > 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.0.M4 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Docs, code, forums, chat room (motd), Jira, web pages > Need to add *.c, *.bat, *.sh, makefile to NarayanaReleaseProcess script when search and replacing -- 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

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

[ https://issues.jboss.org/browse/JBTM-1556?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1556: ------------------------------------- Perhaps we could add an SPI method: org.jboss.tm.TxUtils::isTimeoutBeingProcessedByTransactionManagerThread() The implementation for Narayana could then be to just check the thread name as you currently do, but it would allow us to alter it in the future if necessary without changing your code. If you both agree, I will ask Mike to add this to the Narayana SPI. Also, please have a think if you agree with the signature: public boolean org.jboss.tm.TxUtils::isTimeoutBeingProcessedByTransactionManagerThread () returns false if the call is issued when the current transaction is not rolling back due to timeout or the thread that is performing the rollback was not created by the transaction manager. returns true if the current thread was one created by the transaction manager AND it is processing a timeout scenario Its quite a niche method but it decouples you from internal Narayana code and moves you to the SPI > 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.5, 5.0.0.M4 > > > 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1611) Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09, 10, 12 with jacorb and HornetQ object store enabled

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1611?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1611: ---------------------------------------- Removing fix for M4 since it works on that version. > Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09,10,12 with jacorb and HornetQ object store enabled > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1611 > URL: https://issues.jboss.org/browse/JBTM-1611 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 4.17.3 > Reporter: Ondřej Chaloupka > Assignee: Michael Musgrove > Fix For: 4.17.5, 5.0.0.M4 > > Attachments: 0001-JBTM-1611-Make-recovery-passes-configurable.patch > > Original Estimate: 3 days > Remaining Estimate: 3 days > > During testing EAP 6.1.0.ER3 I'm hitting problem on QA tests of narayana project for branch 4.17 when running qa tests with jacorb and hornetq object store (happening for NIO and AIO). > Tests which are failing: > org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09 > - CrashRecovery09_Test01 > - CrashRecovery09_Test03 > - CrashRecovery09_Test05 > org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery10 > - CrashRecovery10_Test01 > - CrashRecovery10_Test03 > - CrashRecovery10_Test05 > org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery12 > - CrashRecovery12_Test03 > - CrashRecovery12_Test06 > Detailed log could be found in job: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-61-jbossts-qa-te... > I was trying to get more info on the test CrashRecovery09 but I can say just that the value honlder has value 0 instead of 1 on org.jboss.jbossts.qa.CrashRecovery09Clients.Client01a (line 84). -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1611) Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09, 10, 12 with jacorb and HornetQ object store enabled

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1611?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1611: ----------------------------------- Fix Version/s: (was: 5.0.0.M4) > Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09,10,12 with jacorb and HornetQ object store enabled > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1611 > URL: https://issues.jboss.org/browse/JBTM-1611 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 4.17.3 > Reporter: Ondřej Chaloupka > Assignee: Michael Musgrove > Fix For: 4.17.5 > > Attachments: 0001-JBTM-1611-Make-recovery-passes-configurable.patch > > Original Estimate: 3 days > Remaining Estimate: 3 days > > During testing EAP 6.1.0.ER3 I'm hitting problem on QA tests of narayana project for branch 4.17 when running qa tests with jacorb and hornetq object store (happening for NIO and AIO). > Tests which are failing: > org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09 > - CrashRecovery09_Test01 > - CrashRecovery09_Test03 > - CrashRecovery09_Test05 > org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery10 > - CrashRecovery10_Test01 > - CrashRecovery10_Test03 > - CrashRecovery10_Test05 > org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery12 > - CrashRecovery12_Test03 > - CrashRecovery12_Test06 > Detailed log could be found in job: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-61-jbossts-qa-te... > I was trying to get more info on the test CrashRecovery09 but I can say just that the value honlder has value 0 instead of 1 on org.jboss.jbossts.qa.CrashRecovery09Clients.Client01a (line 84). -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1611) Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09, 10, 12 with jacorb and HornetQ object store enabled

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1611?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1611: ----------------------------------- Git Pull Request: (was: https://github.com/jbosstm/narayana/pull/284, https://github.com/jbosstm/narayana/pull/285) > Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09,10,12 with jacorb and HornetQ object store enabled > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1611 > URL: https://issues.jboss.org/browse/JBTM-1611 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 4.17.3 > Reporter: Ondřej Chaloupka > Assignee: Michael Musgrove > Fix For: 4.17.5, 5.0.0.M4 > > Attachments: 0001-JBTM-1611-Make-recovery-passes-configurable.patch > > Original Estimate: 3 days > Remaining Estimate: 3 days > > During testing EAP 6.1.0.ER3 I'm hitting problem on QA tests of narayana project for branch 4.17 when running qa tests with jacorb and hornetq object store (happening for NIO and AIO). > Tests which are failing: > org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09 > - CrashRecovery09_Test01 > - CrashRecovery09_Test03 > - CrashRecovery09_Test05 > org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery10 > - CrashRecovery10_Test01 > - CrashRecovery10_Test03 > - CrashRecovery10_Test05 > org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery12 > - CrashRecovery12_Test03 > - CrashRecovery12_Test06 > Detailed log could be found in job: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-61-jbossts-qa-te... > I was trying to get more info on the test CrashRecovery09 but I can say just that the value honlder has value 0 instead of 1 on org.jboss.jbossts.qa.CrashRecovery09Clients.Client01a (line 84). -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1568) Install BlackTie as an WildFly subsystem module

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1568?page=com.atlassian.jira.plugin.... ] Work on JBTM-1568 started by Amos Feng. > Install BlackTie as an WildFly subsystem module > ----------------------------------------------- > > Key: JBTM-1568 > URL: https://issues.jboss.org/browse/JBTM-1568 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.0.M4 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Apparently there is a way to deploy a war as a module coming soon, wait till this is available possibly. Though, in the meantime, you could merge the stompconnect ear and blacktie-admin-servers ear into a single ear. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1568) Install BlackTie as an WildFly subsystem module

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1568?focusedWorklogId=12429398&page=... ] Amos Feng logged work on JBTM-1568: ----------------------------------- Author: Amos Feng Created on: 19/Jun/13 4:57 AM Start Date: 19/Jun/13 4:57 AM Worklog Time Spent: 1 day Issue Time Tracking ------------------- Remaining Estimate: 1 week, 4 days (was: 2 weeks) Time Spent: 1 day Worklog Id: (was: 12429398) > Install BlackTie as an WildFly subsystem module > ----------------------------------------------- > > Key: JBTM-1568 > URL: https://issues.jboss.org/browse/JBTM-1568 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.0.M4 > > Original Estimate: 2 weeks > Time Spent: 1 day > Remaining Estimate: 1 week, 4 days > > Apparently there is a way to deploy a war as a module coming soon, wait till this is available possibly. Though, in the meantime, you could merge the stompconnect ear and blacktie-admin-servers ear into a single ear. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1495) Merge in BlackTie

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1495?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1495: ------------------------------------- Docs, code, chat room, Jira all done. Remaining: website and forums > Merge in BlackTie > ----------------- > > Key: JBTM-1495 > URL: https://issues.jboss.org/browse/JBTM-1495 > 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.0.M4 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Docs, code, forums, chat room (motd), Jira, web pages > Need to add *.c, *.bat, *.sh, makefile to NarayanaReleaseProcess script when search and replacing -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1278) Additional debug information required for transaction's Xid with Oracle

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1278?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1278: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/344 > Additional debug information required for transaction's Xid with Oracle > ----------------------------------------------------------------------- > > Key: JBTM-1278 > URL: https://issues.jboss.org/browse/JBTM-1278 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.16.1 > Environment: Jboss EAP 5.x > Reporter: Tom Ross > Assignee: Tom Jenkinson > Fix For: 5.0.0.M4 > > > It seems that Oracle is returning different XIDs each time (with the same content) which makes it difficult to debug if the same XID is in more than one scan. Additional debug information is required in Xid to make debugging easier. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1754) Make project names consistent in poms

by Weinan Li (JIRA)

[ https://issues.jboss.org/browse/JBTM-1754?page=com.atlassian.jira.plugin.... ] Weinan Li commented on JBTM-1754: --------------------------------- Not a problem at all :-) Then I'll rename the prefix to "JBossTS: " for branch 4.17. > Make project names consistent in poms > ------------------------------------- > > Key: JBTM-1754 > URL: https://issues.jboss.org/browse/JBTM-1754 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Gier > Assignee: Paul Gier > Fix For: 5.0.0.M4 > > > The project names used in the build are not consistent which makes it difficult for someone unfamiliar with the project to debug build issues. > Some examples are provided: > ||Dir Name||Artifact ID||Project Name||Proposed Name|| > |/ArjunaJTA|narayana-jta-all|JBoss JTA everything|Narayana: ArjunaJTA| > |/ArjunaJTS/narayana-jts-idlj|narayana-jts-idlj|JBossJTS packaged module with idlj stubs|Narayana: ArjunaJTS idlj| > |/ArjunaJTS/orbportability|orbportability|JBossJTS orb portability|Narayana: ArjunaJTS orbportability| > The project names can be changed without disrupting the way the build works, so these should be changed to match the dir and artifactId as much as possible. -- 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

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2013