[JBoss JIRA] (JBTM-1206) Intermittent XTS CR bug
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1206?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1206:
--------------------------------
Priority: Minor (was: Major)
> Intermittent XTS CR bug
> -----------------------
>
> Key: JBTM-1206
> URL: https://issues.jboss.org/browse/JBTM-1206
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, XTS
> Reporter: Tom Jenkinson
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 4.17.4
>
>
> http://172.17.131.2/job/narayana-java7-idlj/51/
> [INFO] Surefire report directory: /home/hudson/workspace/narayana-java7-idlj/XTS/localjunit/crash-recovery-tests/target/surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running com.arjuna.qa.junit.TestATCrashDuringCommit
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 371.769 sec
> Running com.arjuna.qa.junit.TestATCrashDuringOnePhaseCommit
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 66.163 sec
> Running com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 369.915 sec
> Running com.arjuna.qa.junit.TestATParticipantCrashAndRecover
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 0 sec
> Running com.arjuna.qa.junit.TestATSubordinateCrashDuringCommit
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 149.636 sec
> Running com.arjuna.qa.junit.TestATSubordinateCrashDuringPrepare
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 74.689 sec
> Running com.arjuna.qa.junit.TestBACrashDuringCommit
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,436.51 sec
> Running com.arjuna.qa.junit.TestBACrashDuringOnePhaseCommit
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 159.511 sec
> Running com.arjuna.qa.junit.TestBASubordinateCrashDuringCommit
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 320.848 sec
> Running com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 327.038 sec
> Running com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete
> Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 795.378 sec <<< FAILURE!
> Results :
> Tests in error:
> subordinateMultiParticipantParticipantCompletionParticipantCloseTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete): jboss-as not killed and shutdown
> Tests run: 26, Failures: 0, Errors: 1, Skipped: 3
--
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, 9 months
[JBoss JIRA] (JBTM-1145) TXFramework Code Tidy
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1145?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1145:
--------------------------------
Description:
Test restructuring
Try using annotations in subsystem
Move documentation out and flatten project
Make parent of Narayana
Test by default in managed container and log to file
Remove annotations and properties that are not used.
Remove System.out and System.err. For example:
{code}
15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleInboundMessage()
15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleOutboundMessage()
15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.close()
{code}
Refactor WSBA Handlers into one (Wrap the registration and completion into an object that switches based on participant type)
@Required to something that matched EJB TX annotation
was:
Code format
Test restructuring
Try using annotations in subsystem
Is JAXWSHandlerAnnotatonTest needed?
Move documentation out and flatten project
Make parent of Narayana
Test by default in managed container and log to file
Remove annotations and properties that are not used.
Remove System.out and System.err. For example:
{code}
15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleInboundMessage()
15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleOutboundMessage()
15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.close()
{code}
Refactor WSBA Handlers into one (Wrap the registration and completion into an object that switches based on participant type)
@Required to something that matched EJB TX annotation
> TXFramework Code Tidy
> ---------------------
>
> Key: JBTM-1145
> URL: https://issues.jboss.org/browse/JBTM-1145
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M3
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Test restructuring
> Try using annotations in subsystem
> Move documentation out and flatten project
> Make parent of Narayana
> Test by default in managed container and log to file
> Remove annotations and properties that are not used.
> Remove System.out and System.err. For example:
> {code}
> 15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
> 15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleInboundMessage()
> 15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
> 15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleOutboundMessage()
> 15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.close()
> {code}
> Refactor WSBA Handlers into one (Wrap the registration and completion into an object that switches based on participant type)
> @Required to something that matched EJB TX annotation
--
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, 9 months
[JBoss JIRA] (JBTM-1145) TXFramework Code Tidy Part 2
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1145?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1145:
--------------------------------
Summary: TXFramework Code Tidy Part 2 (was: TXFramework Code Tidy)
> TXFramework Code Tidy Part 2
> ----------------------------
>
> Key: JBTM-1145
> URL: https://issues.jboss.org/browse/JBTM-1145
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M3
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Test restructuring
> Try using annotations in subsystem
> Move documentation out and flatten project
> Make parent of Narayana
> Test by default in managed container and log to file
> Remove annotations and properties that are not used.
> Remove System.out and System.err. For example:
> {code}
> 15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
> 15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleInboundMessage()
> 15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
> 15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleOutboundMessage()
> 15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.close()
> {code}
> Refactor WSBA Handlers into one (Wrap the registration and completion into an object that switches based on participant type)
> @Required to something that matched EJB TX annotation
--
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, 9 months
[JBoss JIRA] (JBTM-1145) TXFramework Code Tidy Part 2
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1145?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1145:
--------------------------------
Fix Version/s: 5.0.0.M2
(was: 5.0.0.M3)
> TXFramework Code Tidy Part 2
> ----------------------------
>
> Key: JBTM-1145
> URL: https://issues.jboss.org/browse/JBTM-1145
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Test restructuring
> Try using annotations in subsystem
> Remove annotations and properties that are not used.
> Remove System.out and System.err. For example:
> {code}
> 15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
> 15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleInboundMessage()
> 15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
> 15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleOutboundMessage()
> 15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.close()
> {code}
> Add logging
> Refactor WSBA Handlers into one (Wrap the registration and completion into an object that switches based on participant type)
> @Required to something that matched EJB TX annotation
--
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, 9 months
[JBoss JIRA] (JBTM-1145) TXFramework Code Tidy Part 2
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1145?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1145:
--------------------------------
Description:
Test restructuring
Try using annotations in subsystem
Remove annotations and properties that are not used.
Remove System.out and System.err. For example:
{code}
15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleInboundMessage()
15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleOutboundMessage()
15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.close()
{code}
Add logging
Refactor WSBA Handlers into one (Wrap the registration and completion into an object that switches based on participant type)
@Required to something that matched EJB TX annotation
was:
Test restructuring
Try using annotations in subsystem
Move documentation out and flatten project
Make parent of Narayana
Test by default in managed container and log to file
Remove annotations and properties that are not used.
Remove System.out and System.err. For example:
{code}
15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleInboundMessage()
15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleOutboundMessage()
15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.close()
{code}
Refactor WSBA Handlers into one (Wrap the registration and completion into an object that switches based on participant type)
@Required to something that matched EJB TX annotation
> TXFramework Code Tidy Part 2
> ----------------------------
>
> Key: JBTM-1145
> URL: https://issues.jboss.org/browse/JBTM-1145
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M3
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Test restructuring
> Try using annotations in subsystem
> Remove annotations and properties that are not used.
> Remove System.out and System.err. For example:
> {code}
> 15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
> 15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleInboundMessage()
> 15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
> 15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleOutboundMessage()
> 15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.close()
> {code}
> Add logging
> Refactor WSBA Handlers into one (Wrap the registration and completion into an object that switches based on participant type)
> @Required to something that matched EJB TX annotation
--
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, 9 months