March 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1351) Narayana Quickstarts: consider putting dependencies in BOM as JDF quickstarts do

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1351?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1351: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M3) > Narayana Quickstarts: consider putting dependencies in BOM as JDF quickstarts do > -------------------------------------------------------------------------------- > > Key: JBTM-1351 > URL: https://issues.jboss.org/browse/JBTM-1351 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Ondřej Chaloupka > Priority: Minor > Fix For: 5.0.0.Final > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Currently the quickstarts for Narayana project does not solve dependency management in some global way. > Each directory contains one quickstart and it manages dependencies on its own what leads to situation that during compilation quickstarts as a whole project common libraries are downloaded several times (e.g. arquillian). > There is idea of using JDF quickstart style of managing dependencies. They use BOMs where all dependencies are defined. Versions are defined in parent pom.xml. > As inspiration could be used BOM from JDF: > https://github.com/jboss-jdf/jboss-bom/blob/master/jboss-javaee-6.0-with-... > It could be used this bom directly or just import it or do it in other way. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1510) QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2#CrashRecovery05_2_Test076

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1510?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1510: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M3) > QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2#CrashRecovery05_2_Test076 > ------------------------------------------------------------------------------------------------------------ > > Key: JBTM-1510 > URL: https://issues.jboss.org/browse/JBTM-1510 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.Final > > Attachments: CrashRecovery05_2_Test076.tar.gz, TEST-org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2.txt > > > See: http://172.17.131.2/job/narayana/173/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1336) DUPID detection for mysql in JTS mode does not work

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1336?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1336: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M3) > DUPID detection for mysql in JTS mode does not work > --------------------------------------------------- > > Key: JBTM-1336 > URL: https://issues.jboss.org/browse/JBTM-1336 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.Final > > Attachments: JBTM-1336.patch > > Original Estimate: 3 days > Time Spent: 1 day > Remaining Estimate: 2 days > > Mysql does not send errorcode of XAException.XAER_DUPID, it sends 0. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1557) If the same resource manager (isSameRM) is enlisted twice, ignore the second call to enlist

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1557?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1557: -------------------------------- Status: Closed (was: Pull Request Sent) Resolution: Rejected > If the same resource manager (isSameRM) is enlisted twice, ignore the second call to enlist > ------------------------------------------------------------------------------------------- > > Key: JBTM-1557 > URL: https://issues.jboss.org/browse/JBTM-1557 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA, JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1537) blacktie-quickstarts-integration1-xatmi_adapter is missing M3 dependencies

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1537?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-1537: --------------------------------------- http://172.17.131.2/job/btny-narayana-quickstarts-taconic/245 > blacktie-quickstarts-integration1-xatmi_adapter is missing M3 dependencies > -------------------------------------------------------------------------- > > Key: JBTM-1537 > URL: https://issues.jboss.org/browse/JBTM-1537 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.M3 > > > See: http://172.17.131.2/job/btny-narayana-quickstarts-taconic/244 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1536) XTS default-context-propagation must be optional to maintain backwards compatability

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1536?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1536. --------------------------------- Resolution: Done > XTS default-context-propagation must be optional to maintain backwards compatability > ------------------------------------------------------------------------------------ > > Key: JBTM-1536 > URL: https://issues.jboss.org/browse/JBTM-1536 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Application Server Integration, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1553) Allow AS branch name to be configured in narayana.sh

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1553?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1553. --------------------------------- Resolution: Won't Fix This is only needed for the 'narayana-AS-PR-M2' job and there is a satisfactory workaround in place at the moment: {code} sed -i "s/5_BRANCH/AS7-6695_Upgrading_JBossTS_to_5.0.0.M2/g" ./scripts/hudson/narayana.sh {code} > Allow AS branch name to be configured in narayana.sh > ---------------------------------------------------- > > Key: JBTM-1553 > URL: https://issues.jboss.org/browse/JBTM-1553 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > This will allow us to do CI against other branches. For example, the PR branch for when we are in the process of upgrading Narayana in the AS. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1482) If a naughty afterCompletion sync throws an exception, log the exception call stack

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1482?page=com.atlassian.jira.plugin.... ] Work on JBTM-1482 started by Gytis Trikleris. > 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: Gytis Trikleris > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1548) Many XTS unit tests hanging

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1548?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1548: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Many XTS unit tests hanging > --------------------------- > > Key: JBTM-1548 > URL: https://issues.jboss.org/browse/JBTM-1548 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.0.0.M3 > > Original Estimate: 2 days > Time Spent: 4 hours, 30 minutes > Remaining Estimate: 0 minutes > > I suspect these are all cause by the same issue: > https://issues.jboss.org/issues/?jql=text%20~%20%22XTS%20Test%20Hang%22%2... > I did a stack dump (kill -quit <pid>) on all the java processes, so you can see what the threads where doing when the job hung. The stack dump is sent to the log for each proces. > If you find out that they are the same issue, can you close them as duplicates and do all work against this issue. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1479) Create a quickstart to show how to use IronJacamar and JBTM inside tomcat

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1479?page=com.atlassian.jira.plugin.... ] Work on JBTM-1479 stopped by Gytis Trikleris. > Create a quickstart to show how to use IronJacamar and JBTM inside tomcat > ------------------------------------------------------------------------- > > Key: JBTM-1479 > URL: https://issues.jboss.org/browse/JBTM-1479 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Attachments: test-ds.xml, transaction.xml > > Original Estimate: 3 days > Time Spent: 4 days, 1 hour, 30 minutes > Remaining Estimate: 3 hours, 30 minutes > > See JBTM-809 for the algorithm > You might want to put the startup in the context listener: > public class MyServletContextListener implements ServletContextListener { > public void contextInitialized(ServletContextEvent sce) { > // Initialize RecoveryManager > // Initialize TransactionManager > // Initialize IronJacamar > } > > @Override > public void contextDestroyed(ServletContextEvent sce) { > // Clean IronJacamar > // Clean TransactionManager > // Clean RecoveryManager > } > } > Quickstart application should connect to the database (say PostgreSQL), dummy XA resource and coordinate the transaction. The PostgreSQL data source needs to be accessed via IronJacamar. -- 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, 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 March 2013