date:20170630

[Dev] net.sf.saxon.om.NamePool$NamePoolLimitException: NamePool limit exceeded:

2017-06-30 Thread Júnior

Hello,

I am facing this exception when doing XQuery or XSLT transformation:


net.sf.saxon.om.NamePool$NamePoolLimitException: NamePool limit exceeded:



Does anyone knows a workaround for this?

Thanks,
-- 
Francisco Ribeiro
*SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.17 RC1

2017-06-30 Thread Rushmin Fernando

Hi,

We ran integration tests for WSO2 Identity Server and manually tested basic
user management functionality.

[x] stable - Go ahead and release


On Fri, Jun 30, 2017 at 1:52 PM, Vinod Kavinda  wrote:

> Hi,
> I have tested Wso2 EI with the staged repo.
>
> [x] stable - Go ahead and release
>
> Regards,
> Vinod
>
> On Thu, Jun 29, 2017 at 3:36 PM, Chandana Napagoda 
> wrote:
>
>> Hi Devs,
>>
>> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.17.
>>
>> This release fixes the following issues
>> https://github.com/wso2/carbon-kernel/milestone/15?closed=1
>>
>> Please test your products with kernel 4.4.17 RC1 and vote. The vote will
>> be open for 72 hours or as longer as needed.
>>
>> Maven staging repository
>> https://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1177/
>>
>> The tag to be voted upon :
>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.17-rc1
>>
>> [ ] Broken - Do not release (explain why)
>> [ ] Stable  - Go ahead and release
>>
>> Thank you
>> Platform Team
>>
>> --
>> *Chandana Napagoda*
>> Associate Technical Lead
>> WSO2 Inc. - http://wso2.org
>>
>> *Email  :  chand...@wso2.com **Mobile : +94718169299
>> <+94%2071%20816%209299>*
>>
>> *Blog  :http://cnapagoda.blogspot.com 
>> | http://chandana.napagoda.com *
>>
>> *Linkedin : http://www.linkedin.com/in/chandananapagoda
>> *
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Vinod Kavinda
> Senior Software Engineer
> *WSO2 Inc. - lean . enterprise . middleware .*
> Mobile : +94 (0) 712 415544
> Blog : http://soatechflicks.blogspot.com/
> [image: http://wso2.com/signature]
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Best Regards*

*Rushmin Fernando*
*Technical Lead*

WSO2 Inc.  - Lean . Enterprise . Middleware

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

Re: [Dev] WSO2 Committers += Yasima Dewmini

2017-06-30 Thread Chamalee De Silva

Congratulations Yasima 




On Fri, Jun 30, 2017 at 3:03 PM, Harsha Kumara  wrote:

> Congratulations!
>
> On Fri, Jun 30, 2017 at 1:41 PM, Tharindu Dharmarathna  > wrote:
>
>> Congratulations Yasima!
>>
>>
>> On Fri, Jun 30, 2017 at 1:31 PM, Roshan Wijesena  wrote:
>>
>>> Congratulations Yasima!
>>>
>>> On Fri, Jun 30, 2017 at 1:20 PM, Sanjeewa Malalgoda 
>>> wrote:
>>>
 Hi All,
 It's my pleasure to welcome  Yasima Dewmini  as a WSO2 Committer.

 Yasima  has been a valuable contributor to the WSO2 API Manager team.
 In recognition of her contribution, dedication, and commitment she has been
 voted as a WSO2 committer.

 Yasima, Congratulations and keep up the good work!

 Thank You,
 sanjeewa.
 --

 *Sanjeewa Malalgoda*
 WSO2 Inc.
 Mobile : +94713068779 <+94%2071%20306%208779>

 blog
 :http://sanjeewamalalgoda.blogspot.com/
 



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


>>>
>>>
>>> --
>>> Roshan Wijesena.
>>> Senior Software Engineer-WSO2 Inc.
>>> Mobile: *+94719154640 <+94%2071%20915%204640>*
>>> Email: ros...@wso2.com
>>> *WSO2, Inc. :** wso2.com *
>>> lean.enterprise.middleware.
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Tharindu Dharmarathna*Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94779109091 <+94%2077%20910%209091>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618 <+94%2077%20550%205618>
> Blog:harshcreationz.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] EI 6.1.1 - Dev studio mediator project issues

2017-06-30 Thread Sohani Weerasinghe

Hi Kasun,

This is fixed at [1] and will be available in the next EI tooling release

[1]
https://github.com/wso2/devstudio-tooling-esb/commit/22efa173652adf1259588debfb1411667f4c4272

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

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

On Thu, Jun 29, 2017 at 11:15 AM, Sohani Weerasinghe 
wrote:

>
>
> Thanks,
> Sohani Weerasinghe
> Senior Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774 <071%20643%209774>
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Thu, Jun 29, 2017 at 11:00 AM, Isuru Udana  wrote:
>
>> Hi Sohani,
>>
>> We also need to include axis2 kernel (this is to get access to axis2
>> message context)
>>
>
> Thanks Isuru, will test and add that as well.
>
>>
>> Thanks.
>>
>> On Thu, Jun 29, 2017 at 10:45 AM, Sohani Weerasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> Based on the offline discussion had with Vijitha, shall we only have 
>>> synapse-core
>>> (the latest version 2.1.7-wso2v15) and commons-logging?
>>>
>>>   
>>>   commons-logging
>>>   commons-logging
>>>   1.1.1
>>> 
>>> 
>>>   org.apache.synapse
>>>   synapse-core
>>>   2.1.7-wso2v15
>>> 
>>>
>>> Please confirm.
>>>
>>>
>>> Thanks,
>>> Sohani Weerasinghe
>>> Senior Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774 <071%20643%209774>
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>> On Wed, Jun 28, 2017 at 8:31 AM, Sohani Weerasinghe 
>>> wrote:
>>>
 Reported the issue at [1] and will work on fixing it

 [1] https://wso2.org/jira/browse/DEVTOOLEI-1117

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

 Mobile  : +94 716439774 <071%20643%209774>
 Blog :http://christinetechtips.blogspot.com/
 Twitter  : https://twitter.com/sohanichristine

 On Wed, Jun 28, 2017 at 8:15 AM, Sohani Weerasinghe 
 wrote:

> Hi Kasun,
>
> Sure. will have a look
>
>
> Thanks,
> Sohani Weerasinghe
> Senior Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774 <071%20643%209774>
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Wed, Jun 28, 2017 at 12:04 AM, Kasun Indrasiri 
> wrote:
>
>> Hi,
>>
>> When creating the mediator project, there are a bunch of unnecessary
>> dependencies added to pom and most of the dependencies are way too old. 
>> Can
>> we please review this and fix, please.
>>
>>
>>
>>   
>> 
>>   commons-codec.wso2
>>   commons-codec
>>   1.4.0.wso2v1
>> 
>> 
>>   org.apache.httpcomponents.wso2
>>   httpcore
>>   4.3.3.wso2v1
>> 
>> 
>>   org.apache.woden.wso2
>>   woden
>>   1.0.0.M9-wso2v1
>> 
>> 
>>   org.wso2.orbit.commons-httpclient
>>   commons-httpclient
>>   3.1.0.wso2v3
>> 
>> 
>>   wsdl4j.wso2
>>   wsdl4j
>>   1.6.2.wso2v4
>> 
>> 
>>   commons-logging
>>   commons-logging
>>   1.1.1
>> 
>> 
>>   commons-io.wso2
>>   commons-io
>>   2.4.0.wso2v1
>> 
>> 
>>   org.apache.synapse
>>   synapse-core
>>   2.1.7-wso2v7
>> 
>> 
>>   org.apache.ws.commons.schema.wso2
>>   XmlSchema
>>   1.4.7.wso2v3
>> 
>> 
>>   org.apache.geronimo.specs.wso2
>>   geronimo-stax-api_1.0_spec
>>   1.0.1.wso2v2
>> 
>> 
>>   org.wso2.orbit.org.apache.neethi
>>   neethi
>>   2.0.4.wso2v5
>> 
>>   
>>
>> --
>> Kasun Indrasiri
>> Director - Integration Architecture
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +1 650 450 2293 <+1%20650-450-2293>
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>

>>>
>>
>>
>> --
>> *Isuru Udana*
>> Senior Technical Lead
>> WSO2 Inc.; http://wso2.com
>> email: isu...@wso2.com cell: +94 77 3791887 <077%20379%201887>
>> blog: http://mytecheye.blogspot.com/
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

2017-06-30 Thread Anuruddha Liyanarachchi

Hi Dileepa,

Your mysql connector jar is different than what puppet is trying to copy.
Rename your mysql jar to mysql-connector-java-5.1.36-bin.jar.

mysql-connector-java-5.1.36.jar != mysql-connector-java-5.1.36-bin.jar


On Fri, Jun 30, 2017 at 12:57 PM, Dileepa Jayakody <
dileepajayak...@gmail.com> wrote:

> Hi Pubudu,
>
> Thanks. Checking out v1.0.0 from puppet-base resolved above error.
> However, I'm getting a new error, related to the mysql jar file.
>
> Notice: /Stage[main]/Wso2base::Configure/Wso2base::Push_
> templates[repository/conf/carbon.xml]/File[/mnt/wso2am-
> 2.1.0/repository/conf/carbon.xml]/content: content changed '{md5}
> 5c92af40d406b3368ceafd3b582017bd' to '{md5}326757437935bb13c3d71d8ae692d0
> 4b'
> Error: /Stage[main]/Wso2base::Configure/Wso2base::Push_
> files[repository/components/lib/mysql-connector-java-5.1.
> 36-bin.jar]/File[/mnt/wso2am-2.1.0/repository/components/
> lib/mysql-connector-java-5.1.36-bin.jar]: Could not evaluate: Could not
> retrieve information from environment production source(s)
> puppet:///modules/wso2am_runtime/configs/repository/components/lib/mysql-connector-java-5.1.36-bin.jar,
> puppet:///modules/wso2base/configs/repository/components/
> lib/mysql-connector-java-5.1.36-bin.jar, puppet:///files/configs/
> repository/components/lib/mysql-connector-java-5.1.36-bin.jar
>
> ERROR: Docker image wso2am-traffic-manager-kubernetes-pattern-3:2.1.0
> creation failed
>
>
> As in the guide step 7, I have copied the following jars to
> *PUPPET_HOME/modules*
> jackson-annotations-2.5.4.jar
> jackson-databind-2.5.4.jar
> jackson-core-2.5.4.jar
> kubernetes-membership-scheme-1.0.0.jar
> mysql-connector-java-5.1.36.jar
>
> jdk-8u131-linux-x64.tar.gz
> wso2am-2.1.0.zip
>
> I also tried executing the build as per the older guide by copying the jdk
> to PUPPET_HOME/modules/wso2base/files and the dependencies,
> kubernetes-membership-schemes to PUPPET_HOME/modules/wso2am/
> wso2am_runtime/files/configs/repository/components/lib
>
> Still I'm getting the same error. :(
>
> Any idea what I might be doing wrong here?
>
> Thanks,
> Dileepa
>
>
> On Fri, Jun 30, 2017 at 3:10 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Dileepa,
>>
>> Could you please check the tag of the wso2base module? By default, it
>> refers the master branch and this has to point to v1.0.0 [1]. In your setup
>> check the git branch in /modules/wso2base. You need to
>> check out this to [1].
>>
>> We are having discussions to remove puppet scripts when creating Docker
>> images. Hopefully, with K8 release we will remove puppet and allow users to
>> provide configuration files. All you need is to have a docker image for the
>> product with relevant configurations to run on K8s.
>>
>> [1] - https://github.com/wso2/puppet-base/tree/v1.0.0
>>
>> Thank you!
>>
>> On Fri, Jun 30, 2017 at 2:39 PM, Dileepa Jayakody <
>> dileepajayak...@gmail.com> wrote:
>>
>>> Hi Pubudu, Isuru,
>>>
>>> Thanks, yes manifests have been deleted by mistake. Now the
>>> PUPPET_HOME/manifests directory has site.pp.
>>> But now when I build again I'm getting another error by the puppet agent.
>>>
>>> log;
>>>
>>> 172.17.0.2 - - [30/Jun/2017 14:34:07] "GET /modules/wso2am_runtime/templa
>>> tes/repository/deployment/server/synapse-configs/default/api/_UserInfoAPI_.xml.erb
>>> HTTP/1.1" 200 -
>>> Running Puppet agent...
>>> Error: Must pass install_java to Class[Wso2base] at
>>> /etc/puppet/modules/wso2am_runtime/manifests/init.pp:165 on node
>>> d01e4f05b24b.mitrai.local
>>> Error: Must pass install_java to Class[Wso2base] at
>>> /etc/puppet/modules/wso2am_runtime/manifests/init.pp:165 on node
>>> d01e4f05b24b.mitrai.local
>>> The command '/bin/sh -c bash /usr/local/bin/image-config.sh' returned a
>>> non-zero code: 1
>>>
>>> ERROR: Docker image wso2am-gateway-manager-kubernetes-pattern-3:2.1.0
>>> creation failed
>>> Cleaning...
>>>
>>> Any idea what might be the issue here?
>>>
>>> Regards,
>>> Dileepa
>>>
>>> On Fri, Jun 30, 2017 at 2:11 PM, Pubudu Gunatilaka 
>>> wrote:
>>>
 Hi Dileepa,

 Based on the log it looks like you are missing the manifest files in
 puppet-home. You need to have the following files in the puppet home
 location.

 1. hieradata
 2. hiera.yaml
 3. manifests
 4. modules

 Please make sure you have the above files in your setup.

 Thank you!

 On Fri, Jun 30, 2017 at 1:06 PM, Dileepa Jayakody <
 dileepajayak...@gmail.com> wrote:

> Hi Pubudu,
>
> We followed the latest guide given above, but we are getting an error
> at step 9, building the docker image.
> The log :
>
> 2.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
> wso2am_runtime/pattern-7/default.yaml HTTP/1.1" 200 -
> 172.17.0.2 - - [30/Jun/2017 12:44:29] "GET
> /hieradata/dev/wso2/hieradata/wso2am_runtime/pattern-7/README.md
> HTTP/1.1" 200 -
> 172.17.0.2 - - [30/Jun/2017 12:44:29] "GET

Re: [Dev] How to get web app directly using app name

2017-06-30 Thread Anuruddha Liyanarachchi

Hi Thusitha,

This worked for me !

Thanks,


On Thu, Jun 29, 2017 at 5:11 PM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi Anuruddha,
>
> Can you try out the below code segment?
>
> Map webApplicationsHolderMap = 
> WebAppUtils.getAllWebappHolders(getConfigContext());
> for (WebApplicationsHolder webApplicationsHolder : 
> webApplicationsHolderMap.values()) {
> WebApplication webApplication = 
> webApplicationsHolder.getStartedWebapps().get(webappFileName);
>
>
> [1] - https://github.com/wso2/carbon-deployment/blob/4.7.x/
> components/webapp-mgt/org.wso2.carbon.webapp.mgt/src/
> main/java/org/wso2/carbon/webapp/mgt/WebappAdmin.java#L149
>
> On Thu, Jun 29, 2017 at 7:14 PM, Anuruddha Liyanarachchi <
> anurudd...@wso2.com> wrote:
>
>> Hi,
>>
>> I need to get a web application deployed in carbon. Following is my
>> approach. Is there any other way that I can optimize the following code.
>>
>> I have to iterate through 2 for loops. Do we have a way to get an
>> application by name without iterating the list?
>>
>> ConfigurationContext configurationContext = 
>> CarbonConfigurationContextFactory.getConfigurationContext();
>> WebApplicationsHolder defaultApplicationsHolder = ((Map> WebApplicationsHolder>) configurationContext.
>> 
>> getProperty(CarbonConstants.WEB_APPLICATIONS_HOLDER_LIST)).get("webapps");
>> if (defaultApplicationsHolder != null && 
>> !defaultApplicationsHolder.getStartedWebapps().isEmpty()) {
>> defaultApplicationsHolder.getStartedWebapps().forEach((appName, 
>> webApplication) -> {
>>>
>>> if (appName.contains("test-app-wso2")) {
>>
>> StandardHost applicationHost = (StandardHost) 
>> webApplication.getContext().getParent();
>> StandardEngine applicationEngine = (StandardEngine) 
>> applicationHost.getParent();
>> for (Connector connector : 
>> applicationEngine.getService().findConnectors()) {
>>String certWebAppPath = connector.getScheme() + "://" +
>> applicationHost.getName() + ":" + 
>> connector.getPort() + webApplication.getContext().getEncodedPath();
>>
>> }
>> }
>> });
>> }
>>
>>
>>
>> --
>> *Thanks and Regards,*
>> Anuruddha Lanka Liyanarachchi
>> Software Engineer - WSO2
>> Mobile : +94 (0) 712762611
>> Tel  : +94 112 145 345
>> a nurudd...@wso2.com
>>
>
>
>
> --
> Thusitha Dayaratne
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809 <+94%2071%20275%206809>
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
> 
>
>


-- 
*Thanks and Regards,*
Anuruddha Lanka Liyanarachchi
Software Engineer - WSO2
Mobile : +94 (0) 712762611
Tel  : +94 112 145 345
a nurudd...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

2017-06-30 Thread Dileepa Jayakody

Hi Pubudu,

Thanks. Checking out v1.0.0 from puppet-base resolved above error. However,
I'm getting a new error, related to the mysql jar file.

Notice:
/Stage[main]/Wso2base::Configure/Wso2base::Push_templates[repository/conf/carbon.xml]/File[/mnt/wso2am-2.1.0/repository/conf/carbon.xml]/content:
content changed '{md5}5c92af40d406b3368ceafd3b582017bd' to
'{md5}326757437935bb13c3d71d8ae692d04b'
Error:
/Stage[main]/Wso2base::Configure/Wso2base::Push_files[repository/components/lib/mysql-connector-java-5.1.36-bin.jar]/File[/mnt/wso2am-2.1.0/repository/components/lib/mysql-connector-java-5.1.36-bin.jar]:
Could not evaluate: Could not retrieve information from environment
production source(s)
puppet:///modules/wso2am_runtime/configs/repository/components/lib/mysql-connector-java-5.1.36-bin.jar,
puppet:///modules/wso2base/configs/repository/components/lib/mysql-connector-java-5.1.36-bin.jar,
puppet:///files/configs/repository/components/lib/mysql-connector-java-5.1.36-bin.jar

ERROR: Docker image wso2am-traffic-manager-kubernetes-pattern-3:2.1.0
creation failed


As in the guide step 7, I have copied the following jars to
*PUPPET_HOME/modules*
jackson-annotations-2.5.4.jar
jackson-databind-2.5.4.jar
jackson-core-2.5.4.jar
kubernetes-membership-scheme-1.0.0.jar
mysql-connector-java-5.1.36.jar

jdk-8u131-linux-x64.tar.gz
wso2am-2.1.0.zip

I also tried executing the build as per the older guide by copying the jdk
to PUPPET_HOME/modules/wso2base/files and the dependencies,
kubernetes-membership-schemes to
PUPPET_HOME/modules/wso2am/wso2am_runtime/files/configs/repository/components/lib

Still I'm getting the same error. :(

Any idea what I might be doing wrong here?

Thanks,
Dileepa


On Fri, Jun 30, 2017 at 3:10 PM, Pubudu Gunatilaka  wrote:

> Hi Dileepa,
>
> Could you please check the tag of the wso2base module? By default, it
> refers the master branch and this has to point to v1.0.0 [1]. In your setup
> check the git branch in /modules/wso2base. You need to check
> out this to [1].
>
> We are having discussions to remove puppet scripts when creating Docker
> images. Hopefully, with K8 release we will remove puppet and allow users to
> provide configuration files. All you need is to have a docker image for the
> product with relevant configurations to run on K8s.
>
> [1] - https://github.com/wso2/puppet-base/tree/v1.0.0
>
> Thank you!
>
> On Fri, Jun 30, 2017 at 2:39 PM, Dileepa Jayakody <
> dileepajayak...@gmail.com> wrote:
>
>> Hi Pubudu, Isuru,
>>
>> Thanks, yes manifests have been deleted by mistake. Now the
>> PUPPET_HOME/manifests directory has site.pp.
>> But now when I build again I'm getting another error by the puppet agent.
>>
>> log;
>>
>> 172.17.0.2 - - [30/Jun/2017 14:34:07] "GET /modules/wso2am_runtime/templa
>> tes/repository/deployment/server/synapse-configs/
>> default/api/_UserInfoAPI_.xml.erb HTTP/1.1" 200 -
>> Running Puppet agent...
>> Error: Must pass install_java to Class[Wso2base] at
>> /etc/puppet/modules/wso2am_runtime/manifests/init.pp:165 on node
>> d01e4f05b24b.mitrai.local
>> Error: Must pass install_java to Class[Wso2base] at
>> /etc/puppet/modules/wso2am_runtime/manifests/init.pp:165 on node
>> d01e4f05b24b.mitrai.local
>> The command '/bin/sh -c bash /usr/local/bin/image-config.sh' returned a
>> non-zero code: 1
>>
>> ERROR: Docker image wso2am-gateway-manager-kubernetes-pattern-3:2.1.0
>> creation failed
>> Cleaning...
>>
>> Any idea what might be the issue here?
>>
>> Regards,
>> Dileepa
>>
>> On Fri, Jun 30, 2017 at 2:11 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Dileepa,
>>>
>>> Based on the log it looks like you are missing the manifest files in
>>> puppet-home. You need to have the following files in the puppet home
>>> location.
>>>
>>> 1. hieradata
>>> 2. hiera.yaml
>>> 3. manifests
>>> 4. modules
>>>
>>> Please make sure you have the above files in your setup.
>>>
>>> Thank you!
>>>
>>> On Fri, Jun 30, 2017 at 1:06 PM, Dileepa Jayakody <
>>> dileepajayak...@gmail.com> wrote:
>>>
 Hi Pubudu,

 We followed the latest guide given above, but we are getting an error
 at step 9, building the docker image.
 The log :

 2.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
 wso2am_runtime/pattern-7/default.yaml HTTP/1.1" 200 -
 172.17.0.2 - - [30/Jun/2017 12:44:29] "GET
 /hieradata/dev/wso2/hieradata/wso2am_runtime/pattern-7/README.md
 HTTP/1.1" 200 -
 172.17.0.2 - - [30/Jun/2017 12:44:29] "GET
 /hieradata/dev/wso2/hieradata/wso2is_prepacked/pattern-1/default.yaml
 HTTP/1.1" 200 -
 172.17.0.2 - - [30/Jun/2017 12:44:29] code 404, message File not found



 *172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /manifests/ HTTP/1.1" 404
 -The command '/bin/sh -c bash /usr/local/bin/image-config.sh' returned a
 non-zero code: 8Docker image
 wso2am-gateway-manager-kubernetes-pattern-3:2.1.0 created.*Build
 process completed in 0 minutes and 12

Re: [Dev] Weird behaviour of the Call mediator and a HTTP endpoint

2017-06-30 Thread Thomas LEGRAND

Hello,

Just so you know, I replaced the use of the http endpoint by an address one
and that works. I modified the HTTP method to use by setting the
property HTTP_METHOD in the axis2 scope.

To use a variable as "uri", I used ${uri.var.parameterServiceEndpoint}.
Which is very weird because it is like the evaluation of the parameter is
not coherent. Sometimes is it is {$ctx:*} , or {*} and here, is it ${*}...

2017-06-28 15:18 GMT+02:00 Thomas LEGRAND :

> Hello,
>
> I have deployed a little RESTweb service on my machine and I try to
> communicate with it to retrieve a list of parameters via the GET method.
> The endpoint of this little web service is http://localhost:9090/
> ParamsPortal/Parameter.
>
> So, I created a template which will call this little endpoint but it is
> like something, somewhere, is blocking the request and answer on behalf of
> my web service.
>
> Here is my call to the web service:
>
> > name="REST_URL_POSTFIX" scope="axis2"/>
>> > expression="get-property('registry', 'conf:/parameterServiceEndpoint')"
>> name="uri.var.parameterServiceEndpoint" scope="default" type="STRING"/>
>>
>> 
>> 
>> 
>> 
>> 
>
>
>
>  Then, here is what it is displayed in the log when I activate the DEBUG
> mode for the wire thingies:
>
> [2017-06-28 15:09:43,369] [] DEBUG - headers http-incoming-134 >>
>> Connection: keep-alive
>> [2017-06-28 15:09:43,369] [] DEBUG - headers http-incoming-134 >>
>> Upgrade-Insecure-Requests: 1
>> [2017-06-28 15:09:43,369] [] DEBUG - headers http-incoming-134 >>
>> Cache-Control: max-age=0
>> [2017-06-28 15:09:43,374] []  INFO - LogMediator To:
>> /MyApi/lala?id=1, MessageID: 
>> urn:uuid:faee257d-86ab-43d3-8c54-43754004f120,
>> Direction: request, uri.var.parameterServiceEndpoint =
>> http://localhost:9090/ParamsPortal/Parameter
>> [2017-06-28 15:09:43,396] [] DEBUG - headers http-incoming-134 <<
>> HTTP/1.1 202 Accepted
>> [2017-06-28 15:09:43,396] [] DEBUG - headers http-incoming-134 << Date:
>> Wed, 28 Jun 2017 13:09:43 GMT
>> [2017-06-28 15:09:43,396] [] DEBUG - headers http-incoming-134 <<
>> Transfer-Encoding: chunked
>> [2017-06-28 15:09:43,397] [] DEBUG - headers http-incoming-134 <<
>> Connection: keep-alive
>> [2017-06-28 15:09:43,397] [] DEBUG - wire HTTP-Listener I/O dispatcher-4
>> << "HTTP/1.1 202 Accepted[\r][\n]"
>> [2017-06-28 15:09:43,397] [] DEBUG - wire HTTP-Listener I/O dispatcher-4
>> << "Date: Wed, 28 Jun 2017 13:09:43 GMT[\r][\n]"
>> [2017-06-28 15:09:43,397] [] DEBUG - wire HTTP-Listener I/O dispatcher-4
>> << "Transfer-Encoding: chunked[\r][\n]"
>> [2017-06-28 15:09:43,397] [] DEBUG - wire HTTP-Listener I/O dispatcher-4
>> << "Connection: keep-alive[\r][\n]"
>> [2017-06-28 15:09:43,397] [] DEBUG - wire HTTP-Listener I/O dispatcher-4
>> << "[\r][\n]"
>> [2017-06-28 15:09:43,397] [] DEBUG - wire HTTP-Listener I/O dispatcher-4
>> << "0[\r][\n]"
>> [2017-06-28 15:09:43,397] [] DEBUG - wire HTTP-Listener I/O dispatcher-4
>> << "[\r][\n]"
>
>
> I even tried with the Header mediator to change the To parameter but it is
> always the same things: I have a 202 Accepted with an empty content whereas
> my web service should return a 200 OK.
>
> Can you help me, please?
>
> Regards,
>
> Thomas
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

2017-06-30 Thread Pubudu Gunatilaka

Hi Dileepa,

Could you please check the tag of the wso2base module? By default, it
refers the master branch and this has to point to v1.0.0 [1]. In your setup
check the git branch in /modules/wso2base. You need to check
out this to [1].

We are having discussions to remove puppet scripts when creating Docker
images. Hopefully, with K8 release we will remove puppet and allow users to
provide configuration files. All you need is to have a docker image for the
product with relevant configurations to run on K8s.

[1] - https://github.com/wso2/puppet-base/tree/v1.0.0

Thank you!

On Fri, Jun 30, 2017 at 2:39 PM, Dileepa Jayakody  wrote:

> Hi Pubudu, Isuru,
>
> Thanks, yes manifests have been deleted by mistake. Now the
> PUPPET_HOME/manifests directory has site.pp.
> But now when I build again I'm getting another error by the puppet agent.
>
> log;
>
> 172.17.0.2 - - [30/Jun/2017 14:34:07] "GET /modules/wso2am_runtime/
> templates/repository/deployment/server/synapse-configs/default/api/_UserInfoAPI_.xml.erb
> HTTP/1.1" 200 -
> Running Puppet agent...
> Error: Must pass install_java to Class[Wso2base] at
> /etc/puppet/modules/wso2am_runtime/manifests/init.pp:165 on node
> d01e4f05b24b.mitrai.local
> Error: Must pass install_java to Class[Wso2base] at
> /etc/puppet/modules/wso2am_runtime/manifests/init.pp:165 on node
> d01e4f05b24b.mitrai.local
> The command '/bin/sh -c bash /usr/local/bin/image-config.sh' returned a
> non-zero code: 1
>
> ERROR: Docker image wso2am-gateway-manager-kubernetes-pattern-3:2.1.0
> creation failed
> Cleaning...
>
> Any idea what might be the issue here?
>
> Regards,
> Dileepa
>
> On Fri, Jun 30, 2017 at 2:11 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Dileepa,
>>
>> Based on the log it looks like you are missing the manifest files in
>> puppet-home. You need to have the following files in the puppet home
>> location.
>>
>> 1. hieradata
>> 2. hiera.yaml
>> 3. manifests
>> 4. modules
>>
>> Please make sure you have the above files in your setup.
>>
>> Thank you!
>>
>> On Fri, Jun 30, 2017 at 1:06 PM, Dileepa Jayakody <
>> dileepajayak...@gmail.com> wrote:
>>
>>> Hi Pubudu,
>>>
>>> We followed the latest guide given above, but we are getting an error at
>>> step 9, building the docker image.
>>> The log :
>>>
>>> 2.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
>>> wso2am_runtime/pattern-7/default.yaml HTTP/1.1" 200 -
>>> 172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
>>> wso2am_runtime/pattern-7/README.md HTTP/1.1" 200 -
>>> 172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
>>> wso2is_prepacked/pattern-1/default.yaml HTTP/1.1" 200 -
>>> 172.17.0.2 - - [30/Jun/2017 12:44:29] code 404, message File not found
>>>
>>>
>>>
>>> *172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /manifests/ HTTP/1.1" 404
>>> -The command '/bin/sh -c bash /usr/local/bin/image-config.sh' returned a
>>> non-zero code: 8Docker image
>>> wso2am-gateway-manager-kubernetes-pattern-3:2.1.0 created.*Build
>>> process completed in 0 minutes and 12 seconds
>>> Cleaning...
>>>
>>>
>>> Although it says the image is created, when we try to list the images we
>>> don't see it.
>>> docker images
>>> REPOSITORY  TAG
>>> IMAGE IDCREATED SIZE
>>>   
>>> bb1fbd050e8220 minutes ago  232MB
>>>   
>>> e115a82ab1c930 minutes ago  232MB
>>>   
>>> 63f7208ec0ca41 minutes ago  232MB
>>>   
>>> 8d7232ae31d942 minutes ago  232MB
>>>   
>>> 82d067d96a2443 minutes ago  232MB
>>>   
>>> 849952ec5cfc44 minutes ago  232MB
>>>   
>>> f0940512761d45 minutes ago  232MB
>>>   
>>> ce7f1779b17445 minutes ago  232MB
>>>   
>>> f9011faab51b45 minutes ago  232MB
>>>   
>>> 6b2550bd75b445 minutes ago  232MB
>>>   
>>> 9331674976a6About an hour ago   232MB
>>>
>>> I think  it fails to execute the image-config.sh due to some reason.
>>> Any idea how to resolve this?
>>>
>>> Thanks,
>>> Dileepa
>>>
>>> On Wed, Jun 28, 2017 at 11:01 PM, Dileepa Jayakody <
>>> dileepajayak...@gmail.com> wrote:
>>>
 Hi Pubudu,

 Thank you very much for the pointer. We will try out the new kubernetes
 artifacts and get back to you with our findings.

 Regards,
 Dileepa

 On Wed, Jun 28, 2017 at 8:00 PM, Pubudu Gunatilaka 
 wrote:

> Hi

Re: [Dev] WSO2 Committers += Yasima Dewmini

2017-06-30 Thread Harsha Kumara

Congratulations!

On Fri, Jun 30, 2017 at 1:41 PM, Tharindu Dharmarathna 
wrote:

> Congratulations Yasima!
>
>
> On Fri, Jun 30, 2017 at 1:31 PM, Roshan Wijesena  wrote:
>
>> Congratulations Yasima!
>>
>> On Fri, Jun 30, 2017 at 1:20 PM, Sanjeewa Malalgoda 
>> wrote:
>>
>>> Hi All,
>>> It's my pleasure to welcome  Yasima Dewmini  as a WSO2 Committer.
>>>
>>> Yasima  has been a valuable contributor to the WSO2 API Manager team.
>>> In recognition of her contribution, dedication, and commitment she has been
>>> voted as a WSO2 committer.
>>>
>>> Yasima, Congratulations and keep up the good work!
>>>
>>> Thank You,
>>> sanjeewa.
>>> --
>>>
>>> *Sanjeewa Malalgoda*
>>> WSO2 Inc.
>>> Mobile : +94713068779 <+94%2071%20306%208779>
>>>
>>> blog
>>> :http://sanjeewamalalgoda.blogspot.com/
>>> 
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Roshan Wijesena.
>> Senior Software Engineer-WSO2 Inc.
>> Mobile: *+94719154640 <+94%2071%20915%204640>*
>> Email: ros...@wso2.com
>> *WSO2, Inc. :** wso2.com *
>> lean.enterprise.middleware.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Tharindu Dharmarathna*Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94779109091 <+94%2077%20910%209091>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

2017-06-30 Thread Dileepa Jayakody

Hi Pubudu, Isuru,

Thanks, yes manifests have been deleted by mistake. Now the
PUPPET_HOME/manifests directory has site.pp.
But now when I build again I'm getting another error by the puppet agent.

log;

172.17.0.2 - - [30/Jun/2017 14:34:07] "GET
/modules/wso2am_runtime/templates/repository/deployment/server/synapse-configs/default/api/_UserInfoAPI_.xml.erb
HTTP/1.1" 200 -
Running Puppet agent...
Error: Must pass install_java to Class[Wso2base] at
/etc/puppet/modules/wso2am_runtime/manifests/init.pp:165 on node
d01e4f05b24b.mitrai.local
Error: Must pass install_java to Class[Wso2base] at
/etc/puppet/modules/wso2am_runtime/manifests/init.pp:165 on node
d01e4f05b24b.mitrai.local
The command '/bin/sh -c bash /usr/local/bin/image-config.sh' returned a
non-zero code: 1

ERROR: Docker image wso2am-gateway-manager-kubernetes-pattern-3:2.1.0
creation failed
Cleaning...

Any idea what might be the issue here?

Regards,
Dileepa

On Fri, Jun 30, 2017 at 2:11 PM, Pubudu Gunatilaka  wrote:

> Hi Dileepa,
>
> Based on the log it looks like you are missing the manifest files in
> puppet-home. You need to have the following files in the puppet home
> location.
>
> 1. hieradata
> 2. hiera.yaml
> 3. manifests
> 4. modules
>
> Please make sure you have the above files in your setup.
>
> Thank you!
>
> On Fri, Jun 30, 2017 at 1:06 PM, Dileepa Jayakody <
> dileepajayak...@gmail.com> wrote:
>
>> Hi Pubudu,
>>
>> We followed the latest guide given above, but we are getting an error at
>> step 9, building the docker image.
>> The log :
>>
>> 2.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
>> wso2am_runtime/pattern-7/default.yaml HTTP/1.1" 200 -
>> 172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
>> wso2am_runtime/pattern-7/README.md HTTP/1.1" 200 -
>> 172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
>> wso2is_prepacked/pattern-1/default.yaml HTTP/1.1" 200 -
>> 172.17.0.2 - - [30/Jun/2017 12:44:29] code 404, message File not found
>>
>>
>>
>> *172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /manifests/ HTTP/1.1" 404
>> -The command '/bin/sh -c bash /usr/local/bin/image-config.sh' returned a
>> non-zero code: 8Docker image
>> wso2am-gateway-manager-kubernetes-pattern-3:2.1.0 created.*Build process
>> completed in 0 minutes and 12 seconds
>> Cleaning...
>>
>>
>> Although it says the image is created, when we try to list the images we
>> don't see it.
>> docker images
>> REPOSITORY  TAG
>> IMAGE IDCREATED SIZE
>>   
>> bb1fbd050e8220 minutes ago  232MB
>>   
>> e115a82ab1c930 minutes ago  232MB
>>   
>> 63f7208ec0ca41 minutes ago  232MB
>>   
>> 8d7232ae31d942 minutes ago  232MB
>>   
>> 82d067d96a2443 minutes ago  232MB
>>   
>> 849952ec5cfc44 minutes ago  232MB
>>   
>> f0940512761d45 minutes ago  232MB
>>   
>> ce7f1779b17445 minutes ago  232MB
>>   
>> f9011faab51b45 minutes ago  232MB
>>   
>> 6b2550bd75b445 minutes ago  232MB
>>   
>> 9331674976a6About an hour ago   232MB
>>
>> I think  it fails to execute the image-config.sh due to some reason.
>> Any idea how to resolve this?
>>
>> Thanks,
>> Dileepa
>>
>> On Wed, Jun 28, 2017 at 11:01 PM, Dileepa Jayakody <
>> dileepajayak...@gmail.com> wrote:
>>
>>> Hi Pubudu,
>>>
>>> Thank you very much for the pointer. We will try out the new kubernetes
>>> artifacts and get back to you with our findings.
>>>
>>> Regards,
>>> Dileepa
>>>
>>> On Wed, Jun 28, 2017 at 8:00 PM, Pubudu Gunatilaka 
>>> wrote:
>>>
 Hi Dileepa,

 What you have followed is very old and we haven't tested those
 Kubernetes artifacts with APIM 2.1.0. We are currently in the process of
 updating Kubernetes artifacts for the APIM 2.1.0. You can find the latest
 artifacts in [1]. Please follow this and let us know if you find any 
 issues.

 The reason for the above behavior is that it keeps waiting for the
 service to be active. Do you see any wso2am pods in the deployment?
 Kubernetes data model has been changed and it is always better to try the
 latest artifacts as we have tested some of the patterns with the new
 deployment model [1].

 [1] - https://github.com/wso2/kubernetes-apim/tree/2.1.0

 Thank you!

 On Tue, Jun 27, 2017 at 7:00 PM, Dileepa Jayakody <

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

2017-06-30 Thread Pubudu Gunatilaka

Hi Dileepa,

Based on the log it looks like you are missing the manifest files in
puppet-home. You need to have the following files in the puppet home
location.

1. hieradata
2. hiera.yaml
3. manifests
4. modules

Please make sure you have the above files in your setup.

Thank you!

On Fri, Jun 30, 2017 at 1:06 PM, Dileepa Jayakody  wrote:

> Hi Pubudu,
>
> We followed the latest guide given above, but we are getting an error at
> step 9, building the docker image.
> The log :
>
> 2.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
> wso2am_runtime/pattern-7/default.yaml HTTP/1.1" 200 -
> 172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
> wso2am_runtime/pattern-7/README.md HTTP/1.1" 200 -
> 172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
> wso2is_prepacked/pattern-1/default.yaml HTTP/1.1" 200 -
> 172.17.0.2 - - [30/Jun/2017 12:44:29] code 404, message File not found
>
>
>
> *172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /manifests/ HTTP/1.1" 404 -The
> command '/bin/sh -c bash /usr/local/bin/image-config.sh' returned a
> non-zero code: 8Docker image
> wso2am-gateway-manager-kubernetes-pattern-3:2.1.0 created.*Build process
> completed in 0 minutes and 12 seconds
> Cleaning...
>
>
> Although it says the image is created, when we try to list the images we
> don't see it.
> docker images
> REPOSITORY  TAG
> IMAGE IDCREATED SIZE
>   
> bb1fbd050e8220 minutes ago  232MB
>   
> e115a82ab1c930 minutes ago  232MB
>   
> 63f7208ec0ca41 minutes ago  232MB
>   
> 8d7232ae31d942 minutes ago  232MB
>   
> 82d067d96a2443 minutes ago  232MB
>   
> 849952ec5cfc44 minutes ago  232MB
>   
> f0940512761d45 minutes ago  232MB
>   
> ce7f1779b17445 minutes ago  232MB
>   
> f9011faab51b45 minutes ago  232MB
>   
> 6b2550bd75b445 minutes ago  232MB
>   
> 9331674976a6About an hour ago   232MB
>
> I think  it fails to execute the image-config.sh due to some reason.
> Any idea how to resolve this?
>
> Thanks,
> Dileepa
>
> On Wed, Jun 28, 2017 at 11:01 PM, Dileepa Jayakody <
> dileepajayak...@gmail.com> wrote:
>
>> Hi Pubudu,
>>
>> Thank you very much for the pointer. We will try out the new kubernetes
>> artifacts and get back to you with our findings.
>>
>> Regards,
>> Dileepa
>>
>> On Wed, Jun 28, 2017 at 8:00 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Dileepa,
>>>
>>> What you have followed is very old and we haven't tested those
>>> Kubernetes artifacts with APIM 2.1.0. We are currently in the process of
>>> updating Kubernetes artifacts for the APIM 2.1.0. You can find the latest
>>> artifacts in [1]. Please follow this and let us know if you find any issues.
>>>
>>> The reason for the above behavior is that it keeps waiting for the
>>> service to be active. Do you see any wso2am pods in the deployment?
>>> Kubernetes data model has been changed and it is always better to try the
>>> latest artifacts as we have tested some of the patterns with the new
>>> deployment model [1].
>>>
>>> [1] - https://github.com/wso2/kubernetes-apim/tree/2.1.0
>>>
>>> Thank you!
>>>
>>> On Tue, Jun 27, 2017 at 7:00 PM, Dileepa Jayakody <
>>> dileepajayak...@gmail.com> wrote:
>>>
 Hi All,

 We have been following the kubernetes deployment guide for WSO2
 products [1] to deploy APIM 2.1.0 in kubernetes on Google cloud. We have
 also followed the blog post [2] as a reference.
 When I execute the final deploy command by running
 $KUBERNETES_HOME/wso2am/deploy.sh it keeps on idling at message : *Waiting
 wso2am to launch on http://104.198.75.29:32003 
 *

 When we try to access above given URL, we get a connection time-out.
 Further we have also created firewall rules in GC to open ports :
 9443,9763,8280,8243.
 But cannot access any of these endpoints, and can't access the carbon
 mgt console.

 Also in the kubernetes service deployed in GC we can't see any external
 endpoint exposed.

 Appreciate if someone can please give us any tip to resolve this and
 get the deployment working.

 Regards,
 Dileepa


 [1] https://docs.wso2.com/display/KA100/Deploying+and+Undeployin
 g+a+WSO2+Product+on+Kubernetes
 [2]

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

2017-06-30 Thread Isuru Haththotuwa

Hi Dileepa,

Looking at the logs, seems the GET request for /manifests has failed. Can
you check whether the puppet manifests are there in the PUPPET_HOME
location?


On Fri, Jun 30, 2017 at 1:06 PM, Dileepa Jayakody  wrote:

> Hi Pubudu,
>
> We followed the latest guide given above, but we are getting an error at
> step 9, building the docker image.
> The log :
>
> 2.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
> wso2am_runtime/pattern-7/default.yaml HTTP/1.1" 200 -
> 172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
> wso2am_runtime/pattern-7/README.md HTTP/1.1" 200 -
> 172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
> wso2is_prepacked/pattern-1/default.yaml HTTP/1.1" 200 -
> 172.17.0.2 - - [30/Jun/2017 12:44:29] code 404, message File not found
>
>
>
> *172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /manifests/ HTTP/1.1" 404 -The
> command '/bin/sh -c bash /usr/local/bin/image-config.sh' returned a
> non-zero code: 8Docker image
> wso2am-gateway-manager-kubernetes-pattern-3:2.1.0 created.*Build process
> completed in 0 minutes and 12 seconds
> Cleaning...
>
>
> Although it says the image is created, when we try to list the images we
> don't see it.
> docker images
> REPOSITORY  TAG
> IMAGE IDCREATED SIZE
>   
> bb1fbd050e8220 minutes ago  232MB
>   
> e115a82ab1c930 minutes ago  232MB
>   
> 63f7208ec0ca41 minutes ago  232MB
>   
> 8d7232ae31d942 minutes ago  232MB
>   
> 82d067d96a2443 minutes ago  232MB
>   
> 849952ec5cfc44 minutes ago  232MB
>   
> f0940512761d45 minutes ago  232MB
>   
> ce7f1779b17445 minutes ago  232MB
>   
> f9011faab51b45 minutes ago  232MB
>   
> 6b2550bd75b445 minutes ago  232MB
>   
> 9331674976a6About an hour ago   232MB
>
> I think  it fails to execute the image-config.sh due to some reason.
> Any idea how to resolve this?
>
> Thanks,
> Dileepa
>
> On Wed, Jun 28, 2017 at 11:01 PM, Dileepa Jayakody <
> dileepajayak...@gmail.com> wrote:
>
>> Hi Pubudu,
>>
>> Thank you very much for the pointer. We will try out the new kubernetes
>> artifacts and get back to you with our findings.
>>
>> Regards,
>> Dileepa
>>
>> On Wed, Jun 28, 2017 at 8:00 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Dileepa,
>>>
>>> What you have followed is very old and we haven't tested those
>>> Kubernetes artifacts with APIM 2.1.0. We are currently in the process of
>>> updating Kubernetes artifacts for the APIM 2.1.0. You can find the latest
>>> artifacts in [1]. Please follow this and let us know if you find any issues.
>>>
>>> The reason for the above behavior is that it keeps waiting for the
>>> service to be active. Do you see any wso2am pods in the deployment?
>>> Kubernetes data model has been changed and it is always better to try the
>>> latest artifacts as we have tested some of the patterns with the new
>>> deployment model [1].
>>>
>>> [1] - https://github.com/wso2/kubernetes-apim/tree/2.1.0
>>>
>>> Thank you!
>>>
>>> On Tue, Jun 27, 2017 at 7:00 PM, Dileepa Jayakody <
>>> dileepajayak...@gmail.com> wrote:
>>>
 Hi All,

 We have been following the kubernetes deployment guide for WSO2
 products [1] to deploy APIM 2.1.0 in kubernetes on Google cloud. We have
 also followed the blog post [2] as a reference.
 When I execute the final deploy command by running
 $KUBERNETES_HOME/wso2am/deploy.sh it keeps on idling at message : *Waiting
 wso2am to launch on http://104.198.75.29:32003 
 *

 When we try to access above given URL, we get a connection time-out.
 Further we have also created firewall rules in GC to open ports :
 9443,9763,8280,8243.
 But cannot access any of these endpoints, and can't access the carbon
 mgt console.

 Also in the kubernetes service deployed in GC we can't see any external
 endpoint exposed.

 Appreciate if someone can please give us any tip to resolve this and
 get the deployment working.

 Regards,
 Dileepa


 [1] https://docs.wso2.com/display/KA100/Deploying+and+Undeployin
 g+a+WSO2+Product+on+Kubernetes
 [2] http://rushmin.blogspot.com/2016/11/deploying-wso2-products-
 in-google.html

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.17 RC1

2017-06-30 Thread Vinod Kavinda

Hi,
I have tested Wso2 EI with the staged repo.

[x] stable - Go ahead and release

Regards,
Vinod

On Thu, Jun 29, 2017 at 3:36 PM, Chandana Napagoda 
wrote:

> Hi Devs,
>
> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.17.
>
> This release fixes the following issues
> https://github.com/wso2/carbon-kernel/milestone/15?closed=1
>
> Please test your products with kernel 4.4.17 RC1 and vote. The vote will
> be open for 72 hours or as longer as needed.
>
> Maven staging repository
> https://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1177/
>
> The tag to be voted upon :
> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.17-rc1
>
> [ ] Broken - Do not release (explain why)
> [ ] Stable  - Go ahead and release
>
> Thank you
> Platform Team
>
> --
> *Chandana Napagoda*
> Associate Technical Lead
> WSO2 Inc. - http://wso2.org
>
> *Email  :  chand...@wso2.com **Mobile : +94718169299
> <+94%2071%20816%209299>*
>
> *Blog  :http://cnapagoda.blogspot.com 
> | http://chandana.napagoda.com *
>
> *Linkedin : http://www.linkedin.com/in/chandananapagoda
> *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Vinod Kavinda
Senior Software Engineer
*WSO2 Inc. - lean . enterprise . middleware .*
Mobile : +94 (0) 712 415544
Blog : http://soatechflicks.blogspot.com/
[image: http://wso2.com/signature]

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

Re: [Dev] WSO2 Committers += Yasima Dewmini

2017-06-30 Thread Tharindu Dharmarathna

Congratulations Yasima!


On Fri, Jun 30, 2017 at 1:31 PM, Roshan Wijesena  wrote:

> Congratulations Yasima!
>
> On Fri, Jun 30, 2017 at 1:20 PM, Sanjeewa Malalgoda 
> wrote:
>
>> Hi All,
>> It's my pleasure to welcome  Yasima Dewmini  as a WSO2 Committer.
>>
>> Yasima  has been a valuable contributor to the WSO2 API Manager team. In
>> recognition of her contribution, dedication, and commitment she has been
>> voted as a WSO2 committer.
>>
>> Yasima, Congratulations and keep up the good work!
>>
>> Thank You,
>> sanjeewa.
>> --
>>
>> *Sanjeewa Malalgoda*
>> WSO2 Inc.
>> Mobile : +94713068779 <+94%2071%20306%208779>
>>
>> blog
>> :http://sanjeewamalalgoda.blogspot.com/
>> 
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Roshan Wijesena.
> Senior Software Engineer-WSO2 Inc.
> Mobile: *+94719154640 <+94%2071%20915%204640>*
> Email: ros...@wso2.com
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Tharindu Dharmarathna*Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

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

Re: [Dev] WSO2 Committers += Yasima Dewmini

2017-06-30 Thread Roshan Wijesena

Congratulations Yasima!

On Fri, Jun 30, 2017 at 1:20 PM, Sanjeewa Malalgoda 
wrote:

> Hi All,
> It's my pleasure to welcome  Yasima Dewmini  as a WSO2 Committer.
>
> Yasima  has been a valuable contributor to the WSO2 API Manager team. In
> recognition of her contribution, dedication, and commitment she has been
> voted as a WSO2 committer.
>
> Yasima, Congratulations and keep up the good work!
>
> Thank You,
> sanjeewa.
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779 <+94%2071%20306%208779>
>
> blog :http://sanjeewamalalgoda.
> blogspot.com/ 
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Roshan Wijesena.
Senior Software Engineer-WSO2 Inc.
Mobile: *+94719154640*
Email: ros...@wso2.com
*WSO2, Inc. :** wso2.com *
lean.enterprise.middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Yasima Dewmini

2017-06-30 Thread Sanjeewa Malalgoda

Hi All,
It's my pleasure to welcome  Yasima Dewmini  as a WSO2 Committer.

Yasima  has been a valuable contributor to the WSO2 API Manager team. In
recognition of her contribution, dedication, and commitment she has been
voted as a WSO2 committer.

Yasima, Congratulations and keep up the good work!

Thank You,
sanjeewa.
-- 

*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779

blog
:http://sanjeewamalalgoda.blogspot.com/

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

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

2017-06-30 Thread Dileepa Jayakody

Hi Pubudu,

We followed the latest guide given above, but we are getting an error at
step 9, building the docker image.
The log :

2.17.0.2 - - [30/Jun/2017 12:44:29] "GET
/hieradata/dev/wso2/hieradata/wso2am_runtime/pattern-7/default.yaml
HTTP/1.1" 200 -
172.17.0.2 - - [30/Jun/2017 12:44:29] "GET
/hieradata/dev/wso2/hieradata/wso2am_runtime/pattern-7/README.md HTTP/1.1"
200 -
172.17.0.2 - - [30/Jun/2017 12:44:29] "GET
/hieradata/dev/wso2/hieradata/wso2is_prepacked/pattern-1/default.yaml
HTTP/1.1" 200 -
172.17.0.2 - - [30/Jun/2017 12:44:29] code 404, message File not found



*172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /manifests/ HTTP/1.1" 404 -The
command '/bin/sh -c bash /usr/local/bin/image-config.sh' returned a
non-zero code: 8Docker image
wso2am-gateway-manager-kubernetes-pattern-3:2.1.0 created.*Build process
completed in 0 minutes and 12 seconds
Cleaning...


Although it says the image is created, when we try to list the images we
don't see it.
docker images
REPOSITORY  TAG
IMAGE IDCREATED SIZE
  
bb1fbd050e8220 minutes ago  232MB
  
e115a82ab1c930 minutes ago  232MB
  
63f7208ec0ca41 minutes ago  232MB
  
8d7232ae31d942 minutes ago  232MB
  
82d067d96a2443 minutes ago  232MB
  
849952ec5cfc44 minutes ago  232MB
  
f0940512761d45 minutes ago  232MB
  
ce7f1779b17445 minutes ago  232MB
  
f9011faab51b45 minutes ago  232MB
  
6b2550bd75b445 minutes ago  232MB
  
9331674976a6About an hour ago   232MB

I think  it fails to execute the image-config.sh due to some reason.
Any idea how to resolve this?

Thanks,
Dileepa

On Wed, Jun 28, 2017 at 11:01 PM, Dileepa Jayakody <
dileepajayak...@gmail.com> wrote:

> Hi Pubudu,
>
> Thank you very much for the pointer. We will try out the new kubernetes
> artifacts and get back to you with our findings.
>
> Regards,
> Dileepa
>
> On Wed, Jun 28, 2017 at 8:00 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Dileepa,
>>
>> What you have followed is very old and we haven't tested those Kubernetes
>> artifacts with APIM 2.1.0. We are currently in the process of updating
>> Kubernetes artifacts for the APIM 2.1.0. You can find the latest artifacts
>> in [1]. Please follow this and let us know if you find any issues.
>>
>> The reason for the above behavior is that it keeps waiting for the
>> service to be active. Do you see any wso2am pods in the deployment?
>> Kubernetes data model has been changed and it is always better to try the
>> latest artifacts as we have tested some of the patterns with the new
>> deployment model [1].
>>
>> [1] - https://github.com/wso2/kubernetes-apim/tree/2.1.0
>>
>> Thank you!
>>
>> On Tue, Jun 27, 2017 at 7:00 PM, Dileepa Jayakody <
>> dileepajayak...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> We have been following the kubernetes deployment guide for WSO2 products
>>> [1] to deploy APIM 2.1.0 in kubernetes on Google cloud. We have also
>>> followed the blog post [2] as a reference.
>>> When I execute the final deploy command by running
>>> $KUBERNETES_HOME/wso2am/deploy.sh it keeps on idling at message : *Waiting
>>> wso2am to launch on http://104.198.75.29:32003 *
>>>
>>> When we try to access above given URL, we get a connection time-out.
>>> Further we have also created firewall rules in GC to open ports :
>>> 9443,9763,8280,8243.
>>> But cannot access any of these endpoints, and can't access the carbon
>>> mgt console.
>>>
>>> Also in the kubernetes service deployed in GC we can't see any external
>>> endpoint exposed.
>>>
>>> Appreciate if someone can please give us any tip to resolve this and get
>>> the deployment working.
>>>
>>> Regards,
>>> Dileepa
>>>
>>>
>>> [1] https://docs.wso2.com/display/KA100/Deploying+and+Undeployin
>>> g+a+WSO2+Product+on+Kubernetes
>>> [2] http://rushmin.blogspot.com/2016/11/deploying-wso2-products-
>>> in-google.html
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Invoking Human Task in BPEL

2017-06-30 Thread Lipsa Pradhan

Thanks for the docs... But is there any document either for the process of
triggering a Human Task from a BPEL or for adding a RemoteTask in a BPEL.

On Fri, Jun 30, 2017 at 11:56 AM, Heshitha Hettihewa 
wrote:

> Hi Lipsa,
>
> For this you should install BPS Tooling pack as described in this doc[1].
> There is a human task editor which can be used to create a human task
> easily. You can find a step by step guide in here[2]. More over you can use
> the BPEL editor to create a BPEL and you can find a guide to create a BPEL
> using developer studio here[3]. With these you can create your own BPEL and
> human task artifacts.
>
> [1]. https://docs.wso2.com/display/BPS360/Installing+the+BPS+
> Tooling+Plug-In
> [2]. https://docs.wso2.com/display/BPS360/Writing+a+Human+Task+
> Artifact+using+the+Editor
> [3]. https://docs.wso2.com/display/BPS360/Creating+a+BPEL+Process
>
> Thanks.
>
> On Fri, Jun 30, 2017 at 11:23 AM, Lipsa Pradhan  adnatesolutions.com> wrote:
>
>> Hi everyone
>>
>> I want to know the procedure of creating a human task in a BPEL, which is
>> being created in developer studio. Actually, in the
>> avalable documentations, there is a single example of ClaimApprovalTask
>> everywhere. That too, not from scratch, we are supposed to deploy the files
>> from samples folder directly.
>>
>> So, can anyone provide me documentation for the BPEL Creation with
>> Humantask in developer studio?
>>
>> Thanks in advance!
>>
>> Warm Regards
>> Lipsa Pradhan
>>
>> ___
>> 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

Re: [Dev] Invoking Human Task in BPEL

2017-06-30 Thread Heshitha Hettihewa

Hi Lipsa,

For this you should install BPS Tooling pack as described in this doc[1].
There is a human task editor which can be used to create a human task
easily. You can find a step by step guide in here[2]. More over you can use
the BPEL editor to create a BPEL and you can find a guide to create a BPEL
using developer studio here[3]. With these you can create your own BPEL and
human task artifacts.

[1]. https://docs.wso2.com/display/BPS360/Installing+the+BPS+Tooling+Plug-In
[2].
https://docs.wso2.com/display/BPS360/Writing+a+Human+Task+Artifact+using+the+Editor
[3]. https://docs.wso2.com/display/BPS360/Creating+a+BPEL+Process

Thanks.

On Fri, Jun 30, 2017 at 11:23 AM, Lipsa Pradhan <
lipsa.prad...@adnatesolutions.com> wrote:

> Hi everyone
>
> I want to know the procedure of creating a human task in a BPEL, which is
> being created in developer studio. Actually, in the
> avalable documentations, there is a single example of ClaimApprovalTask
> everywhere. That too, not from scratch, we are supposed to deploy the files
> from samples folder directly.
>
> So, can anyone provide me documentation for the BPEL Creation with
> Humantask in developer studio?
>
> Thanks in advance!
>
> Warm Regards
> Lipsa Pradhan
>
> ___
> 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

[Dev] net.sf.saxon.om.NamePool$NamePoolLimitException: NamePool limit exceeded:

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.17 RC1

Re: [Dev] WSO2 Committers += Yasima Dewmini

Re: [Dev] EI 6.1.1 - Dev studio mediator project issues

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

Re: [Dev] How to get web app directly using app name

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

Re: [Dev] Weird behaviour of the Call mediator and a HTTP endpoint

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

Re: [Dev] WSO2 Committers += Yasima Dewmini

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.17 RC1

Re: [Dev] WSO2 Committers += Yasima Dewmini

Re: [Dev] WSO2 Committers += Yasima Dewmini

[Dev] WSO2 Committers += Yasima Dewmini

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

Re: [Dev] Invoking Human Task in BPEL

Re: [Dev] Invoking Human Task in BPEL

20 matches

Site Navigation

Mail list logo

Footer information