activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Hearn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-388) No obvious way to discover whether an embedded server actually started OK or not
Date Mon, 20 Jun 2016 13:10:05 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339452#comment-15339452
] 

Mike Hearn commented on ARTEMIS-388:
------------------------------------

Thanks guys! We have upgraded internally and are now benefiting from this feature.

> 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)

Mime
View raw message