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 2016/03/17 16:07:33 UTC
[jira] [Closed] (UIMA-4773) UIMA DUCC: JP throws BindException on
startup if port is not available
[ https://issues.apache.org/jira/browse/UIMA-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-4773.
-------------------------------
Resolution: Fixed
Modified Agent and JP to stop using Socket for private socket channel for communicating STOP requests. Instead an agent sends SIGTERM to force JP to stop
> UIMA DUCC: JP throws BindException on startup if port is not available
> ----------------------------------------------------------------------
>
> Key: UIMA-4773
> URL: https://issues.apache.org/jira/browse/UIMA-4773
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.1.0-Ducc
>
>
> On startup a JP throws
> java.net.BindException: Address already in use
> A JP starts a Camel route on a socket to listen for agent STOP requests. This route can fail if a socket port is not available.
> Change Agent to send SIGTERM signal to JP to force an orderly shutdown instead of sending a STOP request over a dedicated socket channel. with this change, the JP no longer needs to create a Camel route over socket listener. Instead it just needs to catch the SIGTERM signal, quiesce and stop.
> The Agent will send SIGKILL (-9) to a process that refuses to stop for SIGTERM.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)