Hi,
Yes it might cause problems in long run. Some cleanup process to subscribe
to the ping topic and discard might be useful.
Touched, not typed. Erroneous words are a feature, not a typo.
On May 11, 2014 8:55 AM, "Amila Maha Arachchi" <ami...@wso2.com> wrote:
> Hi Devs,
>
> I am working with a Stratos deployment these days. In our deployment, we
> are using WSO2 Message Broker as the message broker. There I see the
> following log getting printed very frequently (every second).
>
> TID: [0] [MB] [2014-05-05 08:31:52,352] INFO
> {org.wso2.andes.server.exchange.TopicExchange} - Message routing key: ping
> No routes. {org.wso2.andes.server.exchange.TopicExchange}
>
> TID: [0] [MB] [2014-05-05 08:31:52,352] WARN
> {org.wso2.andes.server.AMQChannel} - MESSAGE DISCARDED: No routes for
> message - Message[(HC:449176483 ID:366318838955900928 Ref:0)]:
> 366318838955900928; ref count: 0 {org.wso2.andes.server.AMQChannel}
>
> TID: [0] [MB] [2014-05-05 08:31:52,621] INFO
> {org.wso2.andes.server.exchange.TopicExchange} - Message routing key: ping
> No routes. {org.wso2.andes.server.exchange.TopicExchange}
>
> TID: [0] [MB] [2014-05-05 08:31:52,621] WARN
> {org.wso2.andes.server.AMQChannel} - MESSAGE DISCARDED: No routes for
> message - Message[(HC:1522105342 ID:366318839026417664 Ref:0)]:
> 366318839026417664; ref count: 0 {org.wso2.andes.server.AMQChannel}
>
> I came to know that this is due to a mechanism used to check whether the
> Message Broker (MB) is alive. i.e. subscribers publish an event to this
> "ping" topic to see whether the MB is alive, but no one is consuming it.
> Thats why the above log is getting printed.
>
> Since no one is consuming this messages, is it possible that MB gets
> loaded with this message and cause problems?
>
> Regards,
> Amila.
>
> --
> *Amila Maharachchi*
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>
