[
https://issues.apache.org/jira/browse/ARTEMIS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137740#comment-15137740
]
ASF GitHub Bot commented on ARTEMIS-388:
----------------------------------------
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/381
ARTEMIS-388 listen for activation failures
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-388
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/381.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #381
----
commit 8cecaed528a472280e7ba12465e58c166e3de3a9
Author: jbertram <jbert...@apache.org>
Date: 2016-02-05T18:11:21Z
ARTEMIS-388 listen for activation failures
----
> 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)
