[Dev] How to validate email adddress

[Dilusha Alphonso]

Hi All,

Requirement: I need to check a condition " Patient ID is the email address
of given patient". When I give any string to the ID, it must be an email
address. I have to validate ID whether it is in email format. For this, I
used the filter mediator in ESB, But I noticed my request didn't go through
that filter mediator.

I attached my API configuration in ESB. Please, anyone, help me to validate
the email address with ID.

http://ws.apache.org/ns/synapse; name="Durdan" context="/test">
   
  
 
 


   
  
 http://schemas.xmlsoap.org/soap/envelope/;>

   17


   http://service.sample.durdans.com;>
  $1
   

 
  
  
 
  
   
   
   
   
  
 
  
   
   
   


   
  
   

 
  
  
 
  
   


Thanks
Dilusha





before loop back to out sequence whether the USER_NAME and PATIENT_ID are
equal.

-- 


*Best Regards,Dilusha Alphonso*

*Software Engineer - Support Team*


*WSO2*
*Mobile : *

*+94766837098[image: http://wso2.com/signature] *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] WSO2 Enterprise Integrator 6.1.1-update10 Released !

[Samisa Abeysinghe]

I think we will have to move onto an aggressive hackathon mode to get this
fixed. We can learn some lessons from what IAM team did.

Please arrange a meeting Monday to discuss the plans with the issue fixing
sub team.

Thanks,
Samisa...


Samisa Abeysinghe

Chief Engineering and Delivery Officer

WSO2 Inc.
http://wso2.com


On Fri, Nov 24, 2017 at 4:47 PM, Jasintha Dasanayake 
wrote:

> HI Nandika
>
> On Fri, Nov 24, 2017 at 2:16 PM, Nandika Jayawardana 
> wrote:
>
>> Actually, we have another 489 issues in DEVTOOLEI project which I think
>> is also critically important since dev studio is the primary development
>> tool the developers interact with. The perception generated from dev studio
>> will have a lasting effect on the product quality.
>>
>> In order to reduce the bug count, we will start with
>> classifying/prioritizing the issues.
>>
>
>  Please let me know if you need any help for this effort
>
> /Jasintha
>
>>
>> 1. There could be many issues which are already fixed and not resolved or
>> no longer relevant due to changes which can be resolved straight away.
>> 2. For the relevant issues, we can classify them depending on the
>> importance/relevance of the issue and identify the components which have
>> the most number of critical issues and work on them one component at a
>> time.
>>
>> Regards
>> Nandika
>>
>> On Fri, Nov 24, 2017 at 12:14 PM, Vijitha Ekanayake 
>> wrote:
>>
>>> Hi Samisa,
>>>
>>> We are continuously working on fixing the bugs reported under JIRA and
>>> GitHub along with the EI 6 weekly updates. The plan is to pick a set up
>>> issues by filtering the priority and label those for the upcoming update
>>> release.
>>>
>>> Thanks,
>>> Vijitha.
>>>
>>> On Fri, Nov 24, 2017 at 3:14 AM, Samisa Abeysinghe 
>>> wrote:
>>>
 We have 803 Jira and 265 Git open issues, what is the plan to flush
 them?

 Thanks,
 Samisa...


 Samisa Abeysinghe

 Chief Engineering and Delivery Officer

 WSO2 Inc.
 http://wso2.com


 On Fri, Nov 24, 2017 at 12:08 AM, Vijitha Ekanayake 
 wrote:

>
> Please find the correct link for the distribution: https://github.c
> om/wso2/product-ei/releases/download/v6.1.1-update10/wso2ei-
> 6.1.1-update10.zip
>
>
> On Fri, Nov 24, 2017 at 12:01 AM, Vijitha Ekanayake  > wrote:
>
>> Hi all,
>>
>> The WSO2 Integration team is pleased to announce the release of
>> Enterprise Integrator 6.1.1-update10. It is available for download from
>> here
>> 
>> .
>>
>
>> *Tasks/Bug Fixes and Improvements*
>>
>> https://github.com/wso2/product-ei/issues?q=is%3Aissue+miles
>> tone%3A6.1.1-update-10+is%3Aclosed
>>
>> *​​List of Open Issues*
>>
>> https://wso2.org/jira/issues/?filter=13994
>>
>> https://github.com/wso2/product-ei/issues?q=is%3Aopen+is%3Aissue
>>
>>
>> *Mailing Lists*
>>
>> Join our mailing lists and correspond with the developers directly.
>>
>> Developer List : dev@wso2.org | Subscribe | Mail Archive
>>
>> WSO2 Architecture List: architect...@wso2.org
>>
>> User Forum : StackOverflow 
>>
>> *How To Contribute*
>>
>> Your feedback is most welcome!
>>
>> *Reporting Issues​*
>>
>> We encourage you to report issues, improvements and feature requests
>> regarding WSO2 Integrator through WSO2 EI GIT Issues
>> .
>>
>> ~ The WSO2 Integration Team ~
>>
>
>>
>
>
> --
> Vijitha Ekanayake
> Senior Software Engineer*, *WSO2, Inc.; http://wso2.com/
> Mobile : +94 777 24 73 39 | +94 718 74 44 08
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

>>>
>>>
>>> --
>>> Vijitha Ekanayake
>>> Senior Software Engineer*, *WSO2, Inc.; http://wso2.com/
>>> Mobile : +94 777 24 73 39 | +94 718 74 44 08
>>> lean.enterprise.middleware
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Nandika Jayawardana
>> WSO2 Inc ; http://wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> *Jasintha Dasanayake**Associate Technical Lead*
>
> *WSO2 Inc. | http://wso2.com lean . 

Re: [Dev] [SP][Windows] Error during startup

[Sriskandarajah Suhothayan]

@Gokul also please test and verity whether it fixes in SP.

On Fri, Nov 24, 2017 at 7:54 PM, Danesh Kuruppu  wrote:

> Hi Gokul,
>
> This Issue is fixed with PR[1]. Can you please test with new changes.
> @Kishanthan/Nira/Jayanga, please review and merge
>
> 1. https://github.com/wso2/carbon-config/pull/62
>
> Thanks
> Danesh
>
> On Fri, Nov 24, 2017 at 5:19 AM, Gokul Balakrishnan 
> wrote:
>
>> Hi,
>>
>> We're seeing the following error while starting up Stream Processor
>> Alpha2/3 in Windows. The main reason appears to be the server failing to
>> resolve the ${sys:carbon.home} properties in deployment.yaml:
>>
>> Bad pathname"; "E:wso2sp-4.0.0-Alpha3-SNAPSHOTbin../wso2/editor/database/
>> WSO2_CARBON_DB.mv.db"
>>
>> As you can see, the path delimiter ("\") is missing between the drive and
>> the initial path elements.
>>
>> Opened [1] to track this issue. Could you please take a look since this
>> is critical for us?
>>
>> [1] https://github.com/wso2/carbon-kernel/issues/1615
>>
>> Thanks,
>>
>> --
>> Gokul Balakrishnan
>> Senior Software Engineer,
>> WSO2, Inc. http://wso2.com
>> M +94 77 5935 789 | +44 7563 570502 <+44%207563%20570502>
>>
>>
>
>
> --
>
> *Danesh Kuruppu*
> Senior Software Engineer | WSO2
>
> Email: dan...@wso2.com
> Mobile: +94 (77) 1690552 <077%20169%200552>
> Web: WSO2 Inc 
>
>


-- 

*S. Suhothayan*
Associate Director / Architect
*WSO2 Inc. *http://wso2.com
* *
lean . enterprise . middleware


*cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
twitter: http://twitter.com/suhothayan
 | linked-in:
http://lk.linkedin.com/in/suhothayan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [SP][Windows] Error during startup

[Danesh Kuruppu]

Hi Gokul,

This Issue is fixed with PR[1]. Can you please test with new changes.
@Kishanthan/Nira/Jayanga, please review and merge

1. https://github.com/wso2/carbon-config/pull/62

Thanks
Danesh

On Fri, Nov 24, 2017 at 5:19 AM, Gokul Balakrishnan  wrote:

> Hi,
>
> We're seeing the following error while starting up Stream Processor
> Alpha2/3 in Windows. The main reason appears to be the server failing to
> resolve the ${sys:carbon.home} properties in deployment.yaml:
>
> Bad pathname"; "E:wso2sp-4.0.0-Alpha3-SNAPSHOTbin../wso2/editor/
> database/WSO2_CARBON_DB.mv.db"
>
> As you can see, the path delimiter ("\") is missing between the drive and
> the initial path elements.
>
> Opened [1] to track this issue. Could you please take a look since this is
> critical for us?
>
> [1] https://github.com/wso2/carbon-kernel/issues/1615
>
> Thanks,
>
> --
> Gokul Balakrishnan
> Senior Software Engineer,
> WSO2, Inc. http://wso2.com
> M +94 77 5935 789 | +44 7563 570502 <+44%207563%20570502>
>
>


-- 

*Danesh Kuruppu*
Senior Software Engineer | WSO2

Email: dan...@wso2.com
Mobile: +94 (77) 1690552
Web: WSO2 Inc 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][puppet-apim]

[Prasanna Dangalla]

On Fri, Nov 24, 2017 at 10:08 AM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi Nuwan,
>
> As per the current patterns, there is no HA in traffic manager. The
> approach you have taken should work. However, you will need to configure
> dep-sync between two nodes if you are deploying custom policies.
>
I'm not sure whether we are using dep-sync now since in APIM docker
patterns we removed depsync and added rsync.[1]

[1] -
https://github.com/wso2/docker-apim/blob/v2.1.0/docker-compose/pattern-4/gateway-worker-2/worker-manager-rsync.sh

>
> On Fri, Nov 24, 2017 at 9:54 AM, Nuwan Silva  wrote:
>
>> Hi Team,
>>
>> While deploying the puppet-apim [1] I had an issue where there was no
>> pattern for deploying Traffic Manager as an HA deployment. I added the
>> following snippet to achieve HA in the cluster. Do we have another way of
>> doing this? Please advise.
>>
>> wso2::clustering:
>>   enabled: true
>>   domain: tm.am.wso2.domain
>>   sub_domain: mgt
>>   local_member_host: "%{::ipaddress}"
>>   local_member_port: 4000
>> # WKA membership scheme
>>   membership_scheme: wka
>>   wka:
>> members:
>>   -
>> hostname: 192.168.48.33
>> port: 4000
>>   -
>> hostname: 192.168.48.34
>> port: 4000
>>
>>
>> [1] https://github.com/wso2/puppet-apim
>> [2] https://github.com/wso2/puppet-apim/issues/47
>>
>> Cheers,
>> NuwanS.
>> --
>>
>>
>> *Nuwan Silva*
>> *Associate Technical Lead*
>> Mobile: +9477 980 4543 <+94%2077%20980%204543>
>>
>> WSO2 Inc.
>> lean . enterprise . middleware.
>> http://www.wso2.com
>>
>
>
>
> --
> *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

[Dev] [Validate Mediator] JSON validation issue

[Lahiru Cooray]

Hi team,
Im using ESB 5.0.0 and trying to validate a json payload against a schema.
Below is my sample synapse code snippet

 


   
  {"Error":$1"}
  
 
  
   
   
   

 

When I try to send an invalid payload it gets validated but the specific
erroneous property is not returned.

DEBUG - wire HTTP-Listener I/O dispatcher-3 << "{"Error":the following
keywords are unknown and will be ignored: [$id]"}[\r][\n]"

Is there a way to access the specific invalid property and return a custom
message. Appreciate your help!

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

Re: [Dev] [DEV][puppet-apim]

[Pubudu Gunatilaka]

Hi Nuwan,

It is not actually Spark clustering, you need to do the CEP related
clustering [1] when you are using TM in clustered mode.

Read more on TM articles [2] and [3].

[1] - https://docs.wso2.com/display/CLUSTER44x/Clustering+CEP+4.0.0
[2] -
https://wso2.com/library/articles/2016/10/article-scalable-traffic-manager-deployment-patterns-for-wso2-api-manager-part-1/
[3] -
https://wso2.com/library/articles/2016/10/article-scalable-traffic-manager-deployment-patterns-for-wso2-api-manager-part-2/

Thank you!

On Fri, Nov 24, 2017 at 5:29 PM, Tharindu Dharmarathna 
wrote:

> Hi Nuwan,
>
> I think pubudu get missed understanding as Analytics nodes. We do not need
> to have spark clustering in TM .
>
> On Fri, Nov 24, 2017 at 11:28 AM, Nuwan Silva  wrote:
>
>> Thanks for the info but, do we need to configure spark cluster
>> configurations for traffic manager? If so why?
>>
>> On Fri, Nov 24, 2017 at 10:57 AM, Samitha Chathuranga 
>> wrote:
>>
>>> I'm not sure whether we are using dep-sync now since in APIM docker
 patterns we removed depsync and added rsync.[1]

>>> Using rsync [1] is completely external configuration with wso2 product
>>> configs, hence different to the usage of svn-dep-sync. But if you follow up
>>> with svn dep sync, required templates are already added to the template
>>> files and so you have to add only the required hiera data. Anyway now we
>>> recommend rsync over svn, so better to go with rsync.
>>>
>>> [1] - https://docs.wso2.com/display/AM210/Configuring+rsync+for+De
>>> ployment+Synchronization
>>>
>>> On Fri, Nov 24, 2017 at 10:36 AM, Prasanna Dangalla 
>>> wrote:
>>>

 On Fri, Nov 24, 2017 at 10:08 AM, Anuruddha Liyanarachchi <
 anurudd...@wso2.com> wrote:

> Hi Nuwan,
>
> As per the current patterns, there is no HA in traffic manager. The
> approach you have taken should work. However, you will need to configure
> dep-sync between two nodes if you are deploying custom policies.
>
 I'm not sure whether we are using dep-sync now since in APIM docker
 patterns we removed depsync and added rsync.[1]

 [1] - https://github.com/wso2/docker-apim/blob/v2.1.0/docker-compo
 se/pattern-4/gateway-worker-2/worker-manager-rsync.sh

>
> On Fri, Nov 24, 2017 at 9:54 AM, Nuwan Silva  wrote:
>
>> Hi Team,
>>
>> While deploying the puppet-apim [1] I had an issue where there was no
>> pattern for deploying Traffic Manager as an HA deployment. I added the
>> following snippet to achieve HA in the cluster. Do we have another way of
>> doing this? Please advise.
>>
>> wso2::clustering:
>>   enabled: true
>>   domain: tm.am.wso2.domain
>>   sub_domain: mgt
>>   local_member_host: "%{::ipaddress}"
>>   local_member_port: 4000
>> # WKA membership scheme
>>   membership_scheme: wka
>>   wka:
>> members:
>>   -
>> hostname: 192.168.48.33
>> port: 4000
>>   -
>> hostname: 192.168.48.34
>> port: 4000
>>
>>
>> [1] https://github.com/wso2/puppet-apim
>> [2] https://github.com/wso2/puppet-apim/issues/47
>>
>> Cheers,
>> NuwanS.
>> --
>>
>>
>> *Nuwan Silva*
>> *Associate Technical Lead*
>> Mobile: +9477 980 4543 <+94%2077%20980%204543>
>>
>> WSO2 Inc.
>> lean . enterprise . middleware.
>> http://www.wso2.com
>>
>
>
>
> --
> *Thanks and Regards,*
> Anuruddha Lanka Liyanarachchi
> Software Engineer - WSO2
> Mobile : +94 (0) 712762611
> Tel  : +94 112 145 345
> a nurudd...@wso2.com
>


>>>
>>>
>>> --
>>> Samitha Chathuranga
>>> Software Engineer, WSO2 Inc.
>>> lean.enterprise.middleware
>>> Mobile: +94715123761
>>>
>>> [image: http://wso2.com/signature] 
>>>
>>
>>
>>
>> --
>>
>>
>> *Nuwan Silva*
>> *Associate Technical Lead*
>> Mobile: +9477 980 4543 <+94%2077%20980%204543>
>>
>> WSO2 Inc.
>> lean . enterprise . middleware.
>> http://www.wso2.com
>>
>
>
>
> --
>
> *Tharindu Dharmarathna*Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94779109091 <+94%2077%20910%209091>*
>



-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Senior 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] How to set ThriftClientPort in APIM Gate Way Node in a cluster setup

[Chamalee De Silva]

[1] Port offsetting the Thrift port in APIM

On Fri, Nov 24, 2017 at 7:01 PM, Chamalee De Silva 
wrote:

> hi Dushantha,
>
> For API Manager 2.0.0 and later versions, we do not need to configure the
> ThriftClient and ThriftServer ports as they get incremented according to
> the offset.
>
> For API Manager versions prior to APIM 2.0.0 we need to modify these ports
> according to the port offset.
>
> Please refer mail thread [1] for more information.
>
>
>
> Thanks,
> Chamalee
>
> On Fri, Nov 24, 2017 at 11:40 AM, Samitha Chathuranga 
> wrote:
>
>> Hi Dushantha,
>>
>> The point is that by default those thrift port values are commented out.
>> (if they are commented-out the all the port values are changed by the
>> offset value ) If you uncomment them, you have to configure them correctly.
>> By the way in the doc [1] you mentioned, note the below section, under the
>> 3rd point under the topic "Installing and configuring API Manager".
>>
>> [image: Inline image 1]
>>
>> So the doc has been written not considering that optional step of port
>> offsetting. So all ports mentioned in the doc are considering that there
>> are no offsets.
>>
>> [1] - https://docs.wso2.com/display/CLUSTER44x/Clustering+API+Mana
>> ger+2.0.0
>>
>> Regards,
>> Samitha
>>
>> On Fri, Nov 24, 2017 at 9:09 AM, Viduranga Gunarathne > > wrote:
>>
>>> Hi Dushantha,
>>>
>>> Yes. If you are using port offset to deploy the Gateway and KeyManager
>>> nodes, then the default Thrift port (10397) in both the nodes will get
>>> offset by the specified offset value.
>>> Eg:
>>> Gateway offset = 2,
>>> Then  will be 10399
>>>
>>> KeyManager offset = 3,
>>> Then  will be 10400
>>>
>>> In a clustered deployment, the KeyManager acts as the Thrift Server and
>>> the Gateway as the Thrift client. Hence the Gateway uses the
>>>  to send a request to the KeyManager where the request is
>>> handled at the . For the communication to happen, both
>>> the port values (ThriftServerPort in KeyManager and ThriftClientPort in
>>> Gateway) should be of the same value. Unless the port offset of both the
>>> Gateway and the KeyManager is the same, you will have to manually set the
>>> two values.
>>>
>>> Thanks,
>>> Viduranga.
>>>
>>> On Thu, Nov 23, 2017 at 9:24 PM, Chamara Silva  wrote:
>>>
 This already in the public documentation. Please refer "Changing the
 Thrift client and server ports" section.


 [2] https://docs.wso2.com/display/AM210/Changing+the+Default
 +Ports+with+Offset

 Thanks,
 Chamara Silva

 On Thu, Nov 23, 2017 at 7:57 PM, Dushantha Batuwita  wrote:

> Hi
> I'm involved in a gateway cluster set up in the local machine where
> the architecture is explained as follows
>
>1. IS 5.3.0 as KM offset 0
>2. Publisher/store/TM  offset 1
>3. Gateway worker   offset 3
>4. GatewayWorkerManger  offset 2
>
> I'm following the [1] Clustering API Manager document where it
> explains
> Configuring the Gateway > Configure key management related
> communication. >  c.  Specify the ThriftClientPort and Thrif
> tServerPort values. 10397 is the default.
> 10397
> 10397
> My query is should this port values be incremented according to the
> given offset values
>
>
> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+API+
> Manager+2.0.0#b099f11ea91344af8835595ac455a7c1
>
>
> many thanks
> --
> *Dushantha Nayanajith Chandima Batuwita*
> Software Engineer Support | WSO2
> dushan...@wso2.com
> mobile : 0094777453010 <077%20745%203010>
>



 --
 Suminda Chamara Silva
 Technical Lead
 WSO2 Inc.
 Mobile: +94718302858 <+94%2071%20830%202858>
 blog: http://chamaras.blogspot.com


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


>>>
>>>
>>> --
>>> Regards,
>>>
>>> *Viduranga Gunarathne*
>>>
>>> *Software Engineer Intern*
>>>
>>>
>>> *WSO2*
>>> Email : vidura...@wso2.com
>>> Mobile : +94712437484 <+94%2071%20243%207484>
>>> Web : http://wso2.com
>>> [image: https://wso2.com/signature] 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Samitha Chathuranga
>> Software Engineer, WSO2 Inc.
>> lean.enterprise.middleware
>> Mobile: +94715123761
>>
>> [image: http://wso2.com/signature] 
>>
>> ___
>> 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 

Re: [Dev] How to set ThriftClientPort in APIM Gate Way Node in a cluster setup

[Chamalee De Silva]

hi Dushantha,

For API Manager 2.0.0 and later versions, we do not need to configure the
ThriftClient and ThriftServer ports as they get incremented according to
the offset.

For API Manager versions prior to APIM 2.0.0 we need to modify these ports
according to the port offset.

Please refer mail thread [1] for more information.



Thanks,
Chamalee

On Fri, Nov 24, 2017 at 11:40 AM, Samitha Chathuranga 
wrote:

> Hi Dushantha,
>
> The point is that by default those thrift port values are commented out.
> (if they are commented-out the all the port values are changed by the
> offset value ) If you uncomment them, you have to configure them correctly.
> By the way in the doc [1] you mentioned, note the below section, under the
> 3rd point under the topic "Installing and configuring API Manager".
>
> [image: Inline image 1]
>
> So the doc has been written not considering that optional step of port
> offsetting. So all ports mentioned in the doc are considering that there
> are no offsets.
>
> [1] - https://docs.wso2.com/display/CLUSTER44x/Clustering+API+
> Manager+2.0.0
>
> Regards,
> Samitha
>
> On Fri, Nov 24, 2017 at 9:09 AM, Viduranga Gunarathne 
> wrote:
>
>> Hi Dushantha,
>>
>> Yes. If you are using port offset to deploy the Gateway and KeyManager
>> nodes, then the default Thrift port (10397) in both the nodes will get
>> offset by the specified offset value.
>> Eg:
>> Gateway offset = 2,
>> Then  will be 10399
>>
>> KeyManager offset = 3,
>> Then  will be 10400
>>
>> In a clustered deployment, the KeyManager acts as the Thrift Server and
>> the Gateway as the Thrift client. Hence the Gateway uses the
>>  to send a request to the KeyManager where the request is
>> handled at the . For the communication to happen, both
>> the port values (ThriftServerPort in KeyManager and ThriftClientPort in
>> Gateway) should be of the same value. Unless the port offset of both the
>> Gateway and the KeyManager is the same, you will have to manually set the
>> two values.
>>
>> Thanks,
>> Viduranga.
>>
>> On Thu, Nov 23, 2017 at 9:24 PM, Chamara Silva  wrote:
>>
>>> This already in the public documentation. Please refer "Changing the
>>> Thrift client and server ports" section.
>>>
>>>
>>> [2] https://docs.wso2.com/display/AM210/Changing+the+Default
>>> +Ports+with+Offset
>>>
>>> Thanks,
>>> Chamara Silva
>>>
>>> On Thu, Nov 23, 2017 at 7:57 PM, Dushantha Batuwita 
>>> wrote:
>>>
 Hi
 I'm involved in a gateway cluster set up in the local machine where the
 architecture is explained as follows

1. IS 5.3.0 as KM offset 0
2. Publisher/store/TM  offset 1
3. Gateway worker   offset 3
4. GatewayWorkerManger  offset 2

 I'm following the [1] Clustering API Manager document where it explains
 Configuring the Gateway > Configure key management related
 communication. >  c.  Specify the ThriftClientPort and ThriftServerPort
  values. 10397 is the default.
 10397
 10397
 My query is should this port values be incremented according to the
 given offset values


 [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+API+
 Manager+2.0.0#b099f11ea91344af8835595ac455a7c1


 many thanks
 --
 *Dushantha Nayanajith Chandima Batuwita*
 Software Engineer Support | WSO2
 dushan...@wso2.com
 mobile : 0094777453010 <077%20745%203010>

>>>
>>>
>>>
>>> --
>>> Suminda Chamara Silva
>>> Technical Lead
>>> WSO2 Inc.
>>> Mobile: +94718302858 <+94%2071%20830%202858>
>>> blog: http://chamaras.blogspot.com
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> *Viduranga Gunarathne*
>>
>> *Software Engineer Intern*
>>
>>
>> *WSO2*
>> Email : vidura...@wso2.com
>> Mobile : +94712437484 <+94%2071%20243%207484>
>> Web : http://wso2.com
>> [image: https://wso2.com/signature] 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Samitha Chathuranga
> Software Engineer, WSO2 Inc.
> lean.enterprise.middleware
> Mobile: +94715123761
>
> [image: http://wso2.com/signature] 
>
> ___
> 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] Error occurs with Response caching enabled.

[Thivya Mahenthirarasa]

Hi all,

Does the caching is needed for the Creation scenarios too?. Is it a good
practice to have to cache for 200 ok responses?


Thanks,
Thivya


On Fri, Nov 24, 2017 at 4:23 PM, Krishan Wijesena  wrote:

> Hi buddhimala,
>
> Can you check your payload of put method again, refer [1]
>
> [1] https://docs.wso2.com/display/AM210/Configuring+
> Caching#ConfiguringCaching-Responsecache
>
> Thanks,
> krishan.
>
> On Fri, Nov 24, 2017 at 2:18 PM, Buddhimala Ranasinghe <
> buddhim...@wso2.com> wrote:
>
>> Hi All,
>>
>> I'm trying a scenario where I need to have caching enabled to improve
>> perfomance at API level.So I enabled response caching from my API. The API
>> contains resources to perform CRUD operations.
>>
>> My problem is, when I try to invoke PUT method in my API after enabling
>> response caching, it gives me the following error.
>>
>> [2017-11-24 14:16:39,969] ERROR - JsonUtil #writeAsJson. Payload could
>> not be written as JSON. MessageID: urn:uuid:ccc5fb5c-ec7b-4e51-87
>> 9f-345cd8a54804
>> [2017-11-24 14:16:39,972] ERROR - PassThroughHttpSSLSender Failed to
>> submit the response
>> org.apache.axis2.AxisFault: Payload could not be written as JSON.
>> at org.apache.synapse.commons.json.JsonUtil.writeAsJson(JsonUti
>> l.java:276)
>> at org.apache.synapse.commons.json.JsonFormatter.writeTo(JsonFo
>> rmatter.java:62)
>> at org.apache.synapse.transport.passthru.PassThroughHttpSender.
>> submitResponse(PassThroughHttpSender.java:573)
>> at org.apache.synapse.transport.passthru.PassThroughHttpSender.
>> invoke(PassThroughHttpSender.java:264)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Send
>> er.java:230)
>> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(A
>> xis2SynapseEnvironment.java:531)
>> at org.apache.synapse.mediators.builtin.SendMediator.mediate(Se
>> ndMediator.java:118)
>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>> stractListMediator.java:97)
>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>> stractListMediator.java:59)
>> at org.apache.synapse.mediators.base.SequenceMediator.mediate(S
>> equenceMediator.java:158)
>> at org.apache.synapse.rest.Resource.process(Resource.java:343)
>> at org.apache.synapse.rest.API.process(API.java:338)
>> at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RES
>> TRequestHandler.java:90)
>> at org.apache.synapse.rest.RESTRequestHandler.process(RESTReque
>> stHandler.java:56)
>> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.inject
>> Message(Axis2SynapseEnvironment.java:304)
>> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handle
>> Message(SynapseCallbackReceiver.java:554)
>> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receiv
>> e(SynapseCallbackReceiver.java:188)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at org.apache.synapse.transport.passthru.ClientWorker.run(Clien
>> tWorker.java:262)
>> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.
>> run(NativeWorkerPool.java:172)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:748)
>> [2017-11-24 14:16:39,972] ERROR - Axis2Sender
>> Access-Control-Allow-Headers:authorization,Access-Control-Al
>> low-Origin,Content-Type,SOAPAction,Access-Control-Allow-
>> Methods:PUT,Access-Control-Allow-Origin:*,Content-Type:application/json;
>> charset=UTF-8,> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/;>> oapenv:Body/> Unexpected error sending message back
>> org.apache.axis2.AxisFault: Failed to submit the response
>> at org.apache.synapse.transport.passthru.PassThroughHttpSender.
>> handleException(PassThroughHttpSender.java:632)
>> at org.apache.synapse.transport.passthru.PassThroughHttpSender.
>> invoke(PassThroughHttpSender.java:266)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Send
>> er.java:230)
>> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(A
>> xis2SynapseEnvironment.java:531)
>> at org.apache.synapse.mediators.builtin.SendMediator.mediate(Se
>> ndMediator.java:118)
>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>> stractListMediator.java:97)
>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>> stractListMediator.java:59)
>> at org.apache.synapse.mediators.base.SequenceMediator.mediate(S
>> equenceMediator.java:158)
>> at org.apache.synapse.rest.Resource.process(Resource.java:343)
>> at org.apache.synapse.rest.API.process(API.java:338)
>> at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RES
>> 

Re: [Dev] [Architecture] WSO2 Enterprise Integrator 6.1.1-update10 Released !

[Jasintha Dasanayake]

HI Nandika

On Fri, Nov 24, 2017 at 2:16 PM, Nandika Jayawardana 
wrote:

> Actually, we have another 489 issues in DEVTOOLEI project which I think is
> also critically important since dev studio is the primary development tool
> the developers interact with. The perception generated from dev studio will
> have a lasting effect on the product quality.
>
> In order to reduce the bug count, we will start with
> classifying/prioritizing the issues.
>

 Please let me know if you need any help for this effort

/Jasintha

>
> 1. There could be many issues which are already fixed and not resolved or
> no longer relevant due to changes which can be resolved straight away.
> 2. For the relevant issues, we can classify them depending on the
> importance/relevance of the issue and identify the components which have
> the most number of critical issues and work on them one component at a
> time.
>
> Regards
> Nandika
>
> On Fri, Nov 24, 2017 at 12:14 PM, Vijitha Ekanayake 
> wrote:
>
>> Hi Samisa,
>>
>> We are continuously working on fixing the bugs reported under JIRA and
>> GitHub along with the EI 6 weekly updates. The plan is to pick a set up
>> issues by filtering the priority and label those for the upcoming update
>> release.
>>
>> Thanks,
>> Vijitha.
>>
>> On Fri, Nov 24, 2017 at 3:14 AM, Samisa Abeysinghe 
>> wrote:
>>
>>> We have 803 Jira and 265 Git open issues, what is the plan to flush
>>> them?
>>>
>>> Thanks,
>>> Samisa...
>>>
>>>
>>> Samisa Abeysinghe
>>>
>>> Chief Engineering and Delivery Officer
>>>
>>> WSO2 Inc.
>>> http://wso2.com
>>>
>>>
>>> On Fri, Nov 24, 2017 at 12:08 AM, Vijitha Ekanayake 
>>> wrote:
>>>

 Please find the correct link for the distribution: https://github.c
 om/wso2/product-ei/releases/download/v6.1.1-update10/wso2ei-
 6.1.1-update10.zip


 On Fri, Nov 24, 2017 at 12:01 AM, Vijitha Ekanayake 
 wrote:

> Hi all,
>
> The WSO2 Integration team is pleased to announce the release of
> Enterprise Integrator 6.1.1-update10. It is available for download from
> here
> 
> .
>

> *Tasks/Bug Fixes and Improvements*
>
> https://github.com/wso2/product-ei/issues?q=is%3Aissue+miles
> tone%3A6.1.1-update-10+is%3Aclosed
>
> *​​List of Open Issues*
>
> https://wso2.org/jira/issues/?filter=13994
>
> https://github.com/wso2/product-ei/issues?q=is%3Aopen+is%3Aissue
>
>
> *Mailing Lists*
>
> Join our mailing lists and correspond with the developers directly.
>
> Developer List : dev@wso2.org | Subscribe | Mail Archive
>
> WSO2 Architecture List: architect...@wso2.org
>
> User Forum : StackOverflow 
>
> *How To Contribute*
>
> Your feedback is most welcome!
>
> *Reporting Issues​*
>
> We encourage you to report issues, improvements and feature requests
> regarding WSO2 Integrator through WSO2 EI GIT Issues
> .
>
> ~ The WSO2 Integration Team ~
>

>


 --
 Vijitha Ekanayake
 Senior Software Engineer*, *WSO2, Inc.; http://wso2.com/
 Mobile : +94 777 24 73 39 | +94 718 74 44 08
 lean.enterprise.middleware

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


>>>
>>
>>
>> --
>> Vijitha Ekanayake
>> Senior Software Engineer*, *WSO2, Inc.; http://wso2.com/
>> Mobile : +94 777 24 73 39 | +94 718 74 44 08
>> lean.enterprise.middleware
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Nandika Jayawardana
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Jasintha Dasanayake**Associate Technical Lead*

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


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

Re: [Dev] [APIM]Cannot login to APIM Management console with admin credentials

[roshan wijesena]

So this is not because of java problem?

On Fri, Nov 24, 2017 at 10:24 PM Isuru Uyanage  wrote:

> Hi Irham,
> Yes it worked with *carbon/** with java build 1.8.0_144-b01.
>
>
> Thanks
> Isuru
>
> *Thanks and Best Regards,*
>
> *Isuru Uyanage*
> *Software Engineer - QA | WSO2*
> *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
> *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
> *
>
>
>
>
> On Fri, Nov 24, 2017 at 7:56 AM, Irham Iqbal  wrote:
>
>> Hi Isuru,
>>
>> The reason for the issue your facing is the request is not going
>> for /carbon/admin/* IMO if you making it /carbon/* it should work.
>>
>> Thanks,
>> Iqbal
>>
>> On Thu, Nov 23, 2017 at 8:20 PM, Bhathiya Jayasekara 
>> wrote:
>>
>>> Hi Roshan,
>>>
>>> No, that's not a public thread.
>>>
>>> Here[1] is the original bug.
>>>
>>> @Isuru: Make sure you don't have the previous version in your PATH
>>> variable.
>>>
>>> [1] https://bugs.openjdk.java.net/browse/JDK-8189789
>>>
>>> Thanks,
>>> Bhathiya
>>>
>>> On Thu, Nov 23, 2017 at 4:30 PM, Isuru Uyanage  wrote:
>>>
 Hi All,
 I downgraded Java to (build 1.8.0_144-b01) and restarted the APIM 2.1.0

 But still, I'm getting the same error. Any thoughts about this.

 *Thanks and Best Regards,*

 *Isuru Uyanage*
 *Software Engineer - QA | WSO2*
 *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
 *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
 *




 On Thu, Nov 23, 2017 at 1:22 PM, Isuru Uyanage 
 wrote:

> Hi All,
>
> I tried updating Owasp.CsrfGuard.Carbon.properties file, which is in
> $APIM_HOME/repository/conf/security folder by adding the below entry.
>
> org.owasp.csrfguard.unprotected.mgtconsolelogin=%servletContext%/carbon/admin/*
>
> I could log in to the Management console with admin credentials but
> once try to creating user/user roles, cannot proceed further and the same
> issue is repeating. I think the best option is to downgrade the java.
>
> Thanks,
>
> *Thanks and Best Regards,*
>
> *Isuru Uyanage*
> *Software Engineer - QA | WSO2*
> *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
> *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
> *
>
>
>
>
> On Thu, Nov 23, 2017 at 4:54 AM, roshan wijesena <
> roshan86...@gmail.com> wrote:
>
>> Hi Rumy,
>>
>> is this mail public ?, [Important][Critical] None of WSO2 products
>> are working with latest JDK.
>>
>> I am also facing the same problem, however downgrade java is not a
>> option for me :(
>>
>> On Wed, Nov 22, 2017 at 11:09 PM, Mushthaq Rumy 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Seems like the java version is causing this issue. This issue is
>>> there with java JDK 8u151. Please refer [1] for more details.
>>>
>>> [1] - [Important][Critical] None of WSO2 products are working with
>>> latest JDK [Was: GZIP decoding issue in APIM/EI when deployed in MC]
>>>
>>> Thanks & Regards,
>>> Mushthaq
>>>
>>> On Wed, Nov 22, 2017 at 3:35 PM, Irham Iqbal  wrote:
>>>
 Hi Isuru,

 The reason might the java version you're using.

 You can update the Owasp.CsrfGuard.Carbon.properties file, which
 is in $APIM_HOME/repository/conf/security folder with the
 bellowing entry to ignore this error, IMO it's better if you use the 
 proper
 java version.

 org.owasp.csrfguard.unprotected.mgtconsolelogin=%servletContext%/carbon/admin/*

 Thanks,
 Iqbal

 On Wed, Nov 22, 2017 at 3:08 PM, Isuru Uyanage 
 wrote:

> Hi All,
>
> I'm using wum updated pack (wso2am-2.1.0.1511201090302) for API
> Manager. After APIM server is started with the fresh pack, I can 
> navigate
> to Management Console. But once I'm trying to log in with admin
> credentials, I cannot log in. The error is as below.
>
> Error: 403 Forbidden
> JavaLogger potential cross-site request forgery (CSRF) attack
> thwarted (user:, ip:10.100.5.136, method:POST,
> uri:/carbon/admin/login_action.jsp, error:required token is missing 
> from
> the request)
>
> Affected Product Version:
> wum updated pack: wso2am-2.1.0.1511201090302.zip
>
> Environment details and versions:
>
> macOS High Sierra
> Version 10.13.1
> Google Chrome: Version 62.0.3202.94 (Official Build) (64-bit)
> Firefox: 57.0
>

Re: [Dev] [DEV][puppet-apim] pre-packed IS as the KM throwing The service cannot be found for the endpoint reference (EPR)

[Samitha Chathuranga]

Hi Nuwan,

Probably there is a connection issue from store node to is-as-km node. Can
you check whether the host mappings are correct in /etc/hosts file?

Regards,
Samitha

On Fri, Nov 24, 2017 at 12:34 PM, Chalitha Waldeniyage 
wrote:

> Hi Nuwan,
>
> I'm working on similar setup and this flow is working for me(using 22nd
> WUM pack). I'm suspecting your WUM updated pack is having some issue
> Can you please check on this.
>
> Thank you,
> Chalitha
>
>
> On Fri, Nov 24, 2017 at 12:21 PM, Nuwan Silva  wrote:
>
>> Hi Team,
>>
>> While deploying the IS as the KM via puppet I used [1] with the
>> pre-packaged IS that is updated through wum "wso2is-km-5.3.0.zip".
>> Installation was successful and after deploying I tried to generate keys
>> with the Default Application in the store. (please see below logs)
>>
>> I've notices this happens when the KM feature is not installed. but
>> shouldnt the pre-packaged wum downloadable IS instance come with the
>> feature installed?
>>
>> TID: [-1234] [] [2017-11-24 06:17:38,007] ERROR
>> {org.apache.axis2.engine.AxisEngine} -  The service cannot be found for
>> the endpoint reference (EPR) https://km.dev.wso2.org:9443/s
>> ervices/APIKeyMgtSubscriberService
>> org.apache.axis2.AxisFault: The service cannot be found for the endpoint
>> reference (EPR) https://km.dev.wso2.org:9443/s
>> ervices/APIKeyMgtSubscriberService
>> at org.apache.axis2.engine.DispatchPhase.checkPostConditions(Di
>> spatchPhase.java:78)
>> at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>> at org.apache.axis2.transport.http.HTTPTransportUtils.processHT
>> TPPostRequest(HTTPTransportUtils.java:173)
>> at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServl
>> et.java:147)
>> at org.wso2.carbon.core.transports.CarbonServlet.doPost(
>> CarbonServlet.java:231)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.eclipse.equinox.http.servlet.internal.ServletRegistratio
>> n.service(ServletRegistration.java:61)
>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce
>> ssAlias(ProxyServlet.java:128)
>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi
>> ce(ProxyServlet.java:68)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service
>> (DelegationServlet.java:68)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>> lter(ApplicationFilterChain.java:303)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>> licationFilterChain.java:208)
>> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilte
>> r.java:52)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>> lter(ApplicationFilterChain.java:241)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>> licationFilterChain.java:208)
>> at org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilte
>> r(HttpHeaderSecurityFilter.java:124)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>> lter(ApplicationFilterChain.java:241)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>> licationFilterChain.java:208)
>> at org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilte
>> r(CharacterSetFilter.java:61)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>> lter(ApplicationFilterChain.java:241)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>> licationFilterChain.java:208)
>> at org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilte
>> r(HttpHeaderSecurityFilter.java:124)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>> lter(ApplicationFilterChain.java:241)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>> licationFilterChain.java:208)
>> at org.apache.catalina.core.StandardWrapperValve.invoke(Standar
>> dWrapperValve.java:219)
>> at org.apache.catalina.core.StandardContextValve.invoke(Standar
>> dContextValve.java:110)
>> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(A
>> uthenticatorBase.java:506)
>> at org.apache.catalina.core.StandardHostValve.invoke(StandardHo
>> stValve.java:169)
>> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo
>> rtValve.java:103)
>> at org.wso2.carbon.identity.context.rewrite.valve.TenantContext
>> RewriteValve.invoke(TenantContextRewriteValve.java:80)
>> at org.wso2.carbon.identity.authz.valve.AuthorizationValve.
>> invoke(AuthorizationValve.java:91)
>> at org.wso2.carbon.identity.auth.valve.AuthenticationValve.invo
>> ke(AuthenticationValve.java:60)
>> at 

Re: [Dev] [DEV][puppet-apim]

[Samitha Chathuranga]

>
> I'm not sure whether we are using dep-sync now since in APIM docker
> patterns we removed depsync and added rsync.[1]
>
Using rsync [1] is completely external configuration with wso2 product
configs, hence different to the usage of svn-dep-sync. But if you follow up
with svn dep sync, required templates are already added to the template
files and so you have to add only the required hiera data. Anyway now we
recommend rsync over svn, so better to go with rsync.

[1] -
https://docs.wso2.com/display/AM210/Configuring+rsync+for+Deployment+Synchronization

On Fri, Nov 24, 2017 at 10:36 AM, Prasanna Dangalla 
wrote:

>
> On Fri, Nov 24, 2017 at 10:08 AM, Anuruddha Liyanarachchi <
> anurudd...@wso2.com> wrote:
>
>> Hi Nuwan,
>>
>> As per the current patterns, there is no HA in traffic manager. The
>> approach you have taken should work. However, you will need to configure
>> dep-sync between two nodes if you are deploying custom policies.
>>
> I'm not sure whether we are using dep-sync now since in APIM docker
> patterns we removed depsync and added rsync.[1]
>
> [1] - https://github.com/wso2/docker-apim/blob/v2.1.0/
> docker-compose/pattern-4/gateway-worker-2/worker-manager-rsync.sh
>
>>
>> On Fri, Nov 24, 2017 at 9:54 AM, Nuwan Silva  wrote:
>>
>>> Hi Team,
>>>
>>> While deploying the puppet-apim [1] I had an issue where there was no
>>> pattern for deploying Traffic Manager as an HA deployment. I added the
>>> following snippet to achieve HA in the cluster. Do we have another way of
>>> doing this? Please advise.
>>>
>>> wso2::clustering:
>>>   enabled: true
>>>   domain: tm.am.wso2.domain
>>>   sub_domain: mgt
>>>   local_member_host: "%{::ipaddress}"
>>>   local_member_port: 4000
>>> # WKA membership scheme
>>>   membership_scheme: wka
>>>   wka:
>>> members:
>>>   -
>>> hostname: 192.168.48.33
>>> port: 4000
>>>   -
>>> hostname: 192.168.48.34
>>> port: 4000
>>>
>>>
>>> [1] https://github.com/wso2/puppet-apim
>>> [2] https://github.com/wso2/puppet-apim/issues/47
>>>
>>> Cheers,
>>> NuwanS.
>>> --
>>>
>>>
>>> *Nuwan Silva*
>>> *Associate Technical Lead*
>>> Mobile: +9477 980 4543 <+94%2077%20980%204543>
>>>
>>> WSO2 Inc.
>>> lean . enterprise . middleware.
>>> http://www.wso2.com
>>>
>>
>>
>>
>> --
>> *Thanks and Regards,*
>> Anuruddha Lanka Liyanarachchi
>> Software Engineer - WSO2
>> Mobile : +94 (0) 712762611
>> Tel  : +94 112 145 345
>> a nurudd...@wso2.com
>>
>
>


-- 
Samitha Chathuranga
Software Engineer, WSO2 Inc.
lean.enterprise.middleware
Mobile: +94715123761

[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error occurs with Response caching enabled.

[Mushthaq Rumy]

Hi Buddhimala,

By looking at the error log it seem like the JSON conversion is not working
properly. Have you enabled the JSONStreamBuilder in axis2.xml?

Thanks & Regards,
Mushthaq

On Fri, Nov 24, 2017 at 4:23 PM, Krishan Wijesena  wrote:

> Hi buddhimala,
>
> Can you check your payload of put method again, refer [1]
>
> [1] https://docs.wso2.com/display/AM210/Configuring+
> Caching#ConfiguringCaching-Responsecache
>
> Thanks,
> krishan.
>
> On Fri, Nov 24, 2017 at 2:18 PM, Buddhimala Ranasinghe <
> buddhim...@wso2.com> wrote:
>
>> Hi All,
>>
>> I'm trying a scenario where I need to have caching enabled to improve
>> perfomance at API level.So I enabled response caching from my API. The API
>> contains resources to perform CRUD operations.
>>
>> My problem is, when I try to invoke PUT method in my API after enabling
>> response caching, it gives me the following error.
>>
>> [2017-11-24 14:16:39,969] ERROR - JsonUtil #writeAsJson. Payload could
>> not be written as JSON. MessageID: urn:uuid:ccc5fb5c-ec7b-4e51-87
>> 9f-345cd8a54804
>> [2017-11-24 14:16:39,972] ERROR - PassThroughHttpSSLSender Failed to
>> submit the response
>> org.apache.axis2.AxisFault: Payload could not be written as JSON.
>> at org.apache.synapse.commons.json.JsonUtil.writeAsJson(JsonUti
>> l.java:276)
>> at org.apache.synapse.commons.json.JsonFormatter.writeTo(JsonFo
>> rmatter.java:62)
>> at org.apache.synapse.transport.passthru.PassThroughHttpSender.
>> submitResponse(PassThroughHttpSender.java:573)
>> at org.apache.synapse.transport.passthru.PassThroughHttpSender.
>> invoke(PassThroughHttpSender.java:264)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Send
>> er.java:230)
>> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(A
>> xis2SynapseEnvironment.java:531)
>> at org.apache.synapse.mediators.builtin.SendMediator.mediate(Se
>> ndMediator.java:118)
>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>> stractListMediator.java:97)
>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>> stractListMediator.java:59)
>> at org.apache.synapse.mediators.base.SequenceMediator.mediate(S
>> equenceMediator.java:158)
>> at org.apache.synapse.rest.Resource.process(Resource.java:343)
>> at org.apache.synapse.rest.API.process(API.java:338)
>> at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RES
>> TRequestHandler.java:90)
>> at org.apache.synapse.rest.RESTRequestHandler.process(RESTReque
>> stHandler.java:56)
>> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.inject
>> Message(Axis2SynapseEnvironment.java:304)
>> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handle
>> Message(SynapseCallbackReceiver.java:554)
>> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receiv
>> e(SynapseCallbackReceiver.java:188)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at org.apache.synapse.transport.passthru.ClientWorker.run(Clien
>> tWorker.java:262)
>> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.
>> run(NativeWorkerPool.java:172)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:748)
>> [2017-11-24 14:16:39,972] ERROR - Axis2Sender
>> Access-Control-Allow-Headers:authorization,Access-Control-Al
>> low-Origin,Content-Type,SOAPAction,Access-Control-Allow-
>> Methods:PUT,Access-Control-Allow-Origin:*,Content-Type:application/json;
>> charset=UTF-8,> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/;>> oapenv:Body/> Unexpected error sending message back
>> org.apache.axis2.AxisFault: Failed to submit the response
>> at org.apache.synapse.transport.passthru.PassThroughHttpSender.
>> handleException(PassThroughHttpSender.java:632)
>> at org.apache.synapse.transport.passthru.PassThroughHttpSender.
>> invoke(PassThroughHttpSender.java:266)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Send
>> er.java:230)
>> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(A
>> xis2SynapseEnvironment.java:531)
>> at org.apache.synapse.mediators.builtin.SendMediator.mediate(Se
>> ndMediator.java:118)
>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>> stractListMediator.java:97)
>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>> stractListMediator.java:59)
>> at org.apache.synapse.mediators.base.SequenceMediator.mediate(S
>> equenceMediator.java:158)
>> at org.apache.synapse.rest.Resource.process(Resource.java:343)
>> at org.apache.synapse.rest.API.process(API.java:338)
>> at 

[Dev] [Architecture] AWS CloudFormation for WSO2 API Manager 2.1.0

[Chiranga Alwis]

Hi,

the WSO2 Installer Experience team is pleased to announce the release
of AWS CloudFormation for WSO2 API Manager 2.1.0.

This is the first release of AWS CloudFormation resources for WSO2 API
Manager version 2.1.0. It contains the WSO2 API Manager CloudFormation
template and the resources required to create WSO2 API Manager and WSO2 API
Manager Analytics Amazon Machine Images (AMIs).

The source and tag location for this release are available from here
.

WSO2 API Manager CloudFormation Template

The deployment of current release is based on WSO2 API Manager deployment
pattern-1
.
It deploys two WSO2 API Manager nodes publishing statistics to one WSO2 API
Manager Analytics node. The following AWS resources will be created:


   1.

   Virtual Private Cloud (VPC) with two public subnets and two private
   subnets
   2.

   Two API Manager Auto Scaling groups in private subnets
   3.

   An API Manager Analytics Auto Scaling group in one of the private subnets
   4.

   Relational Database Service (RDS) for API Manager and API Manager
   Analytics
   5.

   Elastic File System (EFS) for artifact sharing
   6.

   A NAT Gateway
   7.

   An Internet Gateway
   8.

   Amazon EC2 Security Groups
   9.

   Elastic Load Balancing (ELB) for API Manager
   10.

   Elastic Load Balancing (ELB) for API Manager Analytics


Quick Start Guide

https://github.com/wso2/cloudformation-apim/blob/master/README.md

*Reporting issues*
Issues can be reported to https://github.com/wso2/cloudformation-apim/issues
.

Thank you,
WSO2 Installer Experience team

-- 
Yours sincerely,

*Chiranga Alwis*
Software Engineer | WSO2

*Mobile : *+94775930497 <+94%2077%20593%200497>
*Email: *chirangaal...@gmail.com
*LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9
*Medium:* https://medium.com/@chirangaalwis


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

Re: [Dev] [DEV][puppet-apim] pre-packed IS as the KM throwing The service cannot be found for the endpoint reference (EPR)

[Nuwan Silva]

Checked the /etc/hosts file and it seems to be pointing correctly. Im using
the latest wum packs.

Cheers,
NuwanS.

On Fri, Nov 24, 2017 at 1:14 PM, Samitha Chathuranga 
wrote:

> Hi Nuwan,
>
> Probably there is a connection issue from store node to is-as-km node. Can
> you check whether the host mappings are correct in /etc/hosts file?
>
> Regards,
> Samitha
>
> On Fri, Nov 24, 2017 at 12:34 PM, Chalitha Waldeniyage 
> wrote:
>
>> Hi Nuwan,
>>
>> I'm working on similar setup and this flow is working for me(using 22nd
>> WUM pack). I'm suspecting your WUM updated pack is having some issue
>> Can you please check on this.
>>
>> Thank you,
>> Chalitha
>>
>>
>> On Fri, Nov 24, 2017 at 12:21 PM, Nuwan Silva  wrote:
>>
>>> Hi Team,
>>>
>>> While deploying the IS as the KM via puppet I used [1] with the
>>> pre-packaged IS that is updated through wum "wso2is-km-5.3.0.zip".
>>> Installation was successful and after deploying I tried to generate keys
>>> with the Default Application in the store. (please see below logs)
>>>
>>> I've notices this happens when the KM feature is not installed. but
>>> shouldnt the pre-packaged wum downloadable IS instance come with the
>>> feature installed?
>>>
>>> TID: [-1234] [] [2017-11-24 06:17:38,007] ERROR
>>> {org.apache.axis2.engine.AxisEngine} -  The service cannot be found for
>>> the endpoint reference (EPR) https://km.dev.wso2.org:9443/s
>>> ervices/APIKeyMgtSubscriberService
>>> org.apache.axis2.AxisFault: The service cannot be found for the endpoint
>>> reference (EPR) https://km.dev.wso2.org:9443/s
>>> ervices/APIKeyMgtSubscriberService
>>> at org.apache.axis2.engine.DispatchPhase.checkPostConditions(Di
>>> spatchPhase.java:78)
>>> at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
>>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>>> at org.apache.axis2.transport.http.HTTPTransportUtils.processHT
>>> TPPostRequest(HTTPTransportUtils.java:173)
>>> at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServl
>>> et.java:147)
>>> at org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonS
>>> ervlet.java:231)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>>> at org.eclipse.equinox.http.servlet.internal.ServletRegistratio
>>> n.service(ServletRegistration.java:61)
>>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce
>>> ssAlias(ProxyServlet.java:128)
>>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi
>>> ce(ProxyServlet.java:68)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>>> at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service
>>> (DelegationServlet.java:68)
>>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>>> lter(ApplicationFilterChain.java:303)
>>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>>> licationFilterChain.java:208)
>>> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilte
>>> r.java:52)
>>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>>> lter(ApplicationFilterChain.java:241)
>>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>>> licationFilterChain.java:208)
>>> at org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilte
>>> r(HttpHeaderSecurityFilter.java:124)
>>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>>> lter(ApplicationFilterChain.java:241)
>>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>>> licationFilterChain.java:208)
>>> at org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilte
>>> r(CharacterSetFilter.java:61)
>>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>>> lter(ApplicationFilterChain.java:241)
>>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>>> licationFilterChain.java:208)
>>> at org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilte
>>> r(HttpHeaderSecurityFilter.java:124)
>>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>>> lter(ApplicationFilterChain.java:241)
>>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>>> licationFilterChain.java:208)
>>> at org.apache.catalina.core.StandardWrapperValve.invoke(Standar
>>> dWrapperValve.java:219)
>>> at org.apache.catalina.core.StandardContextValve.invoke(Standar
>>> dContextValve.java:110)
>>> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(A
>>> uthenticatorBase.java:506)
>>> at org.apache.catalina.core.StandardHostValve.invoke(StandardHo
>>> stValve.java:169)
>>> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo
>>> rtValve.java:103)
>>> at org.wso2.carbon.identity.context.rewrite.valve.TenantContext
>>> 

[Dev] [EI] Required permission to invoke secure proxy

[Godwin Shrimal]

Hi Devs,

What are the required permissions for the user to invoking a secure proxy
service using UserTokenPolicy?

Thanks
Godwin

-- 
*Godwin Amila Shrimal*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: *+94772264165*
linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
*
twitter: https://twitter.com/godwinamila

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

Re: [Dev] How to compare two synapse properties in ESB

[Senduran Balasubramaniyam]

On Fri, Nov 24, 2017 at 10:20 AM, Thivya Mahenthirarasa 
wrote:

> Hi Dev,
>
> Requirement: I need to check a condition before loop back to out sequence
> whether the USER_NAME and PATIENT_ID are equal.
>
> I'm using a filter in my in sequence.
>
> 
>
> The above configuration is evaluated as synapse xpath and it is valid.
Should work. Make sure you have both the properties not having null values.

>
>
>   
>
>
>
> I'm seeing always "evaluates to false and no else path - skipping child
> mediators" in console even in the case of synapse properties USER_NAME and
> PATIENT_ID are equal.
>
> Could anyone help?
>
>
> Thanks,
> Thivya
>
>
> --
>
> *Thivya Mahenthirarasa*
>
> *Software Engineer -Support Team | WSO2*
>
>
> *Email: thi...@wso2.com *
>
> *Mobile: +94766461966 <+94%2076%20646%201966> *
> *Web: http://wso2.com *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Senduran *
Senior Software Engineer,
WSO2, Inc.;  http://wso2.com/ 
Mobile: +94 77 952 6548
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][puppet-apim] pre-packed IS as the KM throwing The service cannot be found for the endpoint reference (EPR)

[Nuwan Silva]

Hi Team,

While deploying the IS as the KM via puppet I used [1] with the
pre-packaged IS that is updated through wum "wso2is-km-5.3.0.zip".
Installation was successful and after deploying I tried to generate keys
with the Default Application in the store. (please see below logs)

I've notices this happens when the KM feature is not installed. but
shouldnt the pre-packaged wum downloadable IS instance come with the
feature installed?

TID: [-1234] [] [2017-11-24 06:17:38,007] ERROR
{org.apache.axis2.engine.AxisEngine} -  The service cannot be found for the
endpoint reference (EPR)
https://km.dev.wso2.org:9443/services/APIKeyMgtSubscriberService
org.apache.axis2.AxisFault: The service cannot be found for the endpoint
reference (EPR)
https://km.dev.wso2.org:9443/services/APIKeyMgtSubscriberService
at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:78)
at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:147)
at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:124)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:124)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:506)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at
org.wso2.carbon.identity.context.rewrite.valve.TenantContextRewriteValve.invoke(TenantContextRewriteValve.java:80)
at
org.wso2.carbon.identity.authz.valve.AuthorizationValve.invoke(AuthorizationValve.java:91)
at
org.wso2.carbon.identity.auth.valve.AuthenticationValve.invoke(AuthenticationValve.java:60)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:962)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
at

Re: [Dev] [APIM]Cannot login to APIM Management console with admin credentials

[roshan wijesena]

Ok, thanks Bhathiya.

On Fri, Nov 24, 2017 at 11:02 PM Bhathiya Jayasekara 
wrote:

> It is. What Irham has suggested is a workaround to fix one of a few issues
> which occur due to that bug, and it opens up a security vulnerability too.
> In a production environment, you shouldn't do that.
>
> Thanks,
> Bhathiya
>
> On Fri, Nov 24, 2017 at 4:56 PM, roshan wijesena 
> wrote:
>
>> So this is not because of java problem?
>>
>> On Fri, Nov 24, 2017 at 10:24 PM Isuru Uyanage  wrote:
>>
>>> Hi Irham,
>>> Yes it worked with *carbon/** with java build 1.8.0_144-b01.
>>>
>>>
>>> Thanks
>>> Isuru
>>>
>>> *Thanks and Best Regards,*
>>>
>>> *Isuru Uyanage*
>>> *Software Engineer - QA | WSO2*
>>> *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
>>> *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
>>> *
>>>
>>>
>>>
>>>
>>> On Fri, Nov 24, 2017 at 7:56 AM, Irham Iqbal  wrote:
>>>
 Hi Isuru,

 The reason for the issue your facing is the request is not going
 for /carbon/admin/* IMO if you making it /carbon/* it should work.

 Thanks,
 Iqbal

 On Thu, Nov 23, 2017 at 8:20 PM, Bhathiya Jayasekara  wrote:

> Hi Roshan,
>
> No, that's not a public thread.
>
> Here[1] is the original bug.
>
> @Isuru: Make sure you don't have the previous version in your PATH
> variable.
>
> [1] https://bugs.openjdk.java.net/browse/JDK-8189789
>
> Thanks,
> Bhathiya
>
> On Thu, Nov 23, 2017 at 4:30 PM, Isuru Uyanage 
> wrote:
>
>> Hi All,
>> I downgraded Java to (build 1.8.0_144-b01) and restarted the APIM
>> 2.1.0
>>
>> But still, I'm getting the same error. Any thoughts about this.
>>
>> *Thanks and Best Regards,*
>>
>> *Isuru Uyanage*
>> *Software Engineer - QA | WSO2*
>> *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
>> *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
>> *
>>
>>
>>
>>
>> On Thu, Nov 23, 2017 at 1:22 PM, Isuru Uyanage 
>> wrote:
>>
>>> Hi All,
>>>
>>> I tried updating Owasp.CsrfGuard.Carbon.properties file, which is
>>> in $APIM_HOME/repository/conf/security folder by adding the below
>>> entry.
>>>
>>> org.owasp.csrfguard.unprotected.mgtconsolelogin=%servletContext%/carbon/admin/*
>>>
>>> I could log in to the Management console with admin credentials but
>>> once try to creating user/user roles, cannot proceed further and the 
>>> same
>>> issue is repeating. I think the best option is to downgrade the java.
>>>
>>> Thanks,
>>>
>>> *Thanks and Best Regards,*
>>>
>>> *Isuru Uyanage*
>>> *Software Engineer - QA | WSO2*
>>> *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
>>> *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
>>> *
>>>
>>>
>>>
>>>
>>> On Thu, Nov 23, 2017 at 4:54 AM, roshan wijesena <
>>> roshan86...@gmail.com> wrote:
>>>
 Hi Rumy,

 is this mail public ?, [Important][Critical] None of WSO2 products
 are working with latest JDK.

 I am also facing the same problem, however downgrade java is not a
 option for me :(

 On Wed, Nov 22, 2017 at 11:09 PM, Mushthaq Rumy 
 wrote:

> Hi Isuru,
>
> Seems like the java version is causing this issue. This issue is
> there with java JDK 8u151. Please refer [1] for more details.
>
> [1] - [Important][Critical] None of WSO2 products are working
> with latest JDK [Was: GZIP decoding issue in APIM/EI when deployed in 
> MC]
>
> Thanks & Regards,
> Mushthaq
>
> On Wed, Nov 22, 2017 at 3:35 PM, Irham Iqbal 
> wrote:
>
>> Hi Isuru,
>>
>> The reason might the java version you're using.
>>
>> You can update the Owasp.CsrfGuard.Carbon.properties file, which
>> is in $APIM_HOME/repository/conf/security folder with the
>> bellowing entry to ignore this error, IMO it's better if you use the 
>> proper
>> java version.
>>
>> org.owasp.csrfguard.unprotected.mgtconsolelogin=%servletContext%/carbon/admin/*
>>
>> Thanks,
>> Iqbal
>>
>> On Wed, Nov 22, 2017 at 3:08 PM, Isuru Uyanage 
>> wrote:
>>
>>> Hi All,
>>>
>>> I'm using wum updated pack (wso2am-2.1.0.1511201090302) for API
>>> Manager. After APIM server is started with the fresh pack, I can 
>>> 

Re: [Dev] IS migration client usage of class.forName()

[Ruwan Abeykoon]

Hi Rasika,
The problem this needs to address are,
1. The IS new version connected to old schema on database. The server
should/can not start until migration completes.
2. Migration should only happen when the "migration client jar" is present
(and the jvm parameter present-in new way)
3. Migration should not be attempted on normal server starts.
4. The pack which has migration client installed is not a normal server
5. Migration client needs most of the other java packages(related to
identity server) exposed. Hence OSGI needs to be partially active.

Cheers,
Ruwan


On Fri, Nov 24, 2017 at 5:24 PM, Rasika Perera  wrote:

> Hi Dhanushka and All,
> ​
> ​I don't understand the exact context here. Have few questions based on
> what you have mentioned.
>
> Migration client is called from the identity.core bundle at the
>> activation level
>>
> Would that mean identity.core has a dependency to the Migration Client?​
>
> This is done in that manner because we needed that to run before any of
>> the identity bundles get activated
>
> How does the migration client gets activated if it is not an OSGi bundle ?
>
> In this discussion Ruwan suggested to use a jvm parameter and wait for the
>> migration bundle if jvm parameter is present.
>
> ​If the migration client is a non OSGi JAR +1 for the approach. Or else
> can't we use OSGi declarative services for this relationship?
>
> ​Thanks,
> Rasika​
>
>
> On Fri, Nov 24, 2017 at 12:10 PM, Danushka Fernando 
> wrote:
>
>> Hi All
>>
>> Currently the migration client is developed as an dropin to the server
>> package. Migration client is called from the identity.core bundle at the
>> activation level. This is done in that manner because we needed that to run
>> before any of the identity bundles get activated. So here we are loading
>> the migration client class with Class.forName().
>>
>> Since this is not a good OSGI pattern, we (Myself, Harsha, Ruwan, Sagara)
>> had a discussion over this. In this discussion Ruwan suggested to use a jvm
>> parameter and wait for the migration bundle if jvm parameter is present. I
>> am going to tryout this solution.
>>
>> Any suggestions would be appreciated.
>>
>> Thanks & Regards
>> Danushka Fernando
>> Associate Tech Lead
>> WSO2 inc. http://wso2.com/
>> Mobile : +94716332729 <+94%2071%20633%202729>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> With Regards,
>
> *Rasika Perera*
> Senior Software Engineer
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> 
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Identity Server 5.4.0 Alpha 10 Released !!!

[Jayanga Kaushalya]

The WSO2 Identity and Access Management team is pleased to announce the
release of WSO2 Identity Server 5.4.0 Alpha 10.

You can build the distribution from the source tag https://github.com/wso2/
product-is/releases/tag/v5.4.0-alpha10 following the steps below.


*Building from the source*

   1. Install Java8 or above
   2. Install Apache Maven 3.x.x(https://maven.apache.org/download.cgi#)
   3. Get a clone from https://github.com/wso2/product-is.git and checkout
   to v5.4.0-alpha10 tag or you can directly download the source for the tag
   from https://github.com/wso2/product-is/releases/tag/v5.4.0-alpha10
   4. Run the one of the below maven commands from product-is directory,
  - *mvn** clean install* (To build the binary and source distributions
  with the tests)
  - *mvn** clean install -Dmaven.test.skip=true* (To build the binary
  and source distributions, without running any of the
unit/integration tests)
   5. You can find the wso2is-5.4.0-alpha10.zip binary distribution in
   product-is/modules/distribution/target directory.

The following list contains all the features, improvements, and bug fixes
available with the WSO2 Identity Server 5.4.0 Alpha 10 release.

Patch

   - [IDENTITY-6299 ] - User
   creation via SCIM API does not return updated attribute values of the user
   - [IDENTITY-6800 ] - SAML
   Logout does not work as expected
   - [IDENTITY-6914 ] - Account
   creation (Adding users) take extensive amount of time when a large number
   of confirmation codes are present in the registry
   - [IDENTITY-6921 ] -
   Updating supported grant types of an oauth application through soap service
   will cause to return tokens for invalid user

Bug

   - [IDENTITY-3754 ] -
   Identity Server is only reading the http response status code, not the SAML
   LogoutResponse Messsage
   - [IDENTITY-5031 ] -
   RegistryException Unable to create fixed remote mounts for the initial SAML
   SSO request
   - [IDENTITY-5887 ] -
   commonauth logout throws NPE intermittently
   - [IDENTITY-6078 ] - SSO
   login not responding for some users
   - [IDENTITY-6347 ] - Not
   support some valid URL encoding character for Callback URL when creating
   oauth app
   - [IDENTITY-6356 ] - Self
   sign up flow gives an error in backend when trying to login before user is
   verified
   - [IDENTITY-6363 ] - Content
   of the sts-client.sh is wrong
   - [IDENTITY-6392 ] -
   refresh_grant is not working with RenewRefreshTokenForRefreshGrant=false
   - [IDENTITY-6408 ] -
   Self-signup-REST api - unlocks the account even if the validation is done
   aginst a different tenant domain
   - [IDENTITY-6420 ] - The
   "sub" value is not consistent when invoking UserInfo Endpoint with enabled
   email as user name
   - [IDENTITY-6427 ] - Dumb
   mode update user/group and delete user/group doesn't work
   - [IDENTITY-6448 ] - Error
   while creating saml app with metadata file or url
   - [IDENTITY-6470 ] - When
   invoking .well-known/openid-configuration it returns deprecated DCR
   endpoint
   - [IDENTITY-6548 ] - Subject
   identifier in id_token and user_info is different when "Use tenant domain
   in local subject identifier" config is enabled in SP
   - [IDENTITY-6570 ] -
   Previously added Inbound Authentication Configuration is not visible inside
   SAML2 Web SSO Configuration and adding the same lateron gives a duplication
   error
   - [IDENTITY-6583 ] -
   Assigning groups to users does not provisioned correctly in SCIM outbound
   provisioning
   - [IDENTITY-6679 ] - Mapping
   Roles are not updating accordingly in User/Group update in SCIM outbound
   provisioning
   - [IDENTITY-6702 ] - When
   the Federation Proxy is trying to authenticate with the Federation Hub, the
   SAML Assertion is not found in the Response
   - [IDENTITY-6719 ] - OAuth
   Client Secret gets corrupted or disappeared after TokenPersistenceProcessor
   is set to EncryptionDecryptionPersistenceProcessor
   - [IDENTITY-6765 

Re: [Dev] Error occurs with Response caching enabled.

[Samitha Chathuranga]

Hi Buddhimala,

Same error is reported here [1] and fixed with esb 5.1.0. Please check with
it.

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

Regards,
Samitha

On Fri, Nov 24, 2017 at 2:18 PM, Buddhimala Ranasinghe 
wrote:

> Hi All,
>
> I'm trying a scenario where I need to have caching enabled to improve
> perfomance at API level.So I enabled response caching from my API. The API
> contains resources to perform CRUD operations.
>
> My problem is, when I try to invoke PUT method in my API after enabling
> response caching, it gives me the following error.
>
> [2017-11-24 14:16:39,969] ERROR - JsonUtil #writeAsJson. Payload could not
> be written as JSON. MessageID: urn:uuid:ccc5fb5c-ec7b-4e51-
> 879f-345cd8a54804
> [2017-11-24 14:16:39,972] ERROR - PassThroughHttpSSLSender Failed to
> submit the response
> org.apache.axis2.AxisFault: Payload could not be written as JSON.
> at org.apache.synapse.commons.json.JsonUtil.writeAsJson(
> JsonUtil.java:276)
> at org.apache.synapse.commons.json.JsonFormatter.writeTo(
> JsonFormatter.java:62)
> at org.apache.synapse.transport.passthru.PassThroughHttpSender.
> submitResponse(PassThroughHttpSender.java:573)
> at org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(
> PassThroughHttpSender.java:264)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at org.apache.synapse.core.axis2.Axis2Sender.sendBack(
> Axis2Sender.java:230)
> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(
> Axis2SynapseEnvironment.java:531)
> at org.apache.synapse.mediators.builtin.SendMediator.mediate(
> SendMediator.java:118)
> at org.apache.synapse.mediators.AbstractListMediator.mediate(
> AbstractListMediator.java:97)
> at org.apache.synapse.mediators.AbstractListMediator.mediate(
> AbstractListMediator.java:59)
> at org.apache.synapse.mediators.base.SequenceMediator.mediate(
> SequenceMediator.java:158)
> at org.apache.synapse.rest.Resource.process(Resource.java:343)
> at org.apache.synapse.rest.API.process(API.java:338)
> at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(
> RESTRequestHandler.java:90)
> at org.apache.synapse.rest.RESTRequestHandler.process(
> RESTRequestHandler.java:56)
> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.
> injectMessage(Axis2SynapseEnvironment.java:304)
> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.
> handleMessage(SynapseCallbackReceiver.java:554)
> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(
> SynapseCallbackReceiver.java:188)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at org.apache.synapse.transport.passthru.ClientWorker.run(
> ClientWorker.java:262)
> at org.apache.axis2.transport.base.threads.NativeWorkerPool$
> 1.run(NativeWorkerPool.java:172)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> [2017-11-24 14:16:39,972] ERROR - Axis2Sender Access-Control-Allow-Headers:
> authorization,Access-Control-Allow-Origin,Content-Type,
> SOAPAction,Access-Control-Allow-Methods:PUT,Access-Control-Allow-Origin:*,Content-Type:application/json;
> charset=UTF-8, xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/;><
> soapenv:Body/> Unexpected error sending message back
> org.apache.axis2.AxisFault: Failed to submit the response
> at org.apache.synapse.transport.passthru.PassThroughHttpSender.
> handleException(PassThroughHttpSender.java:632)
> at org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(
> PassThroughHttpSender.java:266)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at org.apache.synapse.core.axis2.Axis2Sender.sendBack(
> Axis2Sender.java:230)
> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(
> Axis2SynapseEnvironment.java:531)
> at org.apache.synapse.mediators.builtin.SendMediator.mediate(
> SendMediator.java:118)
> at org.apache.synapse.mediators.AbstractListMediator.mediate(
> AbstractListMediator.java:97)
> at org.apache.synapse.mediators.AbstractListMediator.mediate(
> AbstractListMediator.java:59)
> at org.apache.synapse.mediators.base.SequenceMediator.mediate(
> SequenceMediator.java:158)
> at org.apache.synapse.rest.Resource.process(Resource.java:343)
> at org.apache.synapse.rest.API.process(API.java:338)
> at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(
> RESTRequestHandler.java:90)
> at org.apache.synapse.rest.RESTRequestHandler.process(
> RESTRequestHandler.java:56)
> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.
> injectMessage(Axis2SynapseEnvironment.java:304)
> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.
> handleMessage(SynapseCallbackReceiver.java:554)
> at 

Re: [Dev] [APIM]Cannot login to APIM Management console with admin credentials

[Bhathiya Jayasekara]

It is. What Irham has suggested is a workaround to fix one of a few issues
which occur due to that bug, and it opens up a security vulnerability too.
In a production environment, you shouldn't do that.

Thanks,
Bhathiya

On Fri, Nov 24, 2017 at 4:56 PM, roshan wijesena 
wrote:

> So this is not because of java problem?
>
> On Fri, Nov 24, 2017 at 10:24 PM Isuru Uyanage  wrote:
>
>> Hi Irham,
>> Yes it worked with *carbon/** with java build 1.8.0_144-b01.
>>
>>
>> Thanks
>> Isuru
>>
>> *Thanks and Best Regards,*
>>
>> *Isuru Uyanage*
>> *Software Engineer - QA | WSO2*
>> *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
>> *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
>> *
>>
>>
>>
>>
>> On Fri, Nov 24, 2017 at 7:56 AM, Irham Iqbal  wrote:
>>
>>> Hi Isuru,
>>>
>>> The reason for the issue your facing is the request is not going
>>> for /carbon/admin/* IMO if you making it /carbon/* it should work.
>>>
>>> Thanks,
>>> Iqbal
>>>
>>> On Thu, Nov 23, 2017 at 8:20 PM, Bhathiya Jayasekara 
>>> wrote:
>>>
 Hi Roshan,

 No, that's not a public thread.

 Here[1] is the original bug.

 @Isuru: Make sure you don't have the previous version in your PATH
 variable.

 [1] https://bugs.openjdk.java.net/browse/JDK-8189789

 Thanks,
 Bhathiya

 On Thu, Nov 23, 2017 at 4:30 PM, Isuru Uyanage 
 wrote:

> Hi All,
> I downgraded Java to (build 1.8.0_144-b01) and restarted the APIM 2.1.0
>
> But still, I'm getting the same error. Any thoughts about this.
>
> *Thanks and Best Regards,*
>
> *Isuru Uyanage*
> *Software Engineer - QA | WSO2*
> *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
> *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
> *
>
>
>
>
> On Thu, Nov 23, 2017 at 1:22 PM, Isuru Uyanage 
> wrote:
>
>> Hi All,
>>
>> I tried updating Owasp.CsrfGuard.Carbon.properties file, which is in
>> $APIM_HOME/repository/conf/security folder by adding the below entry.
>> org.owasp.csrfguard.unprotected.mgtconsolelogin=%
>> servletContext%/carbon/admin/*
>>
>> I could log in to the Management console with admin credentials but
>> once try to creating user/user roles, cannot proceed further and the same
>> issue is repeating. I think the best option is to downgrade the java.
>>
>> Thanks,
>>
>> *Thanks and Best Regards,*
>>
>> *Isuru Uyanage*
>> *Software Engineer - QA | WSO2*
>> *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
>> *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
>> *
>>
>>
>>
>>
>> On Thu, Nov 23, 2017 at 4:54 AM, roshan wijesena <
>> roshan86...@gmail.com> wrote:
>>
>>> Hi Rumy,
>>>
>>> is this mail public ?, [Important][Critical] None of WSO2 products
>>> are working with latest JDK.
>>>
>>> I am also facing the same problem, however downgrade java is not a
>>> option for me :(
>>>
>>> On Wed, Nov 22, 2017 at 11:09 PM, Mushthaq Rumy 
>>> wrote:
>>>
 Hi Isuru,

 Seems like the java version is causing this issue. This issue is
 there with java JDK 8u151. Please refer [1] for more details.

 [1] - [Important][Critical] None of WSO2 products are working with
 latest JDK [Was: GZIP decoding issue in APIM/EI when deployed in MC]

 Thanks & Regards,
 Mushthaq

 On Wed, Nov 22, 2017 at 3:35 PM, Irham Iqbal 
 wrote:

> Hi Isuru,
>
> The reason might the java version you're using.
>
> You can update the Owasp.CsrfGuard.Carbon.properties file, which
> is in $APIM_HOME/repository/conf/security folder with the
> bellowing entry to ignore this error, IMO it's better if you use the 
> proper
> java version.
> org.owasp.csrfguard.unprotected.mgtconsolelogin=%
> servletContext%/carbon/admin/*
>
> Thanks,
> Iqbal
>
> On Wed, Nov 22, 2017 at 3:08 PM, Isuru Uyanage 
> wrote:
>
>> Hi All,
>>
>> I'm using wum updated pack (wso2am-2.1.0.1511201090302) for API
>> Manager. After APIM server is started with the fresh pack, I can 
>> navigate
>> to Management Console. But once I'm trying to log in with admin
>> credentials, I cannot log in. The error is as below.
>>
>> Error: 403 Forbidden
>> JavaLogger potential cross-site request forgery (CSRF) attack
>> thwarted (user:, 

Re: [Dev] IS migration client usage of class.forName()

[Rasika Perera]

Hi Dhanushka and All,
​
​I don't understand the exact context here. Have few questions based on
what you have mentioned.

Migration client is called from the identity.core bundle at the activation
> level
>
Would that mean identity.core has a dependency to the Migration Client?​

This is done in that manner because we needed that to run before any of the
> identity bundles get activated

How does the migration client gets activated if it is not an OSGi bundle ?

In this discussion Ruwan suggested to use a jvm parameter and wait for the
> migration bundle if jvm parameter is present.

​If the migration client is a non OSGi JAR +1 for the approach. Or else
can't we use OSGi declarative services for this relationship?

​Thanks,
Rasika​


On Fri, Nov 24, 2017 at 12:10 PM, Danushka Fernando 
wrote:

> Hi All
>
> Currently the migration client is developed as an dropin to the server
> package. Migration client is called from the identity.core bundle at the
> activation level. This is done in that manner because we needed that to run
> before any of the identity bundles get activated. So here we are loading
> the migration client class with Class.forName().
>
> Since this is not a good OSGI pattern, we (Myself, Harsha, Ruwan, Sagara)
> had a discussion over this. In this discussion Ruwan suggested to use a jvm
> parameter and wait for the migration bundle if jvm parameter is present. I
> am going to tryout this solution.
>
> Any suggestions would be appreciated.
>
> Thanks & Regards
> Danushka Fernando
> Associate Tech Lead
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729 <+94%2071%20633%202729>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
With Regards,

*Rasika Perera*
Senior Software Engineer
LinkedIn: http://lk.linkedin.com/in/rasika90



WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM]Cannot login to APIM Management console with admin credentials

[Isuru Uyanage]

Hi Irham,
Yes it worked with *carbon/** with java build 1.8.0_144-b01.


Thanks
Isuru

*Thanks and Best Regards,*

*Isuru Uyanage*
*Software Engineer - QA | WSO2*
*Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
*LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
*




On Fri, Nov 24, 2017 at 7:56 AM, Irham Iqbal  wrote:

> Hi Isuru,
>
> The reason for the issue your facing is the request is not going
> for /carbon/admin/* IMO if you making it /carbon/* it should work.
>
> Thanks,
> Iqbal
>
> On Thu, Nov 23, 2017 at 8:20 PM, Bhathiya Jayasekara 
> wrote:
>
>> Hi Roshan,
>>
>> No, that's not a public thread.
>>
>> Here[1] is the original bug.
>>
>> @Isuru: Make sure you don't have the previous version in your PATH
>> variable.
>>
>> [1] https://bugs.openjdk.java.net/browse/JDK-8189789
>>
>> Thanks,
>> Bhathiya
>>
>> On Thu, Nov 23, 2017 at 4:30 PM, Isuru Uyanage  wrote:
>>
>>> Hi All,
>>> I downgraded Java to (build 1.8.0_144-b01) and restarted the APIM 2.1.0
>>>
>>> But still, I'm getting the same error. Any thoughts about this.
>>>
>>> *Thanks and Best Regards,*
>>>
>>> *Isuru Uyanage*
>>> *Software Engineer - QA | WSO2*
>>> *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
>>> *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
>>> *
>>>
>>>
>>>
>>>
>>> On Thu, Nov 23, 2017 at 1:22 PM, Isuru Uyanage  wrote:
>>>
 Hi All,

 I tried updating Owasp.CsrfGuard.Carbon.properties file, which is in
 $APIM_HOME/repository/conf/security folder by adding the below entry.
 org.owasp.csrfguard.unprotected.mgtconsolelogin=%servletCont
 ext%/carbon/admin/*

 I could log in to the Management console with admin credentials but
 once try to creating user/user roles, cannot proceed further and the same
 issue is repeating. I think the best option is to downgrade the java.

 Thanks,

 *Thanks and Best Regards,*

 *Isuru Uyanage*
 *Software Engineer - QA | WSO2*
 *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
 *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
 *




 On Thu, Nov 23, 2017 at 4:54 AM, roshan wijesena  wrote:

> Hi Rumy,
>
> is this mail public ?, [Important][Critical] None of WSO2 products
> are working with latest JDK.
>
> I am also facing the same problem, however downgrade java is not a
> option for me :(
>
> On Wed, Nov 22, 2017 at 11:09 PM, Mushthaq Rumy 
> wrote:
>
>> Hi Isuru,
>>
>> Seems like the java version is causing this issue. This issue is
>> there with java JDK 8u151. Please refer [1] for more details.
>>
>> [1] - [Important][Critical] None of WSO2 products are working with
>> latest JDK [Was: GZIP decoding issue in APIM/EI when deployed in MC]
>>
>> Thanks & Regards,
>> Mushthaq
>>
>> On Wed, Nov 22, 2017 at 3:35 PM, Irham Iqbal  wrote:
>>
>>> Hi Isuru,
>>>
>>> The reason might the java version you're using.
>>>
>>> You can update the Owasp.CsrfGuard.Carbon.properties file, which is
>>> in $APIM_HOME/repository/conf/security folder with the bellowing
>>> entry to ignore this error, IMO it's better if you use the proper java
>>> version.
>>> org.owasp.csrfguard.unprotected.mgtconsolelogin=%servletCont
>>> ext%/carbon/admin/*
>>>
>>> Thanks,
>>> Iqbal
>>>
>>> On Wed, Nov 22, 2017 at 3:08 PM, Isuru Uyanage 
>>> wrote:
>>>
 Hi All,

 I'm using wum updated pack (wso2am-2.1.0.1511201090302) for API
 Manager. After APIM server is started with the fresh pack, I can 
 navigate
 to Management Console. But once I'm trying to log in with admin
 credentials, I cannot log in. The error is as below.

 Error: 403 Forbidden
 JavaLogger potential cross-site request forgery (CSRF) attack
 thwarted (user:, ip:10.100.5.136, method:POST,
 uri:/carbon/admin/login_action.jsp, error:required token is
 missing from the request)

 Affected Product Version:
 wum updated pack: wso2am-2.1.0.1511201090302.zip

 Environment details and versions:

 macOS High Sierra
 Version 10.13.1
 Google Chrome: Version 62.0.3202.94 (Official Build) (64-bit)
 Firefox: 57.0

 Any thoughts about this are highly appreciated.


 *Thanks and Best Regards,*

 *Isuru Uyanage*
 *Software Engineer - QA | WSO2*
 *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
 *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/

Re: [Dev] Error occurs with Response caching enabled.

[Krishan Wijesena]

Hi buddhimala,

Can you check your payload of put method again, refer [1]

[1]
https://docs.wso2.com/display/AM210/Configuring+Caching#ConfiguringCaching-Responsecache

Thanks,
krishan.

On Fri, Nov 24, 2017 at 2:18 PM, Buddhimala Ranasinghe 
wrote:

> Hi All,
>
> I'm trying a scenario where I need to have caching enabled to improve
> perfomance at API level.So I enabled response caching from my API. The API
> contains resources to perform CRUD operations.
>
> My problem is, when I try to invoke PUT method in my API after enabling
> response caching, it gives me the following error.
>
> [2017-11-24 14:16:39,969] ERROR - JsonUtil #writeAsJson. Payload could not
> be written as JSON. MessageID: urn:uuid:ccc5fb5c-ec7b-4e51-
> 879f-345cd8a54804
> [2017-11-24 14:16:39,972] ERROR - PassThroughHttpSSLSender Failed to
> submit the response
> org.apache.axis2.AxisFault: Payload could not be written as JSON.
> at org.apache.synapse.commons.json.JsonUtil.writeAsJson(
> JsonUtil.java:276)
> at org.apache.synapse.commons.json.JsonFormatter.writeTo(
> JsonFormatter.java:62)
> at org.apache.synapse.transport.passthru.PassThroughHttpSender.
> submitResponse(PassThroughHttpSender.java:573)
> at org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(
> PassThroughHttpSender.java:264)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at org.apache.synapse.core.axis2.Axis2Sender.sendBack(
> Axis2Sender.java:230)
> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(
> Axis2SynapseEnvironment.java:531)
> at org.apache.synapse.mediators.builtin.SendMediator.mediate(
> SendMediator.java:118)
> at org.apache.synapse.mediators.AbstractListMediator.mediate(
> AbstractListMediator.java:97)
> at org.apache.synapse.mediators.AbstractListMediator.mediate(
> AbstractListMediator.java:59)
> at org.apache.synapse.mediators.base.SequenceMediator.mediate(
> SequenceMediator.java:158)
> at org.apache.synapse.rest.Resource.process(Resource.java:343)
> at org.apache.synapse.rest.API.process(API.java:338)
> at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(
> RESTRequestHandler.java:90)
> at org.apache.synapse.rest.RESTRequestHandler.process(
> RESTRequestHandler.java:56)
> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.
> injectMessage(Axis2SynapseEnvironment.java:304)
> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.
> handleMessage(SynapseCallbackReceiver.java:554)
> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(
> SynapseCallbackReceiver.java:188)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at org.apache.synapse.transport.passthru.ClientWorker.run(
> ClientWorker.java:262)
> at org.apache.axis2.transport.base.threads.NativeWorkerPool$
> 1.run(NativeWorkerPool.java:172)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> [2017-11-24 14:16:39,972] ERROR - Axis2Sender Access-Control-Allow-Headers:
> authorization,Access-Control-Allow-Origin,Content-Type,
> SOAPAction,Access-Control-Allow-Methods:PUT,Access-Control-Allow-Origin:*,Content-Type:application/json;
> charset=UTF-8, xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/;><
> soapenv:Body/> Unexpected error sending message back
> org.apache.axis2.AxisFault: Failed to submit the response
> at org.apache.synapse.transport.passthru.PassThroughHttpSender.
> handleException(PassThroughHttpSender.java:632)
> at org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(
> PassThroughHttpSender.java:266)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at org.apache.synapse.core.axis2.Axis2Sender.sendBack(
> Axis2Sender.java:230)
> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(
> Axis2SynapseEnvironment.java:531)
> at org.apache.synapse.mediators.builtin.SendMediator.mediate(
> SendMediator.java:118)
> at org.apache.synapse.mediators.AbstractListMediator.mediate(
> AbstractListMediator.java:97)
> at org.apache.synapse.mediators.AbstractListMediator.mediate(
> AbstractListMediator.java:59)
> at org.apache.synapse.mediators.base.SequenceMediator.mediate(
> SequenceMediator.java:158)
> at org.apache.synapse.rest.Resource.process(Resource.java:343)
> at org.apache.synapse.rest.API.process(API.java:338)
> at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(
> RESTRequestHandler.java:90)
> at org.apache.synapse.rest.RESTRequestHandler.process(
> RESTRequestHandler.java:56)
> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.
> injectMessage(Axis2SynapseEnvironment.java:304)
> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.
> handleMessage(SynapseCallbackReceiver.java:554)
>  

Re: [Dev] [DEV][puppet-apim]

[Tharindu Dharmarathna]

Hi Nuwan,

I think pubudu get missed understanding as Analytics nodes. We do not need
to have spark clustering in TM .

On Fri, Nov 24, 2017 at 11:28 AM, Nuwan Silva  wrote:

> Thanks for the info but, do we need to configure spark cluster
> configurations for traffic manager? If so why?
>
> On Fri, Nov 24, 2017 at 10:57 AM, Samitha Chathuranga 
> wrote:
>
>> I'm not sure whether we are using dep-sync now since in APIM docker
>>> patterns we removed depsync and added rsync.[1]
>>>
>> Using rsync [1] is completely external configuration with wso2 product
>> configs, hence different to the usage of svn-dep-sync. But if you follow up
>> with svn dep sync, required templates are already added to the template
>> files and so you have to add only the required hiera data. Anyway now we
>> recommend rsync over svn, so better to go with rsync.
>>
>> [1] - https://docs.wso2.com/display/AM210/Configuring+rsync+for+De
>> ployment+Synchronization
>>
>> On Fri, Nov 24, 2017 at 10:36 AM, Prasanna Dangalla 
>> wrote:
>>
>>>
>>> On Fri, Nov 24, 2017 at 10:08 AM, Anuruddha Liyanarachchi <
>>> anurudd...@wso2.com> wrote:
>>>
 Hi Nuwan,

 As per the current patterns, there is no HA in traffic manager. The
 approach you have taken should work. However, you will need to configure
 dep-sync between two nodes if you are deploying custom policies.

>>> I'm not sure whether we are using dep-sync now since in APIM docker
>>> patterns we removed depsync and added rsync.[1]
>>>
>>> [1] - https://github.com/wso2/docker-apim/blob/v2.1.0/docker-compo
>>> se/pattern-4/gateway-worker-2/worker-manager-rsync.sh
>>>

 On Fri, Nov 24, 2017 at 9:54 AM, Nuwan Silva  wrote:

> Hi Team,
>
> While deploying the puppet-apim [1] I had an issue where there was no
> pattern for deploying Traffic Manager as an HA deployment. I added the
> following snippet to achieve HA in the cluster. Do we have another way of
> doing this? Please advise.
>
> wso2::clustering:
>   enabled: true
>   domain: tm.am.wso2.domain
>   sub_domain: mgt
>   local_member_host: "%{::ipaddress}"
>   local_member_port: 4000
> # WKA membership scheme
>   membership_scheme: wka
>   wka:
> members:
>   -
> hostname: 192.168.48.33
> port: 4000
>   -
> hostname: 192.168.48.34
> port: 4000
>
>
> [1] https://github.com/wso2/puppet-apim
> [2] https://github.com/wso2/puppet-apim/issues/47
>
> Cheers,
> NuwanS.
> --
>
>
> *Nuwan Silva*
> *Associate Technical Lead*
> Mobile: +9477 980 4543 <+94%2077%20980%204543>
>
> WSO2 Inc.
> lean . enterprise . middleware.
> http://www.wso2.com
>



 --
 *Thanks and Regards,*
 Anuruddha Lanka Liyanarachchi
 Software Engineer - WSO2
 Mobile : +94 (0) 712762611
 Tel  : +94 112 145 345
 a nurudd...@wso2.com

>>>
>>>
>>
>>
>> --
>> Samitha Chathuranga
>> Software Engineer, WSO2 Inc.
>> lean.enterprise.middleware
>> Mobile: +94715123761
>>
>> [image: http://wso2.com/signature] 
>>
>
>
>
> --
>
>
> *Nuwan Silva*
> *Associate Technical Lead*
> Mobile: +9477 980 4543 <+94%2077%20980%204543>
>
> WSO2 Inc.
> lean . enterprise . middleware.
> http://www.wso2.com
>



-- 

*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

[Dev] Error occurs with Response caching enabled.

[Buddhimala Ranasinghe]

Hi All,

I'm trying a scenario where I need to have caching enabled to improve
perfomance at API level.So I enabled response caching from my API. The API
contains resources to perform CRUD operations.

My problem is, when I try to invoke PUT method in my API after enabling
response caching, it gives me the following error.

[2017-11-24 14:16:39,969] ERROR - JsonUtil #writeAsJson. Payload could not
be written as JSON. MessageID: urn:uuid:ccc5fb5c-ec7b-4e51-879f-345cd8a54804
[2017-11-24 14:16:39,972] ERROR - PassThroughHttpSSLSender Failed to submit
the response
org.apache.axis2.AxisFault: Payload could not be written as JSON.
at
org.apache.synapse.commons.json.JsonUtil.writeAsJson(JsonUtil.java:276)
at
org.apache.synapse.commons.json.JsonFormatter.writeTo(JsonFormatter.java:62)
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:573)
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:264)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:230)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:531)
at
org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:118)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:59)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
at org.apache.synapse.rest.Resource.process(Resource.java:343)
at org.apache.synapse.rest.API.process(API.java:338)
at
org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:90)
at
org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:56)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:304)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:554)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:188)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:262)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
[2017-11-24 14:16:39,972] ERROR - Axis2Sender
Access-Control-Allow-Headers:authorization,Access-Control-Allow-Origin,Content-Type,SOAPAction,Access-Control-Allow-Methods:PUT,Access-Control-Allow-Origin:*,Content-Type:application/json;
charset=UTF-8,http://schemas.xmlsoap.org/soap/envelope/;>
Unexpected error sending message back
org.apache.axis2.AxisFault: Failed to submit the response
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.handleException(PassThroughHttpSender.java:632)
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:266)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:230)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:531)
at
org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:118)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:59)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
at org.apache.synapse.rest.Resource.process(Resource.java:343)
at org.apache.synapse.rest.API.process(API.java:338)
at
org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:90)
at
org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:56)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:304)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:554)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:188)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:262)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at

Re: [Dev] How to compare two synapse properties in ESB

[Irham Iqbal]

Hi Thivya,

Did you try as below. IMO this should work.



 

 
  

   


Thanks,
Iqbal

On Fri, Nov 24, 2017 at 2:13 PM, Rukshan Premathunga 
wrote:

> Hi Thivya,
>
> You may be able to use script mediator[1]. You can perfume the string
> comparison in the script mediator and then use the filter mediator for the
> result.
>
> 
> var user =  mc.getProperty("USER_NAME");
>var patient = mc.getProperty("PATIENT_ID");
>mc.setProperty("RESULT", user == patient);
> ]]>
> 
>
> 
>
> 
> 
> 
> 
> 
>
> 
>
> [1] https://docs.wso2.com/display/ESB500/Script+Mediator
>
> Thanks and Regards
>
> On Fri, Nov 24, 2017 at 10:20 AM, Thivya Mahenthirarasa 
> wrote:
>
>> Hi Dev,
>>
>> Requirement: I need to check a condition before loop back to out sequence
>> whether the USER_NAME and PATIENT_ID are equal.
>>
>> I'm using a filter in my in sequence.
>>
>> 
>>
>>   
>>
>>
>>
>> I'm seeing always "evaluates to false and no else path - skipping child
>> mediators" in console even in the case of synapse properties USER_NAME and
>> PATIENT_ID are equal.
>>
>> Could anyone help?
>>
>>
>> Thanks,
>> Thivya
>>
>>
>> --
>>
>> *Thivya Mahenthirarasa*
>>
>> *Software Engineer -Support Team | WSO2*
>>
>>
>> *Email: thi...@wso2.com *
>>
>> *Mobile: +94766461966 <+94%2076%20646%201966> *
>> *Web: http://wso2.com *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rukshan Chathuranga.
> Software Engineer.
> WSO2, Inc.
> +94711822074 <+94%2071%20182%202074>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Irham Iqbal
Software Engineer
WSO2
phone: +94 777888452

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

Re: [Dev] [Architecture] WSO2 Enterprise Integrator 6.1.1-update10 Released !

[Nandika Jayawardana]

Actually, we have another 489 issues in DEVTOOLEI project which I think is
also critically important since dev studio is the primary development tool
the developers interact with. The perception generated from dev studio will
have a lasting effect on the product quality.

In order to reduce the bug count, we will start with
classifying/prioritizing the issues.

1. There could be many issues which are already fixed and not resolved or
no longer relevant due to changes which can be resolved straight away.
2. For the relevant issues, we can classify them depending on the
importance/relevance of the issue and identify the components which have
the most number of critical issues and work on them one component at a
time.

Regards
Nandika

On Fri, Nov 24, 2017 at 12:14 PM, Vijitha Ekanayake 
wrote:

> Hi Samisa,
>
> We are continuously working on fixing the bugs reported under JIRA and
> GitHub along with the EI 6 weekly updates. The plan is to pick a set up
> issues by filtering the priority and label those for the upcoming update
> release.
>
> Thanks,
> Vijitha.
>
> On Fri, Nov 24, 2017 at 3:14 AM, Samisa Abeysinghe 
> wrote:
>
>> We have 803 Jira and 265 Git open issues, what is the plan to flush them?
>>
>> Thanks,
>> Samisa...
>>
>>
>> Samisa Abeysinghe
>>
>> Chief Engineering and Delivery Officer
>>
>> WSO2 Inc.
>> http://wso2.com
>>
>>
>> On Fri, Nov 24, 2017 at 12:08 AM, Vijitha Ekanayake 
>> wrote:
>>
>>>
>>> Please find the correct link for the distribution: https://github.c
>>> om/wso2/product-ei/releases/download/v6.1.1-update10/wso2ei-
>>> 6.1.1-update10.zip
>>>
>>>
>>> On Fri, Nov 24, 2017 at 12:01 AM, Vijitha Ekanayake 
>>> wrote:
>>>
 Hi all,

 The WSO2 Integration team is pleased to announce the release of
 Enterprise Integrator 6.1.1-update10. It is available for download from
 here
 
 .

>>>
 *Tasks/Bug Fixes and Improvements*

 https://github.com/wso2/product-ei/issues?q=is%3Aissue+miles
 tone%3A6.1.1-update-10+is%3Aclosed

 *​​List of Open Issues*

 https://wso2.org/jira/issues/?filter=13994

 https://github.com/wso2/product-ei/issues?q=is%3Aopen+is%3Aissue


 *Mailing Lists*

 Join our mailing lists and correspond with the developers directly.

 Developer List : dev@wso2.org | Subscribe | Mail Archive

 WSO2 Architecture List: architect...@wso2.org

 User Forum : StackOverflow 

 *How To Contribute*

 Your feedback is most welcome!

 *Reporting Issues​*

 We encourage you to report issues, improvements and feature requests
 regarding WSO2 Integrator through WSO2 EI GIT Issues
 .

 ~ The WSO2 Integration Team ~

>>>

>>>
>>>
>>> --
>>> Vijitha Ekanayake
>>> Senior Software Engineer*, *WSO2, Inc.; http://wso2.com/
>>> Mobile : +94 777 24 73 39 | +94 718 74 44 08
>>> lean.enterprise.middleware
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> Vijitha Ekanayake
> Senior Software Engineer*, *WSO2, Inc.; http://wso2.com/
> Mobile : +94 777 24 73 39 | +94 718 74 44 08
> lean.enterprise.middleware
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Nandika Jayawardana
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to set ThriftClientPort in APIM Gate Way Node in a cluster setup

[Samitha Chathuranga]

Hi Dushantha,

The point is that by default those thrift port values are commented out.
(if they are commented-out the all the port values are changed by the
offset value ) If you uncomment them, you have to configure them correctly.
By the way in the doc [1] you mentioned, note the below section, under the
3rd point under the topic "Installing and configuring API Manager".

[image: Inline image 1]

So the doc has been written not considering that optional step of port
offsetting. So all ports mentioned in the doc are considering that there
are no offsets.

[1] - https://docs.wso2.com/display/CLUSTER44x/Clustering+API+Manager+2.0.0

Regards,
Samitha

On Fri, Nov 24, 2017 at 9:09 AM, Viduranga Gunarathne 
wrote:

> Hi Dushantha,
>
> Yes. If you are using port offset to deploy the Gateway and KeyManager
> nodes, then the default Thrift port (10397) in both the nodes will get
> offset by the specified offset value.
> Eg:
> Gateway offset = 2,
> Then  will be 10399
>
> KeyManager offset = 3,
> Then  will be 10400
>
> In a clustered deployment, the KeyManager acts as the Thrift Server and
> the Gateway as the Thrift client. Hence the Gateway uses the
>  to send a request to the KeyManager where the request is
> handled at the . For the communication to happen, both
> the port values (ThriftServerPort in KeyManager and ThriftClientPort in
> Gateway) should be of the same value. Unless the port offset of both the
> Gateway and the KeyManager is the same, you will have to manually set the
> two values.
>
> Thanks,
> Viduranga.
>
> On Thu, Nov 23, 2017 at 9:24 PM, Chamara Silva  wrote:
>
>> This already in the public documentation. Please refer "Changing the
>> Thrift client and server ports" section.
>>
>>
>> [2] https://docs.wso2.com/display/AM210/Changing+the+Default
>> +Ports+with+Offset
>>
>> Thanks,
>> Chamara Silva
>>
>> On Thu, Nov 23, 2017 at 7:57 PM, Dushantha Batuwita 
>> wrote:
>>
>>> Hi
>>> I'm involved in a gateway cluster set up in the local machine where the
>>> architecture is explained as follows
>>>
>>>1. IS 5.3.0 as KM offset 0
>>>2. Publisher/store/TM  offset 1
>>>3. Gateway worker   offset 3
>>>4. GatewayWorkerManger  offset 2
>>>
>>> I'm following the [1] Clustering API Manager document where it explains
>>> Configuring the Gateway > Configure key management related
>>> communication. >  c.  Specify the ThriftClientPort and ThriftServerPort
>>>  values. 10397 is the default.
>>> 10397
>>> 10397
>>> My query is should this port values be incremented according to the
>>> given offset values
>>>
>>>
>>> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+API+
>>> Manager+2.0.0#b099f11ea91344af8835595ac455a7c1
>>>
>>>
>>> many thanks
>>> --
>>> *Dushantha Nayanajith Chandima Batuwita*
>>> Software Engineer Support | WSO2
>>> dushan...@wso2.com
>>> mobile : 0094777453010 <077%20745%203010>
>>>
>>
>>
>>
>> --
>> Suminda Chamara Silva
>> Technical Lead
>> WSO2 Inc.
>> Mobile: +94718302858 <+94%2071%20830%202858>
>> blog: http://chamaras.blogspot.com
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
>
> *Viduranga Gunarathne*
>
> *Software Engineer Intern*
>
>
> *WSO2*
> Email : vidura...@wso2.com
> Mobile : +94712437484 <+94%2071%20243%207484>
> Web : http://wso2.com
> [image: https://wso2.com/signature] 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Samitha Chathuranga
Software Engineer, WSO2 Inc.
lean.enterprise.middleware
Mobile: +94715123761

[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to compare two synapse properties in ESB

[Rukshan Premathunga]

Hi Thivya,

You may be able to use script mediator[1]. You can perfume the string
comparison in the script mediator and then use the filter mediator for the
result.















[1] https://docs.wso2.com/display/ESB500/Script+Mediator

Thanks and Regards

On Fri, Nov 24, 2017 at 10:20 AM, Thivya Mahenthirarasa 
wrote:

> Hi Dev,
>
> Requirement: I need to check a condition before loop back to out sequence
> whether the USER_NAME and PATIENT_ID are equal.
>
> I'm using a filter in my in sequence.
>
> 
>
>   
>
>
>
> I'm seeing always "evaluates to false and no else path - skipping child
> mediators" in console even in the case of synapse properties USER_NAME and
> PATIENT_ID are equal.
>
> Could anyone help?
>
>
> Thanks,
> Thivya
>
>
> --
>
> *Thivya Mahenthirarasa*
>
> *Software Engineer -Support Team | WSO2*
>
>
> *Email: thi...@wso2.com *
>
> *Mobile: +94766461966 <+94%2076%20646%201966> *
> *Web: http://wso2.com *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
+94711822074
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev