[JBoss JIRA] (JBTM-2430) Update openjdk-orb library to 8.0.4.Final
by Tomasz Adamski (JIRA)
[ https://issues.jboss.org/browse/JBTM-2430?page=com.atlassian.jira.plugin.... ]
Tomasz Adamski commented on JBTM-2430:
--------------------------------------
After your fix it is no longer necessary as no runner will perform any operation after run method returns. As a result of that I decided to remove it.
> Update openjdk-orb library to 8.0.4.Final
> -----------------------------------------
>
> Key: JBTM-2430
> URL: https://issues.jboss.org/browse/JBTM-2430
> Project: JBoss Transaction Manager
> Issue Type: Component Upgrade
> Reporter: Michael Musgrove
> Assignee: Tomasz Adamski
>
> openjdk-orb library needs updating to 8.0.4.Final which reverts a change made in 8.0.2.Final that allowed runner threads to finish before shutdown.
> Tomek I cannot find any reference to why you reverted the change - do you have one?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (JBTM-2429) Disable java debugger in the surefire tests
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2429?page=com.atlassian.jira.plugin.... ]
Michael Musgrove resolved JBTM-2429.
------------------------------------
Resolution: Done
> Disable java debugger in the surefire tests
> -------------------------------------------
>
> Key: JBTM-2429
> URL: https://issues.jboss.org/browse/JBTM-2429
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Affects Versions: 5.1.1
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Optional
> Fix For: 5.next
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> We are having intermittent problems with arquillian tests on the mac that start containers one after the other. It seems that a previous one is slow to shut down causing the next one to fail to start with
> {code}
> ERROR: transport error 202: bind failed: Address already in use
> JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized
> {code}
> I plan to disable the debugger (I think we enabled it because of a hang on an old issue where we needed the debugger port open to aid diagnosis).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (JBTM-2430) Update openjdk-orb library to 8.0.4.Final
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-2430:
--------------------------------------
Summary: Update openjdk-orb library to 8.0.4.Final
Key: JBTM-2430
URL: https://issues.jboss.org/browse/JBTM-2430
Project: JBoss Transaction Manager
Issue Type: Component Upgrade
Reporter: Michael Musgrove
Assignee: Tomasz Adamski
openjdk-orb library needs updating to 8.0.4.Final which reverts a change made in 8.0.2.Final that allowed runner threads to finish before shutdown.
Tomek I cannot find any reference to why you reverted the change - do you have one?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (JBTM-2421) Provide some quickstarts for STM
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2421?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2421:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Provide some quickstarts for STM
> --------------------------------
>
> Key: JBTM-2421
> URL: https://issues.jboss.org/browse/JBTM-2421
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Demonstrator, STM
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> As part of my JBug I took the example from the documentation and produced a set of quickstarts that would be useful to contribute to the project.
> The examples show:
> 1. Pessimistic locking
> 2. Optimistic locking
> 3. Use of an STM object in a JTA transaction
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (JBTM-2416) OSGiJTATest #testTransactionManager failed
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2416?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2416:
--------------------------------
Fix Version/s: 5.later
(was: 5.next)
> OSGiJTATest #testTransactionManager failed
> ------------------------------------------
>
> Key: JBTM-2416
> URL: https://issues.jboss.org/browse/JBTM-2416
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: JTA
> Reporter: Gytis Trikleris
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.later
>
>
> http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/837/PROFIL...
> {code}
> Running org.jboss.narayana.osgi.jta.OSGiJTATest
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.09 sec <<< FAILURE!
> testTransactionManager(org.jboss.narayana.osgi.jta.OSGiJTATest) Time elapsed: 0.003 sec <<< FAILURE!
> java.lang.AssertionError: Bundle ACTIVE expected:<32> but was:<4>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.jboss.narayana.osgi.jta.OSGiJTATest.testTransactionManager(OSGiJTATest.java:81)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.... ]
Michael Musgrove resolved JBTM-2308.
------------------------------------
Resolution: Done
> New JTS record types are not showing up in the tooling
> ------------------------------------------------------
>
> Key: JBTM-2308
> URL: https://issues.jboss.org/browse/JBTM-2308
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: Tooling
> Affects Versions: 4.17.23, 5.0.3
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.next, 5.1.0, 4.17.27
>
>
> When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record.
> I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it).
> What is missing is instrumentation for new types:
> {code}
> AssumedCompleteHeuristicTransaction
> AssumedCompleteHeuristicServerTransaction
> AssumedCompleteTransaction
> AssumedCompleteServerTransaction
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (JBTM-2429) Disable java debugger in the surefire tests
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2429?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2429:
-------------------------------------
I am not sure how easy this will be but is it possible to leave it as a system property where we can enable it? e.g. -DenableDebugger
> Disable java debugger in the surefire tests
> -------------------------------------------
>
> Key: JBTM-2429
> URL: https://issues.jboss.org/browse/JBTM-2429
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Affects Versions: 5.1.1
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Optional
> Fix For: 5.next
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> We are having intermittent problems with arquillian tests on the mac that start containers one after the other. It seems that a previous one is slow to shut down causing the next one to fail to start with
> {code}
> ERROR: transport error 202: bind failed: Address already in use
> JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized
> {code}
> I plan to disable the debugger (I think we enabled it because of a hang on an old issue where we needed the debugger port open to aid diagnosis).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months