Hi Imesh, I will work on this issue.
Thank you and Regards On Mon, Oct 27, 2014 at 10:13 PM, Chamila De Alwis <chami...@wso2.com> wrote: > Hi Imesh, > > Additionally I've observed the following related to the messaging > component change. For automated install, we specify the MB_PORT in the > setup.conf file as 1883 for MQTT. setup.sh uses this value for the > "java.naming.provider.url" in > repository/deployment/server/outputeventadaptors/JMSOutputAdaptor.xml. CEP > uses this value to publish events and fails, because it uses the old > messaging model, which publishes to 61616. > > I think we need to introduce a new field to the setup conf for MQTT port > and AMQP port. > > > Regards, > Chamila de Alwis > Software Engineer | WSO2 | +94772207163 > Blog: code.chamiladealwis.com > > > > On Mon, Oct 27, 2014 at 9:55 PM, Imesh Gunaratne <im...@apache.org> wrote: > >> Hi, >> >> This issue was identified while we were fixing MQTT library dependencies >> in the load balancer. It seems like we have not configured Paho MQTT >> logging in any of the stratos components. >> >> The result is that we do not see any of the errors raised by the MQTT >> libarary. In the load balancer it was throwing a class not found exception >> but it was not visible in the log due to this reason. >> >> https://issues.apache.org/jira/browse/STRATOS-914 >> https://wiki.eclipse.org/Paho/Log_and_Debug_in_the_Java_client >> >> Thanks >> >> -- >> Imesh Gunaratne >> >> Technical Lead, WSO2 >> Committer & PMC Member, Apache Stratos >> > > -- *Vishanth Balasubramaniam* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94771737718* about me: *http://about.me/vishanth <http://about.me/vishanth>*
