You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Udara Liyanage <ud...@wso2.com> on 2014/11/10 10:06:29 UTC
MQTT connection lost problem in master branch
Hi Imesh,
Hi got the following error in master branch when an application is
undeployed.
Please note that I got the packs built today morning.
[2014-11-10 10:52:55,292] INFO
{org.apache.stratos.messaging.domain.topology.lifecycle.LifeCycleStateManager}
- Topology element [ mysql-only-app2 ]'s life Cycle State changed from [
Created ] to [ Active ]
[2014-11-10 11:04:41,163] INFO
{org.apache.stratos.autoscaler.applications.topic.ApplicationBuilder} -
Handling application terminating event: [application-id] mysql-only-app2
[2014-11-10 11:04:41,166] INFO
{org.apache.stratos.autoscaler.applications.topic.ApplicationBuilder} -
Updating application status: [application-id] mysql-only-app2 [status]
Terminating
[2014-11-10 11:04:41,166] INFO
{org.apache.stratos.messaging.domain.topology.lifecycle.LifeCycleStateManager}
- Topology element [ mysql-only-app2 ]'s life Cycle State changed from [
Active ] to [ Terminating ]
[2014-11-10 11:04:41,166] INFO
{org.apache.stratos.autoscaler.monitor.application.ApplicationMonitor} -
[ApplicationMonitor] mysql-only-app2 state changes from Active to
Terminating
[2014-11-10 11:04:41,167] INFO
{org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher}
- Publishing Cluster Terminating event for [application]: mysql-only-app2
[cluster]: mymysql.mysql.domain
[2014-11-10 11:04:41,293] INFO
{org.apache.stratos.messaging.domain.topology.lifecycle.LifeCycleStateManager}
- Topology element [ mymysql.mysql.domain ]'s life Cycle State changed
from [ Active ] to [ Terminating ]
[2014-11-10 11:04:41,352] INFO
{org.apache.stratos.cloud.controller.topology.TopologyEventPublisher} -
Publishing Cluster terminating event: [appId] mysql-only-app2 [cluster id]
mymysql.mysql.domain
[2014-11-10 11:04:41,426] INFO
{org.apache.stratos.autoscaler.applications.topic.ApplicationsEventPublisher}
- Publishing Application activated event for [application]: mysql-only-app2
[2014-11-10 11:04:41,682] INFO
{org.apache.stratos.autoscaler.applications.topic.ApplicationsEventPublisher}
- Publishing Application terminated event for [application]:
mysql-only-app2
[2014-11-10 11:04:41,809] INFO
{org.apache.stratos.messaging.domain.topology.lifecycle.LifeCycleStateManager}
- Topology element [ mysql-only-app2 ]'s life Cycle State changed from [
Active ] to [ Terminating ]
[2014-11-10 11:41:01,011] INFO
{org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
re-publish in 60 sec
[2014-11-10 11:42:01,014] INFO
{org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
re-publish in 60 sec
[2014-11-10 11:42:22,569] WARN
{org.apache.stratos.messaging.message.receiver.applications.ApplicationsEventMessageListener}
-* Connection is lost*
*Timed out waiting for a response from the server (32000)*
* at
org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:27)*
* at
org.eclipse.paho.client.mqttv3.internal.ClientState.checkForActivity(ClientState.java:541)*
* at
org.eclipse.paho.client.mqttv3.internal.ClientState.get(ClientState.java:592)*
* at
org.eclipse.paho.client.mqttv3.internal.CommsSender.run(CommsSender.java:96)*
* at java.lang.Thread.run(Thread.java:662)*
[2014-11-10 11:42:22,754] WARN
{org.apache.stratos.messaging.message.receiver.topology.TopologyEventMessageListener}
- Connection is lost
Timed out waiting for a response from the server (32000)
at
org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:27)
at
org.eclipse.paho.client.mqttv3.internal.ClientState.checkForActivity(ClientState.java:541)
at
org.eclipse.paho.client.mqttv3.internal.ClientState.get(ClientState.java:592)
at
org.eclipse.paho.client.mqttv3.internal.CommsSender.run(CommsSender.java:96)
at java.lang.Thread.run(Thread.java:662)
[2014-11-10 11:42:37,277] WARN
{org.apache.stratos.messaging.message.receiver.topology.TopologyEventMessageListener}
- Connection is lost
Timed out waiting for a response from the server (32000)
at
org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:27)
at
org.eclipse.paho.client.mqttv3.internal.ClientState.checkForActivity(ClientState.java:541)
at
org.eclipse.paho.client.mqttv3.internal.ClientState.get(ClientState.java:592)
at
org.eclipse.paho.client.mqttv3.internal.CommsSender.run(CommsSender.java:96)
at java.lang.Thread.run(Thread.java:662)
[2014-11-10 11:43:01,016] INFO
{org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
re-publish in 60 sec
[2014-11-10 11:44:01,018] INFO
{org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
re-publish in 60 sec
[2014-11-10 11:45:01,020] INFO
{org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
re-publish in 60 sec
[2014-11-10 11:46:01,022] INFO
{org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
re-publish in 60 sec
[2014-11-10 11:47:01,023] INFO
{org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
re-publish in 60 sec
[2014-11-10 11:48:01,026] INFO
{org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
re-publish in 60 sec
[2014-11-10 11:49:01,028] INFO
{org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
re-publish in 60 sec
[2014-11-10 11:50:01,031] INFO
{org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
re-publish in 60 sec
[2014-11-10 11:51:01,033] INFO
{org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
re-publish in 60 sec
[2014-11-10 11:52:01,035] INFO
{org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
re-publish in 60 sec
[2014-11-10 11:53:01,038] INFO
{org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
re-publish in 60 s
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
Re: MQTT connection lost problem in master branch
Posted by Udara Liyanage <ud...@wso2.com>.
Hi Imesh,
Just undeployed an application. After sometime this error occured and
application undeployment did not happen due to this.
On Mon, Nov 10, 2014 at 5:39 PM, Chamila De Alwis <ch...@wso2.com> wrote:
>
> On Mon, Nov 10, 2014 at 5:34 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> the problems we have currently with MQTT is that the logs raised by Paho
>> MQTT library are not visible.
>
>
> Wasn't this addressed by STRATOS-914 [1]?
>
> [1] - https://issues.apache.org/jira/browse/STRATOS-914
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
Re: MQTT connection lost problem in master branch
Posted by Chamila De Alwis <ch...@wso2.com>.
On Mon, Nov 10, 2014 at 5:34 PM, Imesh Gunaratne <im...@apache.org> wrote:
> the problems we have currently with MQTT is that the logs raised by Paho
> MQTT library are not visible.
Wasn't this addressed by STRATOS-914 [1]?
[1] - https://issues.apache.org/jira/browse/STRATOS-914
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
Re: MQTT connection lost problem in master branch
Posted by Imesh Gunaratne <im...@apache.org>.
Hi Udara,
Thanks for sharing this, can you please provide more information on how to
re-create this?
Important:
One of the problems we have currently with MQTT is that the logs raised by
Paho MQTT library are not visible. In some scenarios I noticed that Paho
MQTT library is catching exceptions, logging them, closing the connection
and returns without throwing the exceptions to the caller. Since the above
logs are not visible we are not able to find out the root cause of these
issues.
Thanks
On Mon, Nov 10, 2014 at 2:36 PM, Udara Liyanage <ud...@wso2.com> wrote:
> Hi Imesh,
>
> Hi got the following error in master branch when an application is
> undeployed.
> Please note that I got the packs built today morning.
>
> [2014-11-10 10:52:55,292] INFO
> {org.apache.stratos.messaging.domain.topology.lifecycle.LifeCycleStateManager}
> - Topology element [ mysql-only-app2 ]'s life Cycle State changed from [
> Created ] to [ Active ]
> [2014-11-10 11:04:41,163] INFO
> {org.apache.stratos.autoscaler.applications.topic.ApplicationBuilder} -
> Handling application terminating event: [application-id] mysql-only-app2
> [2014-11-10 11:04:41,166] INFO
> {org.apache.stratos.autoscaler.applications.topic.ApplicationBuilder} -
> Updating application status: [application-id] mysql-only-app2 [status]
> Terminating
> [2014-11-10 11:04:41,166] INFO
> {org.apache.stratos.messaging.domain.topology.lifecycle.LifeCycleStateManager}
> - Topology element [ mysql-only-app2 ]'s life Cycle State changed from [
> Active ] to [ Terminating ]
> [2014-11-10 11:04:41,166] INFO
> {org.apache.stratos.autoscaler.monitor.application.ApplicationMonitor} -
> [ApplicationMonitor] mysql-only-app2 state changes from Active to
> Terminating
> [2014-11-10 11:04:41,167] INFO
> {org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher}
> - Publishing Cluster Terminating event for [application]: mysql-only-app2
> [cluster]: mymysql.mysql.domain
> [2014-11-10 11:04:41,293] INFO
> {org.apache.stratos.messaging.domain.topology.lifecycle.LifeCycleStateManager}
> - Topology element [ mymysql.mysql.domain ]'s life Cycle State changed
> from [ Active ] to [ Terminating ]
> [2014-11-10 11:04:41,352] INFO
> {org.apache.stratos.cloud.controller.topology.TopologyEventPublisher} -
> Publishing Cluster terminating event: [appId] mysql-only-app2 [cluster id]
> mymysql.mysql.domain
> [2014-11-10 11:04:41,426] INFO
> {org.apache.stratos.autoscaler.applications.topic.ApplicationsEventPublisher}
> - Publishing Application activated event for [application]: mysql-only-app2
> [2014-11-10 11:04:41,682] INFO
> {org.apache.stratos.autoscaler.applications.topic.ApplicationsEventPublisher}
> - Publishing Application terminated event for [application]:
> mysql-only-app2
> [2014-11-10 11:04:41,809] INFO
> {org.apache.stratos.messaging.domain.topology.lifecycle.LifeCycleStateManager}
> - Topology element [ mysql-only-app2 ]'s life Cycle State changed from [
> Active ] to [ Terminating ]
> [2014-11-10 11:41:01,011] INFO
> {org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
> re-publish in 60 sec
> [2014-11-10 11:42:01,014] INFO
> {org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
> re-publish in 60 sec
> [2014-11-10 11:42:22,569] WARN
> {org.apache.stratos.messaging.message.receiver.applications.ApplicationsEventMessageListener}
> -* Connection is lost*
> *Timed out waiting for a response from the server (32000)*
> * at
> org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:27)*
> * at
> org.eclipse.paho.client.mqttv3.internal.ClientState.checkForActivity(ClientState.java:541)*
> * at
> org.eclipse.paho.client.mqttv3.internal.ClientState.get(ClientState.java:592)*
> * at
> org.eclipse.paho.client.mqttv3.internal.CommsSender.run(CommsSender.java:96)*
> * at java.lang.Thread.run(Thread.java:662)*
> [2014-11-10 11:42:22,754] WARN
> {org.apache.stratos.messaging.message.receiver.topology.TopologyEventMessageListener}
> - Connection is lost
> Timed out waiting for a response from the server (32000)
> at
> org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:27)
> at
> org.eclipse.paho.client.mqttv3.internal.ClientState.checkForActivity(ClientState.java:541)
> at
> org.eclipse.paho.client.mqttv3.internal.ClientState.get(ClientState.java:592)
> at
> org.eclipse.paho.client.mqttv3.internal.CommsSender.run(CommsSender.java:96)
> at java.lang.Thread.run(Thread.java:662)
> [2014-11-10 11:42:37,277] WARN
> {org.apache.stratos.messaging.message.receiver.topology.TopologyEventMessageListener}
> - Connection is lost
> Timed out waiting for a response from the server (32000)
> at
> org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:27)
> at
> org.eclipse.paho.client.mqttv3.internal.ClientState.checkForActivity(ClientState.java:541)
> at
> org.eclipse.paho.client.mqttv3.internal.ClientState.get(ClientState.java:592)
> at
> org.eclipse.paho.client.mqttv3.internal.CommsSender.run(CommsSender.java:96)
> at java.lang.Thread.run(Thread.java:662)
> [2014-11-10 11:43:01,016] INFO
> {org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
> re-publish in 60 sec
> [2014-11-10 11:44:01,018] INFO
> {org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
> re-publish in 60 sec
> [2014-11-10 11:45:01,020] INFO
> {org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
> re-publish in 60 sec
> [2014-11-10 11:46:01,022] INFO
> {org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
> re-publish in 60 sec
> [2014-11-10 11:47:01,023] INFO
> {org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
> re-publish in 60 sec
> [2014-11-10 11:48:01,026] INFO
> {org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
> re-publish in 60 sec
> [2014-11-10 11:49:01,028] INFO
> {org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
> re-publish in 60 sec
> [2014-11-10 11:50:01,031] INFO
> {org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
> re-publish in 60 sec
> [2014-11-10 11:51:01,033] INFO
> {org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
> re-publish in 60 sec
> [2014-11-10 11:52:01,035] INFO
> {org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
> re-publish in 60 sec
> [2014-11-10 11:53:01,038] INFO
> {org.apache.stratos.messaging.broker.publish.TopicPublisher} - Will try to
> re-publish in 60 s
>
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos