[ https://issues.jboss.org/browse/JBTM-2802?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson resolved JBTM-2802.
---------------------------------
Fix Version/s: 5.next
Assignee: Tom Jenkinson
Resolution: Done
> AtomicObject3.java hammer test hard to debug
> --------------------------------------------
>
> Key: JBTM-2802
> URL: https://issues.jboss.org/browse/JBTM-2802
> Project: JBoss Transaction Manager
> Issue Type: Task
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> As the test outputs to console with println and has many many threads it is too hard to debug. Use log4j.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[ https://issues.jboss.org/browse/JBTM-2801?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2801:
--------------------------------
Fix Version/s: 5.next
> ObjectStoreTest.java assumes that Uids are returned in order which is not guaranteed
> ------------------------------------------------------------------------------------
>
> Key: JBTM-2801
> URL: https://issues.jboss.org/browse/JBTM-2801
> Project: JBoss Transaction Manager
> Issue Type: Task
> Reporter: Tom Jenkinson
> Fix For: 5.next
>
>
> The object store API does not make guarantees about the order
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[ https://issues.jboss.org/browse/JBTM-2801?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson resolved JBTM-2801.
---------------------------------
Assignee: Tom Jenkinson
Resolution: Done
> ObjectStoreTest.java assumes that Uids are returned in order which is not guaranteed
> ------------------------------------------------------------------------------------
>
> Key: JBTM-2801
> URL: https://issues.jboss.org/browse/JBTM-2801
> Project: JBoss Transaction Manager
> Issue Type: Task
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> The object store API does not make guarantees about the order
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[ https://issues.jboss.org/browse/JBTM-2804?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson resolved JBTM-2804.
---------------------------------
Fix Version/s: 5.next
Assignee: Tom Jenkinson
Resolution: Done
> ObjStoreBrowserTest.java can miss a recovery scan
> -------------------------------------------------
>
> Key: JBTM-2804
> URL: https://issues.jboss.org/browse/JBTM-2804
> Project: JBoss Transaction Manager
> Issue Type: Task
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> As the ObjStoreBrowserTest.java uses a socket to ask for recovery from a threaded recovery manager it is possible that the recovery manager is just completing a scan and so the state the test expects will not be satisfied.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[ https://issues.jboss.org/browse/JBTM-2801?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2801:
--------------------------------
Component/s: Testing
> ObjectStoreTest.java assumes that Uids are returned in order which is not guaranteed
> ------------------------------------------------------------------------------------
>
> Key: JBTM-2801
> URL: https://issues.jboss.org/browse/JBTM-2801
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> The object store API does not make guarantees about the order
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[ https://issues.jboss.org/browse/JBTM-2800?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2800:
--------------------------------
Component/s: Testing
> Miscellaneous qa suite improvements
> -----------------------------------
>
> Key: JBTM-2800
> URL: https://issues.jboss.org/browse/JBTM-2800
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> Some of the tests are not easy to debug and during debug you have to constantly move your TaskImpl.properties out of the way so provide a way to get more logging and allow setting options such as remote debugger easier.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[ https://issues.jboss.org/browse/JBTM-2802?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2802:
--------------------------------
Component/s: Testing
> AtomicObject3.java hammer test hard to debug
> --------------------------------------------
>
> Key: JBTM-2802
> URL: https://issues.jboss.org/browse/JBTM-2802
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> As the test outputs to console with println and has many many threads it is too hard to debug. Use log4j.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[ https://issues.jboss.org/browse/JBTM-2803?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2803:
--------------------------------
Component/s: JTS
(was: Transaction Core)
> compareHierarchies traceln's wrong elements
> -------------------------------------------
>
> Key: JBTM-2803
> URL: https://issues.jboss.org/browse/JBTM-2803
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: JTS
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> If compareHierarchies is called (only done in trace iirc) then the right elements are compared but if they are not equal the wrong elements are compared IOOBE are possible.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[ https://issues.jboss.org/browse/JBTM-2804?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2804:
--------------------------------
Component/s: Testing
> ObjStoreBrowserTest.java can miss a recovery scan
> -------------------------------------------------
>
> Key: JBTM-2804
> URL: https://issues.jboss.org/browse/JBTM-2804
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> As the ObjStoreBrowserTest.java uses a socket to ask for recovery from a threaded recovery manager it is possible that the recovery manager is just completing a scan and so the state the test expects will not be satisfied.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[ https://issues.jboss.org/browse/JBTM-2803?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2803:
--------------------------------
Component/s: Transaction Core
> compareHierarchies traceln's wrong elements
> -------------------------------------------
>
> Key: JBTM-2803
> URL: https://issues.jboss.org/browse/JBTM-2803
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Transaction Core
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> If compareHierarchies is called (only done in trace iirc) then the right elements are compared but if they are not equal the wrong elements are compared IOOBE are possible.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)