[
https://issues.apache.org/jira/browse/OOZIE-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17647570#comment-17647570
]
ASF subversion and git services commented on OOZIE-3688:
--------------------------------------------------------
Commit e78ffb56310f4bee7ac053a448b2f25437f22321 in oozie's branch
refs/heads/master from Denes Bodo
[ https://gitbox.apache.org/repos/asf?p=oozie.git;h=e78ffb563 ]
OOZIE-3688 Introduce retry mechanism when starting embedded servlet containers
in unit tests (jmakai via dionusos)
> Introduce retry mechanism when starting embedded servlet containers in unit
> tests
> ---------------------------------------------------------------------------------
>
> Key: OOZIE-3688
> URL: https://issues.apache.org/jira/browse/OOZIE-3688
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 5.2.1
> Reporter: Janos Makai
> Assignee: Janos Makai
> Priority: Major
> Attachments: OOZIE-3688-001.patch
>
>
> In the unit tests which uses the embedded servlet container an intermittent
> issue can occur without this change, because those tests start the container
> on a specific port, which is available at the start of the unit tests.
> However, in some corner cases, it can happen that the port is being available
> at the start of the test, but some process occupies that port meanwhile,
> leading to a `java.net.BindException: Address already in use` exception
> during the unit test's execution.
> The goal of this ticket is resolve this by introducing a retry mechanism when
> starting the embedded servlet container.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
