[
https://issues.apache.org/jira/browse/DERBY-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004889#comment-13004889
]
Kathey Marsden commented on DERBY-4852:
---------------------------------------
I am wondering if there is a scenario where
TestConfiguration.getNextAvailablePort() might get called in parallel. Since as
far as I can tell, the first failure occurs when we should be using the port
for the first time, I don't think it could hurt to synchronize access. Even if
that's not the problem it would be good in case there is some scenario of
parallel use in the future.
> Lots of failures with Connection Refused, starting with
> JMXtest.testDerbyRegisteredMBeansSimpleInfo on 10.6.2.3(1022806) codeline
> while running Junit suite with ibm16 on windows machine
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4852
> URL: https://issues.apache.org/jira/browse/DERBY-4852
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3
> Reporter: Mamta A. Satoor
> Assignee: Kathey Marsden
> Labels: derby_triage10_8
> Attachments: 1022806-suites.All_diff.txt
>
>
> Last night's run of Junit with ibm16 on 10.6.2.3(1022806) codeline had 50
> failures which all seem to be related to not being able to open a connection
> to the localhost. The link to that run can be found at
> http://people.apache.org/~myrnavl/derby_test_results/v10_6/windows/testSummary-1022806.html
> I will also attach the result of the run to this jira.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
