[jira] [Resolved] (CAMEL-11177) CoAP component starts redundant server instance

["Andrea Cosentino (JIRA)" <ji...@apache.org>]

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

Andrea Cosentino resolved CAMEL-11177.
--------------------------------------
    Resolution: Fixed

> CoAP component starts redundant server instance
> -----------------------------------------------
>
>                 Key: CAMEL-11177
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11177
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-coap
>    Affects Versions: 2.18.3, 2.19.0
>            Reporter: James Netherton
>            Assignee: Andrea Cosentino
>             Fix For: 2.19.0
>
>
> If I configure a simple camel-coap consumer endpoint like:
> {code}
> from("coap://localhost:8080/foo")
> {code}
> Logging reveals that two server instances were started:
> {code}
> [org.eclipse.californium.core.network.CoapEndpoint] (pool-3-thread-1) Stopping endpoint at address 0.0.0.0/0.0.0.0:52697
> [org.eclipse.californium.core.network.CoapEndpoint] (pool-3-thread-1) Stopping endpoint at address 0.0.0.0/0.0.0.0:8080 
> {code}
> [This|https://github.com/apache/camel/blob/master/components/camel-coap/src/main/java/org/apache/camel/coap/CoAPComponent.java#L148-L153] appears to be the logic that causes the behaviour. 
> Do we need it? It seems to be a duplicate of what already happens in {{createConsumer()}}. Also, the creation of a default server can easily be done in the {{createServer()}} method, I don't think we need it in {{doStart()}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)