You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2016/02/17 16:45:18 UTC

[jira] [Resolved] (ARTEMIS-388) No obvious way to discover whether an embedded server actually started OK or not

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

Justin Bertram resolved ARTEMIS-388.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.0

> 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
>             Fix For: 1.3.0
>
>
> 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)