Hi ESB Team,
I am testing new fearure called "JMS 2.0.0 Support"[1] and found an error
in "JMS 2.0 Feature:Shared Topic Subscription". Feature will successfully
functioning in Standalone mode. But it clustering mode, it will provide an
error as follows;
TID: [-1234] [] [2016-02-24 15:30:13,451] WARN
{org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer} -
Inbound JMS endpoint unable to get a connection.
{org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer}
TID: [-1234] [] [2016-02-24 15:30:14,451] ERROR
{org.wso2.carbon.inbound.endpoint.protocol.jms.factory.JMSConnectionFactory}
- Connection cannot bb establish to the broke. Plese check the broker libs
provided.
{org.wso2.carbon.inbound.endpoint.protocol.jms.factory.JMSConnectionFactory}
This error will pop up from worker nodes. When clustering mode disabled, it
will work properly.
Is there any special configuration for HornetQ when ESB in clustering mode?
As I found out, HornetQ "run.sh" script must modify to bind its' host name.
Likewise is there any special configurations for ESB cluster ?
Thank you in advance.
[1] - https://redmine.wso2.com/issues/4121
--
Best Regards,
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F&sa=D&sntz=1&usg=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware
Mobile: +94773375185
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
