jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3385) DbClusterTest fails when port is already in use
Date Thu, 12 Jul 2012 13:30:35 GMT

    [ https://issues.apache.org/jira/browse/JCR-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412775#comment-13412775

Thomas Mueller commented on JCR-3385:

The problem is that the ports are also hardcoded in the repository-h2.xml file.

The easiest solution is probably to use a non-clustered, embedded database stored in the parent
directory if the cluster nodes.
> DbClusterTest fails when port is already in use
> -----------------------------------------------
>                 Key: JCR-3385
>                 URL: https://issues.apache.org/jira/browse/JCR-3385
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: clustering, jackrabbit-core
>    Affects Versions: 2.5
>            Reporter: Jukka Zitting
>            Assignee: Thomas Mueller
>            Priority: Minor
>         Attachments: 0001-JCR-3385-DbClusterTest-fails-when-port-is-already-in.patch
> The DbClusterTest and DbClusterTestJCR3162 classes use hard-coded TCP port numbes 9001
and 9002 which make the tests fail whenever there already is some process listening on those
> It would be better if the classes automatically looked for unused ports for the tests.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message