April 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1637) XTS Unit Test Failure: Invalid fault type enumeration: Error reading XMLStreamReader

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1637?page=com.atlassian.jira.plugin.... ] Paul Robinson edited comment on JBTM-1637 at 4/17/13 4:55 AM: -------------------------------------------------------------- Disabled in: http://172.17.131.2/job/Narayana+BlacktTie/job/narayana/ Created job: http://172.17.131.2/view/Narayana+BlacktTie-JBTM/job/narayana-JBTM-1637/ was (Author: paul.robinson): Disabled in: http://172.17.131.2/view/Narayana+BlacktTie/job/narayana/ Created job: http://172.17.131.2/view/Narayana+BlacktTie-JBTM/job/narayana-JBTM-1637/ > XTS Unit Test Failure: Invalid fault type enumeration: Error reading XMLStreamReader > ------------------------------------------------------------------------------------ > > Key: JBTM-1637 > URL: https://issues.jboss.org/browse/JBTM-1637 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/247 > In particular see: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/247/artifact/XTS/... > Lots of stacktraces, some of which are only warnings. > The First Groovy one is supposed to be benign. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1472) Initial work on JTA for Compensations

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1472?focusedWorklogId=12429099&page=... ] Paul Robinson logged work on JBTM-1472: --------------------------------------- Author: Paul Robinson Created on: 17/Apr/13 4:46 AM Start Date: 17/Apr/13 4:46 AM Worklog Time Spent: 1 day Issue Time Tracking ------------------- Remaining Estimate: 1 week, 1 day, 4 hours (was: 1 week, 2 days, 4 hours) Time Spent: 3 days, 4 hours (was: 2 days, 4 hours) Worklog Id: (was: 12429099) > Initial work on JTA for Compensations > ------------------------------------- > > Key: JBTM-1472 > URL: https://issues.jboss.org/browse/JBTM-1472 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M3 > > Original Estimate: 2 weeks > Time Spent: 3 days, 4 hours > Remaining Estimate: 1 week, 1 day, 4 hours > > We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS). > It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market. > This first piece of work is to do some initial research and support an API with potentially a subset of features of the final API. > Tasks: > # Investigate existing WS-BA APIs > ## Try code examples if possible > # Produce an initial list of features that should be covered by the API > # Create a simple implementation backed by WS-BA. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1637) XTS Unit Test Failure: Invalid fault type enumeration: Error reading XMLStreamReader

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1637?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1637: ------------------------------------- Disabled in: https://github.com/jbosstm/narayana/pull/273 Created job: http://172.17.131.2/view/Narayana+BlacktTie-JBTM/job/narayana-JBTM-1637/ > XTS Unit Test Failure: Invalid fault type enumeration: Error reading XMLStreamReader > ------------------------------------------------------------------------------------ > > Key: JBTM-1637 > URL: https://issues.jboss.org/browse/JBTM-1637 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/247 > In particular see: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/247/artifact/XTS/... > Lots of stacktraces, some of which are only warnings. > The First Groovy one is supposed to be benign. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1637) XTS Unit Test Failure: Invalid fault type enumeration: Error reading XMLStreamReader

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1637?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1637: ------------------------------------- Caused by: Undertow 1.0.0.Alpha9 + Initial websocket support https://github.com/jbossas/jboss-as/commit/3212bdd91eadfe520ce0c472099c5a... FYI, you also need the following commit (sync with io subsystem) to make the AS compile with the above commit. > XTS Unit Test Failure: Invalid fault type enumeration: Error reading XMLStreamReader > ------------------------------------------------------------------------------------ > > Key: JBTM-1637 > URL: https://issues.jboss.org/browse/JBTM-1637 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/247 > In particular see: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/247/artifact/XTS/... > Lots of stacktraces, some of which are only warnings. > The First Groovy one is supposed to be benign. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1637) XTS Unit Test Failure: Invalid fault type enumeration: Error reading XMLStreamReader

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1637?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1637: ------------------------------------- Running com.arjuna.wsc.tests.arq.ActivationServiceExceptionTest Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.8 sec <<< FAILURE! -- Running com.arjuna.wsc.tests.arq.ActivationServiceTest Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.695 sec <<< FAILURE! -- Running com.arjuna.wsc.tests.arq.EnduranceTest Tests run: 5, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 62.553 sec <<< FAILURE! -- Running com.arjuna.wsc.tests.arq.RegistrationServiceExceptionTest Tests run: 4, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 1.788 sec <<< FAILURE! -- Running com.arjuna.wsc.tests.arq.RegistrationServiceTest Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.96 sec <<< FAILURE! > XTS Unit Test Failure: Invalid fault type enumeration: Error reading XMLStreamReader > ------------------------------------------------------------------------------------ > > Key: JBTM-1637 > URL: https://issues.jboss.org/browse/JBTM-1637 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/247 > In particular see: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/247/artifact/XTS/... > Lots of stacktraces, some of which are only warnings. > The First Groovy one is supposed to be benign. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1522) "no XTS application recovery module found" during XTS Recovery Tests

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1522?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1522: --------------------------------- Paul, I've done rebase and will take a look at the examples, thanks! > "no XTS application recovery module found" during XTS Recovery Tests > -------------------------------------------------------------------- > > Key: JBTM-1522 > URL: https://issues.jboss.org/browse/JBTM-1522 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Critical > Fix For: 4.17.4, 5.0.0.M3 > > Attachments: 2013-04-01_jbtm-1522_outputs.zip, com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit-output.txt, com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-2.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-output-2.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-output.txt, com.arjuna.qa.junit.TestBACrashDuringCommit.txt, com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit-output.txt, com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit.txt > > > See: http://172.17.131.2/view/Narayana+BlackTie/job/narayana/211/artifact/XTS/... > Notice the following log is displayed repeatedly until the test gives up waiting for recovery: > {code} > WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046032: no XTS application recovery module found to help reactivate recovered WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > {code} > This error comes from org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple#recoverParticipants(). In particular: > {code} > if (!found) { > // we failed to find a helper to convert a participant record so log a warning > // but leave it in the table for next time > RecoveryLogger.i18NLogger.warn_participant_at_XTSATRecoveryModule_4(participantRecoveryRecord.getId()); > } > {code} > It looks like the code is unable to restore the participant from the log due to restoreParticipant(XTSATRecoveryModule module) returning false. There is ParticipantRecoveryRecord in the log as you can see it dumped to the console in the above log. Maybe there is a problem with that log, or maybe we are missing another log entry? > This problem is intermittent, so it's unlikely that you will see this happen when you attach a debugger. However, we could attach a debugger to see what happens in the normal case and also to inspect the log to see if anything is missing in the failing case. But I have a cunning plan... > h4.Cunning Plan > We need to get a copy of the failing log, before recovery is attempted. We should then be able to use that log to reproduce the issue on our own machines. Steps to take: > # Update BaseCrashTest to copy the contents of the tx-object-store to a unique folder location (So we can retrieve it later for a failed run). Make sure you create the folder structure under target/surefire-reports so that CI archives it off. Do the copy between controller.kill and controller.start. This way we get the log before the recovery manager has had chance to tamper with it. > # Update the "narayana-JBTM-1522" job in CI to use your branch, containing the change above. > # Configure the job to run @hourly until it fails with this problem. > # Take a copy of the tx-object-store from the failing test and then put it in place on your AS8 build. > # Boot the AS and confirm that the issue is reproduced. > # You can now keep putting the tx-object-store back in place every time you need to reproduce the issue. > # Attach a debugger to find out what the problem is. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1637) XTS Unit Test Failure: Invalid fault type enumeration: Error reading XMLStreamReader

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1637: ----------------------------------- Summary: XTS Unit Test Failure: Invalid fault type enumeration: Error reading XMLStreamReader Key: JBTM-1637 URL: https://issues.jboss.org/browse/JBTM-1637 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing, XTS Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M3 http://172.17.131.2/view/Narayana+BlackTie/job/narayana/247 In particular see: http://172.17.131.2/view/Narayana+BlackTie/job/narayana/247/artifact/XTS/... Lots of stacktraces, some of which are only warnings. The First Groovy one is supposed to be benign. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1598) version tags missed for all the sub-components

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1598?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-1598: --------------------------------------- JavaEE version was incorrect. Updated PR. > version tags missed for all the sub-components > ---------------------------------------------- > > Key: JBTM-1598 > URL: https://issues.jboss.org/browse/JBTM-1598 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Weinan Li > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 4.17.4, 5.0.0.M3 > > Original Estimate: 1 hour > Time Spent: 1 day, 2 hours, 50 minutes > Remaining Estimate: 0 minutes > > Hi Tom, the problem I've found is that all the dependencies of its own components are lack of version section. For example: > {code} > <dependencies> > <dependency> > <groupId>org.jboss.jbossts</groupId> > <artifactId>common</artifactId> > </dependency> > </dependencies> > {code} > Should be: > {code} > <dependencies> > <dependency> > <groupId>org.jboss.jbossts</groupId> > <artifactId>common</artifactId> > <version>${project.version}</version> > </dependency> > </dependencies> > {code} > Could you please help to add these tags? Thanks! -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1598) version tags missed for all the sub-components

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1598?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1598: ---------------------------------- Status: Pull Request Sent (was: Coding In Progress) > version tags missed for all the sub-components > ---------------------------------------------- > > Key: JBTM-1598 > URL: https://issues.jboss.org/browse/JBTM-1598 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Weinan Li > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 4.17.4, 5.0.0.M3 > > Original Estimate: 1 hour > Time Spent: 1 day, 2 hours, 50 minutes > Remaining Estimate: 0 minutes > > Hi Tom, the problem I've found is that all the dependencies of its own components are lack of version section. For example: > {code} > <dependencies> > <dependency> > <groupId>org.jboss.jbossts</groupId> > <artifactId>common</artifactId> > </dependency> > </dependencies> > {code} > Should be: > {code} > <dependencies> > <dependency> > <groupId>org.jboss.jbossts</groupId> > <artifactId>common</artifactId> > <version>${project.version}</version> > </dependency> > </dependencies> > {code} > Could you please help to add these tags? Thanks! -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1598) version tags missed for all the sub-components

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1598?focusedWorklogId=12429098&page=... ] Gytis Trikleris logged work on JBTM-1598: ----------------------------------------- Author: Gytis Trikleris Created on: 16/Apr/13 12:27 PM Start Date: 16/Apr/13 12:27 PM Worklog Time Spent: 1 hour, 20 minutes Issue Time Tracking ------------------- Time Spent: 1 day, 2 hours, 50 minutes (was: 1 day, 1 hour, 30 minutes) Worklog Id: (was: 12429098) > version tags missed for all the sub-components > ---------------------------------------------- > > Key: JBTM-1598 > URL: https://issues.jboss.org/browse/JBTM-1598 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Weinan Li > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 4.17.4, 5.0.0.M3 > > Original Estimate: 1 hour > Time Spent: 1 day, 2 hours, 50 minutes > Remaining Estimate: 0 minutes > > Hi Tom, the problem I've found is that all the dependencies of its own components are lack of version section. For example: > {code} > <dependencies> > <dependency> > <groupId>org.jboss.jbossts</groupId> > <artifactId>common</artifactId> > </dependency> > </dependencies> > {code} > Should be: > {code} > <dependencies> > <dependency> > <groupId>org.jboss.jbossts</groupId> > <artifactId>common</artifactId> > <version>${project.version}</version> > </dependency> > </dependencies> > {code} > Could you please help to add these tags? Thanks! -- 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, 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 April 2013