-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.18.3, 2.19.0
-
Fix Version/s: 2.19.0
-
Component/s: camel-coap
-
Labels:None
-
Estimated Complexity:Unknown
If I configure a simple camel-coap consumer endpoint like:
from("coap://localhost:8080/foo")
Logging reveals that two server instances were started:
[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
This 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().
- links to