[
https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055685#comment-13055685
]
Myrna van Lunteren commented on DERBY-5288:
-------------------------------------------
Forgot to mention there were some additional stack traces, which apparently did
not result in test errors or failures.
For instance, there was a 'java.net.SocketException: Connection reset' in both
the 10.8 and trunk ibm1.5 runs in testReplication_Local_3_p5_DERBY_3878, which
looks the same as one encountered by Kathey (as per a comment in DERBY-4565:
https://issues.apache.org/jira/browse/DERBY-4564?focusedCommentId=12837564&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12837564).
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.5, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff, join-threads.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a
> different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread:
> http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
