You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2015/07/16 22:17:04 UTC

[jira] [Updated] (UIMA-4514) DUCC JP fails with SocketException Addreas Already Bound

     [ https://issues.apache.org/jira/browse/UIMA-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik updated UIMA-4514:
--------------------------------
    Component/s: DUCC

> DUCC JP fails with SocketException Addreas Already Bound
> --------------------------------------------------------
>
>                 Key: UIMA-4514
>                 URL: https://issues.apache.org/jira/browse/UIMA-4514
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.0.0-Ducc
>
>
> When deploying JPs for a DD job on the same node there is a chance of race when two JPs deploy embedded broker using the same port. The code is expecting BindException to handle a port that is not available, The JVM actually throws SocketException with a message Address already in use. Modify code to check for SocketException and the above message and on match retry with another port until success



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)