Re: [Dev] [EMM][iOS] Getting exceptions while installing iOS features

[Kasun Dananjaya Delgolla]

No. This happens only when installing the features.

Thanks

On Wed, May 18, 2016 at 12:03 PM, Inosh Perera  wrote:

> Hi Kasun,
>
> Does this issue continue even after the server is restarted after feature
> installation?
>
> Regards,
> Inosh
>
> On Wed, May 18, 2016 at 11:45 AM, Kasun Dananjaya Delgolla <
> kas...@wso2.com> wrote:
>
>> Hi All,
>>
>> $subject. Seems like it's missing some dependencies.
>>
>> org.springframework.beans.factory.BeanCreationException: Error creating
>> bean with name 'enrollmentService': Cannot resolve reference to bean
>> 'enrollmentServiceBean' while setting bean property 'serviceBeans' with key
>> [0]; nested exception is
>> org.springframework.beans.factory.BeanCreationException: Error creating
>> bean with name 'enrollmentServiceBean' defined in URL
>> [jndi:/localhost/ios-enrollment/WEB-INF/cxf-servlet.xml]: Instantiation of
>> bean failed; nested exception is java.lang.NoClassDefFoundError:
>> org/wso2/carbon/device/mgt/ios/core/exception/IOSEnrollmentException
>> at
>> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)
>> at
>> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
>> at
>> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:353)
>> at
>> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:153)
>> at
>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1327)
>> at
>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1085)
>> at
>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:516)
>> at
>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:455)
>> at
>> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
>> at
>> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
>> at
>> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
>> at
>> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
>> at
>> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
>> at
>> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
>> at
>> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
>> at
>> org.apache.cxf.transport.servlet.CXFServlet.createSpringContext(CXFServlet.java:151)
>> at org.apache.cxf.transport.servlet.CXFServlet.loadBus(CXFServlet.java:74)
>> at
>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.init(CXFNonSpringServlet.java:76)
>> at
>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1284)
>> at
>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1197)
>> at
>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
>> at
>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5262)
>> at
>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5550)
>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> at
>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
>> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
>> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
>> at
>> org.wso2.carbon.tomcat.internal.CarbonTomcat.addWebApp(CarbonTomcat.java:290)
>> at
>> org.wso2.carbon.tomcat.internal.CarbonTomcat.addWebApp(CarbonTomcat.java:198)
>> at
>> org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleWebappDeployment(TomcatGenericWebappsDeployer.java:258)
>> at
>> org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleWarWebappDeployment(TomcatGenericWebappsDeployer.java:208)
>> at
>> org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleHotDeployment(TomcatGenericWebappsDeployer.java:175)
>> at
>> org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.deploy(TomcatGenericWebappsDeployer.java:140)
>> at
>> org.wso2.carbon.webapp.mgt.AbstractWebappDeployer.deployThisWebApp(AbstractWebappDeployer.java:224)
>> at
>> org.wso2.carbon.webapp.mgt.AbstractWebappDeployer.deploy(AbstractWebappDeployer.java:114)
>> at
>> 

Re: [Dev] [EMM][iOS] Getting exceptions while installing iOS features

[Geeth Munasinghe]

Hi Kasun,

This happens because iOS plugins includes both osgi bundles and a jax-rs
web application. When  the iOS feature is installed on EMM, all of those
files are copied to relevant folders such as osgi bundles to
repository/components/plungins and web-application to
repository/deployment/server/webapps and so forth. When a web application
is copied, it is automatically deployed by the web app deployer. But it
requires a restart for the plugins to be deployed to osgi environment. This
causes the above issue, due the fact plugins are not available at time of
web application get deployed. But restarting will solve the issue.

Thanks
Geeth


*G. K. S. Munasinghe*
*Senior Software Engineer,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: ge...@wso2.com
phone:(+94) 777911226

On Wed, May 18, 2016 at 12:18 PM, Kasun Dananjaya Delgolla 
wrote:

> No. This happens only when installing the features.
>
> Thanks
>
> On Wed, May 18, 2016 at 12:03 PM, Inosh Perera  wrote:
>
>> Hi Kasun,
>>
>> Does this issue continue even after the server is restarted after feature
>> installation?
>>
>> Regards,
>> Inosh
>>
>> On Wed, May 18, 2016 at 11:45 AM, Kasun Dananjaya Delgolla <
>> kas...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> $subject. Seems like it's missing some dependencies.
>>>
>>> org.springframework.beans.factory.BeanCreationException: Error creating
>>> bean with name 'enrollmentService': Cannot resolve reference to bean
>>> 'enrollmentServiceBean' while setting bean property 'serviceBeans' with key
>>> [0]; nested exception is
>>> org.springframework.beans.factory.BeanCreationException: Error creating
>>> bean with name 'enrollmentServiceBean' defined in URL
>>> [jndi:/localhost/ios-enrollment/WEB-INF/cxf-servlet.xml]: Instantiation of
>>> bean failed; nested exception is java.lang.NoClassDefFoundError:
>>> org/wso2/carbon/device/mgt/ios/core/exception/IOSEnrollmentException
>>> at
>>> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)
>>> at
>>> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
>>> at
>>> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:353)
>>> at
>>> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:153)
>>> at
>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1327)
>>> at
>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1085)
>>> at
>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:516)
>>> at
>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:455)
>>> at
>>> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
>>> at
>>> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
>>> at
>>> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
>>> at
>>> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
>>> at
>>> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
>>> at
>>> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
>>> at
>>> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
>>> at
>>> org.apache.cxf.transport.servlet.CXFServlet.createSpringContext(CXFServlet.java:151)
>>> at
>>> org.apache.cxf.transport.servlet.CXFServlet.loadBus(CXFServlet.java:74)
>>> at
>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.init(CXFNonSpringServlet.java:76)
>>> at
>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1284)
>>> at
>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1197)
>>> at
>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
>>> at
>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5262)
>>> at
>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5550)
>>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>> at
>>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
>>> at
>>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
>>> at 

Re: [Dev] Representing a JSON payload with null values - visual datamapper editor

[Sohani Weerasinghe]

Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com

Mobile  : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter  : https://twitter.com/sohanichristine

On Wed, May 18, 2016 at 12:00 PM, Nuwan Pallewela  wrote:

> Hi All,
>
> @Vivekanathan : If we need to process/map any value in the payload though
> it is optional we have to know the type when generating the schema. So the
> sample pay load should not contain null values first place. We need to
> modify the sample payload with expected values so that in the schema
> generation we could set the type correctly for that field.
>
> @Sohani : +1 for the above mention approach in the schema generation. One
> small suggestion to remove the arrow head of type null elements to restrict
> users from mapping such elements.
>

Will do.

>
> Thanks,
> Nuwan
>
> On Wed, May 18, 2016 at 11:51 AM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> Hi Sohani,
>>
>> Normally we are getting null value for optional parameter in the API
>> response, suppose if we get the actual value for that json object , does
>> this schema handle that case?
>>
>>
>>
>>
>>
>> *Thank youVivekananthan Sivanayagam*
>>
>> *Associate Software Engineer | WSO2*
>>
>> *E:vivekanant...@wso2.com *
>> *M:+94752786138 <%2B94752786138>*
>>
>> On Wed, May 18, 2016 at 11:19 AM, Sohani Weerasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> If a json payload has null values as shown below, how are we going to
>>> represent this in the json schema?
>>>
>>> {
>>>   "root": {
>>> "tasklist_id": "12345",
>>> "test"=null
>>> }
>>> }
>>>
>>> If we are serializing that value, then the generated schema and the tree
>>> view will be as follows
>>>
>>> {
>>>   "$schema" : "http://json-schema.org/draft-04/schema#;,
>>>   "id" : "http://wso2jsonschema.org;,
>>>   "title" : "root",
>>>   "type" : "object",
>>>   "properties" : {
>>> *"test" : {*
>>> *  "id" : "http://wso2jsonschema.org/test
>>> ",*
>>> *  "type" : "null"*
>>> *},*
>>> "tasklist_id" : {
>>>   "id" : "http://wso2jsonschema.org/tasklist_id;,
>>>   "type" : "string"
>>> }
>>>   }
>>> }
>>>
>>>
>>> ​
>>>
>>> Appreciate your input on this
>>>
>>> Thanks,
>>> Sohani
>>> Sohani Weerasinghe
>>> Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>
>>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Sinthuja Ragendran]

Hi Tanya,

Can't we fix this during the shinding-server feature generation?

Thanks,
Sinthuja.

On Wed, May 18, 2016 at 11:56 AM, Harsha Kumara  wrote:

> Adding Bhathiya.
>
> We got same exception yesterday in APIM as well. We will need to same
> thing for DS as well.
>
> Thanks,
> Harsha
>
> On Wed, May 18, 2016 at 11:38 AM, Ruwan Abeykoon  wrote:
>
>> Thanks Tanya for the information. We will follow the same as in DS.
>>
>> On Wed, May 18, 2016 at 11:34 AM, Tanya Madurapperuma 
>> wrote:
>>
>>> Hi Ruwan,
>>>
>>> Usually this error is thrown as shindig is trying to load some google
>>> analytics apis. So when there is no internet connection this error can be
>>> observed.
>>> To get rid of this error we have to remove google related stuff from
>>> shindig features.txt file
>>>
>>> *features-extras/analytics/feature.xml*
>>> *features-extras/com.google.gadgets.analytics/feature.xml*
>>>
>>> But since we don't maintain a shindig fork, we can't do this from
>>> carbon-dashboards level. So in the Dashboard Server level we are replacing
>>> the features.txt file with a file which doesn't have above 2 entries [1].
>>> We'll have to do the same for apim analytics as well.
>>>
>>> [1]
>>> https://github.com/wso2/product-ds/commit/2d763ce1d9f5362d559e9d46eb0bcedf1446ee9e
>>>
>>> Thanks,
>>> Tanya
>>>
>>> On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon 
>>> wrote:
>>>
 Hi DS team,
 I am getting the following error in APIM 2.0.0-SNAPSHOT which integrate
 DS features. Any Idea why? can we not print those errors due to outside
 dependencies?

 ---

 achines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libinstrument.dylib. One
 of the two will be used. Which one is undefined.

 [2016-05-17 17:35:49,176]  INFO - FeatureRegistry Resources from
 res:features/features.txt are loading.

 [2016-05-17 17:35:49,186]  INFO - XmlUtil The XML processor being used
 does not support secure parsing.

 [2016-05-17 17:35:49,187]  INFO - XmlUtil Document builders are being
 reused.

 [2016-05-17 17:35:49,396]  INFO - FeatureRegistry Resources from
 res:features-extras/features.txt are loading.

 [2016-05-17 17:36:11,707]  INFO - CarbonEventManagementService Starting
 polling event receivers

 [2016-05-17 17:36:19,510]  INFO - BasicHttpFetcher The following
 exception occurred when fetching
 http://www.google-analytics.com/urchin.js: 30,103 ms elapsed.

 [2016-05-17 17:36:19,511]  INFO - BasicHttpFetcher

 org.apache.http.conn.ConnectTimeoutException: Connect to
 www.google-analytics.com:80 timed out

 at
 org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)

 at
 org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)

 at
 org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)

 at
 org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)

 at
 org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)

 at
 org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)

 at
 org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)

 at
 org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:115)

 at
 org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)

 at
 org.apache.shindig.gadgets.http.BasicHttpFetcher.fetch(BasicHttpFetcher.java:359)

 at
 org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.getContent(FeatureResourceLoader.java:291)

 at
 org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.(FeatureResourceLoader.java:270)

 at
 org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.(FeatureResourceLoader.java:256)

 at
 org.apache.shindig.gadgets.features.FeatureResourceLoader.loadUri(FeatureResourceLoader.java:135)

 at
 org.apache.shindig.gadgets.features.FeatureResourceLoader.load(FeatureResourceLoader.java:88)

 at
 org.apache.shindig.gadgets.features.FeatureRegistry.loadFeature(FeatureRegistry.java:486)

 at
 org.apache.shindig.gadgets.features.FeatureRegistry.loadResources(FeatureRegistry.java:425)

 at
 org.apache.shindig.gadgets.features.FeatureRegistry.register(FeatureRegistry.java:180)

 at
 org.apache.shindig.gadgets.features.FeatureRegistry.(FeatureRegistry.java:112)

 at
 org.apache.shindig.gadgets.features.FeatureRegistry.(FeatureRegistry.java:99)

 at
 

Re: [Dev] Representing a JSON payload with null values - visual datamapper editor

[Nuwan Pallewela]

Hi All,

@Vivekanathan : If we need to process/map any value in the payload though
it is optional we have to know the type when generating the schema. So the
sample pay load should not contain null values first place. We need to
modify the sample payload with expected values so that in the schema
generation we could set the type correctly for that field.

@Sohani : +1 for the above mention approach in the schema generation. One
small suggestion to remove the arrow head of type null elements to restrict
users from mapping such elements.

Thanks,
Nuwan

On Wed, May 18, 2016 at 11:51 AM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Hi Sohani,
>
> Normally we are getting null value for optional parameter in the API
> response, suppose if we get the actual value for that json object , does
> this schema handle that case?
>
>
>
>
>
> *Thank youVivekananthan Sivanayagam*
>
> *Associate Software Engineer | WSO2*
>
> *E:vivekanant...@wso2.com *
> *M:+94752786138 <%2B94752786138>*
>
> On Wed, May 18, 2016 at 11:19 AM, Sohani Weerasinghe 
> wrote:
>
>> Hi All,
>>
>> If a json payload has null values as shown below, how are we going to
>> represent this in the json schema?
>>
>> {
>>   "root": {
>> "tasklist_id": "12345",
>> "test"=null
>> }
>> }
>>
>> If we are serializing that value, then the generated schema and the tree
>> view will be as follows
>>
>> {
>>   "$schema" : "http://json-schema.org/draft-04/schema#;,
>>   "id" : "http://wso2jsonschema.org;,
>>   "title" : "root",
>>   "type" : "object",
>>   "properties" : {
>> *"test" : {*
>> *  "id" : "http://wso2jsonschema.org/test
>> ",*
>> *  "type" : "null"*
>> *},*
>> "tasklist_id" : {
>>   "id" : "http://wso2jsonschema.org/tasklist_id;,
>>   "type" : "string"
>> }
>>   }
>> }
>>
>>
>> ​
>>
>> Appreciate your input on this
>>
>> Thanks,
>> Sohani
>> Sohani Weerasinghe
>> Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Ruwan Abeykoon]

Thanks Tanya for the information. We will follow the same as in DS.

On Wed, May 18, 2016 at 11:34 AM, Tanya Madurapperuma 
wrote:

> Hi Ruwan,
>
> Usually this error is thrown as shindig is trying to load some google
> analytics apis. So when there is no internet connection this error can be
> observed.
> To get rid of this error we have to remove google related stuff from
> shindig features.txt file
>
> *features-extras/analytics/feature.xml*
> *features-extras/com.google.gadgets.analytics/feature.xml*
>
> But since we don't maintain a shindig fork, we can't do this from
> carbon-dashboards level. So in the Dashboard Server level we are replacing
> the features.txt file with a file which doesn't have above 2 entries [1].
> We'll have to do the same for apim analytics as well.
>
> [1]
> https://github.com/wso2/product-ds/commit/2d763ce1d9f5362d559e9d46eb0bcedf1446ee9e
>
> Thanks,
> Tanya
>
> On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon  wrote:
>
>> Hi DS team,
>> I am getting the following error in APIM 2.0.0-SNAPSHOT which integrate
>> DS features. Any Idea why? can we not print those errors due to outside
>> dependencies?
>>
>> ---
>>
>> achines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libinstrument.dylib. One of
>> the two will be used. Which one is undefined.
>>
>> [2016-05-17 17:35:49,176]  INFO - FeatureRegistry Resources from
>> res:features/features.txt are loading.
>>
>> [2016-05-17 17:35:49,186]  INFO - XmlUtil The XML processor being used
>> does not support secure parsing.
>>
>> [2016-05-17 17:35:49,187]  INFO - XmlUtil Document builders are being
>> reused.
>>
>> [2016-05-17 17:35:49,396]  INFO - FeatureRegistry Resources from
>> res:features-extras/features.txt are loading.
>>
>> [2016-05-17 17:36:11,707]  INFO - CarbonEventManagementService Starting
>> polling event receivers
>>
>> [2016-05-17 17:36:19,510]  INFO - BasicHttpFetcher The following
>> exception occurred when fetching
>> http://www.google-analytics.com/urchin.js: 30,103 ms elapsed.
>>
>> [2016-05-17 17:36:19,511]  INFO - BasicHttpFetcher
>>
>> org.apache.http.conn.ConnectTimeoutException: Connect to
>> www.google-analytics.com:80 timed out
>>
>> at
>> org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
>>
>> at
>> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
>>
>> at
>> org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
>>
>> at
>> org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
>>
>> at
>> org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
>>
>> at
>> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
>>
>> at
>> org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
>>
>> at
>> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:115)
>>
>> at
>> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
>>
>> at
>> org.apache.shindig.gadgets.http.BasicHttpFetcher.fetch(BasicHttpFetcher.java:359)
>>
>> at
>> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.getContent(FeatureResourceLoader.java:291)
>>
>> at
>> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.(FeatureResourceLoader.java:270)
>>
>> at
>> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.(FeatureResourceLoader.java:256)
>>
>> at
>> org.apache.shindig.gadgets.features.FeatureResourceLoader.loadUri(FeatureResourceLoader.java:135)
>>
>> at
>> org.apache.shindig.gadgets.features.FeatureResourceLoader.load(FeatureResourceLoader.java:88)
>>
>> at
>> org.apache.shindig.gadgets.features.FeatureRegistry.loadFeature(FeatureRegistry.java:486)
>>
>> at
>> org.apache.shindig.gadgets.features.FeatureRegistry.loadResources(FeatureRegistry.java:425)
>>
>> at
>> org.apache.shindig.gadgets.features.FeatureRegistry.register(FeatureRegistry.java:180)
>>
>> at
>> org.apache.shindig.gadgets.features.FeatureRegistry.(FeatureRegistry.java:112)
>>
>> at
>> org.apache.shindig.gadgets.features.FeatureRegistry.(FeatureRegistry.java:99)
>>
>> at
>> org.apache.shindig.gadgets.features.FeatureRegistry$$FastClassByGuice$$536f6a5.newInstance()
>>
>> at
>> com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
>>
>> at
>> com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:60)
>>
>> at
>> com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
>>
>> at
>> com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
>>
>> at
>> com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
>>
>> at
>> 

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Harsha Kumara]

Adding Bhathiya.

We got same exception yesterday in APIM as well. We will need to same thing
for DS as well.

Thanks,
Harsha

On Wed, May 18, 2016 at 11:38 AM, Ruwan Abeykoon  wrote:

> Thanks Tanya for the information. We will follow the same as in DS.
>
> On Wed, May 18, 2016 at 11:34 AM, Tanya Madurapperuma 
> wrote:
>
>> Hi Ruwan,
>>
>> Usually this error is thrown as shindig is trying to load some google
>> analytics apis. So when there is no internet connection this error can be
>> observed.
>> To get rid of this error we have to remove google related stuff from
>> shindig features.txt file
>>
>> *features-extras/analytics/feature.xml*
>> *features-extras/com.google.gadgets.analytics/feature.xml*
>>
>> But since we don't maintain a shindig fork, we can't do this from
>> carbon-dashboards level. So in the Dashboard Server level we are replacing
>> the features.txt file with a file which doesn't have above 2 entries [1].
>> We'll have to do the same for apim analytics as well.
>>
>> [1]
>> https://github.com/wso2/product-ds/commit/2d763ce1d9f5362d559e9d46eb0bcedf1446ee9e
>>
>> Thanks,
>> Tanya
>>
>> On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon  wrote:
>>
>>> Hi DS team,
>>> I am getting the following error in APIM 2.0.0-SNAPSHOT which integrate
>>> DS features. Any Idea why? can we not print those errors due to outside
>>> dependencies?
>>>
>>> ---
>>>
>>> achines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libinstrument.dylib. One
>>> of the two will be used. Which one is undefined.
>>>
>>> [2016-05-17 17:35:49,176]  INFO - FeatureRegistry Resources from
>>> res:features/features.txt are loading.
>>>
>>> [2016-05-17 17:35:49,186]  INFO - XmlUtil The XML processor being used
>>> does not support secure parsing.
>>>
>>> [2016-05-17 17:35:49,187]  INFO - XmlUtil Document builders are being
>>> reused.
>>>
>>> [2016-05-17 17:35:49,396]  INFO - FeatureRegistry Resources from
>>> res:features-extras/features.txt are loading.
>>>
>>> [2016-05-17 17:36:11,707]  INFO - CarbonEventManagementService Starting
>>> polling event receivers
>>>
>>> [2016-05-17 17:36:19,510]  INFO - BasicHttpFetcher The following
>>> exception occurred when fetching
>>> http://www.google-analytics.com/urchin.js: 30,103 ms elapsed.
>>>
>>> [2016-05-17 17:36:19,511]  INFO - BasicHttpFetcher
>>>
>>> org.apache.http.conn.ConnectTimeoutException: Connect to
>>> www.google-analytics.com:80 timed out
>>>
>>> at
>>> org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
>>>
>>> at
>>> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
>>>
>>> at
>>> org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
>>>
>>> at
>>> org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
>>>
>>> at
>>> org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
>>>
>>> at
>>> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
>>>
>>> at
>>> org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
>>>
>>> at
>>> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:115)
>>>
>>> at
>>> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
>>>
>>> at
>>> org.apache.shindig.gadgets.http.BasicHttpFetcher.fetch(BasicHttpFetcher.java:359)
>>>
>>> at
>>> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.getContent(FeatureResourceLoader.java:291)
>>>
>>> at
>>> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.(FeatureResourceLoader.java:270)
>>>
>>> at
>>> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.(FeatureResourceLoader.java:256)
>>>
>>> at
>>> org.apache.shindig.gadgets.features.FeatureResourceLoader.loadUri(FeatureResourceLoader.java:135)
>>>
>>> at
>>> org.apache.shindig.gadgets.features.FeatureResourceLoader.load(FeatureResourceLoader.java:88)
>>>
>>> at
>>> org.apache.shindig.gadgets.features.FeatureRegistry.loadFeature(FeatureRegistry.java:486)
>>>
>>> at
>>> org.apache.shindig.gadgets.features.FeatureRegistry.loadResources(FeatureRegistry.java:425)
>>>
>>> at
>>> org.apache.shindig.gadgets.features.FeatureRegistry.register(FeatureRegistry.java:180)
>>>
>>> at
>>> org.apache.shindig.gadgets.features.FeatureRegistry.(FeatureRegistry.java:112)
>>>
>>> at
>>> org.apache.shindig.gadgets.features.FeatureRegistry.(FeatureRegistry.java:99)
>>>
>>> at
>>> org.apache.shindig.gadgets.features.FeatureRegistry$$FastClassByGuice$$536f6a5.newInstance()
>>>
>>> at
>>> com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
>>>
>>> at
>>> com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:60)
>>>
>>> at
>>> 

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Ruwan Abeykoon]

>>Can't we fix this during the shinding-server feature generation?
+1
So that every product using shindig does not have to unzip and zip the war
file to fix it.

Cheers,
Ruwan

On Wed, May 18, 2016 at 12:01 PM, Sinthuja Ragendran 
wrote:

> Hi Tanya,
>
> Can't we fix this during the shinding-server feature generation?
>
> Thanks,
> Sinthuja.
>
> On Wed, May 18, 2016 at 11:56 AM, Harsha Kumara  wrote:
>
>> Adding Bhathiya.
>>
>> We got same exception yesterday in APIM as well. We will need to same
>> thing for DS as well.
>>
>> Thanks,
>> Harsha
>>
>> On Wed, May 18, 2016 at 11:38 AM, Ruwan Abeykoon  wrote:
>>
>>> Thanks Tanya for the information. We will follow the same as in DS.
>>>
>>> On Wed, May 18, 2016 at 11:34 AM, Tanya Madurapperuma 
>>> wrote:
>>>
 Hi Ruwan,

 Usually this error is thrown as shindig is trying to load some google
 analytics apis. So when there is no internet connection this error can be
 observed.
 To get rid of this error we have to remove google related stuff from
 shindig features.txt file

 *features-extras/analytics/feature.xml*
 *features-extras/com.google.gadgets.analytics/feature.xml*

 But since we don't maintain a shindig fork, we can't do this from
 carbon-dashboards level. So in the Dashboard Server level we are replacing
 the features.txt file with a file which doesn't have above 2 entries [1].
 We'll have to do the same for apim analytics as well.

 [1]
 https://github.com/wso2/product-ds/commit/2d763ce1d9f5362d559e9d46eb0bcedf1446ee9e

 Thanks,
 Tanya

 On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon 
 wrote:

> Hi DS team,
> I am getting the following error in APIM 2.0.0-SNAPSHOT which
> integrate DS features. Any Idea why? can we not print those errors due to
> outside dependencies?
>
> ---
>
> achines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libinstrument.dylib. One
> of the two will be used. Which one is undefined.
>
> [2016-05-17 17:35:49,176]  INFO - FeatureRegistry Resources from
> res:features/features.txt are loading.
>
> [2016-05-17 17:35:49,186]  INFO - XmlUtil The XML processor being used
> does not support secure parsing.
>
> [2016-05-17 17:35:49,187]  INFO - XmlUtil Document builders are being
> reused.
>
> [2016-05-17 17:35:49,396]  INFO - FeatureRegistry Resources from
> res:features-extras/features.txt are loading.
>
> [2016-05-17 17:36:11,707]  INFO - CarbonEventManagementService
> Starting polling event receivers
>
> [2016-05-17 17:36:19,510]  INFO - BasicHttpFetcher The following
> exception occurred when fetching
> http://www.google-analytics.com/urchin.js: 30,103 ms elapsed.
>
> [2016-05-17 17:36:19,511]  INFO - BasicHttpFetcher
>
> org.apache.http.conn.ConnectTimeoutException: Connect to
> www.google-analytics.com:80 timed out
>
> at
> org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
>
> at
> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
>
> at
> org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
>
> at
> org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
>
> at
> org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
>
> at
> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
>
> at
> org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
>
> at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:115)
>
> at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
>
> at
> org.apache.shindig.gadgets.http.BasicHttpFetcher.fetch(BasicHttpFetcher.java:359)
>
> at
> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.getContent(FeatureResourceLoader.java:291)
>
> at
> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.(FeatureResourceLoader.java:270)
>
> at
> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.(FeatureResourceLoader.java:256)
>
> at
> org.apache.shindig.gadgets.features.FeatureResourceLoader.loadUri(FeatureResourceLoader.java:135)
>
> at
> org.apache.shindig.gadgets.features.FeatureResourceLoader.load(FeatureResourceLoader.java:88)
>
> at
> org.apache.shindig.gadgets.features.FeatureRegistry.loadFeature(FeatureRegistry.java:486)
>
> at
> 

Re: [Dev] [C5] [MB] Failed to initialize startup resolver

[Hemika Kodikara]

Hi Sameera,

I saw this "dependentComponentName" in the carbon.component tag in [1]. May
I know the purpose of it ? Best if you could add it to the blog :) . The
blog is very understandable.

[1] -
https://github.com/wso2/msf4j/pull/169/files#diff-357e4854869b2e21c38b1b437f11095aR334

Regards,
Hemika

Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com

Mobile : +9477762

On Fri, May 13, 2016 at 4:56 PM, Sameera Jayasoma  wrote:

> Refer the following article to get information about the new syntax.
>
>
> https://medium.com/@sameera.jayasoma/resolving-startup-order-of-carbon-components-in-wso2-carbon-5-0-0-497fe3287e67
>
> On Fri, May 13, 2016 at 4:26 PM, Niranjan Karunanandham  > wrote:
>
>> Hi Hemika,
>>
>> The startup resolver changes compatible to kernel 5.1.0-alpha2 is
>> available in the master branch (PR [1]) of carbon-datasources. The
>> carbon-datasources 1.0.0-alpha depends on the older format.
>>
>> [1] - https://github.com/wso2/carbon-datasources/pull/14
>>
>> Regards,
>> Nira
>>
>> On Fri, May 13, 2016 at 4:22 PM, Hemika Kodikara  wrote:
>>
>>> Thanks for the response. I have changed the kernel version to
>>> 5.1.0-alpha2 as mentioned. The earlier error is not coming. But I am
>>> getting the following error. Seems like its coming from carbon-datasources.
>>> I checked this with m1 version and also alpha version for datasources.
>>>
>>> =
>>> [2016-05-13 15:16:04,974] ERROR {org.wso2.carbon.core} - FrameworkEvent
>>> ERROR - org.wso2.carbon.core
>>> org.wso2.carbon.kernel.internal.startupresolver.StartOrderResolverException:
>>> componentName value is missing in the services registered with the key
>>> org.wso2.carbon.kernel.startupresolver.RequiredCapabilityListener,
>>> implementation class name is
>>> org.wso2.carbon.datasource.core.internal.DataSourceListenerComponent
>>> at
>>> org.wso2.carbon.kernel.internal.startupresolver.OSGiServiceCapabilityTracker$CapabilityServiceTrackerCustomizer.addingService(OSGiServiceCapabilityTracker.java:142)
>>> at
>>> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
>>> at
>>> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)
>>> at
>>> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
>>> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
>>> at
>>> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:901)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:109)
>>> at
>>> org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:914)
>>> at
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>> at
>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:862)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:801)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:127)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:225)
>>> at
>>> org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:464)
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.registerService(InstanceProcess.java:536)
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:213)
>>> at
>>> org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:473)
>>> at
>>> org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:217)
>>> at
>>> org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:816)
>>> at
>>> org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:783)
>>> at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
>>> at
>>> org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)
>>>
>>> ==
>>>
>>> Regards,
>>> Hemika
>>>
>>>
>>> Hemika Kodikara
>>> Software Engineer
>>> WSO2 Inc.
>>> lean . enterprise . middleware
>>> http://wso2.com
>>>
>>> Mobile : +9477762
>>>
>>> On Fri, May 13, 2016 at 3:00 PM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi Hemika,

 There has been some changes to the Startup Resolver in the 5.1.0-alpha2
 release. Therefore IMO it would be better if you can use 5.1.0-alpha2 and
 carbon-parent version 5.

 Regards,
 Nira

 On Fri, May 13, 2016 at 2:51 PM, Hemika Kodikara 
 wrote:

> Hi All,
>
> I am getting 

Re: [Dev] [EMM][iOS] Getting exceptions while installing iOS features

[Inosh Perera]

Hi Kasun,

Does this issue continue even after the server is restarted after feature
installation?

Regards,
Inosh

On Wed, May 18, 2016 at 11:45 AM, Kasun Dananjaya Delgolla 
wrote:

> Hi All,
>
> $subject. Seems like it's missing some dependencies.
>
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'enrollmentService': Cannot resolve reference to bean
> 'enrollmentServiceBean' while setting bean property 'serviceBeans' with key
> [0]; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'enrollmentServiceBean' defined in URL
> [jndi:/localhost/ios-enrollment/WEB-INF/cxf-servlet.xml]: Instantiation of
> bean failed; nested exception is java.lang.NoClassDefFoundError:
> org/wso2/carbon/device/mgt/ios/core/exception/IOSEnrollmentException
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:353)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:153)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1327)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1085)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:516)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:455)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
> at
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
> at
> org.apache.cxf.transport.servlet.CXFServlet.createSpringContext(CXFServlet.java:151)
> at org.apache.cxf.transport.servlet.CXFServlet.loadBus(CXFServlet.java:74)
> at
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.init(CXFNonSpringServlet.java:76)
> at
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1284)
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1197)
> at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
> at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5262)
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5550)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
> at
> org.wso2.carbon.tomcat.internal.CarbonTomcat.addWebApp(CarbonTomcat.java:290)
> at
> org.wso2.carbon.tomcat.internal.CarbonTomcat.addWebApp(CarbonTomcat.java:198)
> at
> org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleWebappDeployment(TomcatGenericWebappsDeployer.java:258)
> at
> org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleWarWebappDeployment(TomcatGenericWebappsDeployer.java:208)
> at
> org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleHotDeployment(TomcatGenericWebappsDeployer.java:175)
> at
> org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.deploy(TomcatGenericWebappsDeployer.java:140)
> at
> org.wso2.carbon.webapp.mgt.AbstractWebappDeployer.deployThisWebApp(AbstractWebappDeployer.java:224)
> at
> org.wso2.carbon.webapp.mgt.AbstractWebappDeployer.deploy(AbstractWebappDeployer.java:114)
> at
> org.wso2.carbon.webapp.deployer.WebappDeployer.deploy(WebappDeployer.java:42)
> at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
> at
> 

[Dev] [EMM][iOS] Getting exceptions while installing iOS features

[Kasun Dananjaya Delgolla]

Hi All,

$subject. Seems like it's missing some dependencies.

org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'enrollmentService': Cannot resolve reference to bean
'enrollmentServiceBean' while setting bean property 'serviceBeans' with key
[0]; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'enrollmentServiceBean' defined in URL
[jndi:/localhost/ios-enrollment/WEB-INF/cxf-servlet.xml]: Instantiation of
bean failed; nested exception is java.lang.NoClassDefFoundError:
org/wso2/carbon/device/mgt/ios/core/exception/IOSEnrollmentException
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:353)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:153)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1327)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1085)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:516)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:455)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
at
org.apache.cxf.transport.servlet.CXFServlet.createSpringContext(CXFServlet.java:151)
at org.apache.cxf.transport.servlet.CXFServlet.loadBus(CXFServlet.java:74)
at
org.apache.cxf.transport.servlet.CXFNonSpringServlet.init(CXFNonSpringServlet.java:76)
at
org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1284)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1197)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5262)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5550)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
at
org.wso2.carbon.tomcat.internal.CarbonTomcat.addWebApp(CarbonTomcat.java:290)
at
org.wso2.carbon.tomcat.internal.CarbonTomcat.addWebApp(CarbonTomcat.java:198)
at
org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleWebappDeployment(TomcatGenericWebappsDeployer.java:258)
at
org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleWarWebappDeployment(TomcatGenericWebappsDeployer.java:208)
at
org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleHotDeployment(TomcatGenericWebappsDeployer.java:175)
at
org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.deploy(TomcatGenericWebappsDeployer.java:140)
at
org.wso2.carbon.webapp.mgt.AbstractWebappDeployer.deployThisWebApp(AbstractWebappDeployer.java:224)
at
org.wso2.carbon.webapp.mgt.AbstractWebappDeployer.deploy(AbstractWebappDeployer.java:114)
at
org.wso2.carbon.webapp.deployer.WebappDeployer.deploy(WebappDeployer.java:42)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
at
org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
at

Re: [Dev] Representing a JSON payload with null values - visual datamapper editor

[Malaka Silva]

Actually those are options for the given configuration. We don't really
have a clear idea what are the optional response elements. (Unless we refer
api docs)

So I guess we can proceed with sample values.

>From datamapper mediator(ESB Side) level we need to handle if we receive a
null value. Guess this is already considered?

On Wed, May 18, 2016 at 12:02 PM, Sohani Weerasinghe 
wrote:

>
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Wed, May 18, 2016 at 12:00 PM, Nuwan Pallewela  wrote:
>
>> Hi All,
>>
>> @Vivekanathan : If we need to process/map any value in the payload though
>> it is optional we have to know the type when generating the schema. So the
>> sample pay load should not contain null values first place. We need to
>> modify the sample payload with expected values so that in the schema
>> generation we could set the type correctly for that field.
>>
>> @Sohani : +1 for the above mention approach in the schema generation. One
>> small suggestion to remove the arrow head of type null elements to restrict
>> users from mapping such elements.
>>
>
> Will do.
>
>>
>> Thanks,
>> Nuwan
>>
>> On Wed, May 18, 2016 at 11:51 AM, Vivekananthan Sivanayagam <
>> vivekanant...@wso2.com> wrote:
>>
>>> Hi Sohani,
>>>
>>> Normally we are getting null value for optional parameter in the API
>>> response, suppose if we get the actual value for that json object , does
>>> this schema handle that case?
>>>
>>>
>>>
>>>
>>>
>>> *Thank youVivekananthan Sivanayagam*
>>>
>>> *Associate Software Engineer | WSO2*
>>>
>>> *E:vivekanant...@wso2.com *
>>> *M:+94752786138 <%2B94752786138>*
>>>
>>> On Wed, May 18, 2016 at 11:19 AM, Sohani Weerasinghe 
>>> wrote:
>>>
 Hi All,

 If a json payload has null values as shown below, how are we going to
 represent this in the json schema?

 {
   "root": {
 "tasklist_id": "12345",
 "test"=null
 }
 }

 If we are serializing that value, then the generated schema and the
 tree view will be as follows

 {
   "$schema" : "http://json-schema.org/draft-04/schema#;,
   "id" : "http://wso2jsonschema.org;,
   "title" : "root",
   "type" : "object",
   "properties" : {
 *"test" : {*
 *  "id" : "http://wso2jsonschema.org/test
 ",*
 *  "type" : "null"*
 *},*
 "tasklist_id" : {
   "id" : "http://wso2jsonschema.org/tasklist_id;,
   "type" : "string"
 }
   }
 }


 ​

 Appreciate your input on this

 Thanks,
 Sohani
 Sohani Weerasinghe
 Software Engineer
 WSO2, Inc: http://wso2.com

 Mobile  : +94 716439774
 Blog :http://christinetechtips.blogspot.com/
 Twitter  : https://twitter.com/sohanichristine

>>>
>>>
>>
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *http://wso2.com
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>@*
>>
>>
>>
>


-- 

Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/

https://store.wso2.com/store/

Save a tree -Conserve nature & Save the world for your future. Print this
email only if it is absolutely necessary.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Sinthuja Ragendran]

Hi Megala,

Please check the shindig-server feature and try to remove the unwanted
files from there it self, hence we can omit this behaviour.

Thanks,
Sinthuja.

On Wed, May 18, 2016 at 12:13 PM, Ruwan Abeykoon  wrote:

> >>Can't we fix this during the shinding-server feature generation?
> +1
> So that every product using shindig does not have to unzip and zip the war
> file to fix it.
>
> Cheers,
> Ruwan
>
> On Wed, May 18, 2016 at 12:01 PM, Sinthuja Ragendran 
> wrote:
>
>> Hi Tanya,
>>
>> Can't we fix this during the shinding-server feature generation?
>>
>> Thanks,
>> Sinthuja.
>>
>> On Wed, May 18, 2016 at 11:56 AM, Harsha Kumara  wrote:
>>
>>> Adding Bhathiya.
>>>
>>> We got same exception yesterday in APIM as well. We will need to same
>>> thing for DS as well.
>>>
>>> Thanks,
>>> Harsha
>>>
>>> On Wed, May 18, 2016 at 11:38 AM, Ruwan Abeykoon 
>>> wrote:
>>>
 Thanks Tanya for the information. We will follow the same as in DS.

 On Wed, May 18, 2016 at 11:34 AM, Tanya Madurapperuma 
 wrote:

> Hi Ruwan,
>
> Usually this error is thrown as shindig is trying to load some google
> analytics apis. So when there is no internet connection this error can be
> observed.
> To get rid of this error we have to remove google related stuff from
> shindig features.txt file
>
> *features-extras/analytics/feature.xml*
> *features-extras/com.google.gadgets.analytics/feature.xml*
>
> But since we don't maintain a shindig fork, we can't do this from
> carbon-dashboards level. So in the Dashboard Server level we are replacing
> the features.txt file with a file which doesn't have above 2 entries [1].
> We'll have to do the same for apim analytics as well.
>
> [1]
> https://github.com/wso2/product-ds/commit/2d763ce1d9f5362d559e9d46eb0bcedf1446ee9e
>
> Thanks,
> Tanya
>
> On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon 
> wrote:
>
>> Hi DS team,
>> I am getting the following error in APIM 2.0.0-SNAPSHOT which
>> integrate DS features. Any Idea why? can we not print those errors due to
>> outside dependencies?
>>
>> ---
>>
>> achines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libinstrument.dylib.
>> One of the two will be used. Which one is undefined.
>>
>> [2016-05-17 17:35:49,176]  INFO - FeatureRegistry Resources from
>> res:features/features.txt are loading.
>>
>> [2016-05-17 17:35:49,186]  INFO - XmlUtil The XML processor being
>> used does not support secure parsing.
>>
>> [2016-05-17 17:35:49,187]  INFO - XmlUtil Document builders are being
>> reused.
>>
>> [2016-05-17 17:35:49,396]  INFO - FeatureRegistry Resources from
>> res:features-extras/features.txt are loading.
>>
>> [2016-05-17 17:36:11,707]  INFO - CarbonEventManagementService
>> Starting polling event receivers
>>
>> [2016-05-17 17:36:19,510]  INFO - BasicHttpFetcher The following
>> exception occurred when fetching
>> http://www.google-analytics.com/urchin.js: 30,103 ms elapsed.
>>
>> [2016-05-17 17:36:19,511]  INFO - BasicHttpFetcher
>>
>> org.apache.http.conn.ConnectTimeoutException: Connect to
>> www.google-analytics.com:80 timed out
>>
>> at
>> org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
>>
>> at
>> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
>>
>> at
>> org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
>>
>> at
>> org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
>>
>> at
>> org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
>>
>> at
>> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
>>
>> at
>> org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
>>
>> at
>> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:115)
>>
>> at
>> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
>>
>> at
>> org.apache.shindig.gadgets.http.BasicHttpFetcher.fetch(BasicHttpFetcher.java:359)
>>
>> at
>> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.getContent(FeatureResourceLoader.java:291)
>>
>> at
>> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.(FeatureResourceLoader.java:270)
>>
>> at
>> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.(FeatureResourceLoader.java:256)
>>
>> at
>> 

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Kernel RC3

[Jasintha Dasanayake]

Hi All

I have tested the update tool , new feature installation and kernel patch
process , no major issues found

+1

Thanks and Regards
/Jasintha

On Wed, May 18, 2016 at 11:23 AM, Heshitha Hettihewa 
wrote:

> Hi all,
>
> I have tested BPS Tooling and no major issues found.
>
> +1
>
> Thanks.
>
> On Wed, May 18, 2016 at 9:10 AM, Isuru Udana  wrote:
>
>> Hi,
>>
>> Tested with ESB tools and found no major issues.
>>
>> +1.
>>
>> On Wed, May 18, 2016 at 9:05 AM, Sohani Weerasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have tested the updater tool functionality including installing
>>> features and also the updater tool preferences.
>>>
>>> +1
>>>
>>> Thanks,
>>> Sohani
>>>
>>> Sohani Weerasinghe
>>> Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>> On Wed, May 18, 2016 at 8:32 AM, Awanthika Senarath 
>>> wrote:
>>>
 I have tested,

 Installation of Developer Studio Platform, ESB and CEP tools on top of
 kernel
 Updater tool functionality, installation and job running



  +1,

 Regards
 Awanthika

 Awanthika Senarath
 Software Engineer, WSO2 Inc.
 Mobile: +94717681791



 On Mon, May 16, 2016 at 3:10 PM, Awanthika Senarath  wrote:

> Hello Devs,
>
>
> We are pleased to announce the vote for RC-3 of
> *WSO2 Developer Studio Kernel 4.1.0.*
>
> P2 repository of WSO2 developer Studio kernel 4.1.0 is available here
> .
>  Source
> and Tag Location to be voted upon is available here
> 
> .
>
> Developer Studio 4.1.0 Kernel is released on Eclipse Mars (Eclipse 4.5)
>
> Developer Studio Kernel contains a single feature which has the
> bundles that are required to implement WSO2 specific product tooling on
> Eclipse.
>
>- This release contains Developer Studio migration to Eclipse mars
>- Improvements in the Developer Studio Updater tool for automatic
>updates
>
>
>
>1. [+] Stable - go ahead and release
>2. [-]  Broken - do not release (please explain why)
>
>
>
> Regards,
> Dev Studio Team
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>

 ___
 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
>>>
>>>
>>
>>
>> --
>> *Isuru Udana*
>> Associate Technical Lead
>> WSO2 Inc.; http://wso2.com
>> email: isu...@wso2.com cell: +94 77 3791887
>> blog: http://mytecheye.blogspot.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Heshitha Hettihewa
> *Software Engineer*
> Mobile : +94716866386
> <%2B94%20%280%29%20773%20451194>
> heshit...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Jasintha Dasanayake*

*Senior Software EngineerWSO2 Inc. | http://wso2.com lean
. enterprise . middleware*


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

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Ayyoob Hamza]

Hi All,
We also got the same error in the IoT Server from yesterday hope we can
have a fix for this.

Thanks

*Ayyoob Hamza*
*Software Engineer*
WSO2 Inc.; http://wso2.com
email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>

On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon  wrote:

> Hi DS team,
> I am getting the following error in APIM 2.0.0-SNAPSHOT which integrate DS
> features. Any Idea why? can we not print those errors due to outside
> dependencies?
>
> ---
>
> achines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libinstrument.dylib. One of
> the two will be used. Which one is undefined.
>
> [2016-05-17 17:35:49,176]  INFO - FeatureRegistry Resources from
> res:features/features.txt are loading.
>
> [2016-05-17 17:35:49,186]  INFO - XmlUtil The XML processor being used
> does not support secure parsing.
>
> [2016-05-17 17:35:49,187]  INFO - XmlUtil Document builders are being
> reused.
>
> [2016-05-17 17:35:49,396]  INFO - FeatureRegistry Resources from
> res:features-extras/features.txt are loading.
>
> [2016-05-17 17:36:11,707]  INFO - CarbonEventManagementService Starting
> polling event receivers
>
> [2016-05-17 17:36:19,510]  INFO - BasicHttpFetcher The following exception
> occurred when fetching http://www.google-analytics.com/urchin.js: 30,103
> ms elapsed.
>
> [2016-05-17 17:36:19,511]  INFO - BasicHttpFetcher
>
> org.apache.http.conn.ConnectTimeoutException: Connect to
> www.google-analytics.com:80 timed out
>
> at
> org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
>
> at
> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
>
> at
> org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
>
> at
> org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
>
> at
> org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
>
> at
> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
>
> at
> org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
>
> at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:115)
>
> at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
>
> at
> org.apache.shindig.gadgets.http.BasicHttpFetcher.fetch(BasicHttpFetcher.java:359)
>
> at
> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.getContent(FeatureResourceLoader.java:291)
>
> at
> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.(FeatureResourceLoader.java:270)
>
> at
> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.(FeatureResourceLoader.java:256)
>
> at
> org.apache.shindig.gadgets.features.FeatureResourceLoader.loadUri(FeatureResourceLoader.java:135)
>
> at
> org.apache.shindig.gadgets.features.FeatureResourceLoader.load(FeatureResourceLoader.java:88)
>
> at
> org.apache.shindig.gadgets.features.FeatureRegistry.loadFeature(FeatureRegistry.java:486)
>
> at
> org.apache.shindig.gadgets.features.FeatureRegistry.loadResources(FeatureRegistry.java:425)
>
> at
> org.apache.shindig.gadgets.features.FeatureRegistry.register(FeatureRegistry.java:180)
>
> at
> org.apache.shindig.gadgets.features.FeatureRegistry.(FeatureRegistry.java:112)
>
> at
> org.apache.shindig.gadgets.features.FeatureRegistry.(FeatureRegistry.java:99)
>
> at
> org.apache.shindig.gadgets.features.FeatureRegistry$$FastClassByGuice$$536f6a5.newInstance()
>
> at
> com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
>
> at
> com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:60)
>
> at
> com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
>
> at
> com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
>
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
>
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
>
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
>
> at com.google.inject.Scopes$1$1.get(Scopes.java:65)
>
> at
> com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
>
> at
> com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:38)
>
> at
> com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:62)
>
> at
> com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:84)
>
> at
> com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
>
> at
> 

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Tanya Madurapperuma]

Hi Ruwan,

Usually this error is thrown as shindig is trying to load some google
analytics apis. So when there is no internet connection this error can be
observed.
To get rid of this error we have to remove google related stuff from
shindig features.txt file

*features-extras/analytics/feature.xml*
*features-extras/com.google.gadgets.analytics/feature.xml*

But since we don't maintain a shindig fork, we can't do this from
carbon-dashboards level. So in the Dashboard Server level we are replacing
the features.txt file with a file which doesn't have above 2 entries [1].
We'll have to do the same for apim analytics as well.

[1]
https://github.com/wso2/product-ds/commit/2d763ce1d9f5362d559e9d46eb0bcedf1446ee9e

Thanks,
Tanya

On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon  wrote:

> Hi DS team,
> I am getting the following error in APIM 2.0.0-SNAPSHOT which integrate DS
> features. Any Idea why? can we not print those errors due to outside
> dependencies?
>
> ---
>
> achines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libinstrument.dylib. One of
> the two will be used. Which one is undefined.
>
> [2016-05-17 17:35:49,176]  INFO - FeatureRegistry Resources from
> res:features/features.txt are loading.
>
> [2016-05-17 17:35:49,186]  INFO - XmlUtil The XML processor being used
> does not support secure parsing.
>
> [2016-05-17 17:35:49,187]  INFO - XmlUtil Document builders are being
> reused.
>
> [2016-05-17 17:35:49,396]  INFO - FeatureRegistry Resources from
> res:features-extras/features.txt are loading.
>
> [2016-05-17 17:36:11,707]  INFO - CarbonEventManagementService Starting
> polling event receivers
>
> [2016-05-17 17:36:19,510]  INFO - BasicHttpFetcher The following exception
> occurred when fetching http://www.google-analytics.com/urchin.js: 30,103
> ms elapsed.
>
> [2016-05-17 17:36:19,511]  INFO - BasicHttpFetcher
>
> org.apache.http.conn.ConnectTimeoutException: Connect to
> www.google-analytics.com:80 timed out
>
> at
> org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
>
> at
> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
>
> at
> org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
>
> at
> org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
>
> at
> org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
>
> at
> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
>
> at
> org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
>
> at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:115)
>
> at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
>
> at
> org.apache.shindig.gadgets.http.BasicHttpFetcher.fetch(BasicHttpFetcher.java:359)
>
> at
> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.getContent(FeatureResourceLoader.java:291)
>
> at
> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.(FeatureResourceLoader.java:270)
>
> at
> org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.(FeatureResourceLoader.java:256)
>
> at
> org.apache.shindig.gadgets.features.FeatureResourceLoader.loadUri(FeatureResourceLoader.java:135)
>
> at
> org.apache.shindig.gadgets.features.FeatureResourceLoader.load(FeatureResourceLoader.java:88)
>
> at
> org.apache.shindig.gadgets.features.FeatureRegistry.loadFeature(FeatureRegistry.java:486)
>
> at
> org.apache.shindig.gadgets.features.FeatureRegistry.loadResources(FeatureRegistry.java:425)
>
> at
> org.apache.shindig.gadgets.features.FeatureRegistry.register(FeatureRegistry.java:180)
>
> at
> org.apache.shindig.gadgets.features.FeatureRegistry.(FeatureRegistry.java:112)
>
> at
> org.apache.shindig.gadgets.features.FeatureRegistry.(FeatureRegistry.java:99)
>
> at
> org.apache.shindig.gadgets.features.FeatureRegistry$$FastClassByGuice$$536f6a5.newInstance()
>
> at
> com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
>
> at
> com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:60)
>
> at
> com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
>
> at
> com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
>
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
>
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
>
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
>
> at com.google.inject.Scopes$1$1.get(Scopes.java:65)
>
> at
> 

Re: [Dev] Representing a JSON payload with null values - visual datamapper editor

[Vivekananthan Sivanayagam]

Hi Sohani,

Normally we are getting null value for optional parameter in the API
response, suppose if we get the actual value for that json object , does
this schema handle that case?





*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com *
*M:+94752786138*

On Wed, May 18, 2016 at 11:19 AM, Sohani Weerasinghe 
wrote:

> Hi All,
>
> If a json payload has null values as shown below, how are we going to
> represent this in the json schema?
>
> {
>   "root": {
> "tasklist_id": "12345",
> "test"=null
> }
> }
>
> If we are serializing that value, then the generated schema and the tree
> view will be as follows
>
> {
>   "$schema" : "http://json-schema.org/draft-04/schema#;,
>   "id" : "http://wso2jsonschema.org;,
>   "title" : "root",
>   "type" : "object",
>   "properties" : {
> *"test" : {*
> *  "id" : "http://wso2jsonschema.org/test
> ",*
> *  "type" : "null"*
> *},*
> "tasklist_id" : {
>   "id" : "http://wso2jsonschema.org/tasklist_id;,
>   "type" : "string"
> }
>   }
> }
>
>
> ​
>
> Appreciate your input on this
>
> Thanks,
> Sohani
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][ESB]Access URI, Headers and Query params in Java script

[Dushan Abeyruwan]

Hi
 The $subject, I guess this can be a valid use case, anyway, it seems [1]
having setProperty, but ideally, that should have improved to select
whichever property according to developer preferred scope.

Can we consider this in our roadmap?

[1]
https://github.com/wso2/wso2-synapse/blob/master/modules/extensions/src/main/java/org/apache/synapse/mediators/bsf/ScriptMessageContext.java

-- 
Dushan Abeyruwan | Technical Lead

PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:*http://www.dushantech.com/ *
LinkedIn:*https://www.linkedin.com/in/dushanabeyruwan
*
Mobile:(001)408-791-9312
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC 2016 - Project 21 : MongoDB Userstore Development

[Tharindu Edirisinghe]

Hi Asantha,

Great progress so far !

Since the reference is given to realm service in the bundle activator, you
should be facing the issue. Can you remove the service reference from the
bundle activator class. (You can delete the following from the class).

* @scr.reference name="user.realmservice.default"
 * interface="org.wso2.carbon.user.core.service.RealmService"
cardinality="1..1"
 * policy="dynamic" bind="setRealmService"
 * unbind="unsetRealmService"

Also delete the following methods where realm service is used.

getRealmService()
setRealmService(RealmService rlmService)
unsetRealmService(RealmService rlmService)

After that can you try if the userstore manager is working as expected. If
you face any issues, please get back.

Thank you,
TharinduE






On Sun, May 15, 2016 at 7:48 PM, Asantha Thilina 
wrote:

> Hi Tharindu,
>
> I found the issue after debugging into my code ,my service bundle is not
> get activated because i referring into mongodb-driver which is not osgi
> comaptible and i just found another library in here[1] and it is worked for
> me ,fixed project i pushed into my github repository [2].
> i found out that *DefaultRealmService* which is used in Bundle Activator
> of JDBCUserstoreManager cannot be used for MongoDB since it used
> *java.sql.DataSource*.
> Is their having any DataSource class like that for MongoDB? or would i
> have to create a different logic to implement that scenario in MongoDB?
> waiting for your suggestion
>
> [1]. http://central.maven.org/maven2/org/mongodb/mongo-java-driver/3.2.2/
> [2]. https://github.com/asanthamax/mongodbuserstore
> Thanks,
> Asantha
>
> On Sat, May 14, 2016 at 10:53 AM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Tharindu,
>>
>> i faced following issue while i developing ,
>> after adding my new json query support i didn't able to see My
>> MongoDBUserStore in dropdown in create user store option.
>> for json related activites i used an external json dependency from
>> here[1] and i added it jar to lib folder in IS as well,i have enabled
>> remote debugging and inspect my code and there i found in my 
>> *MongoDBUserStoreDSComponent
>> *class *activate *method triggered but execute 1st line of code only. it
>> will not registered the service but in my osgi console window when i run *ss
>> mongo* command i get monodb.userstore bundle and mongodb java driver
>> bundle are activated successfully i attached my console output and identity
>> server output for your consideration as well
>> any suggestion would be grateful
>>
>> [1]. http://mvnrepository.com/artifact/org.json/json/20160212
>> my github repository
>>
>> https://github.com/asanthamax/mongodbuserstore/tree/master/mongodb.userstoremanager
>> Thanks,
>> Asantha
>>
>>
>> On Thu, May 12, 2016 at 2:01 AM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> since mongodb driver not having prepared statement support earlier i
>>> developed a logic to support prepared statement but i realized that it has
>>> a limitation such as parameters has to be pass as same order it exists in
>>> prepared statement then as you suggested to use key value relationship
>>> instead of order during our hangout conversation i created a new logic same
>>> to prepared statement in sql and it will work according to key value
>>> relationship and i created standard query format for mongodb with json to
>>> support prepared statements and i rewrite the JDBCRealmConstants class with
>>> those supporting json queries instead of sql queries
>>>
>>> All of my prepared statement methods contain in MongoDBPreparedStatement
>>> interface and its implementation in MongoDBPreparedStatementImpl class
>>>
>>> All the changes i have pushed to my repo in here[1]
>>>
>>> security of this prepared statements has to be improve
>>>
>>> I'll be grateful if you can provide me some suggestions to improve it
>>> and also another small issue i having is can i write a DataSource for
>>> MongoDB as in java.sql.DataSource ?
>>>
>>> [1]
>>> https://github.com/asanthamax/mongodbuserstore/tree/master/mongodb.userstoremanager
>>>
>>> Thanks,
>>> Asantha
>>>
>>
>>
>


-- 

Tharindu Edirisinghe
Software Engineer | WSO2 Inc
Platform Security Team
Blog : tharindue.blogspot.com
mobile : +94 775181586
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Kernel RC3

[Awanthika Senarath]

Thanks all,

We are closing this vote with 5 +1's and 0 -1's.

The RC has passed the vote.

Regards
Awanthika

Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Wed, May 18, 2016 at 12:54 PM, Jasintha Dasanayake 
wrote:

> Hi All
>
> I have tested the update tool , new feature installation and kernel patch
> process , no major issues found
>
> +1
>
> Thanks and Regards
> /Jasintha
>
> On Wed, May 18, 2016 at 11:23 AM, Heshitha Hettihewa 
> wrote:
>
>> Hi all,
>>
>> I have tested BPS Tooling and no major issues found.
>>
>> +1
>>
>> Thanks.
>>
>> On Wed, May 18, 2016 at 9:10 AM, Isuru Udana  wrote:
>>
>>> Hi,
>>>
>>> Tested with ESB tools and found no major issues.
>>>
>>> +1.
>>>
>>> On Wed, May 18, 2016 at 9:05 AM, Sohani Weerasinghe 
>>> wrote:
>>>
 Hi All,

 I have tested the updater tool functionality including installing
 features and also the updater tool preferences.

 +1

 Thanks,
 Sohani

 Sohani Weerasinghe
 Software Engineer
 WSO2, Inc: http://wso2.com

 Mobile  : +94 716439774
 Blog :http://christinetechtips.blogspot.com/
 Twitter  : https://twitter.com/sohanichristine

 On Wed, May 18, 2016 at 8:32 AM, Awanthika Senarath  wrote:

> I have tested,
>
> Installation of Developer Studio Platform, ESB and CEP tools on top of
> kernel
> Updater tool functionality, installation and job running
>
>
>
>  +1,
>
> Regards
> Awanthika
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Mon, May 16, 2016 at 3:10 PM, Awanthika Senarath <
> awanth...@wso2.com> wrote:
>
>> Hello Devs,
>>
>>
>> We are pleased to announce the vote for RC-3 of
>> *WSO2 Developer Studio Kernel 4.1.0.*
>>
>> P2 repository of WSO2 developer Studio kernel 4.1.0 is available here
>> .
>>  Source
>> and Tag Location to be voted upon is available here
>> 
>> .
>>
>> Developer Studio 4.1.0 Kernel is released on Eclipse Mars (Eclipse
>> 4.5)
>>
>> Developer Studio Kernel contains a single feature which has the
>> bundles that are required to implement WSO2 specific product tooling on
>> Eclipse.
>>
>>- This release contains Developer Studio migration to Eclipse mars
>>- Improvements in the Developer Studio Updater tool for automatic
>>updates
>>
>>
>>
>>1. [+] Stable - go ahead and release
>>2. [-]  Broken - do not release (please explain why)
>>
>>
>>
>> Regards,
>> Dev Studio Team
>>
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>
> ___
> 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


>>>
>>>
>>> --
>>> *Isuru Udana*
>>> Associate Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>> email: isu...@wso2.com cell: +94 77 3791887
>>> blog: http://mytecheye.blogspot.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Heshitha Hettihewa
>> *Software Engineer*
>> Mobile : +94716866386
>> <%2B94%20%280%29%20773%20451194>
>> heshit...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Jasintha Dasanayake*
>
> *Senior Software EngineerWSO2 Inc. | http://wso2.com
> lean . enterprise . middleware*
>
>
> *mobile :- 0711368118*
>
> ___
> 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] GSoC Dockerfiles weekly status meeting minutes

[Abhishek Tiwari]

Hi All,

Following are the meeting notes from our weekly status update meeting:

Tasks completed:
1. Completed code walk-through of Dockerfiles project.
2. Understanding and build of clustered configuration for WSO2 ESB. This was a 
huge step in understanding various profiles for clustered environment.
3. Debugging and testing of docker-build and docker-run scripts.
4. Added ability to fail fast when docker daemon is not running in the host. 
Pull request [1].

Current tasks:
1. Deploy docker products using puppet provisioning modules [2].
2. Use puppet provisioning to configure manager and worker profiles for ESB.
3. Investigate suitable programming languages and technologies for the proposed 
test framework. 

Thanks,
Abhishek

[1]. https://github.com/wso2/dockerfiles/pull/44 

[2]. https://github.com/wso2/puppet-modules 


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

[Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC

[Awanthika Senarath]

Hello Devs,


We are pleased to announce the vote for RC-3 of *WSO2 Developer Studio Tooling
for Platform 4.1.0.*

P2 repository of WSO2 developer Studio  Tooling for Platform 4.1.0 is
available here
.
Source
and Tag Location to be voted upon is available here

.

Developer Studio 4.1.0  Tooling for Platform is released on Developer
Studio kernel 4.1.0
Developer Studio Kernel contains a single feature which has the bundles
that are required to implement WSO2 specific product tooling on Eclipse.

   - This release contains Developer Studio migration to Eclipse mars
   - Improvements in the Developer Studio Updater tool for automatic updates



   1. [+] Stable - go ahead and release
   2. [-]  Broken - do not release (please explain why)


The platform could to be tested on top of Developer Studio Kernel with
compatible tooling SNAPSHOT versions available at [1].


[1]
http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/



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

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC

[Awanthika Senarath]

We are withdrawing this vote as we have to upgrade the maven versions in
the maven car plugins of platform bundles.

We will put the RC 2 with the changes.


Regards
Awanthika.

Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Thu, May 19, 2016 at 8:08 AM, Awanthika Senarath 
wrote:

> Hello Devs,
>
>
> We are pleased to announce the vote for RC-3 of *WSO2 Developer Studio Tooling
> for Platform 4.1.0.*
>
> P2 repository of WSO2 developer Studio  Tooling for Platform 4.1.0 is
> available here
> .
>  Source
> and Tag Location to be voted upon is available here
> 
> .
>
> Developer Studio 4.1.0  Tooling for Platform is released on Developer
> Studio kernel 4.1.0
> Developer Studio Kernel contains a single feature which has the bundles
> that are required to implement WSO2 specific product tooling on Eclipse.
>
>- This release contains Developer Studio migration to Eclipse mars
>- Improvements in the Developer Studio Updater tool for automatic
>updates
>
>
>
>1. [+] Stable - go ahead and release
>2. [-]  Broken - do not release (please explain why)
>
>
> The platform could to be tested on top of Developer Studio Kernel with
> compatible tooling SNAPSHOT versions available at [1].
>
>
> [1]
> http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/
>
>
>
> Regards,
> Dev Studio Team
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"

[Dilshani Subasinghe]

Noted and reported a jira [1] to cover up fixing the issue.

[1] https://wso2.org/jira/browse/ESBJAVA-4625

Regards,
Dilshani


On Thu, May 19, 2016 at 10:47 AM, Nuwan Wimalasekara 
wrote:

> HI Dilshani,
>
> On Wed, May 18, 2016 at 6:27 PM, Dilshani Subasinghe 
> wrote:
>
>> Hi Nuwan,
>>
>> Thanks a lot for your clarification. But need more explanation on your
>> comments.
>>
>> 1. *if the user define only transport.jms.InitialReconnectDuration, It
>> will always be multiplied by the transport.jms.ReconnectProgressFactor
>> until it reach to transport.jms.MaxReconnectDuration. *
>>
>> We can define "transport.jms.MaxReconnectDuration" as 30 seconds and
>> shut down the jms broker. It may increase retry time interval by
>> ReconnectProgressFactor and doesn't consider about MaxReconnectDuration.
>>
>
> The log is not correct. It waits for MaxReconnectDuration. But logs show
> incorrect value. Thanks for reporting the issue. Will fix the logs.
>
>>
>> As I know MaxReconnectDuration is used to define upper level of
>> reconnect time limit. I don't understand exact relationship between "
>> ReconnectProgressFactor" and "MaxReconnectDuration". Can you verify it
>> further?
>>
>> When include "> locked="false">3" and testing with exact scenario you can
>> find logs as follows:
>>
>> [2016-05-18 18:01:21,257] ERROR - ServiceTaskManager Reconnection attempt
>> : 1 for service : QueueProxy failed. Next retry in 20 seconds
>> [2016-05-18 18:01:21,258] ERROR - ServiceTaskManager Reconnection attempt
>> : 1 for service : TopicProxy failed. Next retry in 20 seconds
>> [2016-05-18 18:01:51,262] ERROR - ServiceTaskManager Reconnection attempt
>> : 2 for service : QueueProxy failed. Next retry in 40 seconds
>> [2016-05-18 18:01:51,263] ERROR - ServiceTaskManager Reconnection attempt
>> : 2 for service : TopicProxy failed. Next retry in 40 seconds
>> [2016-05-18 18:02:31,269] ERROR - ServiceTaskManager Reconnection attempt
>> : 3 for service : QueueProxy failed. Next retry in 60 seconds
>> [2016-05-18 18:02:31,271] ERROR - ServiceTaskManager Reconnection attempt
>> : 3 for service : TopicProxy failed. Next retry in 60 seconds
>>
>>  2.
>>
>>
>> *if the user define only transport.jms.InitialReconnectDuration, It will
>> always be multiplied by the transport.jms.ReconnectProgressFactor until it
>> reach to transport.jms.MaxReconnectDuration. *
>> I also tried above scenario while adding both InitialReconnectDuration
>> and MaxReconnectDuration. What do you mean by "*It will always be
>> multiplied by the transport.jms.ReconnectProgressFactor until it reach
>> to transport.jms.MaxReconnectDuration.*"
>>
>> When I am testing got the same result as above scenario:
>>
>> > locked="false">1
>> > locked="false">3
>>
>> Logs:
>>
>> [2016-05-18 18:19:02,148] ERROR - ServiceTaskManager Reconnection attempt
>> : 1 for service : QueueProxy failed. Next retry in 20 seconds
>> [2016-05-18 18:19:02,148] ERROR - ServiceTaskManager Reconnection attempt
>> : 1 for service : TopicProxy failed. Next retry in 20 seconds
>> [2016-05-18 18:19:32,153] ERROR - ServiceTaskManager Reconnection attempt
>> : 2 for service : QueueProxy failed. Next retry in 40 seconds
>> [2016-05-18 18:19:32,153] ERROR - ServiceTaskManager Reconnection attempt
>> : 2 for service : TopicProxy failed. Next retry in 40 seconds
>>
>> Hope you will clarify more on these factors.
>>
>> Regards,
>> Dilshani
>>
>>
>> On Wed, May 18, 2016 at 5:53 PM, Nuwan Wimalasekara 
>> wrote:
>>
>>> Hi Dilshani,
>>>
>>> If the user need to define constant interval for reconnect, user can
>>> define transport.jms.ReconnectInterval. Then it will wait defined value for
>>> each reconnect attempt.
>>>
>>> if the user define only transport.jms.InitialReconnectDuration, It will
>>> always be multiplied by the transport.jms.ReconnectProgressFactor until
>>> it reach to transport.jms.MaxReconnectDuration.
>>>
>>> transport.jms.ReconnectProgressFactor is set to 2 by default to
>>> increasing the reconnect interval exponential until it reach
>>> to transport.jms.MaxReconnectDuration.
>>>
>>>
>>> On Wed, May 18, 2016 at 1:59 PM, Dilshani Subasinghe 
>>> wrote:
>>>
 Hi ESB Team,

 When consider about "JMS connection factory parameters" [1] , user can
 define "transport.jms.InitialReconnectDuration" parameter to give time
 duration which will define initial reconnection time after broken JMS
 connection.

 But the given value will be multiply with 2. That 2 is coming from
 "reconnectionProgressionFactor" which can be over ride by
 "transport.jms.ReconnectProgressFactor" (Which is another jms connection
 factory parameter).

 ServiceTaskManager.java class will handle above function as follows:

>>>
>>>
i
 *f (reconnectDuration != null) {*

>>>//if transport.jms.ReconnectInterval is available.
>>>

Re: [Dev] Fwd: GSOC2016: [ML][CEP] Predictive analytic with online data for WSO2 Machine Learner

[Maheshakya Wijewardena]

Hi Mahesh,

I've look into your code sample of streaming linear regression. Looks good
to me, apart from few issues in coding practices which we can improve when
you're doing the implementations in carbon-ml and during the code reviews.
You are using a set of files as mini-batches of data, right? Can you also
send us the datasets you've been using. I'd like to run this.

does that cep problem is now all right that we were trying to fix. I am
> still using those pre-build versions. If so i can merge with the latest one.


I'll check this and let you know.

Can we arrange a meeting (preferably in WSO2 offices) in next week with ML
team members as well. Coding period begins on next Monday, so it's better
to get overall feedback from others and discuss more about the project. Let
me know convenient time slots for you. I'll arrange a meeting with ML team.

Best regards.

On Wed, May 18, 2016 at 9:53 AM, Mahesh Dananjaya  wrote:

> Hi Maheshakya,
> Ok. I will check it.you have sent me those relevant references and i am
> working on that thing.thank you. does that cep problem is now all right
> that we were trying to fix. I am still using those pre-build versions. If
> so i can merge with the latest one.thanks.
> BR,
> Mahesh.
>
> On Wed, May 18, 2016 at 9:44 AM, Maheshakya Wijewardena <
> mahesha...@wso2.com> wrote:
>
>> Hi Mahesh,
>>
>> You don't actually have to implement anything in spark streaming. Try to
>> understand how streaming data is handled in and the specifics of the
>> underlying algorithms in streaming.
>> What we want to do is having the similar algorithms that support CEP
>> event streams with siddhi.
>>
>> Best regards.
>>
>> On Wed, May 18, 2016 at 9:38 AM, Mahesh Dananjaya <
>> dananjayamah...@gmail.com> wrote:
>>
>>> Hi Maheshakya,
>>> Did you check the repo. I will add recent works today.And also i was
>>> going through the Java docs related to spark streaming work. It is with
>>> that scala API. thank you.
>>> regards,
>>> Mahesh.
>>>
>>> On Tue, May 17, 2016 at 10:11 AM, Mahesh Dananjaya <
>>> dananjayamah...@gmail.com> wrote:
>>>
 Hi Maheshakya,
 I have gone through the Java Docs and run some of the Spark examples on
 spark shell which are paramount improtant for our work. Then i have been
 writing my codes to check the Linear regression, K means for streaming.
 please check my git repo [1]. I think now i have to ask on dev regarding
 the capturing event streams for our work. I will update the recent things
 on git. check the park-example directory for java. examples run on git
 shell is not included there. In my case i think i have to build mini
 batches from data streams that comes as individual samples. Now i am
 working on some coding to collect mini batches from data streams.thank you.
 regards,
 Mahesh.
 [1]https://github.com/dananjayamahesh/GSOC2016

 On Tue, May 17, 2016 at 10:10 AM, Mahesh Dananjaya <
 dananjayamah...@gmail.com> wrote:

> Hi Maheshakya,
> I have gone through the Java Docs and run some of the Spark examples
> on spark shell which are paramount improtant for our work. Then i have 
> been
> writing my codes to check the Linear regression, K means for streaming.
> please check my git repo [1]. I think now i have to ask on dev regarding
> the capturing event streams for our work. I will update the recent things
> on git. check the park-example directory for java. examples run on git
> shell is not included there. In my case i think i have to build mini
> batches from data streams that comes as individual samples. Now i am
> working on some coding to collect mini batches from data streams.thank 
> you.
> regards,
> Mahesh.
> [1]https://github.com/dananjayamahesh/GSOC2016
>
> On Mon, May 16, 2016 at 1:19 PM, Mahesh Dananjaya <
> dananjayamah...@gmail.com> wrote:
>
>> Hi Maheshakya,
>> thank you. i will update the repo today.thank you.i changed the
>> carbon ml siddhi extention and see how the changes are effecting. i will
>> update the progress as soon as possible.thank you. i had some problem in
>> spark mllib dependency. i was fixing that.
>> regards,
>> Mahesh.
>> p.s: do i need to maintain a blog?
>>
>> On Mon, May 16, 2016 at 10:02 AM, Maheshakya Wijewardena <
>> mahesha...@wso2.com> wrote:
>>
>>> Hi Mahesh,
>>>
>>> Sorry for replying late.
>>>
>>> Thank you for the update. I believe you have done some
>>> implementations with with Spark MLLIb algorithms in streaming fashion 
>>> as we
>>> have discussed. If so, can you please share your code in a Github repo.
>>>
>>> Now i want to implements some machine learning algorithms with
 importing mllib and want to run within your code base

>>>
>>> For the moment you can try out editing the same class
>>> PredictStreamProcessor in the 

Re: [Dev] Representing a JSON payload with null values - visual datamapper editor

[Shakila Sivagnanarajah]

Hi,

IMO, As Nuwan said, generating the schema without null is the best way.
Since there may be chances to get values for those nullable fields. So we
will create the schema by replacing possible values for the null as shown
in [1]. Currently we replace those nulls with string values.

The problem in this approach is; It is difficult to find the types of
all response
fields. Since they don't document all response fields. So we can guess from
the name of the field or some APIs provide sample response.

It should not allow to map with another one, in case the field in the
actual response is null.

[1]

Response Payload:

{
 "id": 731513399901851600,
 "name": "Josh",
 "message":null,
 "isProtected":null
}

Modified Payload:

{
 "id": 731513399901851600,
 "name": "Josh",
 "message":"Test Message",
 "isProtected":true
}


Thanks

On Wed, May 18, 2016 at 1:31 PM, Nuwan Pallewela  wrote:

> Hi Malaka,
>
> Yes. We may have to refer api docs and find the expected value for those
> optional fields and in the esb runtime data mapper engine should handle
> them. But the engine is not implemented up-to that level yet. We should
> handle these null-able fields.
>
> Thanks,
> Nuwan
>
> On Wed, May 18, 2016 at 12:07 PM, Malaka Silva  wrote:
>
>> Actually those are options for the given configuration. We don't really
>> have a clear idea what are the optional response elements. (Unless we refer
>> api docs)
>>
>> So I guess we can proceed with sample values.
>>
>> From datamapper mediator(ESB Side) level we need to handle if we receive
>> a null value. Guess this is already considered?
>>
>> On Wed, May 18, 2016 at 12:02 PM, Sohani Weerasinghe 
>> wrote:
>>
>>>
>>>
>>> Sohani Weerasinghe
>>> Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>> On Wed, May 18, 2016 at 12:00 PM, Nuwan Pallewela 
>>> wrote:
>>>
 Hi All,

 @Vivekanathan : If we need to process/map any value in the payload
 though it is optional we have to know the type when generating the schema.
 So the sample pay load should not contain null values first place. We need
 to modify the sample payload with expected values so that in the schema
 generation we could set the type correctly for that field.

 @Sohani : +1 for the above mention approach in the schema generation.
 One small suggestion to remove the arrow head of type null elements to
 restrict users from mapping such elements.

>>>
>>> Will do.
>>>

 Thanks,
 Nuwan

 On Wed, May 18, 2016 at 11:51 AM, Vivekananthan Sivanayagam <
 vivekanant...@wso2.com> wrote:

> Hi Sohani,
>
> Normally we are getting null value for optional parameter in the API
> response, suppose if we get the actual value for that json object , does
> this schema handle that case?
>
>
>
>
>
> *Thank youVivekananthan Sivanayagam*
>
> *Associate Software Engineer | WSO2*
>
> *E:vivekanant...@wso2.com *
> *M:+94752786138 <%2B94752786138>*
>
> On Wed, May 18, 2016 at 11:19 AM, Sohani Weerasinghe 
> wrote:
>
>> Hi All,
>>
>> If a json payload has null values as shown below, how are we going to
>> represent this in the json schema?
>>
>> {
>>   "root": {
>> "tasklist_id": "12345",
>> "test"=null
>> }
>> }
>>
>> If we are serializing that value, then the generated schema and the
>> tree view will be as follows
>>
>> {
>>   "$schema" : "http://json-schema.org/draft-04/schema#;,
>>   "id" : "http://wso2jsonschema.org;,
>>   "title" : "root",
>>   "type" : "object",
>>   "properties" : {
>> *"test" : {*
>> *  "id" : "http://wso2jsonschema.org/test
>> ",*
>> *  "type" : "null"*
>> *},*
>> "tasklist_id" : {
>>   "id" : "http://wso2jsonschema.org/tasklist_id;,
>>   "type" : "string"
>> }
>>   }
>> }
>>
>>
>> ​
>>
>> Appreciate your input on this
>>
>> Thanks,
>> Sohani
>> Sohani Weerasinghe
>> Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>
>


 --
 --

 *Nuwan Chamara Pallewela*


 *Software Engineer*

 *WSO2, Inc. *http://wso2.com
 *lean . enterprise . middleware*

 Email   *nuw...@wso2.com *
 Mobile  *+94719079739 <%2B94719079739>@*



>>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech 

Re: [Dev] WSO2 BPS - Email Task

[Himasha Guruge]

Hi Luis,

I have tested email task in BPS 3.5.1 server with following steps.

1. Add the configurations in /repository/conf/activti.xml. Please
look into attached, for further reference.
2. Add required jars mentioned in [1]  into
/repository/components/lib.
3. Deploy the sample, and start the process from bpmn-explorer.

As Amal mentioned make sure you have enabled less secure apps to access.
I'm also attaching the sample I used. (MyProcess.bar)

[1] https://docs.wso2.com/display/BPS351/Working+With+Email+Task

Thanks,
Himasha


On Thu, May 19, 2016 at 10:08 AM, Nandika Jayawardana 
wrote:

>
> -- Forwarded message --
> From: Amal Gunatilake 
> Date: Wed, May 18, 2016 at 9:29 PM
> Subject: Re: WSO2 BPS - Email Task
> To: Luis Calderon Rodríguez 
> Cc: Nandika Jayawardana , Hasitha Hiranya <
> hasit...@wso2.com>, Miler Alberto García Villanueva <
> miler.gar...@proxus.pe>
>
>
> Hi Luis,
>
> Seems like you have everything in order from BPS side configurations.
>
> I can only think of one more configuration that is missing on your steps.
> Have you enabled Gmail security settings[1] to allow less secure apps to
> access?
>
> [1] https://support.google.com/accounts/answer/6010255?hl=en
>
> Best regards,
> Amal.
>
> On Wed, May 18, 2016 at 9:05 PM, Luis Calderon Rodríguez <
> luis.calde...@proxus.pe> wrote:
>
>> Hi Amal,
>>
>>
>> Thanks for answering this mail.
>>
>>
>> If I have installed the latest version:
>> /opt/wso2bps-3.5.1/repository/deployment/server/
>>
>>
>> Copy the dependencies jar : /opt/wso2bps-3.5.1./repository/components/lib/
>>
>>
>> org.apache.commons:commons-email:jar:1.3
>>
>> javax.mail:mail:jar:1.4.7
>>
>> javax.activation:activation:jar:1.1
>>
>>
>> Then, set the parameters in the file activiti.xml:
>> /opt/wso2bps-3.5.1./repository/conf/
>>
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>>
>>
>> Finally restart the server, but still the problem persists.
>>
>>
>> Best regards
>> Luis
>>
>> 2016-05-18 1:09 GMT-05:00 Amal Gunatilake :
>>
>>> Hi Luis,
>>>
>>> There was a dependency issue[1] in email task which we fixed in BPS
>>> 3.5.1 release. Could you please try it out with the latest BPS release?
>>> This should probably resolve the error.
>>>
>>> [1] https://wso2.org/jira/browse/BPS-978
>>>
>>> Best regards,
>>> Amal.
>>>
>>> On Wed, May 18, 2016 at 11:13 AM, Luis Calderon Rodríguez <
>>> luis.calde...@proxus.pe> wrote:
>>>
 Hi guys,


 I hope you are very well.


 I've had some problems with mail tasks,I have this error message: “Error
 starting process:
 org.apache.commons.mail.Email.setSSLOnConnect(Z)Lorg/apache/commons/mail/Email
 ”



 I 'm using these jar:



 org.apache.commons:commons-email:jar:1.3

 javax.mail:mail:jar:1.4.7

 javax.activation:activation:jar:1.1


 activity.xml

 ==

 http://www.springframework.org/schema/beans;

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;

xsi:schemaLocation="http://www.springframework.org/schema/beans
 http://www.springframework.org/schema/beans/spring-beans.xsd;>



 >>> class="org.activiti.engine.impl.cfg.StandaloneProcessEngineConfiguration">



 

 

 





  

  

  

  

  

  



 



 

 

 



 

 

 

 



 

 

 



 

 ==


 Thanks

 Luis




 2016-04-12 16:17 GMT-05:00 Luis Calderon Rodríguez <
 luis.calde...@proxus.pe>:

> I'm very grateful for your answers.
>
> Thanks
>
> 2016-04-12 2:12 GMT-05:00 Nandika Jayawardana :
>
>> Hi Luis,
>>
>> A BPMN process executed in a transactional manner from one wait state
>> to another wait state, Please refer to [1] for more details. Hence,
>> the bpmn db which keeps the state of the process instance will always
>> be at a consistent state even if a sudden BPS server shutdown occurred.
>>
>> However, within your process, if you are calling externals services ,
>> and these service invocations may result in state changes in those
>> services, there needs to be  compensation option provided by the service 
>> to
>> handle those. For example, let's assume your process invokes Operation A
>> and B one after the other. If operation B failed, we need to catch the
>> 

[Dev] Adding a user with '@' sign (username == test@user) without enable Email User

[Dhanuka Ranasinghe]

Hi All,

Currently we can add user with user name with @ sign, say for example if
the user name is "test@user" without enabling Email User, Carbon Management
console allow to add this user. But when we are trying to do the same thing
as user sign up with APIM manager it's getting failed with super tenant. We
found the root cause is at [1] line. Reason is from following highlighted
code line we are getting *tenantAwareUserName* as *test* by removing* @user*
part. Also *tenantName* also getting as *user*, which are wrong, and due to
that realm become *Null*.

There are few things need to be consider here.

1.  Is it correct allowing to add username with *@* sign at Carbon
Management Console without enable Email User?
2. Assume we have tenant domain called *wso2.com *, then
create user as *abc* with password *admin* in that domain space and again
 we create user as *a...@wso2.com * from super tenant space
with password as *admin.*

So when we try to login as* a...@wso2.com *, it login to 
*wso2.com
* tenant space. To login to super tenant user we need to
login as *a...@wso2.com@carbon.super*. Will this be OK?

[1] *org.wso2.carbon.identity.user.registration.UserRegistrationService.*
*addUser(UserDTO)*
*String tenantAwareUserName =
MultitenantUtils.getTenantAwareUsername(user.getUserName());*
*String tenantName = MultitenantUtils.getTenantDomain(user.getUserName());*
*realm = IdentityTenantUtil.getRealm(tenantName, null);*


Cheers,
Dhanuka

*Dhanuka Ranasinghe*

Associate TechLead
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware

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

Re: [Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"

[Nuwan Wimalasekara]

HI Dilshani,

On Wed, May 18, 2016 at 6:27 PM, Dilshani Subasinghe 
wrote:

> Hi Nuwan,
>
> Thanks a lot for your clarification. But need more explanation on your
> comments.
>
> 1. *if the user define only transport.jms.InitialReconnectDuration, It
> will always be multiplied by the transport.jms.ReconnectProgressFactor
> until it reach to transport.jms.MaxReconnectDuration. *
>
> We can define "transport.jms.MaxReconnectDuration" as 30 seconds and shut
> down the jms broker. It may increase retry time interval by
> ReconnectProgressFactor and doesn't consider about MaxReconnectDuration.
>

The log is not correct. It waits for MaxReconnectDuration. But logs show
incorrect value. Thanks for reporting the issue. Will fix the logs.

>
> As I know MaxReconnectDuration is used to define upper level of reconnect
> time limit. I don't understand exact relationship between "
> ReconnectProgressFactor" and "MaxReconnectDuration". Can you verify it
> further?
>
> When include " locked="false">3" and testing with exact scenario you can
> find logs as follows:
>
> [2016-05-18 18:01:21,257] ERROR - ServiceTaskManager Reconnection attempt
> : 1 for service : QueueProxy failed. Next retry in 20 seconds
> [2016-05-18 18:01:21,258] ERROR - ServiceTaskManager Reconnection attempt
> : 1 for service : TopicProxy failed. Next retry in 20 seconds
> [2016-05-18 18:01:51,262] ERROR - ServiceTaskManager Reconnection attempt
> : 2 for service : QueueProxy failed. Next retry in 40 seconds
> [2016-05-18 18:01:51,263] ERROR - ServiceTaskManager Reconnection attempt
> : 2 for service : TopicProxy failed. Next retry in 40 seconds
> [2016-05-18 18:02:31,269] ERROR - ServiceTaskManager Reconnection attempt
> : 3 for service : QueueProxy failed. Next retry in 60 seconds
> [2016-05-18 18:02:31,271] ERROR - ServiceTaskManager Reconnection attempt
> : 3 for service : TopicProxy failed. Next retry in 60 seconds
>
>  2.
>
>
> *if the user define only transport.jms.InitialReconnectDuration, It will
> always be multiplied by the transport.jms.ReconnectProgressFactor until it
> reach to transport.jms.MaxReconnectDuration. *
> I also tried above scenario while adding both InitialReconnectDuration and
> MaxReconnectDuration. What do you mean by "*It will always be multiplied
> by the transport.jms.ReconnectProgressFactor until it reach
> to transport.jms.MaxReconnectDuration.*"
>
> When I am testing got the same result as above scenario:
>
>  locked="false">1
>  locked="false">3
>
> Logs:
>
> [2016-05-18 18:19:02,148] ERROR - ServiceTaskManager Reconnection attempt
> : 1 for service : QueueProxy failed. Next retry in 20 seconds
> [2016-05-18 18:19:02,148] ERROR - ServiceTaskManager Reconnection attempt
> : 1 for service : TopicProxy failed. Next retry in 20 seconds
> [2016-05-18 18:19:32,153] ERROR - ServiceTaskManager Reconnection attempt
> : 2 for service : QueueProxy failed. Next retry in 40 seconds
> [2016-05-18 18:19:32,153] ERROR - ServiceTaskManager Reconnection attempt
> : 2 for service : TopicProxy failed. Next retry in 40 seconds
>
> Hope you will clarify more on these factors.
>
> Regards,
> Dilshani
>
>
> On Wed, May 18, 2016 at 5:53 PM, Nuwan Wimalasekara 
> wrote:
>
>> Hi Dilshani,
>>
>> If the user need to define constant interval for reconnect, user can
>> define transport.jms.ReconnectInterval. Then it will wait defined value for
>> each reconnect attempt.
>>
>> if the user define only transport.jms.InitialReconnectDuration, It will
>> always be multiplied by the transport.jms.ReconnectProgressFactor until
>> it reach to transport.jms.MaxReconnectDuration.
>>
>> transport.jms.ReconnectProgressFactor is set to 2 by default to
>> increasing the reconnect interval exponential until it reach
>> to transport.jms.MaxReconnectDuration.
>>
>>
>> On Wed, May 18, 2016 at 1:59 PM, Dilshani Subasinghe 
>> wrote:
>>
>>> Hi ESB Team,
>>>
>>> When consider about "JMS connection factory parameters" [1] , user can
>>> define "transport.jms.InitialReconnectDuration" parameter to give time
>>> duration which will define initial reconnection time after broken JMS
>>> connection.
>>>
>>> But the given value will be multiply with 2. That 2 is coming from
>>> "reconnectionProgressionFactor" which can be over ride by
>>> "transport.jms.ReconnectProgressFactor" (Which is another jms connection
>>> factory parameter).
>>>
>>> ServiceTaskManager.java class will handle above function as follows:
>>>
>>
>>
>>>i
>>> *f (reconnectDuration != null) {*
>>>
>>//if transport.jms.ReconnectInterval is available.
>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *retryDuration =
>>> reconnectDuration;log.error("Reconnection
>>> attempt : " + (r++) + " for service : "
>>> +serviceName + " failed. Next retry in
>>> " + (retryDuration / 1000) +" 

[Dev] [ES][PC] Requirement for delay for the Advanced Search GET Requests, after adding an asset

[Samitha Chathuranga]

Hi all,

At the present we are writing test cases for the PC and this issue was
caught when trying to write test cases for the Advanced Search feature. We
do the tests by initially adding few processes (assets) and then do the
test by searching via a certain field, (using GET requests) and checking
the Response object values. But issue came out was that, it takes many
seconds (sometimes more than a minute) after adding an asset, for them to
be searchable (using advanced search). It takes much time for that. (But
doing the same via the product UI directly doesn't take that much time).

So as a workaround I tried checking the registry if the asset is added to
it, before making the Advanced Search request. But found out that it is
also not making things correct. The asset is added to the registry quickly,
but still it is not searchable via the Advanced Search - GET Request. What
is the probable issue behind this? What is possible the solution you can
propose for this scenario?

P.S. Pls note that this issue is not apparent when we use the the actual
product directly via the UI.

Thanks

-- 
Samitha Chathuranga
Software Engineer, WSO2 Inc.
lean.enterprise.middleware
Mobile: +94715123761
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Kernel RC3

[Nuwan Pallewela]

Hi All,

I have tested and following issues were found.

https://wso2.org/jira/browse/TOOLS-3413
https://wso2.org/jira/browse/TOOLS-3412
https://wso2.org/jira/browse/TOOLS-3411

Thanks,
Nuwan

On Thu, May 19, 2016 at 9:48 AM, Awanthika Senarath 
wrote:

> Thanks all,
>
> We are closing this vote with 5 +1's and 0 -1's.
>
> The RC has passed the vote.
>
> Regards
> Awanthika
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Wed, May 18, 2016 at 12:54 PM, Jasintha Dasanayake 
> wrote:
>
>> Hi All
>>
>> I have tested the update tool , new feature installation and kernel patch
>> process , no major issues found
>>
>> +1
>>
>> Thanks and Regards
>> /Jasintha
>>
>> On Wed, May 18, 2016 at 11:23 AM, Heshitha Hettihewa 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have tested BPS Tooling and no major issues found.
>>>
>>> +1
>>>
>>> Thanks.
>>>
>>> On Wed, May 18, 2016 at 9:10 AM, Isuru Udana  wrote:
>>>
 Hi,

 Tested with ESB tools and found no major issues.

 +1.

 On Wed, May 18, 2016 at 9:05 AM, Sohani Weerasinghe 
 wrote:

> Hi All,
>
> I have tested the updater tool functionality including installing
> features and also the updater tool preferences.
>
> +1
>
> Thanks,
> Sohani
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Wed, May 18, 2016 at 8:32 AM, Awanthika Senarath <
> awanth...@wso2.com> wrote:
>
>> I have tested,
>>
>> Installation of Developer Studio Platform, ESB and CEP tools on top
>> of kernel
>> Updater tool functionality, installation and job running
>>
>>
>>
>>  +1,
>>
>> Regards
>> Awanthika
>>
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>> On Mon, May 16, 2016 at 3:10 PM, Awanthika Senarath <
>> awanth...@wso2.com> wrote:
>>
>>> Hello Devs,
>>>
>>>
>>> We are pleased to announce the vote for RC-3 of
>>> *WSO2 Developer Studio Kernel 4.1.0.*
>>>
>>> P2 repository of WSO2 developer Studio kernel 4.1.0 is available
>>> here
>>> .
>>>  Source
>>> and Tag Location to be voted upon is available here
>>> 
>>> .
>>>
>>> Developer Studio 4.1.0 Kernel is released on Eclipse Mars (Eclipse
>>> 4.5)
>>>
>>> Developer Studio Kernel contains a single feature which has the
>>> bundles that are required to implement WSO2 specific product tooling on
>>> Eclipse.
>>>
>>>- This release contains Developer Studio migration to Eclipse
>>>mars
>>>- Improvements in the Developer Studio Updater tool for
>>>automatic updates
>>>
>>>
>>>
>>>1. [+] Stable - go ahead and release
>>>2. [-]  Broken - do not release (please explain why)
>>>
>>>
>>>
>>> Regards,
>>> Dev Studio Team
>>>
>>> Awanthika Senarath
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94717681791
>>>
>>>
>>>
>>
>> ___
>> 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
>
>


 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/

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


>>>
>>>
>>> --
>>> Heshitha Hettihewa
>>> *Software Engineer*
>>> Mobile : +94716866386
>>> <%2B94%20%280%29%20773%20451194>
>>> heshit...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Jasintha Dasanayake*
>>
>> *Senior Software EngineerWSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware*
>>
>>
>> *mobile :- 0711368118*
>>
>> ___
>> 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] [App Cloud] Fronting microservice with HA Proxy

[Danushka Fernando]

I tried several combination of options by looking at the descriptions. But
only thing worked for me for microservices is option http-server-close
.
As mentioned before this seems a common issue when haproxy and netty are
together.

Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729

On Mon, May 16, 2016 at 11:32 PM, Manuranga Perera  wrote:

> [2]
> https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#option%20prefer-last-server
>
> On Mon, May 16, 2016 at 1:59 PM, Manuranga Perera  wrote:
>
>> KAL has the lowest latency on both the client and the server and in case
>>> of high request rate, it will be the fastest one. [1]
>>
>>
>> So it seems we should aim for "keep alive" and fix the issues. Maybe you
>> can try with [2] as it suggests.
>>
>> [1] https://www.haproxy.com/doc/aloha/7.0/haproxy/http_modes.html
>> [2] https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#option
>> prefer-last-server
>>
>> On Mon, May 16, 2016 at 11:41 AM, Danushka Fernando 
>> wrote:
>>
>>> Currently with HA proxy fronting microservice we are facing a connection
>>> reset exception [1]. Seems like this is a common issue with netty +
>>> haproxy. According to HA proxy manual[2] there are 5 connection modes. With
>>> connection mode "*httpclose*" I managed to get rid of the exception.
>>>
>>> From manual
>>> "In HTTP mode, the processing applied to requests and responses flowing
>>> over
>>>
>>> a connection depends in the combination of the frontend's HTTP options and
>>> the backend's. HAProxy supports 5 connection modes :
>>>
>>>   - KAL : keep alive ("option http-keep-alive 
>>> ")
>>>  which is the default mode : all
>>> requests and responses are processed, and connections remain open but 
>>> idle
>>> between responses and new requests.
>>>
>>>   - TUN: tunnel ("option http-tunnel 
>>> ")
>>>  : this was the default mode for versions
>>> 1.0 to 1.5-dev21 : only the first request and response are processed, 
>>> and
>>> everything else is forwarded with no analysis at all. This mode should 
>>> not
>>> be used as it creates lots of trouble with logging and HTTP processing.
>>> *  - PCL: passive close ("option httpclose 
>>> ")
>>>  : exactly the same as tunnel mode,
>>> but with "Connection: close" appended in both directions to try to make
>>> both ends close after the first request/response exchange.
>>> *
>>>   - SCL: server close ("option http-server-close 
>>> ")
>>>  : the server-facing
>>> connection is closed after the end of the response is received, but the
>>> client-facing connection remains open.
>>>
>>>   - FCL: forced close ("option forceclose 
>>> ")
>>>  : the connection is actively closed
>>>
>>> after the end of the response."
>>>
>>> But there are few questions in hand.
>>>
>>>
>>>1. Is this the correct approach to solve the issue?
>>>2. If its correct then can we use the same connection mode for other
>>>app types like tomcat and php as well?
>>>3. Are there any better approaches we can take?
>>>
>>>
>>> Any input would be appriciated.
>>>
>>> [1] https://wso2.org/jira/browse/APPCLOUD-79
>>> [2] https://cbonte.github.io/haproxy-dconv/configuration-1.5.html
>>>
>>> Thanks & Regards
>>> Danushka Fernando
>>> Senior Software Engineer
>>> WSO2 inc. http://wso2.com/
>>> Mobile : +94716332729
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> With regards,
>> *Manu*ranga Perera.
>>
>> phone : 071 7 70 20 50
>> mail : m...@wso2.com
>>
>
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"

[Dilshani Subasinghe]

In previous mail, I am referring both points to same thing. Please
consider, it should be correct as follows:

1.


*transport.jms.ReconnectProgressFactor is set to 2 by default to increasing
the reconnect interval exponential until it reach
to transport.jms.MaxReconnectDuration. *
2.
*if the user define only transport.jms.InitialReconnectDuration, It will
always be multiplied by the transport.jms.ReconnectProgressFactor until it
reach to transport.jms.MaxReconnectDuration. *


Regards,
Dilshani


On Wed, May 18, 2016 at 6:27 PM, Dilshani Subasinghe 
wrote:

> Hi Nuwan,
>
> Thanks a lot for your clarification. But need more explanation on your
> comments.
>
> 1. *if the user define only transport.jms.InitialReconnectDuration, It
> will always be multiplied by the transport.jms.ReconnectProgressFactor
> until it reach to transport.jms.MaxReconnectDuration. *
>
> We can define "transport.jms.MaxReconnectDuration" as 30 seconds and shut
> down the jms broker. It may increase retry time interval by
> ReconnectProgressFactor and doesn't consider about MaxReconnectDuration.
>
> As I know MaxReconnectDuration is used to define upper level of reconnect
> time limit. I don't understand exact relationship between "
> ReconnectProgressFactor" and "MaxReconnectDuration". Can you verify it
> further?
>
> When include " locked="false">3" and testing with exact scenario you can
> find logs as follows:
>
> [2016-05-18 18:01:21,257] ERROR - ServiceTaskManager Reconnection attempt
> : 1 for service : QueueProxy failed. Next retry in 20 seconds
> [2016-05-18 18:01:21,258] ERROR - ServiceTaskManager Reconnection attempt
> : 1 for service : TopicProxy failed. Next retry in 20 seconds
> [2016-05-18 18:01:51,262] ERROR - ServiceTaskManager Reconnection attempt
> : 2 for service : QueueProxy failed. Next retry in 40 seconds
> [2016-05-18 18:01:51,263] ERROR - ServiceTaskManager Reconnection attempt
> : 2 for service : TopicProxy failed. Next retry in 40 seconds
> [2016-05-18 18:02:31,269] ERROR - ServiceTaskManager Reconnection attempt
> : 3 for service : QueueProxy failed. Next retry in 60 seconds
> [2016-05-18 18:02:31,271] ERROR - ServiceTaskManager Reconnection attempt
> : 3 for service : TopicProxy failed. Next retry in 60 seconds
>
>  2.
>
>
> *if the user define only transport.jms.InitialReconnectDuration, It will
> always be multiplied by the transport.jms.ReconnectProgressFactor until it
> reach to transport.jms.MaxReconnectDuration. *
> I also tried above scenario while adding both InitialReconnectDuration and
> MaxReconnectDuration. What do you mean by "*It will always be multiplied
> by the transport.jms.ReconnectProgressFactor until it reach
> to transport.jms.MaxReconnectDuration.*"
>
> When I am testing got the same result as above scenario:
>
>  locked="false">1
>  locked="false">3
>
> Logs:
>
> [2016-05-18 18:19:02,148] ERROR - ServiceTaskManager Reconnection attempt
> : 1 for service : QueueProxy failed. Next retry in 20 seconds
> [2016-05-18 18:19:02,148] ERROR - ServiceTaskManager Reconnection attempt
> : 1 for service : TopicProxy failed. Next retry in 20 seconds
> [2016-05-18 18:19:32,153] ERROR - ServiceTaskManager Reconnection attempt
> : 2 for service : QueueProxy failed. Next retry in 40 seconds
> [2016-05-18 18:19:32,153] ERROR - ServiceTaskManager Reconnection attempt
> : 2 for service : TopicProxy failed. Next retry in 40 seconds
>
> Hope you will clarify more on these factors.
>
> Regards,
> Dilshani
>
>
> On Wed, May 18, 2016 at 5:53 PM, Nuwan Wimalasekara 
> wrote:
>
>> Hi Dilshani,
>>
>> If the user need to define constant interval for reconnect, user can
>> define transport.jms.ReconnectInterval. Then it will wait defined value for
>> each reconnect attempt.
>>
>> if the user define only transport.jms.InitialReconnectDuration, It will
>> always be multiplied by the transport.jms.ReconnectProgressFactor until
>> it reach to transport.jms.MaxReconnectDuration.
>>
>> transport.jms.ReconnectProgressFactor is set to 2 by default to
>> increasing the reconnect interval exponential until it reach
>> to transport.jms.MaxReconnectDuration.
>>
>>
>> On Wed, May 18, 2016 at 1:59 PM, Dilshani Subasinghe 
>> wrote:
>>
>>> Hi ESB Team,
>>>
>>> When consider about "JMS connection factory parameters" [1] , user can
>>> define "transport.jms.InitialReconnectDuration" parameter to give time
>>> duration which will define initial reconnection time after broken JMS
>>> connection.
>>>
>>> But the given value will be multiply with 2. That 2 is coming from
>>> "reconnectionProgressionFactor" which can be over ride by
>>> "transport.jms.ReconnectProgressFactor" (Which is another jms connection
>>> factory parameter).
>>>
>>> ServiceTaskManager.java class will handle above function as follows:
>>>
>>
>>
>>>i
>>> *f (reconnectDuration != null) {*
>>>
>>//if transport.jms.ReconnectInterval is available.
>>
>>>
>>>
>>>

Re: [Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"

[Dilshani Subasinghe]

Hi Nuwan,

Thanks a lot for your clarification. But need more explanation on your
comments.

1. *if the user define only transport.jms.InitialReconnectDuration, It will
always be multiplied by the transport.jms.ReconnectProgressFactor until it
reach to transport.jms.MaxReconnectDuration. *

We can define "transport.jms.MaxReconnectDuration" as 30 seconds and shut
down the jms broker. It may increase retry time interval by
ReconnectProgressFactor and doesn't consider about MaxReconnectDuration.

As I know MaxReconnectDuration is used to define upper level of reconnect
time limit. I don't understand exact relationship between "
ReconnectProgressFactor" and "MaxReconnectDuration". Can you verify it
further?

When include "3" and testing with exact scenario you can
find logs as follows:

[2016-05-18 18:01:21,257] ERROR - ServiceTaskManager Reconnection attempt :
1 for service : QueueProxy failed. Next retry in 20 seconds
[2016-05-18 18:01:21,258] ERROR - ServiceTaskManager Reconnection attempt :
1 for service : TopicProxy failed. Next retry in 20 seconds
[2016-05-18 18:01:51,262] ERROR - ServiceTaskManager Reconnection attempt :
2 for service : QueueProxy failed. Next retry in 40 seconds
[2016-05-18 18:01:51,263] ERROR - ServiceTaskManager Reconnection attempt :
2 for service : TopicProxy failed. Next retry in 40 seconds
[2016-05-18 18:02:31,269] ERROR - ServiceTaskManager Reconnection attempt :
3 for service : QueueProxy failed. Next retry in 60 seconds
[2016-05-18 18:02:31,271] ERROR - ServiceTaskManager Reconnection attempt :
3 for service : TopicProxy failed. Next retry in 60 seconds

 2.


*if the user define only transport.jms.InitialReconnectDuration, It will
always be multiplied by the transport.jms.ReconnectProgressFactor until it
reach to transport.jms.MaxReconnectDuration. *
I also tried above scenario while adding both InitialReconnectDuration and
MaxReconnectDuration. What do you mean by "*It will always be multiplied by
the transport.jms.ReconnectProgressFactor until it reach
to transport.jms.MaxReconnectDuration.*"

When I am testing got the same result as above scenario:

1
3

Logs:

[2016-05-18 18:19:02,148] ERROR - ServiceTaskManager Reconnection attempt :
1 for service : QueueProxy failed. Next retry in 20 seconds
[2016-05-18 18:19:02,148] ERROR - ServiceTaskManager Reconnection attempt :
1 for service : TopicProxy failed. Next retry in 20 seconds
[2016-05-18 18:19:32,153] ERROR - ServiceTaskManager Reconnection attempt :
2 for service : QueueProxy failed. Next retry in 40 seconds
[2016-05-18 18:19:32,153] ERROR - ServiceTaskManager Reconnection attempt :
2 for service : TopicProxy failed. Next retry in 40 seconds

Hope you will clarify more on these factors.

Regards,
Dilshani


On Wed, May 18, 2016 at 5:53 PM, Nuwan Wimalasekara  wrote:

> Hi Dilshani,
>
> If the user need to define constant interval for reconnect, user can
> define transport.jms.ReconnectInterval. Then it will wait defined value for
> each reconnect attempt.
>
> if the user define only transport.jms.InitialReconnectDuration, It will
> always be multiplied by the transport.jms.ReconnectProgressFactor until
> it reach to transport.jms.MaxReconnectDuration.
>
> transport.jms.ReconnectProgressFactor is set to 2 by default to
> increasing the reconnect interval exponential until it reach
> to transport.jms.MaxReconnectDuration.
>
>
> On Wed, May 18, 2016 at 1:59 PM, Dilshani Subasinghe 
> wrote:
>
>> Hi ESB Team,
>>
>> When consider about "JMS connection factory parameters" [1] , user can
>> define "transport.jms.InitialReconnectDuration" parameter to give time
>> duration which will define initial reconnection time after broken JMS
>> connection.
>>
>> But the given value will be multiply with 2. That 2 is coming from
>> "reconnectionProgressionFactor" which can be over ride by
>> "transport.jms.ReconnectProgressFactor" (Which is another jms connection
>> factory parameter).
>>
>> ServiceTaskManager.java class will handle above function as follows:
>>
>
>
>>i
>> *f (reconnectDuration != null) {*
>>
>//if transport.jms.ReconnectInterval is available.
>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *retryDuration =
>> reconnectDuration;log.error("Reconnection
>> attempt : " + (r++) + " for service : "
>> +serviceName + " failed. Next retry in
>> " + (retryDuration / 1000) +" seconds.
>> (Fixed Interval)");} else
>> {retryDuration = (long) (retryDuration *
>> reconnectionProgressionFactor);
>> log.error("Reconnection attempt : " + (r++) + " for service : "
>> +serviceName + " failed. Next retry in
>> " + (retryDuration / 1000) +"
>> seconds");*
>>
>>
>> There are two facts to clarify with above situation.
>>
>> 1. 

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

[Willian Antunes]

Vivekananthan,

Did you see what happened during the communication process? If didn't try
to install an sniffer like Wireshark to understand which error the LDAP
server sent to you.

There are two scenarios which you can use to test:

1 - Set *secureConnection* and *disableSSLCertificateChecking both as true*
in order to use a SSL port and ignore the certificate provided by the LDAP
server.
2 - Set *secureConnection* *as* *true* and *disableSSLCertificateChecking
as* *false* in order to use a SSL port and to validate the certificate
provided by the LDAP server. You have to make sure you have the ROOT CA was
imported in your OS which was used to sign the LDAP certificate, if you
don't then the connection will fail. Try to use an sniffer to understand
what is happening.

Important: Does not make sense to configure secureConnection as false
and disableSSLCertificateChecking as true because you're not using a secure
port like 636.

If you have any doubt please contact me!

Regards,
Antunes

On Wed, May 18, 2016 at 4:05 AM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Hi Malaka,
>
> I am working on that and still I have a problem in configure LDAP with SSL
> connection. Without SSL connection, the connector is working and according
> to the his changes, the SearchEntry method is working with onlyOneReference
> parameter. I need to check in SSL connection part.
>
> I configured in ubuntu and I could not connect LDAP over SSL connection.
> When I configure with port 636,it shows "ldap_result: Can't contact LDAP
> server (-1)" error.
>
>
>
>
>
> *Thank youVivekananthan Sivanayagam*
>
> *Associate Software Engineer | WSO2*
>
> *E:vivekanant...@wso2.com *
> *M:+94752786138 <%2B94752786138>*
>
> On Wed, May 18, 2016 at 9:22 AM, Malaka Silva  wrote:
>
>> Hi Vivekananthan,
>>
>> Please update the progress please?
>>
>> Shakila went through some of the methods in this connector. The
>> description for parameters are not added in all templates. This is not the
>> standard that we followed so far.
>>
>> On Sat, May 7, 2016 at 3:26 PM, Rajjaz Mohammed  wrote:
>>
>>> Hi Willian,
>>>
>>> Sorry for the missing headers. I edited the files from Developer Studio,
 it erases the XML file to a new one every time you open it. So even when a
 comment is inserted, the file will be erased again in the design view.

>>>
>>>
>>> I will look on that and update.
>>>
>>> --
>>> Thank you
>>> Best Regards
>>>
>>> *Rajjaz HM*
>>> Associate Software Engineer
>>> Platform Extension Team
>>> WSO2 Inc. 
>>> lean | enterprise | middleware
>>> Mobile | +94752833834|+94777226874
>>> Email   | raj...@wso2.com
>>> LinkedIn  | Blogger
>>>  | WSO2 Profile
>>> 
>>>
>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> 
>> https://store.wso2.com/store/
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Kubernetes Artifacts 1.0.0 Released!

[Isuru Haththotuwa]

WSO2 PaaS team is pleased to announce the release of WSO2 Kubernetes
Artifacts 1.0.0.

Main features of this release:

   -

   A consistent set of Kubernetes Artifacts with recommended best practices
   for deploying following WSO2 Products on Kubernetes:


   -

  WSO2 API Manager 1.10.0
  -

  WSO2 Application Server 5.3.0
  -

  WSO2 Business Process Server 3.5.0
  -

  WSO2 Business Rules Server 2.2.0
  -

  WSO2 Complex Event Processor 4.0.0
  -

  WSO2 Data Analytics Server 3.0.1
  -

  WSO2 Data Services Server 3.5.0
  -

  WSO2 Enterprise Store 2.0.0
  -

  WSO2 Enterprise Service Bus 4.9.0
  -

  WSO2 Governance Registry 5.1.0
  -

  WSO2 Identity Server 5.1.0
  -

  WSO2 Message Broker 3.1.0



   -

   A well-defined workflow for building Docker images using WSO2
   Dockerfiles and WSO2 Puppet Modules, which is used to deploy WSO2 products
   on Kubernetes
   -

   Support for distributed deployment patterns for WSO2 products on
   Kubernetes with minimum configuration steps
   -

   A Carbon membership scheme for automated cluster discovery on Kubernetes
   -

   A set of helper scripts for deployment automation on Kubernetes:
   -

  Load Docker images to Kubernetes nodes
  -

  Create shared databases
  -

  Deploy and undeploy Kubernetes Artifacts


Release Artifacts:

https://github.com/wso2/kubernetes-artifacts/releases/tag/v1.0.0

Documentation:

https://docs.wso2.com/display/KA100/Introduction

Please report any issues/suggestion for improvements at:
https://wso2.org/jira/browse/KUBARTIFAC


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

Re: [Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"

[Nuwan Wimalasekara]

Hi Dilshani,

If the user need to define constant interval for reconnect, user can
define transport.jms.ReconnectInterval. Then it will wait defined value for
each reconnect attempt.

if the user define only transport.jms.InitialReconnectDuration, It will
always be multiplied by the transport.jms.ReconnectProgressFactor until it
reach to transport.jms.MaxReconnectDuration.

transport.jms.ReconnectProgressFactor is set to 2 by default to increasing
the reconnect interval exponential until it reach
to transport.jms.MaxReconnectDuration.


On Wed, May 18, 2016 at 1:59 PM, Dilshani Subasinghe 
wrote:

> Hi ESB Team,
>
> When consider about "JMS connection factory parameters" [1] , user can
> define "transport.jms.InitialReconnectDuration" parameter to give time
> duration which will define initial reconnection time after broken JMS
> connection.
>
> But the given value will be multiply with 2. That 2 is coming from
> "reconnectionProgressionFactor" which can be over ride by
> "transport.jms.ReconnectProgressFactor" (Which is another jms connection
> factory parameter).
>
> ServiceTaskManager.java class will handle above function as follows:
>


>i
> *f (reconnectDuration != null) {*
>
   //if transport.jms.ReconnectInterval is available.

>
>
>
>
>
>
>
>
>
> *retryDuration =
> reconnectDuration;log.error("Reconnection
> attempt : " + (r++) + " for service : "
> +serviceName + " failed. Next retry in
> " + (retryDuration / 1000) +" seconds.
> (Fixed Interval)");} else
> {retryDuration = (long) (retryDuration *
> reconnectionProgressionFactor);
> log.error("Reconnection attempt : " + (r++) + " for service : "
> +serviceName + " failed. Next retry in
> " + (retryDuration / 1000) +"
> seconds");*
>
>
> There are two facts to clarify with above situation.
>
> 1. According to user perspective, it may be wrong to multiply the value
> which is given by user.
>
> Ex: User may add 10 seconds as initial retry interval, but ESB does it
> within 20 seconds.
>
> Note: When we add "transport.jms.ReconnectProgressFactor" in to axis2.xml,
> it can be override.
>
> * locked="false">1*
>
> 2. Why we hard code *reconnectionProgressionFactor *as 2 ? Can we change
> it or is it impossible because of the behavior of axis2 ?
>
> As a suggestion, it will be better to add it as 1. (It may also solve the
> problem discussed above step)
>
>
>
>
>
> */** Progression factory for geometric series that calculates
> re-connection times */private double reconnectionProgressionFactor =
> 2.0; // default to [bounded] exponential*
> Any clarification on above factors will be really appreciated.
>
>
> [1] - https://docs.wso2.com/display/ESB500/JMS+Transport
> [2] - https://axis.apache.org/axis2/java/transports/jms.html
>
> Thank you.
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> 
> lean.enterprise.middleware
> Mobile: +94773375185
> Blog: dilshanilive.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Developer Studio Kernel 4.1.0. Released!

[Awanthika Senarath]

Hi all,

We are pleased to announce the release of *WSO2 Developer Studio Kernel
4.1.0.*

P2 repository of WSO2 developer Studio Kernel 4.1.0 is available here
.
Source
and Tag Location for this release is available here

.

Developer Studio 4.1.0 Kernel is released on Eclipse Mars (Eclipse 4.5)

Developer Studio Kernel contains a single feature which has the bundles
that are required to implement WSO2 Platform based tooling on Eclipse mars

   - Improvements to WSO2 Developer Studio updater Tool
   - Clear Separation of Eclipse based support for WSO2 Tooling
   - Eclipse migration to Eclipse Mars.


Regards
Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Output Schema generation for Data Mapper - Byte generated as String

[Nuwan Pallewela]

Hi Hariprasath,

Raw field holds a byte stream value. As the JSON Schema only have seven
primitive data types[1], I think current way of defining the type as String
is the correct way to represent it in the schema. That is because we are
not going to process this raw in the data mapper any way. We will only map
it's value into some field in the output message.
WDYT?

[1] http://json-schema.org/latest/json-schema-core.html#anchor8

Thanks,
Nuwan

On Wed, May 18, 2016 at 3:47 PM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:

> Hi Nuwan,
>
> I have attached the file that I used to create the output schema for
> listTheHistory method for Gmail REST connector.
>
> On Wed, May 18, 2016 at 3:42 PM, Nuwan Pallewela  wrote:
>
>> Hi Hariprasath,
>>
>> How did you generate the schema and what is the payload you used to
>> generate it?
>>
>> Thanks,
>> Nuwan
>>
>> On Wed, May 18, 2016 at 3:32 PM, Hariprasath Thanarajah <
>> haripras...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> Currently I am doing the schema generation for Gmail REST connector. In
>>> most of the methods in this connector have the response part as[1], But in
>>> the JSON schema the type was generated as string[2].
>>>
>>> Is there any way to generate as bytes or is it ok to proceed as below?
>>>
>>> [1] - {
>>>   "id": string,
>>>   "threadId": string,
>>>   "labelIds": [
>>> string
>>>   ],
>>>   "snippet": string,
>>>   "historyId": unsigned long,
>>>   "internalDate": long,
>>>   "payload": {
>>> "partId": string,
>>> "mimeType": string,
>>> "filename": string,
>>> "headers": [
>>>   {
>>> "name": string,
>>> "value": string
>>>   }
>>> ],
>>> "body": users.messages.attachments Resource,
>>> "parts": [
>>>   (MessagePart)
>>> ]
>>>   },
>>>   "sizeEstimate": integer,
>>>   "raw": bytes
>>> }
>>>
>>> [2] -
>>> {"id":"http:\/\/wso2jsonschema.org","title":"root","$schema":"http:\/\/
>>> json-schema.org
>>> \/draft-04\/schema#","properties":{"history":{"id":"http:\/\/
>>> wso2jsonschema.org\/history","items":[{"id":"http:\/\/wso2jsonschema.org
>>> \/history\/0","properties":{"id":{"id":"http:\/\/wso2jsonschema.org
>>> \/history\/0\/id","type":"number"},"labelsRemoved":{"id":"http:\/\/
>>> wso2jsonschema.org\/history\/0\/labelsRemoved","items":[{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0","properties":{"message":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message","properties":{
>>> "raw":{"id":"http:\/\/wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/raw","type":"string"
>>> },"id":{"id":"http:\/\/wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/id","type":"string"},"labelIds":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/labelIds","items":[{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/labelIds\/0","type":"string"}],"type":"array"},"threadId":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/threadId","type":"string"},"historyId":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/historyId","type":"string"},"payload":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/payload","properties":{"headers":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/payload\/headers","items":[{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/payload\/headers\/0","type":"object"}],"type":"array"},"body":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/payload\/body","properties":{"attachmentId":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/payload\/body\/attachmentId","type":"string"},"data":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/payload\/body\/data","type":"string"},"size":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/payload\/body\/size","type":"string"}},"type":"object"},"filename":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/payload\/filename","type":"string"},"parts":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts","items":[{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0","properties":{"headers":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers","items":[{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers\/0","properties":{"name":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers\/0\/name","type":"string"},"value":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> 

Re: [Dev] [App Cloud] Fronting microservice with HA Proxy

[Danushka Fernando]

By analyzing it further what I understand is netty server closes connection
while ha proxy trying to keep it alive. So best option for netty
server is option
http-server-close

AFAIU
by looking at descriptions. If no obligations we would use that as the
solution.

Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729

On Wed, May 18, 2016 at 1:33 PM, Danushka Fernando 
wrote:

> Sorry its option httpclose
> .
> But seems option http-server-close
> 
>  and option forceclose
> 
>  also
> works but I didnt tried them since we are focusing on keepalivee. I couldnt
> get keep alive working with any of the options.
>
> Thanks & Regards
> Danushka Fernando
> Senior Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>
> On Wed, May 18, 2016 at 1:29 PM, Danushka Fernando 
> wrote:
>
>> I tried several combination of options by looking at the descriptions.
>> But only thing worked for me for microservices is option
>> http-server-close
>> .
>> As mentioned before this seems a common issue when haproxy and netty are
>> together.
>>
>> Thanks & Regards
>> Danushka Fernando
>> Senior Software Engineer
>> WSO2 inc. http://wso2.com/
>> Mobile : +94716332729
>>
>> On Mon, May 16, 2016 at 11:32 PM, Manuranga Perera  wrote:
>>
>>> [2]
>>> https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#option%20prefer-last-server
>>>
>>> On Mon, May 16, 2016 at 1:59 PM, Manuranga Perera  wrote:
>>>
 KAL has the lowest latency on both the client and the server and in
> case of high request rate, it will be the fastest one. [1]


 So it seems we should aim for "keep alive" and fix the issues. Maybe
 you can try with [2] as it suggests.

 [1] https://www.haproxy.com/doc/aloha/7.0/haproxy/http_modes.html
 [2]
 https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#option
 prefer-last-server

 On Mon, May 16, 2016 at 11:41 AM, Danushka Fernando  wrote:

> Currently with HA proxy fronting microservice we are facing a
> connection reset exception [1]. Seems like this is a common issue with
> netty + haproxy. According to HA proxy manual[2] there are 5 connection
> modes. With connection mode "*httpclose*" I managed to get rid of the
> exception.
>
> From manual
> "In HTTP mode, the processing applied to requests and responses
> flowing over
>
> a connection depends in the combination of the frontend's HTTP options and
> the backend's. HAProxy supports 5 connection modes :
>
>   - KAL : keep alive ("option http-keep-alive 
> ")
>  which is the default mode : all
> requests and responses are processed, and connections remain open but 
> idle
> between responses and new requests.
>
>   - TUN: tunnel ("option http-tunnel 
> ")
>  : this was the default mode for versions
> 1.0 to 1.5-dev21 : only the first request and response are processed, 
> and
> everything else is forwarded with no analysis at all. This mode 
> should not
> be used as it creates lots of trouble with logging and HTTP 
> processing.
> *  - PCL: passive close ("option httpclose 
> ")
>  : exactly the same as tunnel mode,
> but with "Connection: close" appended in both directions to try to 
> make
> both ends close after the first request/response exchange.
> *
>   - SCL: server close ("option http-server-close 
> ")
>  : the server-facing
> connection is closed after the end of the response is received, but 
> the
> client-facing connection remains open.
>
>   - FCL: forced close ("option forceclose 
> ")
>  : the connection is actively closed
>
> after the end of the response."
>
> But there are few questions in hand.
>
>
>1. Is this the correct approach to solve the issue?
>2. If its correct then can we use the same connection mode 

Re: [Dev] Output Schema generation for Data Mapper - Byte generated as String

[Hariprasath Thanarajah]

Yes then it would be fine Nuwan and I'll proceed with this.

On Wed, May 18, 2016 at 4:43 PM, Nuwan Pallewela  wrote:

> Hi Hariprasath,
>
> Raw field holds a byte stream value. As the JSON Schema only have seven
> primitive data types[1], I think current way of defining the type as String
> is the correct way to represent it in the schema. That is because we are
> not going to process this raw in the data mapper any way. We will only map
> it's value into some field in the output message.
> WDYT?
>
> [1] http://json-schema.org/latest/json-schema-core.html#anchor8
>
> Thanks,
> Nuwan
>
> On Wed, May 18, 2016 at 3:47 PM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi Nuwan,
>>
>> I have attached the file that I used to create the output schema for
>> listTheHistory method for Gmail REST connector.
>>
>> On Wed, May 18, 2016 at 3:42 PM, Nuwan Pallewela  wrote:
>>
>>> Hi Hariprasath,
>>>
>>> How did you generate the schema and what is the payload you used to
>>> generate it?
>>>
>>> Thanks,
>>> Nuwan
>>>
>>> On Wed, May 18, 2016 at 3:32 PM, Hariprasath Thanarajah <
>>> haripras...@wso2.com> wrote:
>>>
 Hi All,

 Currently I am doing the schema generation for Gmail REST connector. In
 most of the methods in this connector have the response part as[1], But in
 the JSON schema the type was generated as string[2].

 Is there any way to generate as bytes or is it ok to proceed as below?

 [1] - {
   "id": string,
   "threadId": string,
   "labelIds": [
 string
   ],
   "snippet": string,
   "historyId": unsigned long,
   "internalDate": long,
   "payload": {
 "partId": string,
 "mimeType": string,
 "filename": string,
 "headers": [
   {
 "name": string,
 "value": string
   }
 ],
 "body": users.messages.attachments Resource,
 "parts": [
   (MessagePart)
 ]
   },
   "sizeEstimate": integer,
   "raw": bytes
 }

 [2] -
 {"id":"http:\/\/wso2jsonschema.org","title":"root","$schema":"http:\/\/
 json-schema.org
 \/draft-04\/schema#","properties":{"history":{"id":"http:\/\/
 wso2jsonschema.org\/history","items":[{"id":"http:\/\/
 wso2jsonschema.org\/history\/0","properties":{"id":{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/id","type":"number"},"labelsRemoved":{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved","items":[{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0","properties":{"message":{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message","properties":{
 "raw":{"id":"http:\/\/wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/raw","type":"string"
 },"id":{"id":"http:\/\/wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/id","type":"string"},"labelIds":{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/labelIds","items":[{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/labelIds\/0","type":"string"}],"type":"array"},"threadId":{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/threadId","type":"string"},"historyId":{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/historyId","type":"string"},"payload":{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/payload","properties":{"headers":{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/payload\/headers","items":[{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/payload\/headers\/0","type":"object"}],"type":"array"},"body":{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/payload\/body","properties":{"attachmentId":{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/payload\/body\/attachmentId","type":"string"},"data":{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/payload\/body\/data","type":"string"},"size":{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/payload\/body\/size","type":"string"}},"type":"object"},"filename":{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/payload\/filename","type":"string"},"parts":{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/payload\/parts","items":[{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0","properties":{"headers":{"id":"http:\/\/
 wso2jsonschema.org
 \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers","items":[{"id":"http:\/\/
 wso2jsonschema.org
 

Re: [Dev] [C5] [MB] Failed to initialize startup resolver

[Hemika Kodikara]

Hi All,

As Indika mentioned, we are getting the following error on MB startup.

osgi> 16:55:36.567 [Timer-0] ERROR
org.wso2.carbon.datasource.core.internal.DataSourceListenerComponent -
Error occurred while initializing data sources
org.wso2.carbon.datasource.core.exception.DataSourceException: Error in
initializing system data sources: Error in initializing data sources at
'/Users/hemikakodikara/mb/dev/350/product-mb/product/target/wso2mb-3.5.0-SNAPSHOT/conf/datasources/master-datasources.xml
- Need to specify class name in environment or system property, or as an
applet parameter, or in an application resource file:
 java.naming.factory.initial
at
org.wso2.carbon.datasource.core.DataSourceManager.initDataSources(DataSourceManager.java:142)
~[52:org.wso2.carbon.datasource.core:1.0.0.SNAPSHOT]
at
org.wso2.carbon.datasource.core.internal.DataSourceListenerComponent.onAllRequiredCapabilitiesAvailable(DataSourceListenerComponent.java:84)
[52:org.wso2.carbon.datasource.core:1.0.0.SNAPSHOT]
at
org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver.lambda$notifySatisfiableComponents$30(StartupOrderResolver.java:412)
[51:org.wso2.carbon.core:5.1.0.alpha2]
at
org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver$$Lambda$70/868365166.accept(Unknown
Source) [51:org.wso2.carbon.core:5.1.0.alpha2]
at java.util.ArrayList.forEach(ArrayList.java:1249) [?:?]
at
org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver.notifySatisfiableComponents(StartupOrderResolver.java:397)
[51:org.wso2.carbon.core:5.1.0.alpha2]
at
org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver.access$100(StartupOrderResolver.java:78)
[51:org.wso2.carbon.core:5.1.0.alpha2]
at
org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver$1.run(StartupOrderResolver.java:217)
[51:org.wso2.carbon.core:5.1.0.alpha2]
at java.util.TimerThread.mainLoop(Timer.java:555) [?:?]
at java.util.TimerThread.run(Timer.java:505) [?:?]
Caused by: org.wso2.carbon.datasource.core.exception.DataSourceException:
Error in initializing data sources at
'/Users/hemikakodikara/mb/dev/350/product-mb/product/target/wso2mb-3.5.0-SNAPSHOT/conf/datasources/master-datasources.xml
- Need to specify class name in environment or system property, or as an
applet parameter, or in an application resource file:
 java.naming.factory.initial
at
org.wso2.carbon.datasource.core.DataSourceManager.initDataSource(DataSourceManager.java:169)
~[?:?]
at
org.wso2.carbon.datasource.core.DataSourceManager.initDataSources(DataSourceManager.java:137)
~[?:?]
... 9 more
Caused by: javax.naming.NoInitialContextException: Need to specify class
name in environment or system property, or as an applet parameter, or in an
application resource file:  java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
~[?:?]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
~[?:?]
at
javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:350)
~[?:?]
at javax.naming.InitialContext.lookup(InitialContext.java:417) ~[?:?]
at
org.wso2.carbon.datasource.core.DataSourceJndiManager.lookupJNDISubContext(DataSourceJndiManager.java:135)
~[?:?]
at
org.wso2.carbon.datasource.core.DataSourceJndiManager.checkAndCreateJNDISubContexts(DataSourceJndiManager.java:115)
~[?:?]
at
org.wso2.carbon.datasource.core.DataSourceJndiManager.getBindingContext(DataSourceJndiManager.java:95)
~[?:?]
at
org.wso2.carbon.datasource.core.DataSourceJndiManager.register(DataSourceJndiManager.java:75)
~[?:?]
at
org.wso2.carbon.datasource.core.DataSourceJndiManager.register(DataSourceJndiManager.java:50)
~[?:?]
at
org.wso2.carbon.datasource.core.DataSourceManager.initDataSource(DataSourceManager.java:165)
~[?:?]
at
org.wso2.carbon.datasource.core.DataSourceManager.initDataSources(DataSourceManager.java:137)
~[?:?]
... 9 more


I went through some of the tests in carbon-datasources and noticed that the
following was added in master-datasources.xml file :


org.wso2.carbon.datasource.core.jndi.CustomContextFactory


It seems the issue is occurring because of the above configuration is not
available in MB master-datasources.xml. Do we need to implement a class
like "org.wso2.carbon.datasource.core.jndi.CustomContextFactory" ? Is it a
must have ?

Regards,
Hemika


Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com

Mobile : +9477762

On Wed, May 18, 2016 at 12:28 PM, Hemika Kodikara  wrote:

> Hi Sameera,
>
> I saw this "dependentComponentName" in the carbon.component tag in [1].
> May I know the purpose of it ? Best if you could add it to the blog :) .
> The blog is very understandable.
>
> [1] -
> https://github.com/wso2/msf4j/pull/169/files#diff-357e4854869b2e21c38b1b437f11095aR334
>
> Regards,
> Hemika
>
> Hemika Kodikara
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middleware
> http://wso2.com

Re: [Dev] Representing a JSON payload with null values - visual datamapper editor

[Nuwan Pallewela]

Hi Malaka,

Yes. We may have to refer api docs and find the expected value for those
optional fields and in the esb runtime data mapper engine should handle
them. But the engine is not implemented up-to that level yet. We should
handle these null-able fields.

Thanks,
Nuwan

On Wed, May 18, 2016 at 12:07 PM, Malaka Silva  wrote:

> Actually those are options for the given configuration. We don't really
> have a clear idea what are the optional response elements. (Unless we refer
> api docs)
>
> So I guess we can proceed with sample values.
>
> From datamapper mediator(ESB Side) level we need to handle if we receive a
> null value. Guess this is already considered?
>
> On Wed, May 18, 2016 at 12:02 PM, Sohani Weerasinghe 
> wrote:
>
>>
>>
>> Sohani Weerasinghe
>> Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>> On Wed, May 18, 2016 at 12:00 PM, Nuwan Pallewela 
>> wrote:
>>
>>> Hi All,
>>>
>>> @Vivekanathan : If we need to process/map any value in the payload
>>> though it is optional we have to know the type when generating the schema.
>>> So the sample pay load should not contain null values first place. We need
>>> to modify the sample payload with expected values so that in the schema
>>> generation we could set the type correctly for that field.
>>>
>>> @Sohani : +1 for the above mention approach in the schema generation.
>>> One small suggestion to remove the arrow head of type null elements to
>>> restrict users from mapping such elements.
>>>
>>
>> Will do.
>>
>>>
>>> Thanks,
>>> Nuwan
>>>
>>> On Wed, May 18, 2016 at 11:51 AM, Vivekananthan Sivanayagam <
>>> vivekanant...@wso2.com> wrote:
>>>
 Hi Sohani,

 Normally we are getting null value for optional parameter in the API
 response, suppose if we get the actual value for that json object , does
 this schema handle that case?





 *Thank youVivekananthan Sivanayagam*

 *Associate Software Engineer | WSO2*

 *E:vivekanant...@wso2.com *
 *M:+94752786138 <%2B94752786138>*

 On Wed, May 18, 2016 at 11:19 AM, Sohani Weerasinghe 
 wrote:

> Hi All,
>
> If a json payload has null values as shown below, how are we going to
> represent this in the json schema?
>
> {
>   "root": {
> "tasklist_id": "12345",
> "test"=null
> }
> }
>
> If we are serializing that value, then the generated schema and the
> tree view will be as follows
>
> {
>   "$schema" : "http://json-schema.org/draft-04/schema#;,
>   "id" : "http://wso2jsonschema.org;,
>   "title" : "root",
>   "type" : "object",
>   "properties" : {
> *"test" : {*
> *  "id" : "http://wso2jsonschema.org/test
> ",*
> *  "type" : "null"*
> *},*
> "tasklist_id" : {
>   "id" : "http://wso2jsonschema.org/tasklist_id;,
>   "type" : "string"
> }
>   }
> }
>
>
> ​
>
> Appreciate your input on this
>
> Thanks,
> Sohani
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>


>>>
>>>
>>> --
>>> --
>>>
>>> *Nuwan Chamara Pallewela*
>>>
>>>
>>> *Software Engineer*
>>>
>>> *WSO2, Inc. *http://wso2.com
>>> *lean . enterprise . middleware*
>>>
>>> Email   *nuw...@wso2.com *
>>> Mobile  *+94719079739 <%2B94719079739>@*
>>>
>>>
>>>
>>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> 
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Output Schema generation for Data Mapper - Byte generated as String

[Nuwan Pallewela]

Hi Hariprasath,

How did you generate the schema and what is the payload you used to
generate it?

Thanks,
Nuwan

On Wed, May 18, 2016 at 3:32 PM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:

> Hi All,
>
> Currently I am doing the schema generation for Gmail REST connector. In
> most of the methods in this connector have the response part as[1], But in
> the JSON schema the type was generated as string[2].
>
> Is there any way to generate as bytes or is it ok to proceed as below?
>
> [1] - {
>   "id": string,
>   "threadId": string,
>   "labelIds": [
> string
>   ],
>   "snippet": string,
>   "historyId": unsigned long,
>   "internalDate": long,
>   "payload": {
> "partId": string,
> "mimeType": string,
> "filename": string,
> "headers": [
>   {
> "name": string,
> "value": string
>   }
> ],
> "body": users.messages.attachments Resource,
> "parts": [
>   (MessagePart)
> ]
>   },
>   "sizeEstimate": integer,
>   "raw": bytes
> }
>
> [2] -
> {"id":"http:\/\/wso2jsonschema.org","title":"root","$schema":"http:\/\/
> json-schema.org
> \/draft-04\/schema#","properties":{"history":{"id":"http:\/\/
> wso2jsonschema.org\/history","items":[{"id":"http:\/\/wso2jsonschema.org
> \/history\/0","properties":{"id":{"id":"http:\/\/wso2jsonschema.org
> \/history\/0\/id","type":"number"},"labelsRemoved":{"id":"http:\/\/
> wso2jsonschema.org\/history\/0\/labelsRemoved","items":[{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0","properties":{"message":{"id":"http:\/\/
> wso2jsonschema.org\/history\/0\/labelsRemoved\/0\/message","properties":{
> "raw":{"id":"http:\/\/wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/raw","type":"string"
> },"id":{"id":"http:\/\/wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/id","type":"string"},"labelIds":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/labelIds","items":[{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/labelIds\/0","type":"string"}],"type":"array"},"threadId":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/threadId","type":"string"},"historyId":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/historyId","type":"string"},"payload":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload","properties":{"headers":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/headers","items":[{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/headers\/0","type":"object"}],"type":"array"},"body":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/body","properties":{"attachmentId":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/body\/attachmentId","type":"string"},"data":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/body\/data","type":"string"},"size":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/body\/size","type":"string"}},"type":"object"},"filename":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/filename","type":"string"},"parts":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts","items":[{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0","properties":{"headers":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers","items":[{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers\/0","properties":{"name":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers\/0\/name","type":"string"},"value":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers\/0\/value","type":"string"}},"type":"object"}],"type":"array"},"filename":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/filename","type":"string"},"partId":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/partId","type":"string"},"mimeType":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/mimeType","type":"string"}},"type":"object"}],"type":"array"},"partId":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/partId","type":"string"},"mimeType":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/mimeType","type":"string"}},"type":"object"},"sizeEstimate":{"id":"http:\/\/
> wso2jsonschema.org
> 

[Dev] Output Schema generation for Data Mapper - Byte generated as String

[Hariprasath Thanarajah]

Hi All,

Currently I am doing the schema generation for Gmail REST connector. In
most of the methods in this connector have the response part as[1], But in
the JSON schema the type was generated as string[2].

Is there any way to generate as bytes or is it ok to proceed as below?

[1] - {
  "id": string,
  "threadId": string,
  "labelIds": [
string
  ],
  "snippet": string,
  "historyId": unsigned long,
  "internalDate": long,
  "payload": {
"partId": string,
"mimeType": string,
"filename": string,
"headers": [
  {
"name": string,
"value": string
  }
],
"body": users.messages.attachments Resource,
"parts": [
  (MessagePart)
]
  },
  "sizeEstimate": integer,
  "raw": bytes
}

[2] -
{"id":"http:\/\/wso2jsonschema.org","title":"root","$schema":"http:\/\/
json-schema.org\/draft-04\/schema#","properties":{"history":{"id":"http:\/\/
wso2jsonschema.org\/history","items":[{"id":"http:\/\/wso2jsonschema.org
\/history\/0","properties":{"id":{"id":"http:\/\/wso2jsonschema.org
\/history\/0\/id","type":"number"},"labelsRemoved":{"id":"http:\/\/
wso2jsonschema.org\/history\/0\/labelsRemoved","items":[{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0","properties":{"message":{"id":"http:\/\/
wso2jsonschema.org\/history\/0\/labelsRemoved\/0\/message","properties":{
"raw":{"id":"http:\/\/wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/raw","type":"string"
},"id":{"id":"http:\/\/wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/id","type":"string"},"labelIds":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/labelIds","items":[{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/labelIds\/0","type":"string"}],"type":"array"},"threadId":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/threadId","type":"string"},"historyId":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/historyId","type":"string"},"payload":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload","properties":{"headers":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/headers","items":[{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/headers\/0","type":"object"}],"type":"array"},"body":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/body","properties":{"attachmentId":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/body\/attachmentId","type":"string"},"data":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/body\/data","type":"string"},"size":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/body\/size","type":"string"}},"type":"object"},"filename":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/filename","type":"string"},"parts":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/parts","items":[{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0","properties":{"headers":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers","items":[{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers\/0","properties":{"name":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers\/0\/name","type":"string"},"value":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers\/0\/value","type":"string"}},"type":"object"}],"type":"array"},"filename":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/filename","type":"string"},"partId":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/partId","type":"string"},"mimeType":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/mimeType","type":"string"}},"type":"object"}],"type":"array"},"partId":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/partId","type":"string"},"mimeType":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/payload\/mimeType","type":"string"}},"type":"object"},"sizeEstimate":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/sizeEstimate","type":"number"},"snippet":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/snippet","type":"string"},"internalDate":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/message\/internalDate","type":"string"}},"type":"object"},"labelIds":{"id":"http:\/\/
wso2jsonschema.org
\/history\/0\/labelsRemoved\/0\/labelIds","items":[{"id":"http:\/\/
wso2jsonschema.org

Re: [Dev] [App Cloud] Fronting microservice with HA Proxy

[Danushka Fernando]

Sorry its option httpclose
.
But seems option http-server-close

 and option forceclose

also
works but I didnt tried them since we are focusing on keepalivee. I couldnt
get keep alive working with any of the options.

Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729

On Wed, May 18, 2016 at 1:29 PM, Danushka Fernando 
wrote:

> I tried several combination of options by looking at the descriptions. But
> only thing worked for me for microservices is option http-server-close
> .
> As mentioned before this seems a common issue when haproxy and netty are
> together.
>
> Thanks & Regards
> Danushka Fernando
> Senior Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>
> On Mon, May 16, 2016 at 11:32 PM, Manuranga Perera  wrote:
>
>> [2]
>> https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#option%20prefer-last-server
>>
>> On Mon, May 16, 2016 at 1:59 PM, Manuranga Perera  wrote:
>>
>>> KAL has the lowest latency on both the client and the server and in case
 of high request rate, it will be the fastest one. [1]
>>>
>>>
>>> So it seems we should aim for "keep alive" and fix the issues. Maybe you
>>> can try with [2] as it suggests.
>>>
>>> [1] https://www.haproxy.com/doc/aloha/7.0/haproxy/http_modes.html
>>> [2] https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#option
>>> prefer-last-server
>>>
>>> On Mon, May 16, 2016 at 11:41 AM, Danushka Fernando 
>>> wrote:
>>>
 Currently with HA proxy fronting microservice we are facing a
 connection reset exception [1]. Seems like this is a common issue with
 netty + haproxy. According to HA proxy manual[2] there are 5 connection
 modes. With connection mode "*httpclose*" I managed to get rid of the
 exception.

 From manual
 "In HTTP mode, the processing applied to requests and responses
 flowing over

 a connection depends in the combination of the frontend's HTTP options and
 the backend's. HAProxy supports 5 connection modes :

   - KAL : keep alive ("option http-keep-alive 
 ")
  which is the default mode : all
 requests and responses are processed, and connections remain open but 
 idle
 between responses and new requests.

   - TUN: tunnel ("option http-tunnel 
 ")
  : this was the default mode for versions
 1.0 to 1.5-dev21 : only the first request and response are processed, 
 and
 everything else is forwarded with no analysis at all. This mode should 
 not
 be used as it creates lots of trouble with logging and HTTP processing.
 *  - PCL: passive close ("option httpclose 
 ")
  : exactly the same as tunnel mode,
 but with "Connection: close" appended in both directions to try to make
 both ends close after the first request/response exchange.
 *
   - SCL: server close ("option http-server-close 
 ")
  : the server-facing
 connection is closed after the end of the response is received, but the
 client-facing connection remains open.

   - FCL: forced close ("option forceclose 
 ")
  : the connection is actively closed

 after the end of the response."

 But there are few questions in hand.


1. Is this the correct approach to solve the issue?
2. If its correct then can we use the same connection mode for
other app types like tomcat and php as well?
3. Are there any better approaches we can take?


 Any input would be appriciated.

 [1] https://wso2.org/jira/browse/APPCLOUD-79
 [2] https://cbonte.github.io/haproxy-dconv/configuration-1.5.html

 Thanks & Regards
 Danushka Fernando
 Senior Software Engineer
 WSO2 inc. http://wso2.com/
 Mobile : +94716332729

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


>>>
>>>
>>> --
>>> With regards,
>>> *Manu*ranga Perera.
>>>
>>> phone : 071 7 70 20 50
>>> mail : m...@wso2.com

[Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"

[Dilshani Subasinghe]

Hi ESB Team,

When consider about "JMS connection factory parameters" [1] , user can
define "transport.jms.InitialReconnectDuration" parameter to give time
duration which will define initial reconnection time after broken JMS
connection.

But the given value will be multiply with 2. That 2 is coming from
"reconnectionProgressionFactor" which can be over ride by
"transport.jms.ReconnectProgressFactor" (Which is another jms connection
factory parameter).

ServiceTaskManager.java class will handle above function as follows:

   i









*f (reconnectDuration != null) {retryDuration =
reconnectDuration;log.error("Reconnection
attempt : " + (r++) + " for service : "
+serviceName + " failed. Next retry in
" + (retryDuration / 1000) +" seconds.
(Fixed Interval)");} else
{retryDuration = (long) (retryDuration *
reconnectionProgressionFactor);
log.error("Reconnection attempt : " + (r++) + " for service : "
+serviceName + " failed. Next retry in
" + (retryDuration / 1000) +"
seconds");*


There are two facts to clarify with above situation.

1. According to user perspective, it may be wrong to multiply the value
which is given by user.

Ex: User may add 10 seconds as initial retry interval, but ESB does it
within 20 seconds.

Note: When we add "transport.jms.ReconnectProgressFactor" in to axis2.xml,
it can be override.

*1*

2. Why we hard code *reconnectionProgressionFactor *as 2 ? Can we change it
or is it impossible because of the behavior of axis2 ?

As a suggestion, it will be better to add it as 1. (It may also solve the
problem discussed above step)





*/** Progression factory for geometric series that calculates re-connection
times */private double reconnectionProgressionFactor = 2.0; // default
to [bounded] exponential*
Any clarification on above factors will be really appreciated.


[1] - https://docs.wso2.com/display/ESB500/JMS+Transport
[2] - https://axis.apache.org/axis2/java/transports/jms.html

Thank you.

-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/

lean.enterprise.middleware
Mobile: +94773375185
Blog: dilshanilive.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Ruwan Abeykoon]

Hi Harsha,
Yes, I will create the fix for APIM and send the PR.

Cheers,
Ruwan

On Wed, May 18, 2016 at 11:56 AM, Harsha Kumara  wrote:

> Adding Bhathiya.
>
> We got same exception yesterday in APIM as well. We will need to same
> thing for DS as well.
>
> Thanks,
> Harsha
>
> On Wed, May 18, 2016 at 11:38 AM, Ruwan Abeykoon  wrote:
>
>> Thanks Tanya for the information. We will follow the same as in DS.
>>
>> On Wed, May 18, 2016 at 11:34 AM, Tanya Madurapperuma 
>> wrote:
>>
>>> Hi Ruwan,
>>>
>>> Usually this error is thrown as shindig is trying to load some google
>>> analytics apis. So when there is no internet connection this error can be
>>> observed.
>>> To get rid of this error we have to remove google related stuff from
>>> shindig features.txt file
>>>
>>> *features-extras/analytics/feature.xml*
>>> *features-extras/com.google.gadgets.analytics/feature.xml*
>>>
>>> But since we don't maintain a shindig fork, we can't do this from
>>> carbon-dashboards level. So in the Dashboard Server level we are replacing
>>> the features.txt file with a file which doesn't have above 2 entries [1].
>>> We'll have to do the same for apim analytics as well.
>>>
>>> [1]
>>> https://github.com/wso2/product-ds/commit/2d763ce1d9f5362d559e9d46eb0bcedf1446ee9e
>>>
>>> Thanks,
>>> Tanya
>>>
>>> On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon 
>>> wrote:
>>>
 Hi DS team,
 I am getting the following error in APIM 2.0.0-SNAPSHOT which integrate
 DS features. Any Idea why? can we not print those errors due to outside
 dependencies?

 ---

 achines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libinstrument.dylib. One
 of the two will be used. Which one is undefined.

 [2016-05-17 17:35:49,176]  INFO - FeatureRegistry Resources from
 res:features/features.txt are loading.

 [2016-05-17 17:35:49,186]  INFO - XmlUtil The XML processor being used
 does not support secure parsing.

 [2016-05-17 17:35:49,187]  INFO - XmlUtil Document builders are being
 reused.

 [2016-05-17 17:35:49,396]  INFO - FeatureRegistry Resources from
 res:features-extras/features.txt are loading.

 [2016-05-17 17:36:11,707]  INFO - CarbonEventManagementService Starting
 polling event receivers

 [2016-05-17 17:36:19,510]  INFO - BasicHttpFetcher The following
 exception occurred when fetching
 http://www.google-analytics.com/urchin.js: 30,103 ms elapsed.

 [2016-05-17 17:36:19,511]  INFO - BasicHttpFetcher

 org.apache.http.conn.ConnectTimeoutException: Connect to
 www.google-analytics.com:80 timed out

 at
 org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)

 at
 org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)

 at
 org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)

 at
 org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)

 at
 org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)

 at
 org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)

 at
 org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)

 at
 org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:115)

 at
 org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)

 at
 org.apache.shindig.gadgets.http.BasicHttpFetcher.fetch(BasicHttpFetcher.java:359)

 at
 org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.getContent(FeatureResourceLoader.java:291)

 at
 org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.(FeatureResourceLoader.java:270)

 at
 org.apache.shindig.gadgets.features.FeatureResourceLoader$UriResource.(FeatureResourceLoader.java:256)

 at
 org.apache.shindig.gadgets.features.FeatureResourceLoader.loadUri(FeatureResourceLoader.java:135)

 at
 org.apache.shindig.gadgets.features.FeatureResourceLoader.load(FeatureResourceLoader.java:88)

 at
 org.apache.shindig.gadgets.features.FeatureRegistry.loadFeature(FeatureRegistry.java:486)

 at
 org.apache.shindig.gadgets.features.FeatureRegistry.loadResources(FeatureRegistry.java:425)

 at
 org.apache.shindig.gadgets.features.FeatureRegistry.register(FeatureRegistry.java:180)

 at
 org.apache.shindig.gadgets.features.FeatureRegistry.(FeatureRegistry.java:112)

 at
 org.apache.shindig.gadgets.features.FeatureRegistry.(FeatureRegistry.java:99)

 at
 

Re: [Dev] [ESB][JMS] Documentation - missing main user scenarios and proper clarification on configuration

[Nisrin Sheriff]

Thank you for the information Dilshani.

I will check with the ESB/MB teams on what you have mentioned with regards
to doc bugs/improvements and fix those.

Best Regards,
Nisrin



Nisrin Sheriff
Senior Technical Writer

*WSO2, Inc.*lean.enterprise.middleware.
mobile: +94 776 24 84 56
http://wso2.com

On Mon, May 16, 2016 at 10:09 AM, Dilshani Subasinghe 
wrote:

> Adding Chanaka
>
> On Mon, May 16, 2016 at 8:55 AM, Dilshani Subasinghe 
> wrote:
>
>> Hi all,
>>
>> Currently I am testing JMS transport parameters of ESB 5.0.0 alpha pack
>> with MB 3.1.0 as the broker. While testing that, identified following
>> factors:
>>
>>- As the JMS receiver, ESB can use proxy and inbound endpoints.
>>- While using jms transport within proxy, that will always pick up
>>default parameters defined with in axis2.xml.
>>
>> While enabling jms transport for ESB, have to uncomment following
>> fragments:
>>
>> > class="org.apache.axis2.transport.jms.JMSListener">
>> 
>> > locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory
>> > locked="false">repository/conf/jndi.properties
>> > locked="false">TopicConnectionFactory parameter>
>> > locked="false">topic
>> 
>>
>> 
>> > locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory
>> > locked="false">repository/conf/jndi.properties
>> > locked="false">QueueConnectionFactory
>>> locked="false">queue
>> 
>>
>>
>>
>>
>>
>>
>> *> name="java.naming.factory.initial"
>> locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory
>> > locked="false">repository/conf/jndi.properties
>> > locked="false">QueueConnectionFactory> name="transport.jms.ConnectionFactoryType"
>> locked="false">queue*
>> 
>>
>> But enabling jms transaction only consider about "default" parameters.
>>
>>- With above scenario, *user may cannot listen to topic and queue
>>within one ESB instance.*
>>- As a further identification, found the article [2] which will
>>address above scenario with a proper solution. Within that article, user
>>have to add extra parameters to override default configurations.
>>
>> 
>>  
>>  contentType
>>  application/xml
>>  
>>  
>>  > name="transport.jms.ConnectionFactory">myQueueConnectionFactory
>>  myQueue
>>  queue
>>
>>- With these configuration, it can successfully achieve the use case
>>of listening to both topic and queue within one ESB instance.
>>
>> 1. Is there any other method to fulfill above user requirement ?
>>
>> 2. When considering documentation noticed following bugs and improvements:
>>
>>- Docs were not clearly identified enabling jms transport in proxy [1]
>>- Docs didn't mention about way of addressing above scenario and the
>>need of adding exact parameters for axis2.xml [4]
>>
>> If above mention method is the only one to achieve the scenario, it may
>> have to update docs properly. Added document jira for required
>> modifications [5].
>>
>> @ESB/MB Team - Please correct me if I have any misunderstanding about the
>> flow or functionality of features.
>> [1] https://docs.wso2.com/display/ESB500/JMS+Transport
>> [2]
>> http://wso2.com/library/articles/2013/03/configuring-wso2-esb-wso2-message-broker/
>> [3] https://docs.wso2.com/display/ESB470/Proxy+Services
>> [4]
>> https://docs.wso2.com/display/ESB500/Configure+with+WSO2+Message+Broker
>>
>> Thank you.
>>
>> --
>> Best Regards,
>>
>> Dilshani Subasinghe
>> Software Engineer - QA
>> WSO2, Inc.;http://wso2.com/
>> 
>> lean.enterprise.middleware
>> Mobile: +94773375185
>> Blog: dilshanilive.blogspot.com
>>
>
>
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> 
> lean.enterprise.middleware
> Mobile: +94773375185
> Blog: dilshanilive.blogspot.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

[Willian Antunes]

By the way I believe we could talk directly from the LDAP Connector JIRA
issue  instead from here or use
the pull request that I requested from GitHub
, so we can
keep the history of it from one place.

On Wed, May 18, 2016 at 1:41 PM, Willian Antunes <
willian.lima.antu...@gmail.com> wrote:

> Vivekananthan,
>
> Did you see what happened during the communication process? If didn't try
> to install an sniffer like Wireshark to understand which error the LDAP
> server sent to you.
>
> There are two scenarios which you can use to test:
>
> 1 - Set *secureConnection* and *disableSSLCertificateChecking both as
> true* in order to use a SSL port and ignore the certificate provided by
> the LDAP server.
> 2 - Set *secureConnection* *as* *true* and *disableSSLCertificateChecking
> as* *false* in order to use a SSL port and to validate the certificate
> provided by the LDAP server. You have to make sure you have the ROOT CA was
> imported in your OS which was used to sign the LDAP certificate, if you
> don't then the connection will fail. Try to use an sniffer to understand
> what is happening.
>
> Important: Does not make sense to configure secureConnection as false
> and disableSSLCertificateChecking as true because you're not using a secure
> port like 636.
>
> If you have any doubt please contact me!
>
> Regards,
> Antunes
>
> On Wed, May 18, 2016 at 4:05 AM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> Hi Malaka,
>>
>> I am working on that and still I have a problem in configure LDAP with
>> SSL connection. Without SSL connection, the connector is working and
>> according to the his changes, the SearchEntry method is working
>> with onlyOneReference parameter. I need to check in SSL connection part.
>>
>> I configured in ubuntu and I could not connect LDAP over SSL connection.
>> When I configure with port 636,it shows "ldap_result: Can't contact LDAP
>> server (-1)" error.
>>
>>
>>
>>
>>
>> *Thank youVivekananthan Sivanayagam*
>>
>> *Associate Software Engineer | WSO2*
>>
>> *E:vivekanant...@wso2.com *
>> *M:+94752786138 <%2B94752786138>*
>>
>> On Wed, May 18, 2016 at 9:22 AM, Malaka Silva  wrote:
>>
>>> Hi Vivekananthan,
>>>
>>> Please update the progress please?
>>>
>>> Shakila went through some of the methods in this connector. The
>>> description for parameters are not added in all templates. This is not the
>>> standard that we followed so far.
>>>
>>> On Sat, May 7, 2016 at 3:26 PM, Rajjaz Mohammed  wrote:
>>>
 Hi Willian,

 Sorry for the missing headers. I edited the files from Developer
> Studio, it erases the XML file to a new one every time you open it. So 
> even
> when a comment is inserted, the file will be erased again in the design
> view.
>


 I will look on that and update.

 --
 Thank you
 Best Regards

 *Rajjaz HM*
 Associate Software Engineer
 Platform Extension Team
 WSO2 Inc. 
 lean | enterprise | middleware
 Mobile | +94752833834|+94777226874
 Email   | raj...@wso2.com
 LinkedIn  | Blogger
  | WSO2 Profile
 

>>>
>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>> Malaka Silva
>>> Senior Tech Lead
>>> M: +94 777 219 791
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>> Skype : malaka.sampath.silva
>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>> Blog : http://mrmalakasilva.blogspot.com/
>>>
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> http://www.wso2.com/
>>> http://www.wso2.com/about/team/malaka-silva/
>>> 
>>> https://store.wso2.com/store/
>>>
>>> Save a tree -Conserve nature & Save the world for your future. Print
>>> this email only if it is absolutely necessary.
>>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

[Vivekananthan Sivanayagam]

Hi willian Antunes,

Thank you for more details, I am looking on that.




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com *
*M:+94752786138*

On Wed, May 18, 2016 at 7:53 PM, Willian Antunes <
willian.lima.antu...@gmail.com> wrote:

> By the way I believe we could talk directly from the LDAP Connector JIRA
> issue  instead from here or
> use the pull request that I requested from GitHub
> , so we can
> keep the history of it from one place.
>
> On Wed, May 18, 2016 at 1:41 PM, Willian Antunes <
> willian.lima.antu...@gmail.com> wrote:
>
>> Vivekananthan,
>>
>> Did you see what happened during the communication process? If didn't try
>> to install an sniffer like Wireshark to understand which error the LDAP
>> server sent to you.
>>
>> There are two scenarios which you can use to test:
>>
>> 1 - Set *secureConnection* and *disableSSLCertificateChecking both as
>> true* in order to use a SSL port and ignore the certificate provided by
>> the LDAP server.
>> 2 - Set *secureConnection* *as* *true* and *disableSSLCertificateChecking
>> as* *false* in order to use a SSL port and to validate the certificate
>> provided by the LDAP server. You have to make sure you have the ROOT CA was
>> imported in your OS which was used to sign the LDAP certificate, if you
>> don't then the connection will fail. Try to use an sniffer to understand
>> what is happening.
>>
>> Important: Does not make sense to configure secureConnection as false
>> and disableSSLCertificateChecking as true because you're not using a secure
>> port like 636.
>>
>> If you have any doubt please contact me!
>>
>> Regards,
>> Antunes
>>
>> On Wed, May 18, 2016 at 4:05 AM, Vivekananthan Sivanayagam <
>> vivekanant...@wso2.com> wrote:
>>
>>> Hi Malaka,
>>>
>>> I am working on that and still I have a problem in configure LDAP with
>>> SSL connection. Without SSL connection, the connector is working and
>>> according to the his changes, the SearchEntry method is working
>>> with onlyOneReference parameter. I need to check in SSL connection part.
>>>
>>> I configured in ubuntu and I could not connect LDAP over SSL connection.
>>> When I configure with port 636,it shows "ldap_result: Can't contact LDAP
>>> server (-1)" error.
>>>
>>>
>>>
>>>
>>>
>>> *Thank youVivekananthan Sivanayagam*
>>>
>>> *Associate Software Engineer | WSO2*
>>>
>>> *E:vivekanant...@wso2.com *
>>> *M:+94752786138 <%2B94752786138>*
>>>
>>> On Wed, May 18, 2016 at 9:22 AM, Malaka Silva  wrote:
>>>
 Hi Vivekananthan,

 Please update the progress please?

 Shakila went through some of the methods in this connector. The
 description for parameters are not added in all templates. This is not the
 standard that we followed so far.

 On Sat, May 7, 2016 at 3:26 PM, Rajjaz Mohammed 
 wrote:

> Hi Willian,
>
> Sorry for the missing headers. I edited the files from Developer
>> Studio, it erases the XML file to a new one every time you open it. So 
>> even
>> when a comment is inserted, the file will be erased again in the design
>> view.
>>
>
>
> I will look on that and update.
>
> --
> Thank you
> Best Regards
>
> *Rajjaz HM*
> Associate Software Engineer
> Platform Extension Team
> WSO2 Inc. 
> lean | enterprise | middleware
> Mobile | +94752833834|+94777226874
> Email   | raj...@wso2.com
> LinkedIn  | Blogger
>  | WSO2 Profile
> 
>



 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 
 https://store.wso2.com/store/

 Save a tree -Conserve nature & Save the world for your future. Print
 this email only if it is absolutely necessary.

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

Re: [Dev] [C5] [MB] Failed to initialize startup resolver

[Sameera Jayasoma]

Hi Hemika,

Thanks ;)

This attribute can be used to declare indirect dependencies to a particular
component. I will put a detailed explanation to the blog soon.

Thanks,
Sameera.

On Wed, May 18, 2016 at 12:28 PM, Hemika Kodikara  wrote:

> Hi Sameera,
>
> I saw this "dependentComponentName" in the carbon.component tag in [1].
> May I know the purpose of it ? Best if you could add it to the blog :) .
> The blog is very understandable.
>
> [1] -
> https://github.com/wso2/msf4j/pull/169/files#diff-357e4854869b2e21c38b1b437f11095aR334
>
> Regards,
> Hemika
>
> Hemika Kodikara
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middleware
> http://wso2.com
>
> Mobile : +9477762
>
> On Fri, May 13, 2016 at 4:56 PM, Sameera Jayasoma 
> wrote:
>
>> Refer the following article to get information about the new syntax.
>>
>>
>> https://medium.com/@sameera.jayasoma/resolving-startup-order-of-carbon-components-in-wso2-carbon-5-0-0-497fe3287e67
>>
>> On Fri, May 13, 2016 at 4:26 PM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Hemika,
>>>
>>> The startup resolver changes compatible to kernel 5.1.0-alpha2 is
>>> available in the master branch (PR [1]) of carbon-datasources. The
>>> carbon-datasources 1.0.0-alpha depends on the older format.
>>>
>>> [1] - https://github.com/wso2/carbon-datasources/pull/14
>>>
>>> Regards,
>>> Nira
>>>
>>> On Fri, May 13, 2016 at 4:22 PM, Hemika Kodikara 
>>> wrote:
>>>
 Thanks for the response. I have changed the kernel version to
 5.1.0-alpha2 as mentioned. The earlier error is not coming. But I am
 getting the following error. Seems like its coming from carbon-datasources.
 I checked this with m1 version and also alpha version for datasources.

 =
 [2016-05-13 15:16:04,974] ERROR {org.wso2.carbon.core} - FrameworkEvent
 ERROR - org.wso2.carbon.core
 org.wso2.carbon.kernel.internal.startupresolver.StartOrderResolverException:
 componentName value is missing in the services registered with the key
 org.wso2.carbon.kernel.startupresolver.RequiredCapabilityListener,
 implementation class name is
 org.wso2.carbon.datasource.core.internal.DataSourceListenerComponent
 at
 org.wso2.carbon.kernel.internal.startupresolver.OSGiServiceCapabilityTracker$CapabilityServiceTrackerCustomizer.addingService(OSGiServiceCapabilityTracker.java:142)
 at
 org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
 at
 org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)
 at
 org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
 at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
 at
 org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:901)
 at
 org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:109)
 at
 org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:914)
 at
 org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
 at
 org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:862)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:801)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:127)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:225)
 at
 org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:464)
 at
 org.eclipse.equinox.internal.ds.InstanceProcess.registerService(InstanceProcess.java:536)
 at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:213)
 at
 org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:473)
 at
 org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:217)
 at
 org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:816)
 at
 org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:783)
 at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
 at
 org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)

 ==

 Regards,
 Hemika


 Hemika Kodikara
 Software Engineer
 WSO2 Inc.
 lean . enterprise . middleware
 http://wso2.com

 Mobile : +9477762

 On Fri, May 13, 2016 at 3:00 PM, Niranjan Karunanandham <
 

[Dev] [DEV][Vote] Release WSO2 Puppet Modules 2.0.0

[Chamila De Alwis]

Hi,


This is the first release candidate (RC1) for WSO2 Puppet Modules 2.0.0.
Please download, verify, and vote. Voting will be open for 72 hours.

[ ] Broken - Do not release (explain why)

[ ] Stable - Go ahead and release

Main features and fixes released with this release:

   -

   Updated Hiera data hierarchy to include deployment Platform
   -

   Kubernetes based workflow supported, based on wso2/kubernetes-artifacts
   -

   system_file_list to copy files with scope outside of CARBON_HOME
   -

   Platform specific configuration data sets for Kubernetes
   -

  Kubernetes deployment-ready Puppet modules
  -

  Data sources matching a distributed set of Kubernetes MySQL Services
  -

   Streamlined Default platform YAML configuration data
   -

   Optional update flags to control product pack and JDK cleanup
   -

   Minor fixes on the Hiera data
   -

  Issues in YAML file formatting
  -

  Puppet templates for identity.xml added to relevant products
  -

  Proxy Port values assigned to different products are streamlined
  -

  Hostname entries streamlined in default deployment platform data set
  -

  Pass Through Port Mapping for WSO2 ESB
  -

  Fixing Thrift Server IP configuration for WSO2 MB
  -

  SecureVault parameters made optional
  -

  Reusing Data Source related fields in YAML by inheriting from
  wso2/common.yaml
  -

  Fix Symbolic Link creation in WSO2 DAS
  -

  Fixed installation directory creation failure when parent directory
  doesn’t exist
  -

  Removed use of Kubernetes Master details in Clustering templates
  -

  Streamlined use of hiera, hiera_array, and hiera_hash lookup
  -

   WSO2 API Manager Gateway Manager-Worker separate profiles in Hieradata
   -

   WSO2 PPaaS Puppet module and Hiera data removed
   -

   Deprecated older product versions
   -

  WSO2 AM 1.9.1
  -

  WSO2 BRS 2.1.0
  -

  WSO2 GREG 4.6.0
  -

  WSO2 IS 5.0.0
  -

  WSO2 MB 3.0.0
  -

   Improve Puppet Vagrant setup to use PUPPET_HOME environment variable
   -

   Included sample config.yaml files in the Puppet Vagrant setup to quickly
   test standalone and distributed deployments
   -

   Fixed Java System Prefs location issue
   -

   Included YAML Style Guide for Hiera data files



This release is based on the following tag:

https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1

Release verification guide can be found at:

https://docs.wso2.com/display/PM200/Setting+up+the+Development+Environment

Source and distribution packages can be downloaded at:

https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1


Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [OAuth] Error happens in EMM intermittently

[Kamidu Punchihewa]

Hi Kasun,

Please follow the mail thread "*[DEV][IS] Getting an Unique index or
primary key violation exception*".
Discussion related to the above intermittent issue was conducted earlier in
the above mail thread.

Thanks and Best Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.

On Wed, May 18, 2016 at 10:47 AM, Kasun Dananjaya Delgolla 
wrote:

> Hi All,
>
> We're getting the following error in the EMM intermittently. Any idea why
> this happens?
>
> [2016-05-18 10:13:25,673] ERROR
> {org.wso2.carbon.identity.oauth2.OAuth2Service} -  Error occurred while
> issuing the access token for Client ID : pXPA6a6U9T047rd6vneb4NWtTfUa, User
> ID null, Scope : [PRODUCTION] and Grant Type : refresh_token
> org.wso2.carbon.identity.oauth2.IdentityOAuth2Exception: Error when
> storing the access token for consumer key : pXPA6a6U9T047rd6vneb4NWtTfUa
> at
> org.wso2.carbon.identity.oauth2.dao.TokenMgtDAO.storeAccessToken(TokenMgtDAO.java:246)
> at
> org.wso2.carbon.identity.oauth2.dao.TokenMgtDAO.invalidateAndCreateNewToken(TokenMgtDAO.java:1085)
> at
> org.wso2.carbon.identity.oauth2.token.handlers.grant.RefreshGrantHandler.issue(RefreshGrantHandler.java:259)
> at
> org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.issue(AccessTokenIssuer.java:196)
> at
> org.wso2.carbon.identity.oauth2.OAuth2Service.issueAccessToken(OAuth2Service.java:196)
> at
> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.getAccessToken(OAuth2TokenEndpoint.java:245)
> at
> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:111)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:188)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104)
> 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.doPost(AbstractHTTPServlet.java:209)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
> 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.wso2.carbon.ui.filters.CSRFPreventionFilter.doFilter(CSRFPreventionFilter.java:88)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
>