You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Ryan Yeats (JIRA)" <ji...@apache.org> on 2016/12/19 18:16:58 UTC
[jira] [Comment Edited] (ARTEMIS-895) Osgi multi protocol acceptor
race condition
[ https://issues.apache.org/jira/browse/ARTEMIS-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15761882#comment-15761882 ]
Ryan Yeats edited comment on ARTEMIS-895 at 12/19/16 6:16 PM:
--------------------------------------------------------------
In the 1.5.1 default broker.xml it looks like artemis is moving towards requiring all protocols be specified so the simplest solution may be to be able to use CORE as a protocol in OSGI. Currently it hangs and never starts if CORE is in the protocols list.
2016-12-19 11:09:59,811 | INFO | 941-e9b1f8fc1345 | ProtocolTracker | emq.artemis.osgi.ProtocolTracker 93 | 302 - org.apache.activemq.artemis-server-osgi - 1.5.1 | Required protocol OPENWIRE was added for broker local. Still waiting for [CORE]
was (Author: ryeats):
In the 1.5.1 default broker.xml it looks like artemis is moving towards requiring all protocols be specified so I think the solution may be to be able to use CORE as a protocol in OSGI. Currently it hangs and never starts if CORE is in the protocols list.
2016-12-19 11:09:59,811 | INFO | 941-e9b1f8fc1345 | ProtocolTracker | emq.artemis.osgi.ProtocolTracker 93 | 302 - org.apache.activemq.artemis-server-osgi - 1.5.1 | Required protocol OPENWIRE was added for broker local. Still waiting for [CORE]
> Osgi multi protocol acceptor race condition
> -------------------------------------------
>
> Key: ARTEMIS-895
> URL: https://issues.apache.org/jira/browse/ARTEMIS-895
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: osgi
> Affects Versions: 1.5.1
> Reporter: Ryan Yeats
>
> Artemis running inside of karaf has issues if the protocol doesn't have a acceptor specificly defined. On startup it is possible that it won't get added to the multi protocol acceptor if the bundle doesn't start up in time. This would be a minor issue but currenly the CORE protocol is not accepted on ports with defined protocols and CORE can't be added as a protocol so it creates alot of confusion if CORE and another protocol are being used when trying to setup acceptors.
> to reproduce remove all the acceptors besides the multi protocol acceptor and restart karaf
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)