[
https://issues.apache.org/jira/browse/CAMEL-9493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111277#comment-15111277
]
Quinn Stevenson commented on CAMEL-9493:
----------------------------------------
I still can't reproduce the error in order to diagnose the test failures. I've
tried Vagrant boxes using CentOS 7 and Ubuntu 14.04 - both give me the same
results - i.e. the tests alway pass.
I can't quite figure out how this is happening at all. The unit tests use the
AvailablePortFinder to ensure a port is there, so I don't know how I"m getting
the BindException unless the Jenkins build servers are enough faster than my
systems that the AvailablePortFinder close() and the bind() call from the MLLP
component are happening close enough together to cause the issue.
While looking at the code, I think I can improve the socket cleanup a little
more. Also, I'm going to implement the "bindTimeout" option - it's already
declared in the endpoint but is currently unused. That should fix the tests -
but since I can't reproduce it locally, I'll have to wait until the PR I'm
working on is merged to see for sure.
> camel-mllp - Use dynamic assigned port number for testing
> ---------------------------------------------------------
>
> Key: CAMEL-9493
> URL: https://issues.apache.org/jira/browse/CAMEL-9493
> Project: Camel
> Issue Type: Test
> Components: camel-mllp
> Reporter: Claus Ibsen
> Fix For: 2.17.0
>
>
> We should use dynamic ports instead of hardcoded, as the latter causes CI
> servers and the likes to fail with "Address already in use" errors.
> See how camel-hl7 / camel-mina2 etc assign dynamic ports in their tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
