[
https://issues.apache.org/jira/browse/ARTEMIS-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16188560#comment-16188560
]
ASF GitHub Bot commented on ARTEMIS-1443:
-----------------------------------------
Github user ryeats commented on the issue:
https://github.com/apache/activemq-artemis/pull/1565
If you add ?protocols=CORE to the artemis.xml rebuild and then run
ArtemisFeatureTest it will fail because artemis doesn't start. Since I added
that in this PR it will be tested going forward.
Also Ill explain more since their could be a better solution. CORE protocol
isn't registered as a service factory like the other protocols its just
[manually
registered](https://github.com/apache/activemq-artemis/blob/master/artemis-server/src/main/java/org/apache/activemq/artemis/core/remoting/server/impl/RemotingServiceImpl.java#L150-L152).
This causes an issue in the ProtocolTracker since OSGi will see the other
Protocols that are registered using the java ServiceLoader but since CORE isn't
ProtocolTracker will never start artemis because it is waiting for CORE.
> When running Artemis in OSGI specifying CORE protocol causes it not to start
> ----------------------------------------------------------------------------
>
> Key: ARTEMIS-1443
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1443
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: osgi
> Affects Versions: 1.5.1, 2.0.0
> Reporter: Ryan Yeats
>
> if you specify CORE in the artemis.xml artemis doesn't start and you get a
> message "Required protocol was added for broker local. Still waiting for
> [CORE]"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
