Re: [Dev] [IoTS] how to enable CORS in IOTS (for example: alpha version)

[云展智创]

Ayyoob,

Thank you very much. Can I change the tomcat web.xml file and add the CORS 
filter to implement this requirement as a workaround?

－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

在 2017年6月20日，上午10:56，Ayyoob Hamza <ayy...@wso2.com> 写道：

> Hi Zhanwen,
> 
> The CORS configuration in api-manager.xml is related to the synapse gateway 
> (default port 8243/8280). But the API invocation through port 9443 goes 
> through tomcat gateway(valve). Therefore the configuration change that you 
> did won't work on the alpha pack. However, this should work if you access it 
> through 8243 but you need to try this on the IoTS 3.0.0 pack since synapse 
> gateway was not supported during the alpha release. In addition app creation 
> endpoint https://:9443/dynamic-client-web/register/ is not 
> supported from IoTS 3.0.0 RC, instead of "dynamic-client-web/register/" we 
> have to use the endpoint given in the below curl command to create 
> application.
> 
> curl -k -X POST https://localhost:8243/api-application-registration/register 
> -H 'authorization: Basic YWRtaW46YWRtaW4=' -H 'content-type: 
> application/json' -d '{ "applicationName":"appName", 
> "tags":["device_management"]}'
> 
> Thanks
> 
> Ayyoob Hamza
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> email: ayy...@wso2.com cell: +94 77 1681010
> 
> On Tue, Jun 20, 2017 at 7:33 AM, 云展智创 <i...@smartcloudex.com> wrote:
> Hi team,
> 
> I had changed the api-manager.xml with the following setting, but I still got 
> the errors below:
> 
> 
> 
> XMLHttpRequest cannot load 
> https://:9443/dynamic-client-web/register/. Response to preflight 
> request doesn't pass access control check: No 'Access-Control-Allow-Origin' 
> header is present on the requested resource. Origin 'http://localhost:63342' 
> is therefore not allowed access. The response had HTTP status code 500.
> 
> I want to use the api https://:9443/dynamic-client-web/register/ to 
> get the client secret and client id and then to get access token with 
> oauth2/token
> 
> Could you tell me how to setup CORS in IOTS? 
> 
> Thanks.
> －－
> Zhanwen Zhou (Jason)
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API Management
> 
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
> 
> 

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTS] how to enable CORS in IOTS (for example: alpha version)

[云展智创]

Hi team,

I had changed the api-manager.xml with the following setting, but I still got 
the errors below:



XMLHttpRequest cannot load 
https://:9443/dynamic-client-web/register/. Response to preflight 
request doesn't pass access control check: No 'Access-Control-Allow-Origin' 
header is present on the requested resource. Origin 'http://localhost:63342' is 
therefore not allowed access. The response had HTTP status code 500.

I want to use the api https://:9443/dynamic-client-web/register/ to 
get the client secret and client id and then to get access token with 
oauth2/token

Could you tell me how to setup CORS in IOTS? 

Thanks.
－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IOTS] MQTTAdapterListener Failed to create an https connection after change the SSL certificate in wso2carbon.jks in IOTS alpha version

[云展智创]

Ayyoob,

Thanks. Your solution resolves the problem in last mail. And I think this 
should be done in IoTS3.0.0 too.

But when I created a new device of type fire alarm, downloaded the agent, I got 
the below new errors about JWTClient.getAccessToken :

[2017-05-12 17:24:20,996] ERROR - AbstractFaultChainInitiatorObserver Error 
occurred during error handling, give up!
org.apache.cxf.interceptor.Fault
at 
org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:170)
at 
org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:136)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:204)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:101)
at 
org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
at 
org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:94)
at 
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
at 
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at 
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249)
at 
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)
at 
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)
at 
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)
at 
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171)
at 
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:289)
at 
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:214)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
at 
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:265)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at 
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
at 
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at 
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
at 
org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationValve.processRequest(WebappAuthenticationValve.java:145)
at 
org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationValve.invoke(WebappAuthenticationValve.java:67)
at 
org.wso2.carbon.event.receiver.core.internal.tenantmgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:48)
at 
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at 
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
at 
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at 
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at 

Re: [Dev] [IOTS] MQTTAdapterListener Failed to create an https connection after change the SSL certificate in wso2carbon.jks in IOTS alpha version

[云展智创]

Yes, right. I know it’s a very old version. But I use it in a project. And I 
think it may have the same problem in new versions because lots of config file 
use localhost instead of the domain name. Only for mqtt connections I got the 
SSL certificate error below.
－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

在 2017年5月12日，下午2:01，Sumedha Rubasinghe <sume...@wso2.com> 写道：

> Hi Jason,
> What is the exact version your using? IOTS alpha?
> 
> On Fri, May 12, 2017 at 11:29 AM, 云展智创 <i...@smartcloudex.com> wrote:
> hi,
> 
> Another error after change the dcrUrl of the plugins’ mqtt receivers:
> 
> [2017-05-12 13:56:32,005] ERROR - JWTBearerGrantHandler Signature or Message 
> Authentication invalid.
> [2017-05-12 13:56:32,007] ERROR - JWTBearerGrantHandler Signature or Message 
> Authentication invalid.
> Exception in thread "Thread-91" java.lang.NullPointerException
>   at 
> org.wso2.carbon.identity.jwt.client.extension.JWTClient.getTokenInfo(JWTClient.java:120)
>   at 
> org.wso2.carbon.identity.jwt.client.extension.JWTClient.getAccessToken(JWTClient.java:80)
>   at 
> org.wso2.carbon.device.mgt.iot.input.adapter.mqtt.util.MQTTAdapterListener.startListener(MQTTAdapterListener.java:184)
>   at 
> org.wso2.carbon.device.mgt.iot.input.adapter.mqtt.util.MQTTAdapterListener.run(MQTTAdapterListener.java:274)
>   at java.lang.Thread.run(Thread.java:745)
> Exception in thread "Thread-90" java.lang.NullPointerException
>   at 
> org.wso2.carbon.identity.jwt.client.extension.JWTClient.getTokenInfo(JWTClient.java:120)
>   at 
> org.wso2.carbon.identity.jwt.client.extension.JWTClient.getAccessToken(JWTClient.java:80)
>   at 
> org.wso2.carbon.device.mgt.iot.input.adapter.mqtt.util.MQTTAdapterListener.startListener(MQTTAdapterListener.java:184)
>   at 
> org.wso2.carbon.device.mgt.iot.input.adapter.mqtt.util.MQTTAdapterListener.run(MQTTAdapterListener.java:274)
>   at java.lang.Thread.run(Thread.java:745)
> [2017-05-12 13:56:33,199] ERROR - JWTBearerGrantHandler Signature or Message 
> Authentication invalid.
> Exception in thread "Thread-95" java.lang.NullPointerException
>   at 
> org.wso2.carbon.identity.jwt.client.extension.JWTClient.getTokenInfo(JWTClient.java:120)
>   at 
> org.wso2.carbon.identity.jwt.client.extension.JWTClient.getAccessToken(JWTClient.java:80)
>   at 
> org.wso2.carbon.device.mgt.iot.input.adapter.mqtt.util.MQTTAdapterListener.startListener(MQTTAdapterListener.java:184)
>   at 
> org.wso2.carbon.device.mgt.iot.input.adapter.mqtt.util.MQTTAdapterListener.run(MQTTAdapterListener.java:274)
>   at java.lang.Thread.run(Thread.java:745)
>  
> －－
> Zhanwen Zhou (Jason)
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API Management
> 
> 在 2017年5月11日，下午4:22，云展智创 <i...@smartcloudex.com> 写道：
> 
>> Hi team,
>> 
>> I created a new wso2carbon.jks key store file with mydomain certificate in 
>> it. But when I started the IOTS server (alpha version), I got the following 
>> errors about mismatch hostname. Could you tell me which config files I need 
>> to change to solve this problem? I have tried to change some config files 
>> with my domain name to replace default localhost but didn’t work. And it 
>> seems ok for other components in startup… Thanks.
>> 
>> [2017-05-11 15:40:30,098] ERROR - MQTTAdapterListener Failed to create an 
>> https connection.
>> javax.net.ssl.SSLException: hostname in certificate didn't match: 
>>  !=  OR 
>>  at 
>> org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:231)
>>  at 
>> org.apache.http.conn.ssl.BrowserCompatHostnameVerifier.verify(BrowserCompatHostnameVerifier.java:54)
>>  at 
>> org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:152)
>>  at 
>> org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:133)
>>  at 
>> org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:291)
>>  at 
>> org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:262)
>>  at 
>> org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:118)
>>  at 
>> org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:314)
>>  at 
>> org.apache.http.impl.execchain.MainClient

Re: [Dev] [IOTS] MQTTAdapterListener Failed to create an https connection after change the SSL certificate in wso2carbon.jks in IOTS alpha version

[云展智创]

hi,

Another error after change the dcrUrl of the plugins’ mqtt receivers:

[2017-05-12 13:56:32,005] ERROR - JWTBearerGrantHandler Signature or Message 
Authentication invalid.
[2017-05-12 13:56:32,007] ERROR - JWTBearerGrantHandler Signature or Message 
Authentication invalid.
Exception in thread "Thread-91" java.lang.NullPointerException
at 
org.wso2.carbon.identity.jwt.client.extension.JWTClient.getTokenInfo(JWTClient.java:120)
at 
org.wso2.carbon.identity.jwt.client.extension.JWTClient.getAccessToken(JWTClient.java:80)
at 
org.wso2.carbon.device.mgt.iot.input.adapter.mqtt.util.MQTTAdapterListener.startListener(MQTTAdapterListener.java:184)
at 
org.wso2.carbon.device.mgt.iot.input.adapter.mqtt.util.MQTTAdapterListener.run(MQTTAdapterListener.java:274)
at java.lang.Thread.run(Thread.java:745)
Exception in thread "Thread-90" java.lang.NullPointerException
at 
org.wso2.carbon.identity.jwt.client.extension.JWTClient.getTokenInfo(JWTClient.java:120)
at 
org.wso2.carbon.identity.jwt.client.extension.JWTClient.getAccessToken(JWTClient.java:80)
at 
org.wso2.carbon.device.mgt.iot.input.adapter.mqtt.util.MQTTAdapterListener.startListener(MQTTAdapterListener.java:184)
at 
org.wso2.carbon.device.mgt.iot.input.adapter.mqtt.util.MQTTAdapterListener.run(MQTTAdapterListener.java:274)
at java.lang.Thread.run(Thread.java:745)
[2017-05-12 13:56:33,199] ERROR - JWTBearerGrantHandler Signature or Message 
Authentication invalid.
Exception in thread "Thread-95" java.lang.NullPointerException
at 
org.wso2.carbon.identity.jwt.client.extension.JWTClient.getTokenInfo(JWTClient.java:120)
at 
org.wso2.carbon.identity.jwt.client.extension.JWTClient.getAccessToken(JWTClient.java:80)
at 
org.wso2.carbon.device.mgt.iot.input.adapter.mqtt.util.MQTTAdapterListener.startListener(MQTTAdapterListener.java:184)
at 
org.wso2.carbon.device.mgt.iot.input.adapter.mqtt.util.MQTTAdapterListener.run(MQTTAdapterListener.java:274)
at java.lang.Thread.run(Thread.java:745)
 
－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

在 2017年5月11日，下午4:22，云展智创 <i...@smartcloudex.com> 写道：

> Hi team,
> 
> I created a new wso2carbon.jks key store file with mydomain certificate in 
> it. But when I started the IOTS server (alpha version), I got the following 
> errors about mismatch hostname. Could you tell me which config files I need 
> to change to solve this problem? I have tried to change some config files 
> with my domain name to replace default localhost but didn’t work. And it 
> seems ok for other components in startup… Thanks.
> 
> [2017-05-11 15:40:30,098] ERROR - MQTTAdapterListener Failed to create an 
> https connection.
> javax.net.ssl.SSLException: hostname in certificate didn't match:  
> !=  OR 
>   at 
> org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:231)
>   at 
> org.apache.http.conn.ssl.BrowserCompatHostnameVerifier.verify(BrowserCompatHostnameVerifier.java:54)
>   at 
> org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:152)
>   at 
> org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:133)
>   at 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:291)
>   at 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:262)
>   at 
> org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:118)
>   at 
> org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:314)
>   at 
> org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:357)
>   at 
> org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:218)
>   at 
> org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:194)
>   at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:85)
>   at 
> org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
>   at 
> org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186)
>   at 
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
>   at 
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
>   at 
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
>   at 
> org.wso2.carbon.device.mgt.iot.input.adapter.mqtt.util.MQTTAdapterListener.startListener(MQTTAdapterListener.java:174)
>   at 
> org.wso2.carbon.device.mgt.

[Dev] [IOTS] MQTTAdapterListener Failed to create an https connection after change the SSL certificate in wso2carbon.jks in IOTS alpha version

[云展智创]

Hi team,

I created a new wso2carbon.jks key store file with mydomain certificate in it. 
But when I started the IOTS server (alpha version), I got the following errors 
about mismatch hostname. Could you tell me which config files I need to change 
to solve this problem? I have tried to change some config files with my domain 
name to replace default localhost but didn’t work. And it seems ok for other 
components in startup… Thanks.

[2017-05-11 15:40:30,098] ERROR - MQTTAdapterListener Failed to create an https 
connection.
javax.net.ssl.SSLException: hostname in certificate didn't match:  
!=  OR 
at 
org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:231)
at 
org.apache.http.conn.ssl.BrowserCompatHostnameVerifier.verify(BrowserCompatHostnameVerifier.java:54)
at 
org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:152)
at 
org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:133)
at 
org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:291)
at 
org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:262)
at 
org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:118)
at 
org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:314)
at 
org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:357)
at 
org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:218)
at 
org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:194)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:85)
at 
org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
at 
org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186)
at 
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at 
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
at 
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
at 
org.wso2.carbon.device.mgt.iot.input.adapter.mqtt.util.MQTTAdapterListener.startListener(MQTTAdapterListener.java:174)
at 
org.wso2.carbon.device.mgt.iot.input.adapter.mqtt.util.MQTTAdapterListener.run(MQTTAdapterListener.java:274)
at java.lang.Thread.run(Thread.java:745)
[2017-05-11 15:40:30,302] ERROR - MQTTAdapterListener MQTT Exception occurred 
when starting listener
Bad user name or password (4)
at 
org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:28)
at 
org.eclipse.paho.client.mqttv3.internal.ClientState.notifyReceivedAck(ClientState.java:885)
at 
org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:118)
at java.lang.Thread.run(Thread.java:745)


－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] Unable to show the history data in analytics view with error "Unable to destroy the process"

[云展智创]

Rasika,

Another hint: I might have started the analytics server twice, and after I 
known that, I stop one instance with ‘wso2server.sh stop’ command and kill the 
other one process.

And I got the following error after the above mistake.

－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

在 2017年4月7日，下午5:57，云展智创 <i...@smartcloudex.com> 写道：

> Hi Rasika,
> 
> I have not changed the default admin username or password. However, I have 
> changed some h2 database's username and password, and some database was moved 
> to mysql. I also change the “localhost” to my server ip in some config file 
> following the direction of IoTS3.0.0 document.
> 
> The IoT server version is IoTS3.0.0.
> 
> Thanks.
> －－
> Zhanwen Zhou (Jason)
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API Management
> 
> 在 2017年4月7日，下午5:34，Rasika Perera <rasi...@wso2.com> 写道：
> 
>> Hi Jason,
>> 
>> We are using Analytics Server's HTTP APIs to fetch analytics. This API is 
>> protected using basic authentication. Have you changed the default username 
>> and password? May be due to that you might be getting this issue.
>> 
>> If you have changed the default username & password please go-ahead and 
>> change the credentials on 
>> $CARBON_HOME/repository/conf/analytics-data-config.xml file.
>> 
>> Or else please let us know the product version that you are trying this on, 
>> which would be beneficial for us to help in an efficient manner?
>> 
>> Best Regards,
>> Rasika
>> 
>> On Fri, Apr 7, 2017 at 12:49 PM, 云展智创 <i...@smartcloudex.com> wrote:
>> Hi team,
>> 
>> I started the broker, core and analytics successfully. After I created an 
>> connected cup instance and received some data, I clicked the analytics view 
>> but got the following data. Could you help me for this? Thanks.
>> 
>> https://:9443/devicemgt/device/connectedcup/analytics?deviceId=qdyu3np82rfo=cupmysql
>> ———
>> [2017-04-07 14:51:56,202] [IoT-Core] ERROR - 
>> AbstractFaultChainInitiatorObserver Error occurred during error handling, 
>> give up!
>> org.apache.cxf.interceptor.Fault: Unable to destroy the process . 
>>  at 
>> org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:170)
>>  at 
>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:136)
>>  at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:204)
>>  at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:101)
>>  at 
>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
>>  at 
>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:94)
>>  at 
>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
>>  at 
>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>  at 
>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249)
>>  at 
>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)
>>  at 
>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)
>>  at 
>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)
>>  at 
>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171)
>>  at 
>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:289)
>>  at 
>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:214)
>>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
>>  at 
>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:265)
>>  at 
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>>  at 
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>  at 
>> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>>  at 
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>>  at 
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>  

[Dev] [IoTS] Unable to show the history data in analytics view with error "Unable to destroy the process"

[云展智创]

Hi team,

I started the broker, core and analytics successfully. After I created an 
connected cup instance and received some data, I clicked the analytics view but 
got the following data. Could you help me for this? Thanks.

https://:9443/devicemgt/device/connectedcup/analytics?deviceId=qdyu3np82rfo=cupmysql
———
[2017-04-07 14:51:56,202] [IoT-Core] ERROR - 
AbstractFaultChainInitiatorObserver Error occurred during error handling, give 
up!
org.apache.cxf.interceptor.Fault: Unable to destroy the process . 
at 
org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:170)
at 
org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:136)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:204)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:101)
at 
org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
at 
org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:94)
at 
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
at 
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at 
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249)
at 
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)
at 
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)
at 
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)
at 
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171)
at 
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:289)
at 
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:214)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
at 
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:265)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:218)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at 
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
at 
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at 
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
at 
org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationValve.processRequest(WebappAuthenticationValve.java:138)
at 
org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationValve.invoke(WebappAuthenticationValve.java:68)
at 
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at 
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
at 
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:958)
at 
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:452)
at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1087)
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1756)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1715)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 

Re: [Dev] [IoTS] ApiMgtDAO Unable to find the admin API when change the default H2 database to mysql in IoTS3.0.0

[云展智创]

I have solved the below problem. Please ignore my last mail. Thanks.

－－
Zhanwen Zhou (Jason), 
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

在 2017年4月5日，下午6:45，云展智创 <i...@smartcloudex.com> 写道：

> Hi team,
> 
> I got the following error after I changed the apim database from h2 to mysql. 
> It’s not my first start of this instance. I don’t know if this is the reason 
> of the errors.
> 
> Could anyone help me for this? Thanks.
> 
> [2017-04-05 18:36:34,777] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-SCEP Management-1.0.0 in the database
> [2017-04-05 18:37:38,787] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-SCEP Management-1.0.0 in the database
> [2017-04-05 18:37:38,803] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-Windows Device Management Administrative Service-1.0.0 in the 
> database
> [2017-04-05 18:37:38,810] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-Windows Configuration Management-1.0.0 in the database
> [2017-04-05 18:37:38,825] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-Windows Binary Security Token Service-1.0.0 in the database
> [2017-04-05 18:37:38,830] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-DeviceAccessAuthorizationAdminService-1.0.0 in the database
> [2017-04-05 18:37:38,855] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-DeviceManagementAdmin-1.0.0 in the database
> [2017-04-05 18:37:38,862] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-RoleManagement-1.0.0 in the database
> [2017-04-05 18:37:38,876] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-DeviceAnalyticsDashboard-1.0.0 in the database
> [2017-04-05 18:37:38,892] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-ActivityInfoProvider-1.0.0 in the database
> [2017-04-05 18:37:38,900] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-DeviceManagement-1.0.0 in the database
> [2017-04-05 18:37:38,910] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-ConfigurationManagement-1.0.0 in the database
> [2017-04-05 18:37:38,921] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-DevicePolicyManagement-1.0.0 in the database
> [2017-04-05 18:37:38,926] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-UserManagement-1.0.0 in the database
> [2017-04-05 18:37:38,930] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-UserManagementAdmin-1.0.0 in the database
> [2017-04-05 18:37:38,943] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-GroupManagement-1.0.0 in the database
> [2017-04-05 18:37:38,956] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-DeviceTypeManagement-1.0.0 in the database
> [2017-04-05 18:37:38,966] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-ApplicationManagementAdmin-1.0.0 in the database
> [2017-04-05 18:37:38,973] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-GroupManagementAdmin-1.0.0 in the database
> [2017-04-05 18:37:38,982] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-DeviceNotificationManagement-1.0.0 in the database
> [2017-04-05 18:37:38,996] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-Android Device Management Administrative Service-1.0.0 in the 
> database
> [2017-04-05 18:37:39,001] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-Android Event Receiver-1.0.0 in the database
> [2017-04-05 18:37:39,015] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-Android Device Management-1.0.0 in the database
> [2017-04-05 18:37:39,024] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-Android Configuration Management-1.0.0 in the database
> [2017-04-05 18:37:39,034] [IoT-Core] ERROR - ApiMgtDAO Unable to find the 
> API: admin-Certificate Management-1.0.0 in the database
> [2017-04-05 18:37:39,035] [IoT-Core] ERROR - APIPublisherStartupHandler Error 
> occurred while publishing API ['Certificate Management,Android Configuration 
> Management,Android Device Management,Android Event Receiver,Android Device 
> Management Administrative 
> Service,DeviceNotificationManagement,GroupManagementAdmin,ApplicationManagementAdmin,DeviceTypeManagement,GroupManagement,UserManagementAdmin,UserManagement,DevicePolicyManagement,ConfigurationManagement,DeviceManagement,ActivityInfoProvider,DeviceAnalyticsDashboard,RoleManagement,DeviceManagementAdmin,DeviceAccessAuthorizationAdminService,Windows
>  Binary Security Token Service,Windows Configuration Management,Windows 
> Device Management Administrative Service,SCEP Management,']
> 
> －－
> Zhanwen Zhou (Jason), 
> +86 13922218435
>

[Dev] [IoTS] ApiMgtDAO Unable to find the admin API when change the default H2 database to mysql in IoTS3.0.0

[云展智创]

Hi team,

I got the following error after I changed the apim database from h2 to mysql. 
It’s not my first start of this instance. I don’t know if this is the reason of 
the errors.

Could anyone help me for this? Thanks.

[2017-04-05 18:36:34,777] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-SCEP Management-1.0.0 in the database
[2017-04-05 18:37:38,787] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-SCEP Management-1.0.0 in the database
[2017-04-05 18:37:38,803] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-Windows Device Management Administrative Service-1.0.0 in the database
[2017-04-05 18:37:38,810] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-Windows Configuration Management-1.0.0 in the database
[2017-04-05 18:37:38,825] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-Windows Binary Security Token Service-1.0.0 in the database
[2017-04-05 18:37:38,830] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-DeviceAccessAuthorizationAdminService-1.0.0 in the database
[2017-04-05 18:37:38,855] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-DeviceManagementAdmin-1.0.0 in the database
[2017-04-05 18:37:38,862] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-RoleManagement-1.0.0 in the database
[2017-04-05 18:37:38,876] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-DeviceAnalyticsDashboard-1.0.0 in the database
[2017-04-05 18:37:38,892] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-ActivityInfoProvider-1.0.0 in the database
[2017-04-05 18:37:38,900] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-DeviceManagement-1.0.0 in the database
[2017-04-05 18:37:38,910] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-ConfigurationManagement-1.0.0 in the database
[2017-04-05 18:37:38,921] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-DevicePolicyManagement-1.0.0 in the database
[2017-04-05 18:37:38,926] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-UserManagement-1.0.0 in the database
[2017-04-05 18:37:38,930] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-UserManagementAdmin-1.0.0 in the database
[2017-04-05 18:37:38,943] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-GroupManagement-1.0.0 in the database
[2017-04-05 18:37:38,956] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-DeviceTypeManagement-1.0.0 in the database
[2017-04-05 18:37:38,966] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-ApplicationManagementAdmin-1.0.0 in the database
[2017-04-05 18:37:38,973] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-GroupManagementAdmin-1.0.0 in the database
[2017-04-05 18:37:38,982] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-DeviceNotificationManagement-1.0.0 in the database
[2017-04-05 18:37:38,996] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-Android Device Management Administrative Service-1.0.0 in the database
[2017-04-05 18:37:39,001] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-Android Event Receiver-1.0.0 in the database
[2017-04-05 18:37:39,015] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-Android Device Management-1.0.0 in the database
[2017-04-05 18:37:39,024] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-Android Configuration Management-1.0.0 in the database
[2017-04-05 18:37:39,034] [IoT-Core] ERROR - ApiMgtDAO Unable to find the API: 
admin-Certificate Management-1.0.0 in the database
[2017-04-05 18:37:39,035] [IoT-Core] ERROR - APIPublisherStartupHandler Error 
occurred while publishing API ['Certificate Management,Android Configuration 
Management,Android Device Management,Android Event Receiver,Android Device 
Management Administrative 
Service,DeviceNotificationManagement,GroupManagementAdmin,ApplicationManagementAdmin,DeviceTypeManagement,GroupManagement,UserManagementAdmin,UserManagement,DevicePolicyManagement,ConfigurationManagement,DeviceManagement,ActivityInfoProvider,DeviceAnalyticsDashboard,RoleManagement,DeviceManagementAdmin,DeviceAccessAuthorizationAdminService,Windows
 Binary Security Token Service,Windows Configuration Management,Windows Device 
Management Administrative Service,SCEP Management,']

－－
Zhanwen Zhou (Jason), 
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] Cannot enroll new device with the new created account

[云展智创]

Hi Harshan,

I just created the account in the register link. I can’t select the role by 
myself. In the previous IoTS version, the server will provide a default role 
(maybe devicemgt-user) to the new registered user but not in IoTS 3.0.0.

I need to manually create a new role and assign the user to the role with admin 
user so that the new user can enroll new device. Is that right?

Thanks.


－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API

在 2017年3月9日，下午6:15，Harshan Liyanage <hars...@wso2.com> 写道：

> Hi Zhanwen,
> 
> If the user created at first doesn't have the required permissions to enroll 
> a device, the UI won't show up the "Enroll new device" button in the UI. If 
> that's the case it's the expected behaviour. But if the user has all the 
> required permissions then there's a problem. Could you please tell us what 
> permissions were given to the new role (which did not had in the beginning)?
> 
> Thanks,
> 
> Harshan Liyanage
> EMM/IoT TG
> Mobile: +94765672894
> Email: hars...@wso2.com 
> Blog : http://harshanliyanage.blogspot.com/
> WSO2, Inc. : wso2.com
> lean.enterprise.middleware.
> 
> On Thu, Mar 9, 2017 at 2:36 PM, 云展智创 <i...@smartcloudex.com> wrote:
> Hi team,
> 
> I deployed the WSO2 IOT pack plugins and started the IoTS server 
> successfully. But I could not enroll new device with the new created account 
> and got the following errors in the backend server:
> 
> 
> 
> I tried to use IP instead of localhost but the URL will redirect to 
> localhost:9443 and got the same error. I couldn’t find the “Enroll new 
> device” button below.
> 
> 
> But after I created a new role with necessary permissions and assigned the 
> above user to that role, then I could enroll a new device with that user. Is 
> that right?
> 
> －－
> Zhanwen Zhou (Jason)
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API
> 
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
> 
> 

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] Cannot enroll new device with the new created account

[云展智创]

Hi Harshan,

I just created the account in the register link. I can’t select the role by 
myself. In the previous IoTS version, the server will provide a default role 
(maybe devicemgt-user) to the new registered user but not in IoTS 3.0.0.

I need to manually create a new role and assign the user to the role with admin 
user so that the new user can enroll new device.


－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API

在 2017年3月9日，下午6:15，Harshan Liyanage <hars...@wso2.com> 写道：

> Hi Zhanwen,
> 
> If the user created at first doesn't have the required permissions to enroll 
> a device, the UI won't show up the "Enroll new device" button in the UI. If 
> that's the case it's the expected behaviour. But if the user has all the 
> required permissions then there's a problem. Could you please tell us what 
> permissions were given to the new role (which did not had in the beginning)?
> 
> Thanks,
> 
> Harshan Liyanage
> EMM/IoT TG
> Mobile: +94765672894
> Email: hars...@wso2.com 
> Blog : http://harshanliyanage.blogspot.com/
> WSO2, Inc. : wso2.com
> lean.enterprise.middleware.
> 
> On Thu, Mar 9, 2017 at 2:36 PM, 云展智创 <i...@smartcloudex.com> wrote:
> Hi team,
> 
> I deployed the WSO2 IOT pack plugins and started the IoTS server 
> successfully. But I could not enroll new device with the new created account 
> and got the following errors in the backend server:
> 
> 
> 
> I tried to use IP instead of localhost but the URL will redirect to 
> localhost:9443 and got the same error. I couldn’t find the “Enroll new 
> device” button below.
> 
> 
> But after I created a new role with necessary permissions and assigned the 
> above user to that role, then I could enroll a new device with that user. Is 
> that right?
> 
> －－
> Zhanwen Zhou (Jason)
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API
> 
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
> 
> 

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTS] Build Failure of WSO2 IoTS 3.0.0 with mvn eclipse:eclipse

[云展智创]

Hi teams,

I got the following build errors when run the command mvn eclipse:eclipse. 
Could anyone tell me how to solve this error? Thanks.


[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] WSO2 IoT - Parent .. SUCCESS [  0.971 s]
[INFO] WSO2 IoT - Broker Parent ... SUCCESS [  0.044 s]
[INFO] WSO2 IoT - Broker - P2 Profile Gen . SUCCESS [  0.056 s]
[INFO] WSO2 IoT - Broker - Product Distribution ... SUCCESS [  3.586 s]
[INFO] WSO2 IoT - Core Parent . SUCCESS [  0.022 s]
[INFO] WSO2 IoT - Core - Tools  SUCCESS [  0.024 s]
[INFO] WSO2 IoT - Device Type Archetype ... SUCCESS [  0.530 s]
[INFO] WSO2 IoT - Core - UI Styles  SUCCESS [  0.525 s]
[INFO] WSO2 IoT - Core - Server UI Features ... SUCCESS [  0.025 s]
[INFO] WSO2 IoT - Core - Server Styles Feature  FAILURE [  0.021 s]
[INFO] WSO2 IoT - Core - P2 Profile Gen ... SKIPPED
[INFO] WSO2 IoT - Core - Distribution . SKIPPED
[INFO] WSO2 IoT - Analytics Parent  SKIPPED
[INFO] WSO2 IoT - Analytics - P2 Profile Gen .. SKIPPED
[INFO] WSO2 IoT - Analytics - Product Distribution  SKIPPED
[INFO] WSO2 IoT - Distribution Parent . SKIPPED
[INFO] >WSO2 IoT - Integration Tests .. SKIPPED
[INFO] WSO2 IoT - Integration Test Artifacts .. SKIPPED
[INFO] WSO2 IoT Server - Integration Test Common .. SKIPPED
[INFO] WSO2 IoT - Integration Test Common Web UI Pages  SKIPPED
[INFO] WSO2 IoT - Integration Test UI Module .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 7.422 s
[INFO] Finished at: 2017-03-06T16:22:54+08:00
[INFO] Final Memory: 58M/1449M
[INFO] 
[ERROR] Failed to execute goal on project org.wso2.iot.core.styles.feature: 
Could not resolve dependencies for project 
org.wso2.iot:org.wso2.iot.core.styles.feature:pom:3.0.0: Failure to find 
org.wso2.iot:org.wso2.iot.core.admin.styles:jar:3.0.0 in 
http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local 
repository, resolution will not be reattempted until the update interval of 
wso2-nexus has elapsed or updates are forced -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :org.wso2.iot.core.styles.feature


－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] which config files are need to be changed after changing the admin password with devicemgt console in IoTS3.0.0 release?

[云展智创]

Hi team,

I found the error position and root cause. Please miss the last mail. Thanks.
－－
Zhanwen Zhou (Jason), 
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API

在 2017年2月9日，下午3:36，云展智创 <i...@smartcloudex.com> 写道：

> The complete error stack is:
> 
> [2017-02-09 15:30:06,374] [IoT-Core] ERROR - BasicAuthenticationInterceptor 
> Authentication failed. Please check your username/password
> [2017-02-09 15:30:07,059] [IoT-Analytics] ERROR 
> {org.wso2.carbon.device.mgt.input.adapter.mqtt.util.MQTTAdapterListener} -  
> MQTT Exception occurred when starting listener
> 错误的用户名或密码 (4)
>   at 
> org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:28)
>   at 
> org.eclipse.paho.client.mqttv3.internal.ClientState.notifyReceivedAck(ClientState.java:885)
>   at 
> org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:118)
>   at java.lang.Thread.run(Thread.java:745)
> 
> －－
> Zhanwen Zhou (Jason), 
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API
> 
> 在 2017年2月9日，下午3:31，云展智创 <i...@smartcloudex.com> 写道：
> 
>> I have changed all the default admin password I known but still got this 
>> error:
>> 
>> [2017-02-09 15:30:07,059] [IoT-Analytics] ERROR 
>> {org.wso2.carbon.device.mgt.input.adapter.mqtt.util.MQTTAdapterListener} -  
>> MQTT Exception occurred when starting listener
>> 错误的用户名或密码 (4)
>>  at 
>> org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:28)
>>  at 
>> org.eclipse.paho.client.mqttv3.internal.ClientState.notifyReceivedAck(ClientState.java:885)
>>  at 
>> org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:118)
>>  at java.lang.Thread.run(Thread.java:745)
>> 
>> －－
>> Zhanwen Zhou (Jason), 
>> +86 13922218435
>> zhanwen.z...@smartcloudex.com
>> Guangzhou Smart Cloudex Technology Co., Ltd.
>> Business: IOT, API
>> 
>> 在 2017年2月8日，下午4:45，云展智创 <i...@smartcloudex.com> 写道：
>> 
>>> Hi all,
>>> 
>>> Could you kindly tell me which config files are need to be changed after 
>>> changing the admin password with devicemgt console in IoTS3.0.0 release? 
>>> Thanks.
>>> 
>>> －－
>>> Zhanwen Zhou (Jason), 
>>> +86 13922218435
>>> zhanwen.z...@smartcloudex.com
>>> Guangzhou Smart Cloudex Technology Co., Ltd.
>>> Business: IOT, API
>>> 
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>> 
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] which config files are need to be changed after changing the admin password with devicemgt console in IoTS3.0.0 release?

[云展智创]

The complete error stack is:

[2017-02-09 15:30:06,374] [IoT-Core] ERROR - BasicAuthenticationInterceptor 
Authentication failed. Please check your username/password
[2017-02-09 15:30:07,059] [IoT-Analytics] ERROR 
{org.wso2.carbon.device.mgt.input.adapter.mqtt.util.MQTTAdapterListener} -  
MQTT Exception occurred when starting listener
错误的用户名或密码 (4)
at 
org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:28)
at 
org.eclipse.paho.client.mqttv3.internal.ClientState.notifyReceivedAck(ClientState.java:885)
at 
org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:118)
at java.lang.Thread.run(Thread.java:745)

－－
Zhanwen Zhou (Jason), 
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API

在 2017年2月9日，下午3:31，云展智创 <i...@smartcloudex.com> 写道：

> I have changed all the default admin password I known but still got this 
> error:
> 
> [2017-02-09 15:30:07,059] [IoT-Analytics] ERROR 
> {org.wso2.carbon.device.mgt.input.adapter.mqtt.util.MQTTAdapterListener} -  
> MQTT Exception occurred when starting listener
> 错误的用户名或密码 (4)
>   at 
> org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:28)
>   at 
> org.eclipse.paho.client.mqttv3.internal.ClientState.notifyReceivedAck(ClientState.java:885)
>   at 
> org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:118)
>   at java.lang.Thread.run(Thread.java:745)
> 
> －－
> Zhanwen Zhou (Jason), 
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API
> 
> 在 2017年2月8日，下午4:45，云展智创 <i...@smartcloudex.com> 写道：
> 
>> Hi all,
>> 
>> Could you kindly tell me which config files are need to be changed after 
>> changing the admin password with devicemgt console in IoTS3.0.0 release? 
>> Thanks.
>> 
>> －－
>> Zhanwen Zhou (Jason), 
>> +86 13922218435
>> zhanwen.z...@smartcloudex.com
>> Guangzhou Smart Cloudex Technology Co., Ltd.
>> Business: IOT, API
>> 
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
> 

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] which config files are need to be changed after changing the admin password with devicemgt console in IoTS3.0.0 release?

[云展智创]

I have changed all the default admin password I known but still got this error:

[2017-02-09 15:30:07,059] [IoT-Analytics] ERROR 
{org.wso2.carbon.device.mgt.input.adapter.mqtt.util.MQTTAdapterListener} -  
MQTT Exception occurred when starting listener
错误的用户名或密码 (4)
at 
org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:28)
at 
org.eclipse.paho.client.mqttv3.internal.ClientState.notifyReceivedAck(ClientState.java:885)
at 
org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:118)
at java.lang.Thread.run(Thread.java:745)

－－
Zhanwen Zhou (Jason), 
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API

在 2017年2月8日，下午4:45，云展智创 <i...@smartcloudex.com> 写道：

> Hi all,
> 
> Could you kindly tell me which config files are need to be changed after 
> changing the admin password with devicemgt console in IoTS3.0.0 release? 
> Thanks.
> 
> －－
> Zhanwen Zhou (Jason), 
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTS] which config files are need to be changed after changing the admin password with devicemgt console in IoTS3.0.0 release?

[云展智创]

Hi all,

Could you kindly tell me which config files are need to be changed after 
changing the admin password with devicemgt console in IoTS3.0.0 release? Thanks.

－－
Zhanwen Zhou (Jason), 
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTS] Can not open management console of broker server with the port 9446 in IoTS 3.0.0 release

[云展智创]

Hi team,

After I started the broker server of IoTS, I opened the management console of 
it and got the following errors. Is that right?
https://localhost:9446/carbon/



btw, I could successfully open and login the management console of core and 
analytics server.

Thanks.

－－
Zhanwen Zhou (Jason), 
+86 13922218435
zhanwen.z...@smartcloudex.com
Business: IOT, API


___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTS] what's the complete steps to change the admin password in IoTS alpha version

[云展智创]

Hi all,

Could you tell me what’s the complete steps to change the admin password in 
IoTS alpha version? I had changed almost all the default admin password in 
configuration files but still got lots of following errors (for example, I 
change the password to smart):

[2016-12-23 14:13:55,169]  WARN - CarbonAuthenticationUtil Failed Administrator 
login attempt 'smart[-1234]' at [2016-12-23 14:13:55,169+0800]
[2016-12-23 14:13:55,169]  WARN - AuthenticationHandler Illegal access attempt 
at [2016-12-23 14:13:55,0169] from IP address 127.0.0.1 while trying to 
authenticate access to service OAuth2TokenValidationService
[2016-12-23 14:13:55,170] ERROR - OAuth2BasedMQTTAuthenticator Error on 
connecting with the validation endpoint.
org.apache.axis2.AxisFault: Access Denied. Authentication failed - Invalid 
credentials provided.
at 
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
at 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:445)
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)
[2016-12-23 14:13:55,170]  INFO - ProtocolProcessor Lost connection with client 
paho6643675267853545
[2016-12-23 14:13:55,171]  WARN - ProtocolProcessor MQTTAuthorizationSubject 
for client ID paho6643675267853545 is not removed since the entry does not exist
[2016-12-23 14:13:55,171]  INFO - ProtocolProcessor Lost connection with client 
paho6643673511277781
[2016-12-23 14:13:55,171]  WARN - ProtocolProcessor MQTTAuthorizationSubject 
for client ID paho6643673511277781 is not removed since the entry does not exist
[2016-12-23 14:13:55,172]  INFO - ProtocolProcessor Lost connection with client 
paho6643673893486011
[2016-12-23 14:13:55,172]  WARN - ProtocolProcessor MQTTAuthorizationSubject 
for client ID paho6643673893486011 is not removed since the entry does not exist
[2016-12-23 14:13:55,172] ERROR - MQTTAdapterListener MQTT Exception occurred 
when starting listener
Bad user name or password (4)
at 
org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:28)
at 
org.eclipse.paho.client.mqttv3.internal.ClientState.notifyReceivedAck(ClientState.java:885)
at 
org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:118)
at java.lang.Thread.run(Thread.java:745)




Thanks!

－－
Zhanwen Zhou (Jason), 
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTS] how to recover the removed device in IoTS alpha

[云展智创]

Hi team,

I removed one of the device from my device list from the group device page ( I 
thought that it was used to remove the device from the group, not to deleted 
the device). Could anyone tell me how to recover the device to the active 
status? Thanks.
－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API 

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] How to redeploy the updated device type in IoTS alpha

[云展智创]

Lakshani,

Thanks. Will it delete the original database table when we uninstall the 
features? if not, then what we should do if we need to update the schema of the 
device type table or add more tables in sql file.
－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API

On Oct 28, 2016, at 10:10 PM, Lakshani Gamage <laksh...@wso2.com> wrote:

> Hi Zhanwen,
> 
> Please see the accepted answer in [1]
> 
> [1] 
> http://stackoverflow.com/questions/37517158/wso2-iots-update-device-plugin-code-to-server
> 
> Thanks,
> Lakshani.
> 
> On Fri, Oct 28, 2016 at 6:19 PM, 云展智创 <i...@smartcloudex.com> wrote:
> Hi team,
> 
> I have deployed my device type in IoTS alpha and run for a while. Then I 
> updated some codes in api, agent, etc. Can anyone tell me how to redeploy the 
> updated device type? I want to keep my device instance data in IoTS database. 
> Thanks.
> 
> －－
> Zhanwen Zhou (Jason)
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
> 
> 
> 
> -- 
> Lakshani Gamage
> 
> Software Engineer, WSO2
> 
> Mobile : +94 71 5478184
> Blog : http://lakshanigamage.blogspot.com/

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTS] How to redeploy the updated device type in IoTS alpha

[云展智创]

Hi team,

I have deployed my device type in IoTS alpha and run for a while. Then I 
updated some codes in api, agent, etc. Can anyone tell me how to redeploy the 
updated device type? I want to keep my device instance data in IoTS database. 
Thanks.

－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API 

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTS] Lots of MQTT connection errors after changing the port offset in carbon.xml in IoTS alpha release

[云展智创]

Hi all,

I got lots of MQTT errors after changing the port offset in carbon.xml and 
restart the server with IoTS alpha release. The new agent could not connect to 
the IoTS with mqtt using the new offset port.

The errors were:

1. [2016-10-18 17:11:29,630] ERROR - OAuth2BasedMQTTAuthenticator Error on 
connecting with the validation endpoint.
org.apache.axis2.AxisFault: Connection refused
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)

2. [2016-10-18 17:11:29,684]  INFO - ProtocolProcessor Lost connection with 
client paho952169391265634
[2016-10-18 17:11:29,684]  WARN - ProtocolProcessor MQTTAuthorizationSubject 
for client ID paho952169391265634 is not removed since the entry does not exist
[2016-10-18 17:11:29,690] ERROR - MQTTAdapterListener MQTT Exception occurred 
when starting listener
Bad user name or password (4)
at 
org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:28)
at 
org.eclipse.paho.client.mqttv3.internal.ClientState.notifyReceivedAck(ClientState.java:885)
at 
org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:118)
at java.lang.Thread.run(Thread.java:745)

Anyone knows what happens?

－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTS] Build error with missing package org.wso2.carbon.apimgt.api.model [5.0.0, 6.0.0)

[云展智创]

Hi all,

When I built the product-iot in order of carbon-device-mgt, 
carbon-device-mgt-plugin, then product-iot, I got the following errors. Anyone 
can help me? Thanks.

Installing org.wso2.carbon.device.mgt.analytics.dashboard.feature.group 
1.2.2.SNAPSHOT.
Installing org.wso2.carbon.analytics.cdmf.feature.group 1.0.1.SNAPSHOT.
Installation failed.
Cannot complete the install because one or more required items could not be 
found.
 Software being installed: WSO2 Carbon - MQTT Based Push Notification Provider 
Feature 1.2.2.SNAPSHOT 
(org.wso2.carbon.device.mgt.extensions.push.notification.provider.mqtt.feature.group
 1.2.2.SNAPSHOT)
 Missing requirement: org.wso2.carbon.device.mgt.common 1.2.2.SNAPSHOT 
(org.wso2.carbon.device.mgt.common 1.2.2.SNAPSHOT) requires 'package 
org.wso2.carbon.apimgt.api.model [5.0.0,6.0.0)' but it could not be found
 Cannot satisfy dependency:
  From: org.wso2.carbon.device.mgt.extensions.push.notification.provider.mqtt 
1.2.2.SNAPSHOT 
(org.wso2.carbon.device.mgt.extensions.push.notification.provider.mqtt 
1.2.2.SNAPSHOT)
  To: package org.wso2.carbon.device.mgt.common [1.2.0,2.0.0)
 Cannot satisfy dependency:
  From: WSO2 Carbon - MQTT Based Push Notification Provider Feature 
1.2.2.SNAPSHOT 
(org.wso2.carbon.device.mgt.extensions.push.notification.provider.mqtt.feature.group
 1.2.2.SNAPSHOT)
  To: org.wso2.carbon.device.mgt.extensions.push.notification.provider.mqtt 
[1.2.2.SNAPSHOT]


－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] Errors after change the admin password and restart the IoTS server - No routes in cluster. Ignoring Message

[云展智创]

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.
> 
> 
> 

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] Errors after change the admin password and restart the IoTS server - No routes in cluster. Ignoring Message

[云展智创]

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
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

On Oct 7, 2016, at 5:46 PM, Ayyoob Hamza <ayy...@wso2.com> 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, 云展智创 <i...@smartcloudex.com> 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.Si

Re: [Dev] [IoTS] Errors after change the admin password and restart the IoTS server - No routes in cluster. Ignoring Message

[云展智创]

Hi all,

Could anyone help me? Thanks.

Another error in wsocarbon.log:

[2016-10-07 16:07:27,876] ERROR - OAuth2BasedMQTTAuthenticator Error on 
connecting with the validation endpoint.
org.apache.axis2.AxisFault: Transport error: 404 Error: Not Found
at 
org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:331)
at 
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
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)

－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

On Oct 7, 2016, at 4:15 PM, 云展智创 <i...@smartcloudex.com> 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.Threa

Re: [Dev] [IoTS] Errors after change the admin password and restart the IoTS server - No routes in cluster. Ignoring Message

[云展智创]

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


－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

On Oct 7, 2016, at 3:36 PM, 云展智创 <i...@smartcloudex.com> 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/t4flqyju95y

Re: [Dev] [IoTS] Errors after change the admin password and restart the IoTS server - No routes in cluster. Ignoring Message

[云展智创]

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}


－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT，API Management

On Oct 5, 2016, at 11:11 PM, 云展智创 <i...@smartcloudex.com> 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
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API Management
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTS] Errors after change the admin password and restart the IoTS server

[云展智创]

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
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTS] when will the IoTS be GA?

[云展智创]

Hi,

Could anyone tell me when will the IoTS 1.0.0 release be GA? Thanks a lot.

－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

_
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTS] when will the IoTS be GA?

[云展智创]

Hi,

Could anyone tell me when will the IoTS 1.0.0 release be GA? Thanks a lot.

－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTs][IOT] How to write plugin api to receive photo uploaded from device with python agent

[云展智创]

Hi team,

Does anyone have written a sample IoTS plugins with an api to receive photo 
uploaded from device with python agent? And api to be used by APP to get the 
uploaded photo in IoTS.

Could you guide me how to write these rest apis for post and get photos in IoTS 
plugins?

Thanks.

－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] Errors when creating the device plugin with carbon-device-mgt-maven-plugin and deploy in IoTS alpha release

[云展智创]

Geesara,

Thanks a lot. There are very detail steps to create device type in your 
article. 

I followed your guide and created my device type, and then change the category 
to “iot” in the device type config file. But after I deployed the device type 
to IoTS, it still showed up in the VIRTUAL device section. 

Do you know what’s the problem?

－－
Zhanwen Zhou (Jason), 
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

On Sep 2, 2016, at 5:08 PM, Geesara Prathap <gees...@wso2.com> wrote:

> Hi Jason,
> 
> Sorry, you mean defining 3 sensors when creating new device plugin. Yes, that 
> feature is included after Alpha is released. If you need more than one sensor 
> you need to define like which is already there.  Please follow section 
> three[1] in this article. It will help you to understand how to create your 
> own sensor type and deploy into the server in details.
> 
> 1.https://medium.com/@GPrathap/maven-archetype-for-creating-a-device-plugin-for-wso2-iot-server-34f0d6309e18#.ieom887a5
> 
> Thanks,
> Geesara
> 
> 
> On Fri, Sep 2, 2016 at 2:24 PM, Geesara Prathap <gees...@wso2.com> wrote:
> Hi Jason,
> 
> But I can’t use the feature of defining 3 sensors at the same time with the 
> alpha version of maven archetype.
> 
> Can you explain a little bit more. I didn't get you exactly what is to be 
> done. 
> 
> Thanks,
> Geesara
> 
> 
> On Fri, Sep 2, 2016 at 12:30 PM, 云展智创 <i...@smartcloudex.com> wrote:
> Hi Geesara,
> 
> Yes, it works again now.
> 
> But I can’t use the feature of defining 3 sensors at the same time with the 
> alpha version of maven archetype.
> 
> Thanks.
> －－
> Zhanwen Zhou (Jason)
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API Management
> 
> On Sep 2, 2016, at 1:11 PM, Geesara Prathap <gees...@wso2.com> wrote:
> 
>> Hi Jason,
>> 
>> I think you are not using the correct version of carbon-device-mgt-maven 
>> plugin. Since you are working with IoTS Alpha pack, you need to  clone and 
>> build carbon-device-mgt-maven plugin of Alpha branch. Please check the 
>> version of  carbon.device.mgt.version in your sample device type parent 
>> pom.xml. It should be 1.1.0. If it is 1.1.1-SNAPSHOT then your not using the 
>> correct version of maven archetype. Then you have to rebuild your sample 
>> device plugin which is released for  IoTS Alpha pack. To do that 
>> 
>> 1. Clone maven archetype for  IoTS Alpha.
>>git clone -b IoTS-1.0.0-ALPHA --single-branch 
>> https://github.com/wso2/carbon-device-mgt-maven-plugin.git
>> 2. Navigate to the cloned folder via the console, and install the maven 
>> archetype into your local system. Once you executed below command it  will 
>> overwrite whatever the version you have in your system into correct 
>> version(IoTS-1.0.0-ALPHA).
>>mvn clean install 
>> 
>> Please follow above mentioned steps and let us know would you be able to 
>> resolve your problem.
>> 
>> Thanks,
>> Geesara,
>> 
>> 
>> On Fri, Sep 2, 2016 at 9:48 AM, 云展智创 <i...@smartcloudex.com> wrote:
>> Hi team,
>> 
>> When I used the carbon-device-mgt-maven-plugin to create a new device type 
>> and deployed in IoTS alpha release, I got the following errors:
>> 
>> It seems that the new maven-archetype-tools created device type need 
>> carbon.device.mgt.version to be 1.1.1 but alpha release only support 1.1.0?
>> 
>> Could you help me how to solve this problem? Thanks.
>> 
>> 
>> －－
>> Zhanwen Zhou (Jason),
>> +86 13922218435
>> zhanwen.z...@smartcloudex.com
>> Guangzhou Smart Cloudex Technology Co., Ltd.
>> Business: IOT, API Management
>> 
>> 
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>> 
>> 
>> 
>> 
>> -- 
>> Geesara Prathap Kulathunga
>> Software Engineer
>> WSO2 Inc; http://wso2.com
>> Mobile : +940772684174
>> 
> 
> 
> 
> 
> -- 
> Geesara Prathap Kulathunga
> Software Engineer
> WSO2 Inc; http://wso2.com
> Mobile : +940772684174
> 
> 
> 
> 
> -- 
> Geesara Prathap Kulathunga
> Software Engineer
> WSO2 Inc; http://wso2.com
> Mobile : +940772684174
> 

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] Errors when creating the device plugin with carbon-device-mgt-maven-plugin and deploy in IoTS alpha release

[云展智创]

Hi Geesara,

Yes, it works again now.

But I can’t use the feature of defining 3 sensors at the same time with the 
alpha version of maven archetype.

Thanks.
－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

On Sep 2, 2016, at 1:11 PM, Geesara Prathap <gees...@wso2.com> wrote:

> Hi Jason,
> 
> I think you are not using the correct version of carbon-device-mgt-maven 
> plugin. Since you are working with IoTS Alpha pack, you need to  clone and 
> build carbon-device-mgt-maven plugin of Alpha branch. Please check the 
> version of  carbon.device.mgt.version in your sample device type parent 
> pom.xml. It should be 1.1.0. If it is 1.1.1-SNAPSHOT then your not using the 
> correct version of maven archetype. Then you have to rebuild your sample 
> device plugin which is released for  IoTS Alpha pack. To do that 
> 
> 1. Clone maven archetype for  IoTS Alpha.
>git clone -b IoTS-1.0.0-ALPHA --single-branch 
> https://github.com/wso2/carbon-device-mgt-maven-plugin.git
> 2. Navigate to the cloned folder via the console, and install the maven 
> archetype into your local system. Once you executed below command it  will 
> overwrite whatever the version you have in your system into correct 
> version(IoTS-1.0.0-ALPHA).
>mvn clean install 
> 
> Please follow above mentioned steps and let us know would you be able to 
> resolve your problem.
> 
> Thanks,
> Geesara,
> 
> 
> On Fri, Sep 2, 2016 at 9:48 AM, 云展智创 <i...@smartcloudex.com> wrote:
> Hi team,
> 
> When I used the carbon-device-mgt-maven-plugin to create a new device type 
> and deployed in IoTS alpha release, I got the following errors:
> 
> It seems that the new maven-archetype-tools created device type need 
> carbon.device.mgt.version to be 1.1.1 but alpha release only support 1.1.0?
> 
> Could you help me how to solve this problem? Thanks.
> 
> 
> －－
> Zhanwen Zhou (Jason),
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API Management
> 
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
> 
> 
> 
> 
> -- 
> Geesara Prathap Kulathunga
> Software Engineer
> WSO2 Inc; http://wso2.com
> Mobile : +940772684174
> 

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTS] Errors when creating the device plugin with carbon-device-mgt-maven-plugin and deploy in IoTS alpha release

[云展智创]

Hi team,

When I used the carbon-device-mgt-maven-plugin to create a new device type and 
deployed in IoTS alpha release, I got the following errors:

It seems that the new maven-archetype-tools created device type need 
carbon.device.mgt.version to be 1.1.1 but alpha release only support 1.1.0?

Could you help me how to solve this problem? Thanks.


－－
Zhanwen Zhou (Jason),
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] Failed to connect to the MQTT topic again after disconnect for a while in 1.0.0 alpha

[云展智创]

Ayyoob,

Could you tell me which piece of code in the Raspberry Agent store the client 
information of the device type?

And if I create my new device plugin with "cdmf-devicetype-archetype”, does the 
result codebase will include my device type client information in the agent 
codes? 

Thanks.
－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: API Management, IoT

On Aug 5, 2016, at 11:31 AM, Ayyoob Hamza <ayy...@wso2.com> wrote:

> Hi Jason,
> 
> Device does not require a username/password to refresh the token rather it 
> requires a client Id and client secret[1]. For our sample use cases we can 
> either create a clientId and client secret per device or per device type. In 
> the raspberry pi example the client information will be embedded in the 
> script. Therefore the access token for device can renewed with the client 
> information and refresh token.
> 
> [1] https://docs.wso2.com/display/IS510/Refresh+Token+Grant
> 
> Thanks,
> Ayyoob
> 
> Ayyoob Hamza
> Software Engineer
> WSO2 Inc.; http://wso2.com
> email: ayy...@wso2.com cell: +94 77 1681010
> 
> On Fri, Aug 5, 2016 at 8:07 AM, 云展智创 <i...@smartcloudex.com> wrote:
> Hi Ayyoob,
> 
> Thanks. I am testing to change the AccessTokenDefaultValidityPeriod to 84600 
> seconds (about one day). I want to confirm with you whether my understanding 
> of the following configuration attributes is correct.
> 
>  is used when user login in the 
> application and get the client_id and client_secret, the application need to 
> request for Refresh token and Access token in 300 seconds.
> 
>  is used for setting up the validity period 
> for device agent access token. After 3600 seconds, the device agent CAN NOT 
> access IoTS with the old Access token.
> 
>  is used for setting up the validity 
> period for user access token from UI.
> 
>  is used for setting up the validity period for 
> Refresh token. That’s means, after 84600 seconds, users need to login again 
> to get the new refresh token. But how does the device get the new Refresh 
> token as it can not login with username/password and the old refresh token is 
> expired?
> 
> =
>   
> 
> 300
> 
> 
> 3600
> 
> 
> 3600
> 
> 84600
> 
> 
> －－
> Zhanwen Zhou (Jason)
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: API Management, IoT
> 
> On Aug 5, 2016, at 9:39 AM, Ayyoob Hamza <ayy...@wso2.com> wrote:
> 
>> Hi Jason,
>> 
>> This happens when the OAuth token is expired for the device. In the IoTS 
>> alpha we have not implemented the renewing the token with refresh token 
>> part, however this has been implemented in the master. One way of having a 
>> continuous connection for the samples in alpha pack would be to increase the 
>> expiration time in identity.xml (repository/conf/identity/identity.xml).
>> 
>> Thanks,
>> Ayyoob
>> 
>> Ayyoob Hamza
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> email: ayy...@wso2.com cell: +94 77 1681010
>> 
>> On Fri, Aug 5, 2016 at 6:45 AM, 云展智创 <i...@smartcloudex.com> wrote:
>> I got the following error logs from IoTS:
>> 
>> ==
>> [2016-08-05 08:57:06,466] ERROR - MessageMetricsHandler Connection reset by 
>> peer
>> java.io.IOException: Connection reset by peer
>>  at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
>>  at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
>>  at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
>>  at sun.nio.ch.IOUtil.read(IOUtil.java:192)
>>  at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
>>  at 
>> io.netty.buffer.UnpooledUnsafeDirectByteBuf.setBytes(UnpooledUnsafeDirectByteBuf.java:446)
>>  at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:881)
>>  at 
>> io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:225)
>>  at 
>> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:119)
>>  at 
>> io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
>>  at 
>> io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
>>  at 
>> io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
>>  at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
>>  at 
>>

Re: [Dev] [IoTS] Failed to connect to the MQTT topic again after disconnect for a while in 1.0.0 alpha

[云展智创]

Hi Ayyoob,

Thanks. I am testing to change the AccessTokenDefaultValidityPeriod to 84600 
seconds (about one day). I want to confirm with you whether my understanding of 
the following configuration attributes is correct.

 is used when user login in the 
application and get the client_id and client_secret, the application need to 
request for Refresh token and Access token in 300 seconds.

 is used for setting up the validity period 
for device agent access token. After 3600 seconds, the device agent CAN NOT 
access IoTS with the old Access token.

 is used for setting up the validity 
period for user access token from UI.

 is used for setting up the validity period for 
Refresh token. That’s means, after 84600 seconds, users need to login again to 
get the new refresh token. But how does the device get the new Refresh token as 
it can not login with username/password and the old refresh token is expired?

=


300


3600


3600

84600


－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: API Management, IoT

On Aug 5, 2016, at 9:39 AM, Ayyoob Hamza <ayy...@wso2.com> wrote:

> Hi Jason,
> 
> This happens when the OAuth token is expired for the device. In the IoTS 
> alpha we have not implemented the renewing the token with refresh token part, 
> however this has been implemented in the master. One way of having a 
> continuous connection for the samples in alpha pack would be to increase the 
> expiration time in identity.xml (repository/conf/identity/identity.xml).
> 
> Thanks,
> Ayyoob
> 
> Ayyoob Hamza
> Software Engineer
> WSO2 Inc.; http://wso2.com
> email: ayy...@wso2.com cell: +94 77 1681010
> 
> On Fri, Aug 5, 2016 at 6:45 AM, 云展智创 <i...@smartcloudex.com> wrote:
> I got the following error logs from IoTS:
> 
> ==
> [2016-08-05 08:57:06,466] ERROR - MessageMetricsHandler Connection reset by 
> peer
> java.io.IOException: Connection reset by peer
>   at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
>   at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
>   at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
>   at sun.nio.ch.IOUtil.read(IOUtil.java:192)
>   at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
>   at 
> io.netty.buffer.UnpooledUnsafeDirectByteBuf.setBytes(UnpooledUnsafeDirectByteBuf.java:446)
>   at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:881)
>   at 
> io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:225)
>   at 
> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:119)
>   at 
> io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
>   at 
> io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
>   at 
> io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
>   at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
>   at 
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
>   at 
> io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
>   at java.lang.Thread.run(Thread.java:745)
> [2016-08-05 08:57:06,480]  INFO - ProtocolProcessor Lost connection with 
> client paho/551D5528F7972AE4CD
> [2016-08-05 08:57:06,484]  INFO - MQTTopicManager Disconnecting channel for 
> clientID: paho/551D5528F7972AE4CD
> [2016-08-05 08:57:06,529]  INFO - SubscriptionEngine Local Subscription 
> DELETED 
> [carbon.super/raspberrypi/s4mbetlzspyc]ID=carbon:paho/551D5528F7972AE4CD:carbon.super/raspberrypi/s4mbetlzspyc@NODEZhanwendeMacBook-Air.local/192.168.0.102/T=1470358626484/D=false/X=true/O=/E=amq.topic/ET=/EUD=1/S=false
> [2016-08-05 08:57:06,529]  INFO - OrphanedMessageHandler Purging messages of 
> this node persisted under carbon.super/raspberrypi/s4mbetlzspyc
> [2016-08-05 08:57:06,540]  INFO - MessagingEngine Purged messages of 
> destination carbon.super/raspberrypi/s4mbetlzspyc
> [2016-08-05 08:57:07,775]  INFO - ProtocolProcessor Lost connection with 
> client paho/551D5528F7972AE4CD
> [2016-08-05 08:57:07,776]  WARN - ProtocolProcessor MQTTAuthorizationSubject 
> for client ID paho/551D5528F7972AE4CD is not removed since the entry does not 
> exist
> [2016-08-05 08:57:08,795]  INFO - ProtocolProcessor Lost connection with 
> client paho/551D5528F7972AE4CD
> [2016-08-05 08:57:08,795]  WARN - ProtocolProcessor MQTTAuthorizationSubject 
> for client ID paho/551D5528F7972AE4CD is not removed since the entry does not 
> exist

Re: [Dev] [IoTS] Failed to connect to the MQTT topic again after disconnect for a while in 1.0.0 alpha

[云展智创]

I got the following error logs from IoTS:

==
[2016-08-05 08:57:06,466] ERROR - MessageMetricsHandler Connection reset by peer
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
at sun.nio.ch.IOUtil.read(IOUtil.java:192)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
at 
io.netty.buffer.UnpooledUnsafeDirectByteBuf.setBytes(UnpooledUnsafeDirectByteBuf.java:446)
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:881)
at 
io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:225)
at 
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:119)
at 
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
at 
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
at 
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
at 
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
at 
io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
at java.lang.Thread.run(Thread.java:745)
[2016-08-05 08:57:06,480]  INFO - ProtocolProcessor Lost connection with client 
paho/551D5528F7972AE4CD
[2016-08-05 08:57:06,484]  INFO - MQTTopicManager Disconnecting channel for 
clientID: paho/551D5528F7972AE4CD
[2016-08-05 08:57:06,529]  INFO - SubscriptionEngine Local Subscription DELETED 
[carbon.super/raspberrypi/s4mbetlzspyc]ID=carbon:paho/551D5528F7972AE4CD:carbon.super/raspberrypi/s4mbetlzspyc@NODEZhanwendeMacBook-Air.local/192.168.0.102/T=1470358626484/D=false/X=true/O=/E=amq.topic/ET=/EUD=1/S=false
[2016-08-05 08:57:06,529]  INFO - OrphanedMessageHandler Purging messages of 
this node persisted under carbon.super/raspberrypi/s4mbetlzspyc
[2016-08-05 08:57:06,540]  INFO - MessagingEngine Purged messages of 
destination carbon.super/raspberrypi/s4mbetlzspyc
[2016-08-05 08:57:07,775]  INFO - ProtocolProcessor Lost connection with client 
paho/551D5528F7972AE4CD
[2016-08-05 08:57:07,776]  WARN - ProtocolProcessor MQTTAuthorizationSubject 
for client ID paho/551D5528F7972AE4CD is not removed since the entry does not 
exist
[2016-08-05 08:57:08,795]  INFO - ProtocolProcessor Lost connection with client 
paho/551D5528F7972AE4CD
[2016-08-05 08:57:08,795]  WARN - ProtocolProcessor MQTTAuthorizationSubject 
for client ID paho/551D5528F7972AE4CD is not removed since the entry does not 
exist
[2016-08-05 08:57:09,810]  INFO - ProtocolProcessor Lost connection with client 
paho/551D5528F7972AE4CD
……
==

－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: API Management, IOT

On Aug 4, 2016, at 10:23 AM, 云展智创 <i...@smartcloudex.com> wrote:

> Hi all,
> 
> I downloaded a raspberry pi agent from IoTS 1.0.0 alpha, ran the raspberry pi 
> agent and uploaded the temperature data successfully. But after I 
> disconnected the agent for a while, the MQTT connection could not be setup 
> again. Can anyone help me for this? Thanks.
> 
> 
> MQTT_LISTENER: Connected with result code 4
> MQTT_LISTENER: Subscribing with topic carbon.super/raspberrypi/rkwrklcphsmu
> 
> 
> －－
> Zhanwen Zhou (Jason)
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: API Management, IOT
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IOTS] Failed to get realtime data from IoTS in 1.0.0 alpha

[云展智创]

Ruwan,

Yes, you are right. Thank you very much.

And if you have time, please help to give me some suggestions for question in 
another mail:
-
MAIL: [Dev] [IoTS] Failed to connect to the MQTT topic again after disconnect 
for a while in 1.0.0 alpha

I downloaded a raspberry pi agent from IoTS 1.0.0 alpha, ran the raspberry pi 
agent and uploaded the temperature data successfully. But after I disconnected 
the agent for a while, the MQTT connection could not be setup again. I kill the 
RaspberryAgent process directly. I don’t know if this is the cause of the 
problem.

Can anyone help me for this? Thanks.


MQTT_LISTENER: Connected with result code 4
MQTT_LISTENER: Subscribing with topic carbon.super/raspberrypi/rkwrklcphsmu

-


－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: API Management, IoT

On Aug 4, 2016, at 5:23 PM, Ruwan Yatawara <ruw...@wso2.com> wrote:

> Hi Json,
> 
> This is most likely due to the fact that you are accessing the devicemgt app 
> via a 'localhost' url. Please replace the host section of your devicemgt app 
> url, with the ip address, and you will be able to see the statistics.
> 
> Please let us know if this fixes the issue you are facing.
> 
> Thanks and Regards,
> 
> Ruwan Yatawara
> 
> Associate Technical Lead,
> WSO2 Inc.
> 
> email : ruw...@wso2.com
> mobile : +94 77 9110413
> blog : http://ruwansrants.blogspot.com/
>   https://500px.com/ruwan_ace
> www: :http://wso2.com
> 
> 
> On Thu, Aug 4, 2016 at 7:47 AM, 云展智创 <i...@smartcloudex.com> wrote:
> Hi all,
> 
> When I open the IoTS devicemgt ui to view the realtime statistic data of my 
> raspberry pi device, I always get below error, so that the graph can now show 
> any temperature line. Can anyone help me? Thanks.
> 
> WebSocket connection to 
> 'wss://192.168.2.109:9443/secured-outputui/org.wso2.iot.devices.temperature/1.0.0?token=ecd222ae10d959deb02d3bf2b8f6=1iukwdj4luwxe=raspberrypi'
>  failed: WebSocket opening handshake was canceled
> 
> －－
> Zhanwen Zhou (Jason)
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: API Management, IOT
> 
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
> 
> 

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTS] Failed to connect to the MQTT topic again after disconnect for a while in 1.0.0 alpha

[云展智创]

Hi all,

I downloaded a raspberry pi agent from IoTS 1.0.0 alpha, ran the raspberry pi 
agent and uploaded the temperature data successfully. But after I disconnected 
the agent for a while, the MQTT connection could not be setup again. Can anyone 
help me for this? Thanks.


MQTT_LISTENER: Connected with result code 4
MQTT_LISTENER: Subscribing with topic carbon.super/raspberrypi/rkwrklcphsmu


－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: API Management, IOT

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IOTS] Failed to get realtime data from IoTS in 1.0.0 alpha

[云展智创]

Hi all,

When I open the IoTS devicemgt ui to view the realtime statistic data of my 
raspberry pi device, I always get below error, so that the graph can now show 
any temperature line. Can anyone help me? Thanks.

WebSocket connection to 
'wss://192.168.2.109:9443/secured-outputui/org.wso2.iot.devices.temperature/1.0.0?token=ecd222ae10d959deb02d3bf2b8f6=1iukwdj4luwxe=raspberrypi'
 failed: WebSocket opening handshake was canceled

－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: API Management, IOT

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] when will the IoTS be GA?

[云展智创]

Hi Sumedha,

Any suggestions? Thanks.

－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: API Management, IOT

On Aug 2, 2016, at 12:45 PM, 云展智创 <i...@smartcloudex.com> wrote:

> Hi Sumedha,
> 
> Any suggestions? Thanks.
> 
> －－
> Zhanwen Zhou (Jason), General Manager
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: API Management, IOT
> 
> On Jul 31, 2016, at 9:20 PM, Sumedha Rubasinghe <sume...@wso2.com> wrote:
> 
>> Hi Jason,
>> UIs in IoTS Master is not fully functional due to on going work I mentioned 
>> b4.
>> 
>> Will get back to you with an alternative plan by tomorrow.
>> 
>> 
>> On Jul 31, 2016 2:48 PM, "云展智创" <i...@smartcloudex.com> wrote:
>> Hi Sumedha,
>> 
>> Yes, I thought the IoTS would be GA on mid of July. I have a project using 
>> IoTS to manage some smart devices. IoTS is the core backend component in the 
>> project.  I also need the cdmf-devicetype-archetype tools to create the 
>> plugins. Could you give me some advices on how to build the latest stable 
>> release from the code? 
>> 
>> by the way, I found that the real time device statistics data could not be 
>> showed on the graph of device view in 1.0.0 Alpha release. Is that a know 
>> error? Thanks.
>> 
>> －－
>> Zhanwen Zhou (Jason), General Manager
>> +86 13922218435
>> zhanwen.z...@smartcloudex.com
>> Guangzhou Smart Cloudex Technology Co., Ltd.
>> Business: API Management, IOT
>> 
>> On Jul 31, 2016, at 11:20 AM, Sumedha Rubasinghe <sume...@wso2.com> wrote:
>> 
>>> Hi Jason,
>>> After the IoTS 1.0.0 Alpha, we are in the middle of a strategic change 
>>> which involves our mobile device management capabilities. 
>>> As you may already be aware, we have brought down all core device 
>>> management capabilities into one level and implementing specific device 
>>> management plugins on top of this. These device management plugins also 
>>> cover our Android, iOS, Windows mobile plugins (as well as plugins for all 
>>> other devices).
>>> 
>>> Originally 1.0.0 GA release date of IoTS was scheduled for July. But due to 
>>> a customer commitment we have shifted our focus to stabilising Android 
>>> device management until end of August.
>>> 
>>> Specific new release date of IoTS 1.0.0 GA will be decided after August.
>>> 
>>> If you have a project that gets impacted due to this shift please fill up 
>>> our contact us form @ http://wso2.com/contact/ with your concern and we 
>>> will see what we can do.
>>>  
>>> Thanks,
>>> Sumedha
>>> 
>>> 
>>> On Sat, Jul 30, 2016 at 3:03 PM, 云展智创 <i...@smartcloudex.com> wrote:
>>> Hi,
>>> 
>>> Could anyone tell me when will the IoTS be GA? Thanks a lot.
>>> 
>>> －－
>>> Zhanwen Zhou (Jason),
>>> +86 13922218435
>>> zhanwen.z...@smartcloudex.com
>>> Guangzhou Smart Cloudex Technology Co., Ltd.
>>> Business: API Management, IOT
>>> 
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>> 
>>> 
>>> 
>>> -- 
>>> /sumedha
>>> m: +94 773017743
>>> b :  bit.ly/sumedha
>> 
>> 
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] when will the IoTS be GA?

[云展智创]

Hi Sumedha,

Any suggestions? Thanks.

－－
Zhanwen Zhou (Jason), General Manager
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: API Management, Application Performance Management, IT Service 
Management

On Jul 31, 2016, at 9:20 PM, Sumedha Rubasinghe <sume...@wso2.com> wrote:

> Hi Jason,
> UIs in IoTS Master is not fully functional due to on going work I mentioned 
> b4.
> 
> Will get back to you with an alternative plan by tomorrow.
> 
> 
> On Jul 31, 2016 2:48 PM, "云展智创" <i...@smartcloudex.com> wrote:
> Hi Sumedha,
> 
> Yes, I thought the IoTS would be GA on mid of July. I have a project using 
> IoTS to manage some smart devices. IoTS is the core backend component in the 
> project.  I also need the cdmf-devicetype-archetype tools to create the 
> plugins. Could you give me some advices on how to build the latest stable 
> release from the code? 
> 
> by the way, I found that the real time device statistics data could not be 
> showed on the graph of device view in 1.0.0 Alpha release. Is that a know 
> error? Thanks.
> 
> －－
> Zhanwen Zhou (Jason), General Manager
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: API Management, IOT
> 
> On Jul 31, 2016, at 11:20 AM, Sumedha Rubasinghe <sume...@wso2.com> wrote:
> 
>> Hi Jason,
>> After the IoTS 1.0.0 Alpha, we are in the middle of a strategic change which 
>> involves our mobile device management capabilities. 
>> As you may already be aware, we have brought down all core device management 
>> capabilities into one level and implementing specific device management 
>> plugins on top of this. These device management plugins also cover our 
>> Android, iOS, Windows mobile plugins (as well as plugins for all other 
>> devices).
>> 
>> Originally 1.0.0 GA release date of IoTS was scheduled for July. But due to 
>> a customer commitment we have shifted our focus to stabilising Android 
>> device management until end of August.
>> 
>> Specific new release date of IoTS 1.0.0 GA will be decided after August.
>> 
>> If you have a project that gets impacted due to this shift please fill up 
>> our contact us form @ http://wso2.com/contact/ with your concern and we will 
>> see what we can do.
>>  
>> Thanks,
>> Sumedha
>> 
>> 
>> On Sat, Jul 30, 2016 at 3:03 PM, 云展智创 <i...@smartcloudex.com> wrote:
>> Hi,
>> 
>> Could anyone tell me when will the IoTS be GA? Thanks a lot.
>> 
>> －－
>> Zhanwen Zhou (Jason),
>> +86 13922218435
>> zhanwen.z...@smartcloudex.com
>> Guangzhou Smart Cloudex Technology Co., Ltd.
>> Business: API Management, IOT
>> 
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>> 
>> 
>> 
>> -- 
>> /sumedha
>> m: +94 773017743
>> b :  bit.ly/sumedha
> 
> 

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] when will the IoTS be GA?

[云展智创]

Hi Sumedha,

Yes, I thought the IoTS would be GA on mid of July. I have a project using IoTS 
to manage some smart devices. IoTS is the core backend component in the 
project.  I also need the cdmf-devicetype-archetype tools to create the 
plugins. Could you give me some advices on how to build the latest stable 
release from the code? 

by the way, I found that the real time device statistics data could not be 
showed on the graph of device view in 1.0.0 Alpha release. Is that a know 
error? Thanks.

－－
Zhanwen Zhou (Jason), General Manager
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: API Management, IOT

On Jul 31, 2016, at 11:20 AM, Sumedha Rubasinghe <sume...@wso2.com> wrote:

> Hi Jason,
> After the IoTS 1.0.0 Alpha, we are in the middle of a strategic change which 
> involves our mobile device management capabilities. 
> As you may already be aware, we have brought down all core device management 
> capabilities into one level and implementing specific device management 
> plugins on top of this. These device management plugins also cover our 
> Android, iOS, Windows mobile plugins (as well as plugins for all other 
> devices).
> 
> Originally 1.0.0 GA release date of IoTS was scheduled for July. But due to a 
> customer commitment we have shifted our focus to stabilising Android device 
> management until end of August.
> 
> Specific new release date of IoTS 1.0.0 GA will be decided after August.
> 
> If you have a project that gets impacted due to this shift please fill up our 
> contact us form @ http://wso2.com/contact/ with your concern and we will see 
> what we can do.
>  
> Thanks,
> Sumedha
> 
> 
> On Sat, Jul 30, 2016 at 3:03 PM, 云展智创 <i...@smartcloudex.com> wrote:
> Hi,
> 
> Could anyone tell me when will the IoTS be GA? Thanks a lot.
> 
> －－
> Zhanwen Zhou (Jason),
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: API Management, IOT
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
> 
> 
> 
> -- 
> /sumedha
> m: +94 773017743
> b :  bit.ly/sumedha

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTS] when will the IoTS be GA?

[云展智创]

Hi,

Could anyone tell me when will the IoTS be GA? Thanks a lot.

－－
Zhanwen Zhou (Jason), 
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: API Management, IOT

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] Questions about how to authenticate user and request data from IoTS

[云展智创]

I have solved the problem. please miss the mail.

－－
Zhanwen Zhou (Jason), General Manager
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API

On Jul 13, 2016, at 3:53 PM, 云展智创 <i...@smartcloudex.com> wrote:

> Thanks.
> 
> For the first question, if I call the api https:// IP>:9443/dynamic-client-web/register/ with curl or RESTClient, I can get the 
> client id and secret. But if I call it with ajax or xmlhttprequest, I got the 
> following errors:
> ——
> threw an 
> exception\n\torg.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)\nroot
>  cause java.lang.NoSuchMethodError: 
> javax.ws.rs.InternalServerErrorException.validate(Ljavax/ws/rs/core/Response;Ljavax/ws/rs/core/Response$Status;)Ljavax/ws/rs/core/Response;\n\tjavax.ws.rs.InternalServerErrorException.init(InternalServerErrorException.java:92)\n\torg.apache.cxf.jaxrs.utils.SpecExceptions.toInternalServerErrorException(SpecExceptions.java:77)\n\torg.apache.cxf.jaxrs.utils.ExceptionUtils.toInternalServerErrorException(ExceptionUtils.java:110)\n\torg.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.convertExceptionToResponseIfPossible(JAXRSInInterceptor.java:267)\n\torg.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:256)\n\torg.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:88)\n\torg.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)\n\torg.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)\n\torg.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249)\n\torg.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)\n\torg.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)\n\torg.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)\n\torg.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171)\n\torg.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:289)\n\torg.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:209)\n\tjavax.servlet.http.HttpServlet.service(HttpServlet.java:646)\n\torg.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:265)\n\torg.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)\nnote
>  The full stack trace of the root cause is available in the Apache 
> Tomcat/7.0.59 logs.Apache 
> Tomcat/7.0.59","responseXML":null,"responseType":"","response":"Apache
>  Tomcat/7.0.59 - Error report<!--H1 
> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
>  H2 
> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
>  H3 
> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
>  BODY 
> {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B 
> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P 
> {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
>  {color : black;}A.name {color : black;}HR {color : #525D76;}--> 
> HTTP Status 500 - Servlet execution threw an 
> exceptiontype Exception 
> reportmessage Servlet execution threw an 
> exceptiondescription The server encountered an internal 
> error that prevented it from fulfilling this 
> request.exception javax.servlet.ServletException: 
> Servlet execution threw an 
> exception\n\torg.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)\nroot
>  cause java.lang.NoSuchMethodError: 
> javax.ws.rs.InternalServerErrorException.validate(Ljavax/ws/rs/core/Response;Ljavax/ws/rs/core/Response$Status;)Ljavax/ws/rs/core/Response;\n\tjavax.ws.rs.InternalServerErrorException.init(InternalServerErrorException.java:92)\n\torg.apache.cxf.jaxrs.utils.SpecExceptions.toInternalServerErrorException(SpecExceptions.java:77)\n\torg.apache.cxf.jaxrs.utils.ExceptionUtils.toInternalServerErrorException(ExceptionUtils.java:110)\n\torg.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.convertExceptionToResponseIfPossible(JAXRSInInterceptor.java:267)\n\torg.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:256)\n\torg.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:88)\n\torg.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)\n\torg.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)\n\torg.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249)\n\torg.apache.cxf.trans

Re: [Dev] [IoTS] Questions about how to authenticate user and request data from IoTS

[云展智创]

.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:209)\n\tjavax.servlet.http.HttpServlet.service(HttpServlet.java:646)\n\torg.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:265)\n\torg.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)\nnote
 The full stack trace of the root cause is available in the Apache 
Tomcat/7.0.59 logs.Apache 
Tomcat/7.0.59","status":500,"statusText":"Internal Server 
Error","responseURL":"http://X.cn:9763/dynamic-client-web/register/“}


I think it’s because my H5 apps is run in domain 127.0.0.1 in the mobile phone 
and when it send the request to IoTS server, it is a cross domain call. And 
IoTS refuse the request. Is that right? Could anyone tell me how to config the 
IoTS server to accept CORS request? Thanks.


－－
Zhanwen Zhou (Jason), 
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API

On Jul 13, 2016, at 3:06 PM, Dumidu Handakumbura <dum...@wso2.com> wrote:

> Hi Zhanwen,
> 
> With regard to your second question, an API is published for each device type 
> available in the server these can also be used with an appropriately scoped 
> tokens. Check /api-store for a full list of API available.
> 
> Thanks,
> Dumidu
> 
> On Wed, Jul 13, 2016 at 9:51 AM, 云展智创 <i...@smartcloudex.com> wrote:
> Hi all,
> 
> I am writing a HTML5 mobile app to use with IoTS. I use an open source H5 
> framework called MUI, which support ajax and xmlhttprequest. Could you tell 
> me how to authenticate the user with IoTS and request data with the access 
> token? I tried to use ajax call to https:// IP>:9443/dynamic-client-web/register/but failed. I don’t know if it is 
> because of cross domain request. Could you give me some example?
> 
> Besides the device_mgt API in the following website[1], are there any API I 
> can use to get data from IoTS devices and show in my app. 
> 
> Thanks.
> 
> [1] https://docs.wso2.com/display/iots100/apidocs/index.html#guide
> －－
> Zhanwen Zhou (Jason), General Manager
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, APIM
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
> 
> 
> 
> 
> -- 
> Dumidu Handakumbura
> Software Engineer
> WSO2 Inc; http://www.wso2.com/.
> Mobile; +9406740 

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IoTS] Questions about how to authenticate user and request data from IoTS

[云展智创]

Hi all,

I am writing a HTML5 mobile app to use with IoTS. I use an open source H5 
framework called MUI, which support ajax and xmlhttprequest. Could you tell me 
how to authenticate the user with IoTS and request data with the access token? 
I tried to use ajax call to https://:9443/dynamic-client-web/register/but failed. I don’t know if it is because 
of cross domain request. Could you give me some example?

Besides the device_mgt API in the following website[1], are there any API I can 
use to get data from IoTS devices and show in my app. 

Thanks.

[1] https://docs.wso2.com/display/iots100/apidocs/index.html#guide
－－
Zhanwen Zhou (Jason), General Manager
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, APIM___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IOT] How to start building device types in IoTS using Developer Studio

[云展智创]

Hi Geesara,

Thank you for your so detail reply. It really help me.

I have 2 more questions:
1. As I have to use cdmf-devicetype-archetype for M3 release to create the new 
device type, Is that means the new device type CAN NOT be deploy in M4 or later 
release of IoTS (because of the package dependencies)? Then how to smoothly 
reuse that created new device type in the coming GA version of IoTS? Can I 
build the product-iot project (master) to create the newest deployable IoTS and 
use it for testing, but I think there may be some errors in device-deploy.xml 
and other places because the product-iot is still changing?

2. I have red the the content in "Writing Your Own Device Connector” before, 
but there is little information about UI design. I know that we can create 
extensions for customized UI development as IoTS use UUF framework. My 
questions is do we have a WYSIWYG IDE tools to design the ui extensions for my 
device types. Is it to use jaggery project in Developer Studio to design ui? or 
I need to wait for the next release of IoTS as those features are in that 
release?

Thanks Geesara.

－－
Zhanwen Zhou (Jason)

在 2016年4月12日，下午10:44，Geesara Prathap <gees...@wso2.com> 写道：

> Hi Jason,
> 
> I have forked the product-iot project, cloned into my desktop. After running 
> mvn eclipse:eclipse in product-iot, I can only find 3 projects 
> (cdmf-devicetype-archetype, mdm-android-agent-archetype, 
> org.wso.iot.admin.styles) when I import projects in product-iot folder. Is 
> that right?
> 
> This is not the right approach you need to follow. First of all, you don't 
> need to download product-iots. What you need is download IoTS pack from 
> here[1]. Then there are some sample device type plugins which are in the 
> sample folder you can try out. I hope you have tried how to create new device 
> type plugin using maven archetype by now. 
> 
> How can I import the whole iot project and start creating my blocks and 
> building them with Maven? 
> 
> So open any samples using wso2 developer studio or any other IDE which 
> support maven as a maven project. In M3, some of the dependencies are getting 
> as system dependencies. So don't move or relocated sample device types 
> plugins from sample folder. So once you created device type plugin from maven 
> archetype you can do any changes to each component as you required. But 
> device-deployer.xml can't use to redeploy your device type plugin. This 
> feature wasn't included in M3 pack. What you can do is as an example let's 
> say you have done some changes on  controller or manager web app. Then you 
> have to copy and paste each web app into 
> /repository/deployment/server/webapps. Listed below each component where to 
> copy once done some changes on it. 
> 
> controller/manager web app -  /repository/deployment/server/webapps
> plugin -/repository/components/dropins 
> (need to restart server to apply new changes)
> analytics carbonapps - /repository/deployment/server/carbonapps
> UI units -  
> /repository/deployment/server/jaggeryapps/devicemgt/app/units 
>   
> 
> Note: this structure is applied to M3 and all paths are taken relative to 
> IoTS_HOME.
> This[2] explains each and every component separately how to write your own 
> device type plugin.
> 
> 
> For example, to create and build a new device type with 
> cdmf-devicetype-archetype in Developer Studio.
> 
> This feature will be available in next release of IoTS.
> 
> 
> 1.https://github.com/wso2/product-iots/releases/tag/IoTS-1.0.0-M3
> 2.https://docs.wso2.com/display/IoTS100/Writing+Your+Own+Device+Connector
> 
> Thanks,
> Geesara
> 
> 
> On Tue, Apr 12, 2016 at 6:49 PM, 云展智创 <i...@smartcloudex.com> wrote:
> Hi all,
> 
> Could you give me some advices on how to start building iot device types in 
> IoTS using Developer Studio?
> 
> I have forked the product-iot project, cloned into my desktop. After running 
> mvn eclipse:eclipse in product-iot, I can only find 3 projects 
> (cdmf-devicetype-archetype, mdm-android-agent-archetype, 
> org.wso.iot.admin.styles) when I import projects in product-iot folder. Is 
> that right? How can I import the whole iot project and start creating my 
> blocks and building them with Maven? For example, to create and build a new 
> device type with cdmf-devicetype-archetype in Developer Studio.
> 
> And how can I design the ui of the new iot device type plugin with Developer 
> Studio? Is that WYSIWYG design interface with Developer Studio?
> 
> Thanks.
> 
> －－
> Zhanwen Zhou (Jason)
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.

[Dev] [IOT] How to start building device types in IoTS using Developer Studio

[云展智创]

Hi all,

Could you give me some advices on how to start building iot device types in 
IoTS using Developer Studio? 

I have forked the product-iot project, cloned into my desktop. After running 
mvn eclipse:eclipse in product-iot, I can only find 3 projects 
(cdmf-devicetype-archetype, mdm-android-agent-archetype, 
org.wso.iot.admin.styles) when I import projects in product-iot folder. Is that 
right? How can I import the whole iot project and start creating my blocks and 
building them with Maven? For example, to create and build a new device type 
with cdmf-devicetype-archetype in Developer Studio. 

And how can I design the ui of the new iot device type plugin with Developer 
Studio? Is that WYSIWYG design interface with Developer Studio? 

Thanks.

－－
Zhanwen Zhou (Jason)

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][IOT][CDMF] Errors when building new device type in IoTS using cdmf-devicetype-archetype-master

[云展智创]

Geesara,

Thank you very much! I can pass the building process of the new device types. 

－－
Zhanwen Zhou (Jason)

在 2016年4月11日，下午4:14，Geesara Prathap <gees...@wso2.com> 写道：

> Hi Zhou,
> 
> Is that right to select 4 in below step?  You should select 2
> 
> What’s the difference between 2 and 4 archetype selection? In maven archetype 
> plugin groupId renamed from m3 to m4. In M3 it was named as cdmf.devicetype. 
> But m4 onwards it named as org.wso2.cdmf.devicetype. Please follow the 
> instruction in README[1]. It says everything you need to follow.
> 
> 1. https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3
> 
> Thanks,
> Geesara
> 
> On Mon, Apr 11, 2016 at 1:31 PM, 云展智创 <i...@smartcloudex.com> wrote:
> Hi Shabir/Geesara,
> 
> Is that right to select 4 in below step? What’s the difference between 2 and 
> 4 archetype selection?
> 
> $ mvn archetype:generate -DarchetypeCatalog=local
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=1024m; 
> support was removed in 8.0
> [INFO] Scanning for projects...
> [INFO]
>  
> [INFO] 
> 
> [INFO] Building Maven Stub Project (No POM) 1
> [INFO] 
> 
> [INFO] 
> [INFO] >>> maven-archetype-plugin:2.4:generate (default-cli) > 
> generate-sources @ standalone-pom >>>
> [INFO] 
> [INFO] <<< maven-archetype-plugin:2.4:generate (default-cli) < 
> generate-sources @ standalone-pom <<<
> [INFO] 
> [INFO] --- maven-archetype-plugin:2.4:generate (default-cli) @ standalone-pom 
> ---
> [INFO] Generating project in Interactive mode
> [INFO] No archetype defined. Using maven-archetype-quickstart 
> (org.apache.maven.archetypes:maven-archetype-quickstart:1.0)
> Choose archetype:
> 1: local -> org.wso2.iot:mdm-android-agent-archetype (Creates a MDM-Android 
> agent project)
> 2: local -> cdmf.devicetype:cdmf-devicetype-archetype (WSO2 CDMF Device Type 
> Archetype)
> 3: local -> org.wso2.mdm:mdm-android-agent-archetype (Creates a MDM-Android 
> agent project)
> 4: local -> org.wso2.cdmf.devicetype:cdmf-devicetype-archetype (WSO2 CDMF 
> Device Type Archetype)
> Choose a number or apply filter (format: [groupId:]artifactId, case sensitive 
> contains): : 4
> 
> －－
> Zhanwen Zhou (Jason), 
> 
> 在 2016年4月11日，下午3:08，Shabir Mohamed <sha...@wso2.com> 写道：
> 
>> Hi Zhou,
>> 
>> If you still get any additional errors, please do send us the errors printed 
>> in the error logs at:
>> /Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/
>> 
>> so we could deduce why the device-deployer actually failed.
>> 
>> Regards
>> 
>> -
>> Shabir Mohamed
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> Email: sha...@wso2.com 
>> Mobile: +94 77 3516019 | +94 71 6583393
>> 
>> On Mon, Apr 11, 2016 at 12:27 PM, Geesara Prathap <gees...@wso2.com> wrote:
>> Hi Zhou,
>> 
>> copied file org.wso2.carbon.device.mgt.iot_2.0.4.SNAPSHOT.jar into the 
>> repository/components/plugins folder)
>> 
>> No need to copy any of *.jar files manually. All necessary *jar files are 
>> copied by maven archetype when building device type plugin. 
>> 
>> I found that the feature target file had been built (but I didn’t know why 
>> the version is 1.0-SNAPSHOT, and not 1.0.0-SNAPSHOT) in the feature folder 
>> of my device type, so I used following command to install it, successfully 
>> finished.
>> 
>> the default version is set to 1.0-SNAPSHOT when building new device type 
>> plugin. If you need you can change as you require. But please define correct 
>> version, groupid and artifactId in device-deploye.xml as mention here[1]. 
>> 
>> 
>> 
>> 1. https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3 
>> (branch IoTS-1.0.0-M3)
>> 
>> Thanks,
>> Geesara
>> 
>> On Mon, Apr 11, 2016 at 12:04 PM, Charitha Goonetilleke <charit...@wso2.com> 
>> wrote:
>> [Adding Ayyoob & Geesara to the thread]
>> 
>> Hi Zhou,
>> 
>> Since we are working with next milestone release, archtype in product-iots 
>> master branch will not generate compatible device type plugin for M3 pack. 
>> It is the reason for above mentioned issues. So please checkout M3 
>> compatible archtype from this link[2] and try to regenerate your

Re: [Dev] [DEV][IOT][CDMF] Errors when building new device type in IoTS using cdmf-devicetype-archetype-master

[云展智创]

Hi Shabir/Geesara,

Is that right to select 4 in below step? What’s the difference between 2 and 4 
archetype selection?

$ mvn archetype:generate -DarchetypeCatalog=local
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=1024m; 
support was removed in 8.0
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building Maven Stub Project (No POM) 1
[INFO] 
[INFO] 
[INFO] >>> maven-archetype-plugin:2.4:generate (default-cli) > generate-sources 
@ standalone-pom >>>
[INFO] 
[INFO] <<< maven-archetype-plugin:2.4:generate (default-cli) < generate-sources 
@ standalone-pom <<<
[INFO] 
[INFO] --- maven-archetype-plugin:2.4:generate (default-cli) @ standalone-pom 
---
[INFO] Generating project in Interactive mode
[INFO] No archetype defined. Using maven-archetype-quickstart 
(org.apache.maven.archetypes:maven-archetype-quickstart:1.0)
Choose archetype:
1: local -> org.wso2.iot:mdm-android-agent-archetype (Creates a MDM-Android 
agent project)
2: local -> cdmf.devicetype:cdmf-devicetype-archetype (WSO2 CDMF Device Type 
Archetype)
3: local -> org.wso2.mdm:mdm-android-agent-archetype (Creates a MDM-Android 
agent project)
4: local -> org.wso2.cdmf.devicetype:cdmf-devicetype-archetype (WSO2 CDMF 
Device Type Archetype)
Choose a number or apply filter (format: [groupId:]artifactId, case sensitive 
contains): : 4

－－
Zhanwen Zhou (Jason), 

在 2016年4月11日，下午3:08，Shabir Mohamed <sha...@wso2.com> 写道：

> Hi Zhou,
> 
> If you still get any additional errors, please do send us the errors printed 
> in the error logs at:
> /Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/
> 
> so we could deduce why the device-deployer actually failed.
> 
> Regards
> 
> -
> Shabir Mohamed
> Software Engineer
> WSO2 Inc.; http://wso2.com
> Email: sha...@wso2.com 
> Mobile: +94 77 3516019 | +94 71 6583393
> 
> On Mon, Apr 11, 2016 at 12:27 PM, Geesara Prathap <gees...@wso2.com> wrote:
> Hi Zhou,
> 
> copied file org.wso2.carbon.device.mgt.iot_2.0.4.SNAPSHOT.jar into the 
> repository/components/plugins folder)
> 
> No need to copy any of *.jar files manually. All necessary *jar files are 
> copied by maven archetype when building device type plugin. 
> 
> I found that the feature target file had been built (but I didn’t know why 
> the version is 1.0-SNAPSHOT, and not 1.0.0-SNAPSHOT) in the feature folder of 
> my device type, so I used following command to install it, successfully 
> finished.
> 
> the default version is set to 1.0-SNAPSHOT when building new device type 
> plugin. If you need you can change as you require. But please define correct 
> version, groupid and artifactId in device-deploye.xml as mention here[1]. 
> 
> 
> 
> 1. https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3 
> (branch IoTS-1.0.0-M3)
> 
> Thanks,
> Geesara
> 
> On Mon, Apr 11, 2016 at 12:04 PM, Charitha Goonetilleke <charit...@wso2.com> 
> wrote:
> [Adding Ayyoob & Geesara to the thread]
> 
> Hi Zhou,
> 
> Since we are working with next milestone release, archtype in product-iots 
> master branch will not generate compatible device type plugin for M3 pack. It 
> is the reason for above mentioned issues. So please checkout M3 compatible 
> archtype from this link[2] and try to regenerate your device type with it.
> 
> Also, with given M3 compatible archtype, you don't want to copy any jar file 
> to plugins directory by your self.
> 
> [1] 
> https://github.com/wso2/carbon-device-mgt-plugins/tree/IoTS-1.0.0-M3/components/device-mgt-iot
> [2] 
> https://github.com/wso2/product-iots/tree/master/modules/tools/cdmf-devicetype-archetype
> [3] https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3
> 
> Thanks & Regards,
> /charithag
> 
> 
> On Mon, Apr 11, 2016 at 11:10 AM, 云展智创 <i...@smartcloudex.com> wrote:
> Hi all,
> 
> I created a new device type using cdmf-devicetype-archetype-master tool, and 
> updated the file device-deployer.xml (used IoTS-M3 SNAPSHOT, and copied file 
> org.wso2.carbon.device.mgt.iot_2.0.4.SNAPSHOT.jar into the 
> repository/components/plugins folder) with correct info of my device type, 
> but when I built the file "device-deployer.xml”, I got the following errors:
> 
> Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: 
> Could not find artifact 
> com.smartcloudex:com.smartcloudex.thermometer.feature:zip:1.0.0-SNAPSHOT in 
> wso2-nexus (http://maven.w

[Dev] [DEV][IOT][CDMF] Errors when building new device type in IoTS using cdmf-devicetype-archetype-master

[云展智创]

Hi all,

I created a new device type using cdmf-devicetype-archetype-master tool, and 
updated the file device-deployer.xml (used IoTS-M3 SNAPSHOT, and copied file 
org.wso2.carbon.device.mgt.iot_2.0.4.SNAPSHOT.jar into the 
repository/components/plugins folder) with correct info of my device type, but 
when I built the file "device-deployer.xml”, I got the following errors:

Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Could 
not find artifact 
com.smartcloudex:com.smartcloudex.thermometer.feature:zip:1.0.0-SNAPSHOT in 
wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)

I found that the feature target file had been built (but I didn’t know why the 
version is 1.0-SNAPSHOT, and not 1.0.0-SNAPSHOT) in the feature folder of my 
device type, so I used following command to install it, successfully finished.

mvn install:install-file -DgroupId=com.smartcloudex 
-DartifactId=com.smartcloudex.thermometer.feature -Dversion=1.0.0-SNAPSHOT 
-Dpackaging=zip 
-Dfile=/Users/zhanwen/Documents/WSO2/IOT/wso2iots-1.0.0-SNAPSHOT/samples/thermometer/feature/feature/target/com.smartcloudex.thermometer.feature-1.0-SNAPSHOT.zip

But when I executed the command “mvn clean install -f device-deployer.xml” 
again I got the following errors. Was there any mistake in my steps? Could 
anyone help me? Thanks.

[INFO] 
[INFO] --- carbon-p2-plugin:1.5.3:p2-profile-gen (feature-install) @ 
devicetype-feature-installation ---
[INFO] Running Equinox P2 Director Application
[INFO] Command line:
/bin/sh -c cd /Users/zhanwen/Documents/WSO2/IOT/wso2iots-1.0.0-SNAPSHOT 
&& /Library/Java/JavaVirtualMachines/jdk1.8.0_73.jdk/Contents/Home/jre/bin/java 
-jar 
/Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar
 -nosplash -application org.eclipse.equinox.p2.director -metadataRepository 
file:/Users/zhanwen/Documents/WSO2/IOT/wso2iots-1.0.0-SNAPSHOT/samples/p2-repo 
-artifactRepository 
file:/Users/zhanwen/Documents/WSO2/IOT/wso2iots-1.0.0-SNAPSHOT/samples/p2-repo 
-profileProperties org.eclipse.update.install.features=true -installIU 
org.coffeeking.connectedcup.feature.group/1.9.2.SNAPSHOT,org.homeautomation.currentsensor.feature.group/1.9.2.SNAPSHOT,com.smartcloudex.feature.group/1.0.0.SNAPSHOT,
 -bundlepool repository/components -shared repository/components/p2 
-destination repository/components/default -profile default -roaming
Installation failed.
The installable unit com.smartcloudex.feature.group/1.0.0.SNAPSHOT has not been 
found.
Application failed, log file location: 
/Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1460350536316.log

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] WSO2 IoTS(Device Types) - Connected Cup Component .. SUCCESS [  0.660 s]
[INFO] WSO2 IoTS(Device Types) - Connected Cup Component .. SUCCESS [  0.025 s]
[INFO] WSO2 IoTS(Device Types) - Connected Cup Analytics capp SUCCESS [  1.296 
s]
[INFO] WSO2 IoTS(Device Types) - Connected Cup CDMF Plugin  SUCCESS [  2.029 s]
[INFO] WSO2 IoTS(Device Types) - Connected Cup Controller Service SUCCESS [  
2.668 s]
[INFO] WSO2 IoTS(Device Types) - Connected Cup Manager Service SUCCESS [  1.366 
s]
[INFO] WSO2 IoTS(Device Types) - Connected Cup Agent Web app SUCCESS [  1.292 s]
[INFO] WSO2 IoTS(Device Types) - Connected Cup UI . SUCCESS [  0.137 s]
[INFO] WSO2 IoTS(Device Types) - Connected Cup Feature Parent SUCCESS [  0.017 
s]
[INFO] WSO2 IoTS(Device Types) - Connected Cup Feature  SUCCESS [  2.407 s]
[INFO] org.homeautomation.currentsensor.analytics . SUCCESS [  0.110 s]
[INFO] org.homeautomation.currentsensor.plugin for CDMF ... SUCCESS [  0.801 s]
[INFO] org.homeautomation.currentsensor.controller API  SUCCESS [  1.831 s]
[INFO] org.homeautomation.currentsensor.manager ... SUCCESS [  1.488 s]
[INFO] org.homeautomation.currentsensor.agent . SUCCESS [  0.057 s]
[INFO] org.homeautomation.currentsensor.ui  SUCCESS [  0.097 s]
[INFO] currentsensor .. SUCCESS [  0.015 s]
[INFO] WSO2 IoTS(Device Types) - Current Sensor Component . SUCCESS [  0.018 s]
[INFO] feature  SUCCESS [  0.015 s]
[INFO] org.homeautomation.currentsensor.feature ... SUCCESS [  1.742 s]
[INFO] thermometer  SUCCESS [  0.015 s]
[INFO] thermometer-component .. SUCCESS [  0.018 s]
[INFO] com.smartcloudex.thermometer.plugin  SUCCESS [  0.795 s]
[INFO] com.smartcloudex.thermometer.controller  SUCCESS [  1.297 s]
[INFO] com.smartcloudex.thermometer.manager ... SUCCESS [  0.815 s]
[INFO] com.smartcloudex.thermometer.analytics . SUCCESS [  0.226 s]
[INFO] com.smartcloudex.thermometer.ui 

Re: [Dev] IoTS-1.0.0-M4 Build order

[云展智创]

Hi Charitha,

When I built the master branch of identity-oauth2-grant-jwt, I got the 
following errors. Could you give me some advices. Thanks.

[ERROR] Bundle 
org.wso2.carbon.identity:org.wso2.carbon.identity.oauth2.grant.jwt:bundle:1.0.0 
: Unresolved references to [org.apache.oltu.oauth2.common] by class(es) on the 
Bundle-Classpath[Jar:dot]: 
[org/wso2/carbon/identity/oauth2/grant/jwt/JWTGrantValidator.class]
[ERROR] Error(s) found in bundle configuration
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] WSO2 Carbon Extension - JWT Grant Type Pom . SUCCESS [ 59.176 s]
[INFO] JWT grant type for OAuth2 .. FAILURE [  5.574 s]
[INFO] WSO2 Carbon - identity JWT Grant Type Feature .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 01:05 min
[INFO] Finished at: 2016-04-06T09:12:08+08:00
[INFO] Final Memory: 74M/1983M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.felix:maven-bundle-plugin:2.3.5:bundle (default-bundle) on project 
org.wso2.carbon.identity.oauth2.grant.jwt: Error(s) found in bundle 
configuration -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :org.wso2.carbon.identity.oauth2.grant.jwt


－－
Zhanwen Zhou (Jason)

在 2016年3月31日，下午7:17，Charitha Goonetilleke  写道：

> Hi All,
> 
> We have moved to master branches of carbon-device-mgt and 
> carbon-device-mgt-plugins. Please follow this build order to build IoT Server 
> product.
> https://github.com/wso2-incubator/uuf-template-app  branch:IoTS-1.0.0-M4
> https://github.com/wso2-extensions/identity-oauth2-grant-jwt branch:master
> https://github.com/wso2/carbon-device-mgt  branch:master
> https://github.com/wso2/carbon-device-mgt-plugins  branch:master
> https://github.com/wso2-incubator/product-iot-server  branch:master
> 
> On Mon, Mar 28, 2016 at 11:50 AM, Charitha Goonetilleke  
> wrote:
> Hi All,
> 
> We have made some of changes to product and build order has been changed 
> accordingly. We will be able to move to master branch of carbon-device-mgt 
> and carbon-device-mgt-plugins, once we completed required changes to work 
> with changes in carbon-device-mgt master.
> 
> https://github.com/wso2-incubator/uuf-template-app  branch:IoTS-1.0.0-M4
> https://github.com/wso2-extensions/identity-oauth2-grant-jwt branch:master
> https://github.com/wso2/carbon-device-mgt  branch:IoTS-1.0.0-M4
> https://github.com/wso2/carbon-device-mgt-plugins  branch:IoTS-1.0.0-M4
> https://github.com/wso2-incubator/product-iot-server  branch:master
> 
> 
> On Wed, Mar 16, 2016 at 10:33 AM, Sumedha Rubasinghe  wrote:
> Resending to dev list.
> 
> On Mar 16, 2016 10:22 AM, "Charitha Goonetilleke"  wrote:
> Hi All,
> 
> Since few PRs are merged to depended repos, here is the new build order.
> https://github.com/wso2-incubator/uuf-template-app  branch:IoTS-1.0.0-M4
> https://github.com/wso2/carbon-apimgt  branch:release-4.3.x
> https://github.com/wso2/carbon-device-mgt  branch:IoTS-1.0.0-M4
> https://github.com/wso2/carbon-device-mgt-plugins  branch:IoTS-1.0.0-M4
> https://github.com/wso2-incubator/product-iot-server  branch:master
> 
> 
> On Wed, Feb 24, 2016 at 4:48 PM, Ruwan Yatawara  wrote:
> Please follow the following instructions to build the M4 branch.
> 
> https://github.com/wso2-incubator/uuf-template-app  branch:IoTS-1.0.0-M4
> https://github.com/wso2/carbon-apimgt  branch:release-4.3.x
> https://github.com/ruwany/carbon-analytics-common branch:master
> https://github.com/wso2/carbon-device-mgt  branch:IoTS-1.0.0-M4
> https://github.com/wso2/carbon-device-mgt-plugins  branch:IoTS-1.0.0-M4
> https://github.com/wso2-incubator/product-iot-server  branch:master
> 
> Please note that the analytics-common repo is my personal one, there are some 
> OSGI import related fixes i have done, that have not been merged yet. Once 
> done, building same wont be necessary. However, if in case an carbon-commons 
> related issue is encountered, please build the following as well.
> 
> https://github.com/wso2/carbon-commons branch:4.4.x
> 
> Thanks and Regards,
> 
> Ruwan Yatawara
> 
> Senior Software Engineer,
> WSO2 Inc.
> 
> email : ruw...@wso2.com
> mobile : +94 77 9110413
> blog : 

Re: [Dev] Build error for "WSO2 IoT Server - P2 Profile Gen"

[云展智创]

Ruwan,

Thank you very much! Now I can start the IoTS. I remember I had pull all the 
updates on Tuesday, but anyway, you solve my problem. Thanks again.
－－
Zhanwen 

API & IOT Management 

在 2016年3月10日，下午2:07，Ruwan Yatawara <ruw...@wso2.com> 写道：

> Hi Zhawen,
> 
> We have on-going development happening on the aforementioned set of branches. 
> The CXF error you have quoted is something we have fixed some time ago. Can 
> you please verify if you have taken latest pulls from the branches?
> 
> Thanks and Regards,
> 
> Ruwan Yatawara
> 
> Senior Software Engineer,
> WSO2 Inc.
> 
> email : ruw...@wso2.com
> mobile : +94 77 9110413
> blog : http://ruwansrants.blogspot.com/
> www: :http://wso2.com
> 
> 
> On Thu, Mar 10, 2016 at 11:02 AM, 云展智创 <i...@smartcloudex.com> wrote:
> Hi all,
> 
> After several build tries, the error message were the same as below for every 
> devices:
> 
>>> [2016-03-08 17:05:40,729] ERROR 
>>> {org.apache.catalina.core.ApplicationContext} -  StandardWrapper.Throwable
>>> org.springframework.beans.factory.BeanCreationException: Error creating 
>>> bean with name 'AndroidSenseController': Cannot create inner bean 
>>> 'AndroidSenseControllerService' of type 
>>> [org.wso2.carbon.device.mgt.iot.androidsense.controller.service.impl.AndroidSenseControllerService]
>>>  while setting bean property 'serviceBeans' with key [0]; nested exception 
>>> is org.springframework.beans.factory.BeanCreationException: Error creating 
>>> bean with name 'AndroidSenseControllerService' defined in URL 
>>> [jndi:/localhost/android_sense/WEB-INF/cxf-servlet.xml]: Instantiation of 
>>> bean failed; nested exception is java.lang.NoClassDefFoundError: 
>>> org/wso2/carbon/device/mgt/iot/exception/DeviceControllerException
>>> at 
>>> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:281)
>>> at 
>>> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:120)
>>> at 
>>> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:353)
>>> at 
>>> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:153)
>>> 
>>> [2016-03-08 17:05:40,734] ERROR {org.apache.catalina.core.StandardContext} 
>>> -  Servlet [CXFServlet] in web application [/android_sense] threw load() 
>>> exception
>>> java.lang.ClassNotFoundException: 
>>> org.wso2.carbon.device.mgt.iot.exception.DeviceControllerException
>>> at 
>>> org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154)
>>> at 
>>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
>>> at java.lang.Class.getDeclaredConstructors0(Native Method)
>>> 
>>> [2016-03-08 17:05:40,871] ERROR 
>>> {org.wso2.carbon.apimgt.webapp.publisher.lifecycle.util.AnnotationUtil} -  
>>> Error encountered while scanning for annotations
>>> java.lang.NoClassDefFoundError: 
>>> org/wso2/carbon/device/mgt/iot/exception/DeviceControllerException
>>> at java.lang.Class.getDeclaredMethods0(Native Method)
>>> at java.lang.Class.privateGetDeclaredMethods(Class.java:2570)
>>> at java.lang.Class.getDeclaredMethods(Class.java:1855)
> 
> 
> Any suggestions for this? Thanks.
> －－
> Zhanwen 
> 
> 在 2016年3月9日，上午12:04，云展智创 <i...@smartcloudex.com> 写道：
> 
>> Hi Ruwan,
>> 
>> Thanks for help. I had pulled all the updates of IoTS-1.0.0-M4 and build the 
>> product-iot-server as the order you mentioned, but still got the same errors 
>> when startup.
>> carbon-apimgt  (release-4.3.x)
>> uhf-template-app (IoTS-1.0.0-M4)
>> carbon-device-mgt (IoTS-1.0.0-M4)
>> carbon-device-mgt-plugins (IoTS-1.0.0-M4)
>> product-iot-server (master)
>> 
>> I have attached the error log below.
>> 
>> －－
>> Zhanwen 
>> 
>> IOT & API Management
>> 
>> 在 2016年3月8日，下午6:49，Ruwan Yatawara <ruw...@wso2.com> 写道：
>> 
>>> Hi Zhanwen,
>>> 
>>> Please build the following APIM branch as well, as the particular version 
>>> we are using has not been released yet.
>>> 
>>> https://github.com/wso2/carbon-apimgt/tree/release-4.3.x
>>> 
>>> Thanks and Regards,
>>> 
>>>

Re: [Dev] Build error for "WSO2 IoT Server - P2 Profile Gen"

[云展智创]

Hi all,

After several build tries, the error message were the same as below for every 
devices:

>> [2016-03-08 17:05:40,729] ERROR 
>> {org.apache.catalina.core.ApplicationContext} -  StandardWrapper.Throwable
>> org.springframework.beans.factory.BeanCreationException: Error creating bean 
>> with name 'AndroidSenseController': Cannot create inner bean 
>> 'AndroidSenseControllerService' of type 
>> [org.wso2.carbon.device.mgt.iot.androidsense.controller.service.impl.AndroidSenseControllerService]
>>  while setting bean property 'serviceBeans' with key [0]; nested exception 
>> is org.springframework.beans.factory.BeanCreationException: Error creating 
>> bean with name 'AndroidSenseControllerService' defined in URL 
>> [jndi:/localhost/android_sense/WEB-INF/cxf-servlet.xml]: Instantiation of 
>> bean failed; nested exception is java.lang.NoClassDefFoundError: 
>> org/wso2/carbon/device/mgt/iot/exception/DeviceControllerException
>>  at 
>> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:281)
>>  at 
>> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:120)
>>  at 
>> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:353)
>>  at 
>> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:153)
>> 
>> [2016-03-08 17:05:40,734] ERROR {org.apache.catalina.core.StandardContext} - 
>>  Servlet [CXFServlet] in web application [/android_sense] threw load() 
>> exception
>> java.lang.ClassNotFoundException: 
>> org.wso2.carbon.device.mgt.iot.exception.DeviceControllerException
>>  at 
>> org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154)
>>  at 
>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
>>  at java.lang.Class.getDeclaredConstructors0(Native Method)
>> 
>> [2016-03-08 17:05:40,871] ERROR 
>> {org.wso2.carbon.apimgt.webapp.publisher.lifecycle.util.AnnotationUtil} -  
>> Error encountered while scanning for annotations
>> java.lang.NoClassDefFoundError: 
>> org/wso2/carbon/device/mgt/iot/exception/DeviceControllerException
>>  at java.lang.Class.getDeclaredMethods0(Native Method)
>>  at java.lang.Class.privateGetDeclaredMethods(Class.java:2570)
>>  at java.lang.Class.getDeclaredMethods(Class.java:1855)


Any suggestions for this? Thanks.
－－
Zhanwen 

在 2016年3月9日，上午12:04，云展智创 <i...@smartcloudex.com> 写道：

> Hi Ruwan,
> 
> Thanks for help. I had pulled all the updates of IoTS-1.0.0-M4 and build the 
> product-iot-server as the order you mentioned, but still got the same errors 
> when startup.
> carbon-apimgt  (release-4.3.x)
> uhf-template-app (IoTS-1.0.0-M4)
> carbon-device-mgt (IoTS-1.0.0-M4)
> carbon-device-mgt-plugins (IoTS-1.0.0-M4)
> product-iot-server (master)
> 
> I have attached the error log below.
> 
> －－
> Zhanwen 
> 
> IOT & API Management
> 
> 在 2016年3月8日，下午6:49，Ruwan Yatawara <ruw...@wso2.com> 写道：
> 
>> Hi Zhanwen,
>> 
>> Please build the following APIM branch as well, as the particular version we 
>> are using has not been released yet.
>> 
>> https://github.com/wso2/carbon-apimgt/tree/release-4.3.x
>> 
>> Thanks and Regards,
>> 
>> Ruwan Yatawara
>> 
>> Senior Software Engineer,
>> WSO2 Inc.
>> 
>> email : ruw...@wso2.com
>> mobile : +94 77 9110413
>> blog : http://ruwansrants.blogspot.com/
>> www: :http://wso2.com
>> 
>> 
>> On Tue, Mar 8, 2016 at 3:45 PM, Ruwan Yatawara <ruw...@wso2.com> wrote:
>> Hi Yasith,
>> 
>> Please go ahead and build the components in the following order. You will be 
>> able to build a working distribution.
>> 
>> https://github.com/wso2/carbon-device-mgt/tree/IoTS-1.0.0-M4
>> https://github.com/wso2/carbon-device-mgt-plugins/tree/IoTS-1.0.0-M4
>> 
>> https://github.com/wso2-incubator/product-iot-server/tree/master
>> 
>> 
>> Thanks and Regards,
>> 
>> Ruwan Yatawara
>> 
>> Senior Software Engineer,
>> WSO2 Inc.
>> 
>> email : ruw...@wso2.com
>> mobile : +94 77 9110413
>> blog : http://ruwansrants.blogspot.com/
>> www: :http://wso2.com
>> 
>> 
>> On Tue, Mar 8, 2016 at 3:05 PM, 云展智创 <i...@smartcloudex.com> wrote:
>> Yasith,
>> 
>> Thank

Re: [Dev] Build error for "WSO2 IoT Server - P2 Profile Gen"

[云展智创]

Yasith,

Thank you. Now I can build product-iot-server successfully (I didn’t build the 
carbon-analytics-common in your last mail but still pass the IoTS building 
process. Was that step necessary? But I did build the carbon-event-processing 
branch release 2.0.11 before for other testing). But when I deploy the product 
in the target folder and run wso2server.sh. There were lots of java errors 
about device plugin such as:

[2016-03-08 17:05:40,729] ERROR {org.apache.catalina.core.ApplicationContext} - 
 StandardWrapper.Throwable
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'AndroidSenseController': Cannot create inner bean 
'AndroidSenseControllerService' of type 
[org.wso2.carbon.device.mgt.iot.androidsense.controller.service.impl.AndroidSenseControllerService]
 while setting bean property 'serviceBeans' with key [0]; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'AndroidSenseControllerService' defined in URL 
[jndi:/localhost/android_sense/WEB-INF/cxf-servlet.xml]: Instantiation of bean 
failed; nested exception is java.lang.NoClassDefFoundError: 
org/wso2/carbon/device/mgt/iot/exception/DeviceControllerException
at 
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:281)
at 
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:120)
at 
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:353)
at 
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:153)

[2016-03-08 17:05:40,734] ERROR {org.apache.catalina.core.StandardContext} -  
Servlet [CXFServlet] in web application [/android_sense] threw load() exception
java.lang.ClassNotFoundException: 
org.wso2.carbon.device.mgt.iot.exception.DeviceControllerException
at 
org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154)
at 
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
at java.lang.Class.getDeclaredConstructors0(Native Method)

[2016-03-08 17:05:40,871] ERROR 
{org.wso2.carbon.apimgt.webapp.publisher.lifecycle.util.AnnotationUtil} -  
Error encountered while scanning for annotations
java.lang.NoClassDefFoundError: 
org/wso2/carbon/device/mgt/iot/exception/DeviceControllerException
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2570)
at java.lang.Class.getDeclaredMethods(Class.java:1855)

And I could only see the errors and no devices after I login IoT server device 
management page. Do you know what’s the problem with my IoTS distribution? 

Thanks.
－－
Zhanwen 

API & IOT Management

在 2016年3月8日，下午1:19，Yasith Lokuge <yasi...@gmail.com> 写道：

> Hi Zhanwen,
> 
> Get the updated carbon-device-mgt-plugins branch:IoTS-1.0.0-M4 and build it.
> 
> https://github.com/wso2/carbon-device-mgt-plugins  branch:IoTS-1.0.0-M4
> 
> and build the following component as well,
> 
> https://github.com/ruwany/carbon-analytics-common branch:master
> 
> Then build the product-iot-server again.
> 
> Regards,
> Yasith Lokuge.
> 
> 
> On Tue, Mar 8, 2016 at 8:51 AM, 云展智创 <i...@smartcloudex.com> wrote:
> Hi Yasith,
> 
> Thank you very much. Your solution helped me to pass the installation of WSO2 
> Carbon - Analytics Event Table Server Feature 1.0.6.SNAPSHOT. 
> But now I got another error of missing 
> 'org.wso2.carbon.device.mgt.server.feature.group [1.0.4.SNAPSHOT,1.1.0)’
> 
> And before building IoT Server, I had successfully built uuf-template-app, 
> carbon-device-mgt, carbon-device-mgt-plugins using ‘IoTS-1.0.0-M4’ branch. Do 
> I miss something? Thanks.
> 
> Installing org.wso2.carbon.messaging.andes.feature.group 3.1.0.
> Installing org.wso2.mb.styles.feature.group 3.1.0.
> Installing org.wso2.stratos.mb.dashboard.ui.feature.group 3.1.0.
> Installing org.wso2.carbon.metrics.feature.group 1.2.0.
> Installation failed.
> Cannot complete the install because one or more required items could not be 
> found.
>  Software being installed: WSO2 Carbon - Mobile Device Management Feature 
> 2.0.4.SNAPSHOT (org.wso2.carbon.device.mgt.mobile.feature.group 
> 2.0.4.SNAPSHOT)
>  Missing requirement: WSO2 Carbon - Mobile Device Management Feature 
> 2.0.4.SNAPSHOT (org.wso2.carbon.device.mgt.mobile.feature.group 
> 2.0.4.SNAPSHOT) requires 'org.wso2.carbon.device.mgt.server.feature.group 
> [1.0.4.SNAPSHOT,1.1.0)' but it could not be found
> Application failed,

Re: [Dev] Build error for "WSO2 IoT Server - P2 Profile Gen"

[云展智创]

Hi Yasith,

Thank you very much. Your solution helped me to pass the installation of WSO2 
Carbon - Analytics Event Table Server Feature 1.0.6.SNAPSHOT. 
But now I got another error of missing 
'org.wso2.carbon.device.mgt.server.feature.group [1.0.4.SNAPSHOT,1.1.0)’

And before building IoT Server, I had successfully built uuf-template-app, 
carbon-device-mgt, carbon-device-mgt-plugins using ‘IoTS-1.0.0-M4’ branch. Do I 
miss something? Thanks.

Installing org.wso2.carbon.messaging.andes.feature.group 3.1.0.
Installing org.wso2.mb.styles.feature.group 3.1.0.
Installing org.wso2.stratos.mb.dashboard.ui.feature.group 3.1.0.
Installing org.wso2.carbon.metrics.feature.group 1.2.0.
Installation failed.
Cannot complete the install because one or more required items could not be 
found.
 Software being installed: WSO2 Carbon - Mobile Device Management Feature 
2.0.4.SNAPSHOT (org.wso2.carbon.device.mgt.mobile.feature.group 2.0.4.SNAPSHOT)
 Missing requirement: WSO2 Carbon - Mobile Device Management Feature 
2.0.4.SNAPSHOT (org.wso2.carbon.device.mgt.mobile.feature.group 2.0.4.SNAPSHOT) 
requires 'org.wso2.carbon.device.mgt.server.feature.group 
[1.0.4.SNAPSHOT,1.1.0)' but it could not be found
Application failed, log file location: 
/Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1457404117145.log

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] WSO2 IoT Server - Parent ... SUCCESS [  1.180 s]
[INFO] WSO2 CDMF Tools  SUCCESS [  0.046 s]
[INFO] WSO2 MDM Agent Android Archetype ... SUCCESS [  1.554 s]
[INFO] WSO2 CDMF Device Type Archetype  SUCCESS [  1.122 s]
[INFO] WSO2 IoT Server - UI styles  SUCCESS [  1.250 s]
[INFO] WSO2 IoT Server UI Features  SUCCESS [  0.036 s]
[INFO] WSO2 IoT Server Styles Feature . SUCCESS [  0.854 s]
[INFO] WSO2 IoT Server - P2 Profile Gen ... FAILURE [37:26 min]
[INFO] WSO2 IoT Server - Distribution . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 37:33 min
[INFO] Finished at: 2016-03-08T10:28:42+08:00
[INFO] Final Memory: 34M/982M
[INFO] 
[ERROR] Failed to execute goal 
org.wso2.maven:carbon-p2-plugin:1.5.4:p2-profile-gen (3-p2-profile-generation) 
on project wso2iot-profile-gen: P2 publisher return code was 13 -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :wso2iot-profile-gen


－－
Zhanwen 

IOT & API Management

在 2016年3月7日，下午7:36，Yasith Lokuge <yasi...@gmail.com> 写道：

> Hi,
> 
> In product-iot-server pom.xml change the "carbon.event-processing" version as 
> follows;
> 
> 2.0.12
> 
> Regards,
> Yasith Lokuge
> 
> 
> On Mon, Mar 7, 2016 at 3:32 PM, 云展智创 <i...@smartcloudex.com> wrote:
> Hi all,
> 
> When I compiled and built the product-iot-server(master) project from Github, 
> I got the following error: 
> 'org.wso2.carbon.event.processor.server.feature.group [2.0.12,2.1.0)' but it 
> could not be found.
> 
> Can anyone help me to pass it? Thanks.
> 
> Installing org.wso2.stratos.mb.dashboard.ui.feature.group 3.1.0.
> Installing org.wso2.carbon.metrics.feature.group 1.2.0.
> Installation failed.
> Cannot complete the install because one or more required items could not be 
> found.
>  Software being installed: WSO2 Carbon - Analytics Event Table Server Feature 
> 1.0.6.SNAPSHOT (org.wso2.carbon.analytics.eventtable.feature.group 
> 1.0.6.SNAPSHOT)
>  Missing requirement: WSO2 Carbon - Analytics Event Table Server Feature 
> 1.0.6.SNAPSHOT (org.wso2.carbon.analytics.eventtable.feature.group 
> 1.0.6.SNAPSHOT) requires 
> 'org.wso2.carbon.event.processor.server.feature.group [2.0.12,2.1.0)' but it 
> could not be found
> Application failed, log file location: 
> /Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1457340791209.log
> 
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] WSO2 IoT Server - Parent ..

[Dev] Build error for "WSO2 IoT Server - P2 Profile Gen"

[云展智创]

Hi all,

When I compiled and built the product-iot-server(master) project from Github, I 
got the following error: 
'org.wso2.carbon.event.processor.server.feature.group [2.0.12,2.1.0)' but it 
could not be found.

Can anyone help me to pass it? Thanks.

Installing org.wso2.stratos.mb.dashboard.ui.feature.group 3.1.0.
Installing org.wso2.carbon.metrics.feature.group 1.2.0.
Installation failed.
Cannot complete the install because one or more required items could not be 
found.
 Software being installed: WSO2 Carbon - Analytics Event Table Server Feature 
1.0.6.SNAPSHOT (org.wso2.carbon.analytics.eventtable.feature.group 
1.0.6.SNAPSHOT)
 Missing requirement: WSO2 Carbon - Analytics Event Table Server Feature 
1.0.6.SNAPSHOT (org.wso2.carbon.analytics.eventtable.feature.group 
1.0.6.SNAPSHOT) requires 'org.wso2.carbon.event.processor.server.feature.group 
[2.0.12,2.1.0)' but it could not be found
Application failed, log file location: 
/Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1457340791209.log

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] WSO2 IoT Server - Parent ... SUCCESS [  0.982 s]
[INFO] WSO2 CDMF Tools  SUCCESS [  0.044 s]
[INFO] WSO2 MDM Agent Android Archetype ... SUCCESS [  1.610 s]
[INFO] WSO2 CDMF Device Type Archetype  SUCCESS [  1.075 s]
[INFO] WSO2 IoT Server - UI styles  SUCCESS [  1.025 s]
[INFO] WSO2 IoT Server UI Features  SUCCESS [  0.029 s]
[INFO] WSO2 IoT Server Styles Feature . SUCCESS [  0.705 s]
[INFO] WSO2 IoT Server - P2 Profile Gen ... FAILURE [01:09 min]
[INFO] WSO2 IoT Server - Distribution . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 01:16 min
[INFO] Finished at: 2016-03-07T16:53:16+08:00
[INFO] Final Memory: 51M/1238M
[INFO] 
[ERROR] Failed to execute goal 
org.wso2.maven:carbon-p2-plugin:1.5.4:p2-profile-gen (3-p2-profile-generation) 
on project wso2iot-profile-gen: P2 publisher return code was 13 -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :wso2iot-profile-gen

－－
Zhanwen 

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev