activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (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, 08 Feb 2016 22:28:39 GMT

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

ASF GitHub Bot commented on ARTEMIS-388:
----------------------------------------

Github user clebertsuconic commented on the pull request:

    https://github.com/apache/activemq-artemis/pull/381#issuecomment-181599074
  
    @mikehearn  good point actually :) :+1: 


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

Mime
View raw message