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?
> [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.
>> 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.
－－－－－－
Zhanwen Zhou (Jason)
+86 13922218435
[email protected]
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management
On Oct 7, 2016, at 5:46 PM, Ayyoob Hamza <[email protected]> wrote:
> Hi Jason,
>
> 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
>
> Please find the comments inline for the other issues.
>
> On Fri, Oct 7, 2016 at 1:45 PM, 云展智创 <[email protected]> wrote:
> Hi all,
>
> I got lots of the following errors when startup. I don’t know if it is the
> cause of the problem:
>
> [2016-10-07 16:07:26,944] ERROR - OAuth2BasedMQTTAuthenticator Error on
> connecting with the validation endpoint.
> org.apache.axis2.AxisFault: Connection refused
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
> at
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:199)
> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.wso2.carbon.identity.oauth2.stub.OAuth2TokenValidationServiceStub.validate(OAuth2TokenValidationServiceStub.java:461)
> at
> org.wso2.carbon.andes.authentication.andes.OAuth2BasedMQTTAuthenticator.getAuthenticationInfo(OAuth2BasedMQTTAuthenticator.java:126)
> at
> org.wso2.carbon.andes.authentication.andes.OAuth2BasedMQTTAuthenticator.validateToken(OAuth2BasedMQTTAuthenticator.java:82)
> at
> org.wso2.carbon.andes.authentication.andes.OAuth2BasedMQTTAuthenticator.checkValid(OAuth2BasedMQTTAuthenticator.java:62)
> at
> org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor.processConnect(ProtocolProcessor.java:256)
> at
> org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging.onEvent(SimpleMessaging.java:160)
> at
> org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging.onEvent(SimpleMessaging.java:47)
> at
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
> at org.apache.commons.ssl.Java14.connectSocket(Java14.java:178)
> at org.apache.commons.ssl.Java14.buildSocket(Java14.java:157)
> at org.apache.commons.ssl.JavaImpl.createSocket(JavaImpl.java:204)
> at org.apache.commons.ssl.SSL.createSocket(SSL.java:580)
> at org.apache.commons.ssl.SSLClient.createSocket(SSLClient.java:224)
> at
> org.apache.commons.ssl.HttpSecureProtocol.createSocket(HttpSecureProtocol.java:90)
> at
> org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
> at
> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
> at
> org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:630)
> at
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:195)
> ... 18 more
>
> 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 Zhou (Jason)
> +86 13922218435
> [email protected]
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API Management
>
> On Oct 7, 2016, at 3:36 PM, 云展智创 <[email protected]> wrote:
>
>> Hi,
>>
>> Do you know how to find the message routing map int he cluster? Could you
>> give me some advices on how to solve the below problems.
>>
>> 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}
>> TID: [-1] [] [2016-10-07 15:31:55,724] INFO
>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor} - Message
>> routing key: carbon.super/fourswitchs/t4flqyju95ye/publisher No routes in
>> cluster. Ignoring Message id 47932903449952256
>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor}
>> TID: [-1] [] [2016-10-07 15:31:55,724] INFO
>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor} - Message
>> routing key: carbon.super/fourswitchs/t4flqyju95ye/publisher No routes in
>> cluster. Ignoring Message id 47932903449952257
>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor}
>> TID: [-1] [] [2016-10-07 15:31:55,725] INFO
>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor} - Message
>> routing key: carbon.super/fourswitchs/t4flqyju95ye/publisher No routes in
>> cluster. Ignoring Message id 47932903450214400
>> {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 Zhou (Jason)
>> +86 13922218435
>> [email protected]
>> Guangzhou Smart Cloudex Technology Co., Ltd.
>> Business: IOT，API Management
>>
>> On Oct 5, 2016, at 11:11 PM, 云展智创 <[email protected]> wrote:
>>
>>> Hi all,
>>>
>>> I got these errors after I change the admin password and back to the origin
>>> password and restart the IoTS server again. I confirmed that I had create
>>> streams to process these messages in the topics.
>>>
>>> Could anybody help me? Thanks.
>>>
>>> TID: [-1] [] [2016-10-05 21:51:12,838] INFO
>>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor} - Message
>>> routing key: carbon.super/thgsensors/1ibc0sz4yxsfr/command No routes in
>>> cluster. Ignoring Message id 47893570607644672
>>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor}
>>> TID: [-1] [] [2016-10-05 21:52:47,340] INFO
>>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor} - Message
>>> routing key: carbon.super/thgsensors/rl7wme4wjw4j/command No routes in
>>> cluster. Ignoring Message id 47893595380776960
>>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor}
>>> TID: [-1] [] [2016-10-05 21:54:57,263] INFO
>>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor} - Message
>>> routing key: carbon.super/fourswitchs/1ibhl22d1zzg6/command No routes in
>>> cluster. Ignoring Message id 47893629439311872
>>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor}
>>>
>>> TID: [-1] [] [2016-10-05 22:56:16,659] INFO
>>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor} - Message
>>> routing key: carbon.super/thgsensors/1iuy87wofrv3n/bee No routes in
>>> cluster. Ignoring Message id 47894593970896898
>>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor}
>>> TID: [-1] [] [2016-10-05 22:56:44,202] INFO
>>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor} - Message
>>> routing key: carbon.super/thgsensors/1iuy87wofrv3n/alert No routes in
>>> cluster. Ignoring Message id 47894601191129088
>>> {org.wso2.andes.kernel.disruptor.inbound.MessagePreProcessor}
>>>
>>> －－－－－－
>>> Zhanwen Zhou (Jason)
>>> +86 13922218435
>>> [email protected]
>>> Guangzhou Smart Cloudex Technology Co., Ltd.
>>> Business: IOT, API Management
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> [email protected]
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>> _______________________________________________
>> Dev mailing list
>> [email protected]
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
