Ayyoob,
Do you know what’s the cause of the following log? The agent is keeping
running, but after a while, the server print this error, and then the command
from the server CAN NOT be sent to the agent telling that no routes in cluster.
Do I need to write some code in the agent to subscribe to the command topic in
a fix interval?
TID: [-1] [] [2016-10-08 00:01:06,586] INFO
{org.wso2.andes.subscription.SubscriptionEngine} - Local Subscription DELETED
[carbon.super/fourswitchs/skxuww1q1yed/command]ID=carbon:paho/D4A884D6D87DEE2DA0:carbon.super/fourswitchs/skxuww1q1yed/command@NODEhankz/127.0.1.1/T=1475856066585/D=false/X=true/O=/E=amq.topic/ET=/EUD=1/S=false
{org.wso2.andes.subscription.SubscriptionEngine}
－－－－－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management
On Oct 8, 2016, at 11:49 AM, Ayyoob Hamza <ayy...@wso2.com> wrote:
>
> Hi Zhanwen,
>
> On Fri, Oct 7, 2016 at 7:47 PM, 云展智创 <i...@smartcloudex.com> wrote:
> Ayyoob,
>
> Thanks for you reply.
>
>> If you change the default password then you have to change the password in
>> set of other configuration files(given below).
>> repository/conf/broker.xml,
>> repository/conf/api-manager.xml,
>> repository/conf/analytics/analytics-data-config.xml
>> repository/conf/etc/webapp-authenticator-config.xml
>
> Zhanwen: So, if I have change the admin password to the original password, I
> don’t need to make any change to these configuration files and the IoTS will
> run as before. Right?
> yes you dont need to change the password
>
>> [2016-10-07 16:07:26,944] ERROR - OAuth2BasedMQTTAuthenticator Error on
>> connecting with the validation endpoint.
>> org.apache.axis2.AxisFault: Connection refused
>
>> This error pops up because it is failing to connect to the authentication
>> server. If you are trying this with a cluster then make sure to update the
>> relevant configuration in the broker.xml, However if you are trying this
>> with a single instance then there is a known intermittent issue in alpha
>> pack which was resolved after the alpha release. So this might work after a
>> restart.
> Zhanwen: Yes, I run the IoTS in a single instance server. Every time I
> restarted the server, I got lots of this error message.
> This issue is raised because the server is trying to connect to mqtt before
> the services are up and its failing. Therefore it depends on service
> initialisation order which could change when you restart the server. This
> issue has been fixed in the latest pack.
>
>>> TID: [-1] [] [2016-10-07 15:31:55,578] INFO
>>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor} - Message
>>> routing key: carbon.super/fourswitchs/t4flqyju95ye/publisher No routes in
>>> cluster. Ignoring Message id 47932903411679232
>>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor}
>
>> This is not an issue, In here when a client publishes to a topic and if
>> there aren't any subscription then it will ignore the message without
>> persisting it.
>
> Zhanwen: I have created a mqtt receiver to map
> carbon.super/fourswitchs/+/publisher to a stream, and I have many other
> devices of the same type (fourswitchs) running which had no this problem.
> These devices’ data were received and stored in the stream table, I could
> confirm that through the Data Explorer. So, I think there is a subscription
> for this message, but I don’t know why it is ignored by the backend IoTS
> server. Do you have any advices? Thanks.
> Due to the above error the server might fail to subscribe to the topic, this
> would lead to the data being ignored.
> <PastedGraphic-1.png>
>
>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
