[JBoss JIRA] (JBTM-2429) Disable java debugger in the surefire tests
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-2429?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris commented on JBTM-2429:
---------------------------------------
In WildFly testsuite there is a debug profile which can be enabled via system property
> 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-2431) Arquillian failures due to version mismatches
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2431?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2431:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Arquillian failures due to version mismatches
> ---------------------------------------------
>
> Key: JBTM-2431
> URL: https://issues.jboss.org/browse/JBTM-2431
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> We were getting failures with the current versions of Arquillian WildFly Managed Container Adapter and Arquillian Core when using the current wildfly master branch. This was because we were using incompatible versions which I have just fixed (commit dab8736):
> bq. Arquillian WildFly Managed Container Adapter 1.0.0.Alpha5 is built with Arquillian Core - 1.1.7.Final
> But the osgi tests need to run with karaf and the most recent arquillian osgi karaf container was built with Arquillian Core 1.1.2.Final. So I will fix it by updating the osgi pom to use that version of arquillian core:
> bq. 2.1.0.CR15 is built with Arquillian Core - 1.1.2.Final and ShrinkWrap - 1.1.2
> The version compatibility details are: [WildFly Managed Container Adapter | http://arquillian.org/modules/wildfly-arquillian-wildfly-managed-containe...] and [arquillian osgi karaf container |http://arquillian.org/modules/arquillian-osgi-karaf-embedded-container-adapter]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (JBTM-2409) XARecoveryModuleHelpersUnitTest hang
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2409?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2409:
-----------------------------------
Fix Version/s: 5.later
(was: 5.next)
> XARecoveryModuleHelpersUnitTest hang
> ------------------------------------
>
> Key: JBTM-2409
> URL: https://issues.jboss.org/browse/JBTM-2409
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Recovery
> Affects Versions: 5.1.1
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.later
>
> Attachments: 32287.jstack
>
>
> The test checks that recovery helpers can be removed at the correct stages during recovery scans. The CI job http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/196 shows the hang.
> The junit test thread:
> - starts 2 threads that will remove a recovery helper
> - triggers xaRecoveryModule.periodicWorkFirstPass()
> - triggers xaRecoveryModule.periodicWorkSecondPass()
> - joins with remover threads
> The jstack output shows:
> - the two threads in the process of removing a recovery helper and are waiting for the first pass to finish;
> - the junit test thread is waiting to join with these two threads;
> Since both recovery passes must have completed it looks like the remover threads weren't notified when the first pass completed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (JBTM-2431) Arquillian failures due to version mismatches
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2431?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2431:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstm/narayana/pull/867
> Arquillian failures due to version mismatches
> ---------------------------------------------
>
> Key: JBTM-2431
> URL: https://issues.jboss.org/browse/JBTM-2431
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> We were getting failures with the current versions of Arquillian WildFly Managed Container Adapter and Arquillian Core when using the current wildfly master branch. This was because we were using incompatible versions which I have just fixed (commit dab8736):
> bq. Arquillian WildFly Managed Container Adapter 1.0.0.Alpha5 is built with Arquillian Core - 1.1.7.Final
> But the osgi tests need to run with karaf and the most recent arquillian osgi karaf container was built with Arquillian Core 1.1.2.Final. So I will fix it by updating the osgi pom to use that version of arquillian core:
> bq. 2.1.0.CR15 is built with Arquillian Core - 1.1.2.Final and ShrinkWrap - 1.1.2
> The version compatibility details are: [WildFly Managed Container Adapter | http://arquillian.org/modules/wildfly-arquillian-wildfly-managed-containe...] and [arquillian osgi karaf container |http://arquillian.org/modules/arquillian-osgi-karaf-embedded-container-adapter]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (JBTM-2431) Arquillian failures due to version mismatches
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2431?page=com.atlassian.jira.plugin.... ]
Michael Musgrove reassigned JBTM-2431:
--------------------------------------
Assignee: Michael Musgrove (was: Tom Jenkinson)
> Arquillian failures due to version mismatches
> ---------------------------------------------
>
> Key: JBTM-2431
> URL: https://issues.jboss.org/browse/JBTM-2431
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> We were getting failures with the current versions of Arquillian WildFly Managed Container Adapter and Arquillian Core when using the current wildfly master branch. This was because we were using incompatible versions which I have just fixed (commit dab8736):
> bq. Arquillian WildFly Managed Container Adapter 1.0.0.Alpha5 is built with Arquillian Core - 1.1.7.Final
> But the osgi tests need to run with karaf and the most recent arquillian osgi karaf container was built with Arquillian Core 1.1.2.Final. So I will fix it by updating the osgi pom to use that version of arquillian core:
> bq. 2.1.0.CR15 is built with Arquillian Core - 1.1.2.Final and ShrinkWrap - 1.1.2
> The version compatibility details are: [WildFly Managed Container Adapter | http://arquillian.org/modules/wildfly-arquillian-wildfly-managed-containe...] and [arquillian osgi karaf container |http://arquillian.org/modules/arquillian-osgi-karaf-embedded-container-adapter]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (JBTM-2431) Arquillian failures due to version mismatches
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-2431:
--------------------------------------
Summary: Arquillian failures due to version mismatches
Key: JBTM-2431
URL: https://issues.jboss.org/browse/JBTM-2431
Project: JBoss Transaction Manager
Issue Type: Bug
Reporter: Michael Musgrove
Assignee: Tom Jenkinson
We were getting failures with the current versions of Arquillian WildFly Managed Container Adapter and Arquillian Core when using the current wildfly master branch. This was because we were using incompatible versions which I have just fixed (commit dab8736):
bq. Arquillian WildFly Managed Container Adapter 1.0.0.Alpha5 is built with Arquillian Core - 1.1.7.Final
But the osgi tests need to run with karaf and the most recent arquillian osgi karaf container was built with Arquillian Core 1.1.2.Final. So I will fix it by updating the osgi pom to use that version of arquillian core:
bq. 2.1.0.CR15 is built with Arquillian Core - 1.1.2.Final and ShrinkWrap - 1.1.2
The version compatibility details are: [WildFly Managed Container Adapter | http://arquillian.org/modules/wildfly-arquillian-wildfly-managed-containe...] and [arquillian osgi karaf container |http://arquillian.org/modules/arquillian-osgi-karaf-embedded-container-adapter]
--
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 Tomasz Adamski (JIRA)
[ https://issues.jboss.org/browse/JBTM-2430?page=com.atlassian.jira.plugin.... ]
Tomasz Adamski edited comment on JBTM-2430 at 6/9/15 11:53 AM:
---------------------------------------------------------------
After your fix it is no longer necessary as no runner will perform any ORB operation after run method returns. As a result of that I decided to revert it.
was (Author: tomekadamski):
After your fix it is no longer necessary as no runner will perform any ORB 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-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 edited comment on JBTM-2430 at 6/9/15 11:53 AM:
---------------------------------------------------------------
After your fix it is no longer necessary as no runner will perform any ORB operation after run method returns. As a result of that I decided to remove it.
was (Author: tomekadamski):
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