[
https://issues.apache.org/jira/browse/ARTEMIS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140038#comment-15140038
]
ASF subversion and git services commented on ARTEMIS-388:
---------------------------------------------------------
Commit ece5d81e3d835367927db9adec8f7ff5b654eab0 in activemq-artemis's branch
refs/heads/master from Clebert Suconic
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=ece5d81 ]
ARTEMIS-388 fixing testsuite
(the socket.bind not being closed was preventing other tests to run
successfully)
> No obvious way to discover whether an embedded server actually started OK or
> not
> --------------------------------------------------------------------------------
>
> Key: ARTEMIS-388
> URL: https://issues.apache.org/jira/browse/ARTEMIS-388
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Mike Hearn
> Assignee: Justin Bertram
>
> If I use the embedded Artemis API, then if the port it's listening on is
> taken the server still "starts" correctly, but with the most important
> component in a failed state! I would like to abort the startup of my app in
> case something like this happens but I wasn't able to figure out from the
> documentation how to actually check if all the requested
> connectors/bridges/etc are all functioning correctly or if an exception was
> thrown (I can see the exception in the logs, of course).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
