[JBoss JIRA] (JBTM-1237) qa timeout MFACTOR (was: crashrecovery07 tests failing on Solaris11 x86/x86_64 platform)
by Ondřej Chaloupka (JIRA)
[ https://issues.jboss.org/browse/JBTM-1237?page=com.atlassian.jira.plugin.... ]
Ondřej Chaloupka resolved JBTM-1237.
------------------------------------
During the test cycle of EAP 5.2.0 I've not hit this problem. I suppose that this jira is solved. In case of problems I would reopen it.
You can check runs here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbossts-testsuite-so...
> qa timeout MFACTOR (was: crashrecovery07 tests failing on Solaris11 x86/x86_64 platform)
> ----------------------------------------------------------------------------------------
>
> Key: JBTM-1237
> URL: https://issues.jboss.org/browse/JBTM-1237
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 4.6.1.CP13
> Reporter: Ivo Studensky
> Assignee: Ondřej Chaloupka
> Fix For: 4.6.1.CP14
>
>
> When running QA testsuite on Solaris 11 x86/x86_64 platform with Oracle JDK7 I hit intermittent failures at crashrecovery07 tests.
> Affected tests:
> CrashRecovery07_Test04
> CrashRecovery07_Test05
> CrashRecovery07_Test11
> CrashRecovery07_Test12
> output of Test05 (qa/results/113/task_0_out):
> {noformat}
> Sleeping for 180000ms.
> Test will fail because we have just received value 2 for resource 0
> Test will fail because we have just received value 2 for resource 1
> Test has failed because we got 2 for 2
> Failed
> {noformat}
> output of Test11 (qa/results/25/task_0_out):
> {noformat}
> Sleeping for 360000ms.
> Test will fail because we have just received value 2 for resource 0
> Test will fail because we have just received value 2 for resource 1
> Test will fail because we have just received value 2 for resource 2
> Test has failed because we got 2 for 3
> Failed
> {noformat}
> Complete logs for the two issues detailed above can be found here:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBoss%20TS/view/JBo...
> output of Test04 (qa/results/92/task_0_out):
> {noformat}
> Sleeping for 450000ms.
> Test will fail because we have just received value 2 for resource 0
> Test has failed because we got 2 for 1
> Failed
> {noformat}
> output of Test12 (qa/results/14/task_0_out):
> {noformat}
> Sleeping for 450000ms.
> Test will fail because we have just received value 2 for resource 0
> Test will fail because we have just received value 2 for resource 1
> Test will fail because we have just received value 2 for resource 2
> Test has failed because we got 2 for 3
> Failed
> {noformat}
> Complete logs for Test04 and Test12 can be found here:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBoss%20TS/view/JBo...
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1478) Squash all 5_BRANCH commits into logical groups
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1478?focusedWorklogId=12428717&page=... ]
Paul Robinson logged work on JBTM-1478:
---------------------------------------
Author: Paul Robinson
Created on: 21/Feb/13 10:21 AM
Start Date: 21/Feb/13 10:21 AM
Worklog Time Spent: 2 hours
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 1 hour)
Time Spent: 2 hours
Worklog Id: (was: 12428717)
> Squash all 5_BRANCH commits into logical groups
> -----------------------------------------------
>
> Key: JBTM-1478
> URL: https://issues.jboss.org/browse/JBTM-1478
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Application Server Integration
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 1 hour
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> Before we raise a pull request for our AS changes to M2, we need to reduce the number of commits. To do this we should squash them into logical groups. E.g. TXFramework, artefact name changes and version numbers.
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1478) Squash all 5_BRANCH commits into logical groups
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1478?page=com.atlassian.jira.plugin.... ]
Paul Robinson resolved JBTM-1478.
---------------------------------
Resolution: Done
> Squash all 5_BRANCH commits into logical groups
> -----------------------------------------------
>
> Key: JBTM-1478
> URL: https://issues.jboss.org/browse/JBTM-1478
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Application Server Integration
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 1 hour
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> Before we raise a pull request for our AS changes to M2, we need to reduce the number of commits. To do this we should squash them into logical groups. E.g. TXFramework, artefact name changes and version numbers.
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1483) Add TXFramework support to XTS Subsystem
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1483?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1483:
--------------------------------
Description: This is an umbrella issue for all the issues that were squashed into one commit in preperation for raising a pull request on the AS. (was: This is an umbrella issue for all the issues that were squashed into one commit in preperation for )
> Add TXFramework support to XTS Subsystem
> ----------------------------------------
>
> Key: JBTM-1483
> URL: https://issues.jboss.org/browse/JBTM-1483
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Application Server Integration, TXFramework, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
>
> This is an umbrella issue for all the issues that were squashed into one commit in preperation for raising a pull request on 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
13 years, 1 month
[JBoss JIRA] (JBTM-1477) Migrate TXF subsytem contents into relavent transport subsytem
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1477?focusedWorklogId=12428716&page=... ]
Paul Robinson logged work on JBTM-1477:
---------------------------------------
Author: Paul Robinson
Created on: 21/Feb/13 9:42 AM
Start Date: 21/Feb/13 9:42 AM
Worklog Time Spent: 4 hours
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 4 hours)
Time Spent: 4 hours
Worklog Id: (was: 12428716)
> Migrate TXF subsytem contents into relavent transport subsytem
> --------------------------------------------------------------
>
> Key: JBTM-1477
> URL: https://issues.jboss.org/browse/JBTM-1477
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Application Server Integration, TXFramework, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 4 hours
> Time Spent: 4 hours
> Remaining Estimate: 0 minutes
>
> E.g.
> XTS stuff into xts subsytem and REST-AT stuff (when it exists) into the rts subsytem (when it exists).
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1482) If a naughty afterCompletion sync throws an exception, log the exception call stack
by Scott Marlow (JIRA)
Scott Marlow created JBTM-1482:
----------------------------------
Summary: 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: Feature Request
Security Level: Public (Everyone can see)
Components: Transaction Core
Reporter: Scott Marlow
Assignee: Tom Jenkinson
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
13 years, 1 month