Re: [Dev] [WSO2 IS] Clarification on Claim Configuration in Service Provider

[Dilshani Subasinghe]

@Omindu - Thanks for the explanation and understood the point.

@Tharindu - Thanks and will refer them.

On Thu, Dec 14, 2017 at 3:22 AM, Tharindu Edirisinghe <tharin...@wso2.com>
wrote:

> Hi Dilshani,
>
> The blog post [1] would be useful for you which is exactly the same
> scenario that you have faced. An example OAuth flow is explained in [2].
>
> [1] http://dinukshaish.blogspot.com/2017/02/mandatory-claims-
> in-oauth-20-with.html
> [2] http://dinukshaish.blogspot.com/2017/02/getting-started-
> with-oauth-20-using.html
>
> Thanks,
> TharinduE
>
> On Wed, Dec 13, 2017 at 7:50 AM, Omindu Rathnaweera <omi...@wso2.com>
> wrote:
>
>> Hi Dilshani,
>>
>> If you have marked a requested claim in SP claim configs as mandatory, IS
>> will prompt this page if the claim is not available for the user in the
>> user store and it's not specific to the SPA. In your case, for the
>> authenticated user 'department' claim value is not available in the user
>> store hence the prompt. Refer 'Information on mapping claims' section in
>> [1] for a detailed explanation on mandatory claims.
>>
>> [1] - https://docs.wso2.com/display/IS530/Configuring+Claims+
>> for+a+Service+Provider
>>
>> Regards,
>> Omindu.
>>
>> On Wed, Dec 13, 2017 at 3:57 PM, Dilshani Subasinghe <dilsh...@wso2.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> I am working on scenario 17 (Single Page Application (SPA) proxy) [1].
>>>
>>> In this scenario, I configure SP with OAuth 2.0 authorization code
>>> grant.  So I try out claims configurations in SP side. While testing that,
>>> noticed different behaviors in IS while requesting mandatory claims as
>>> follows;
>>>
>>>
>>> ​
>>>
>>> Above screenshot also showing that only requesting one claim
>>> (department), while it configured two mandatory claims in SP.
>>>
>>> I need to clarify exact way of requesting claims. Is that going to
>>> handle by IS or by web app? If it is going to handle by IS, it should show
>>> all mandatory claims. We tried claim mapping in SP with Travelocity and it
>>> works fine.
>>> According to this scenario, I have to use Single Page Application [2].
>>> Hence bit confuse about the functionality (Whether this is a limitation of
>>> SPA or issue in IS).
>>>
>>> Any help on this will be highly appreciated.
>>>
>>> [1] https://medium.facilelogin.com/thirty-solution-patterns-
>>> with-the-wso2-identity-server-16f9fd0c0389
>>> [2] https://github.com/facilelogin/aratuwa/tree/master/oauth
>>> 2.0-apps/org.wso2.carbon.identity.oauth.spa
>>>
>>> Thanks.
>>>
>>> --
>>>
>>> Dilshani Subasinghe
>>> Software Engineer - QA *|* WSO2
>>> lean *|* enterprise *|* middleware
>>>
>>> Mobile : +94773375185 <+94%2077%20337%205185>
>>> Blog: dilshani.me
>>>
>>> <https://wso2.com/signature>
>>>
>>
>>
>>
>> --
>> Omindu Rathnaweera
>> Senior Software Engineer, WSO2 Inc.
>> Mobile: +94 771 197 211 <+94%2077%20119%207211>
>>
>
>
>
> --
>
> Tharindu Edirisinghe
> Senior Software Engineer | WSO2 Inc
> Platform Security Team
> Blog : http://tharindue.blogspot.com
> mobile : +94 775181586 <+94%2077%20518%201586>
>



-- 

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

[Dev] [WSO2 IS] Clarification on Claim Configuration in Service Provider

[Dilshani Subasinghe]

Hi All,

I am working on scenario 17 (Single Page Application (SPA) proxy) [1].

In this scenario, I configure SP with OAuth 2.0 authorization code grant.
So I try out claims configurations in SP side. While testing that, noticed
different behaviors in IS while requesting mandatory claims as follows;


​

Above screenshot also showing that only requesting one claim (department),
while it configured two mandatory claims in SP.

I need to clarify exact way of requesting claims. Is that going to handle
by IS or by web app? If it is going to handle by IS, it should show all
mandatory claims. We tried claim mapping in SP with Travelocity and it
works fine.
According to this scenario, I have to use Single Page Application [2].
Hence bit confuse about the functionality (Whether this is a limitation of
SPA or issue in IS).

Any help on this will be highly appreciated.

[1]
https://medium.facilelogin.com/thirty-solution-patterns-with-the-wso2-identity-server-16f9fd0c0389
[2]
https://github.com/facilelogin/aratuwa/tree/master/oauth2.0-apps/org.wso2.carbon.identity.oauth.spa

Thanks.

-- 

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] [IS] SAML 2 SSO Login Session Issue

[Dilshani Subasinghe]

Hi,

@ Hasintha/Godwin - As Thanuj explained here, it is the session created by
Travelocity which keeps SAML2 assertion. I misunderstood the scenario as it
is going to set by SAML 2 flow by WSO2 IS. I will look into Travelocity
logic which set the cookie here.

Thanks Thanuja for the explanation.

Regards,
Dilshani

On Tue, Nov 14, 2017 at 10:22 AM, Godwin Shrimal <god...@wso2.com> wrote:

> Hi Dilshani,
>
> What do u mean by "while sending the SAML request it may not set the
> session."  and "it may attach session correctly in the request."  ?
>
> I am not clear what are you referring attaching session in the request
> here?
>
>
> Thanks
> Godwin
>
> On Mon, Nov 13, 2017 at 7:04 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi IS Team,
>>
>> Configured SAML 2 SSO in WSO2 IS 5.3.0 for the scenario of "SAML2 Bearer
>> Assertion Profile for OAuth 2.0 with WSO2 Travelocity". It worked well and
>> moved the setup to cloud instance.
>>
>> When it is working in cloud set up, it identified that while sending the
>> SAML request it may not set the session. I used IP instead of hostname.
>> When we give hostname in assertion URL, it may attach session correctly in
>> the request.
>>
>> Is that the expected behavior? Why we can't attach session correctly with
>> IP.  I tried to use IP as we may have to add hostname as we accessing it
>> remotely. Any solution for that?
>>
>> [1] https://docs.wso2.com/display/IS530/SAML2+Bearer+Asserti
>> on+Profile+for+OAuth+2.0+with+WSO2+Travelocity
>>
>> Thanks,
>> Dilshani
>>
>> --
>>
>> Dilshani Subasinghe
>> Software Engineer - QA *|* WSO2
>> lean *|* enterprise *|* middleware
>>
>> Mobile : +94773375185 <+94%2077%20337%205185>
>> Blog: dilshani.me
>>
>> <https://wso2.com/signature>
>>
>
>
>
> --
> *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/
> <https://www.linkedin.com/in/godwin-amila-2ba26844/>*
> twitter: https://twitter.com/godwinamila
> <http://wso2.com/signature>
>



-- 

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

[Dev] [IS] SAML 2 SSO Login Session Issue

[Dilshani Subasinghe]

Hi IS Team,

Configured SAML 2 SSO in WSO2 IS 5.3.0 for the scenario of "SAML2 Bearer
Assertion Profile for OAuth 2.0 with WSO2 Travelocity". It worked well and
moved the setup to cloud instance.

When it is working in cloud set up, it identified that while sending the
SAML request it may not set the session. I used IP instead of hostname.
When we give hostname in assertion URL, it may attach session correctly in
the request.

Is that the expected behavior? Why we can't attach session correctly with
IP.  I tried to use IP as we may have to add hostname as we accessing it
remotely. Any solution for that?

[1]
https://docs.wso2.com/display/IS530/SAML2+Bearer+Assertion+Profile+for+OAuth+2.0+with+WSO2+Travelocity

Thanks,
Dilshani

-- 

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] [IS as Key Manager] Error when generating keys for application

[Dilshani Subasinghe]

Adding Documentation team.

Yes, I agree with Rajith. It will be better to mention in docs as normal
users not gonna identify the requirement of having client credential grant
type with SAML grant type.

Reported Jira on this to track the progress [1].

[1] https://wso2.org/jira/browse/DOCUMENTATION-6403

On Fri, Nov 10, 2017 at 9:40 AM, Rajith Roshan <raji...@wso2.com> wrote:

> Hi all,
> I think it's better to include this in our documentation (quick start [1],
> cloud -[2]), that in store UI generate keys and regenerate will always
> generate access token using client credentials, even though the Oauth app
> is enabled for multiple grant types.
> Or shall we add a tool tip to generate keys button and regenerate button
> to say that this will use client credential grant type.
>
> [1] - https://docs.wso2.com/display/AM210/Quick+Start+Guide
> [2] - https://docs.wso2.com/display/APICloud/Subscribe+to+
> and+Invoke+an+API
>
> On Thu, Nov 9, 2017 at 7:58 PM, Sanjeewa Malalgoda <sanje...@wso2.com>
> wrote:
>
>> Yes in UI when we click on generate keys button it will create oauth2 app
>> and generate tokens using client credentials(first time).
>> To complete both we need client credentials grant. In back end we do not
>> have such limitation we are anyway doing 2 different service calls.
>> If someone need to enable only SAML then after initial token generation
>> we can disable it. Its good to have options to generate key/secret,
>> generate tokens separately.
>> Since this behavior was there for sometime we will not need to change it
>> suddenly. But we can consider that in future.
>>
>> Thanks,
>> sanjeewa.
>>
>> On Thu, Nov 9, 2017 at 7:32 PM, Saneth Dharmakeerthi <sane...@wso2.com>
>> wrote:
>>
>>> Hi APIM Team,
>>>
>>> Docent this a limitation of Store UI?
>>>
>>> Customer who is using SAML or authorization code grant,  Why he needs
>>> to enable client_credential? Inst this a security risk? The only thing
>>> he needs to do is getting the  Client ID and Client Secret, But in Store UI
>>> it only shows those after click Generate Key button.
>>>
>>>
>>>
>>> Thanks and Best Regards,
>>>
>>> Saneth Dharmakeerthi
>>> *Associate Technical Lead*
>>> WSO2, Inc.
>>> Mobile: +94772325511 <077%20232%205511>
>>>
>>> <http://wso2.com/signature>
>>>
>>> On Thu, Nov 9, 2017 at 9:37 AM, Dilshani Subasinghe <dilsh...@wso2.com>
>>> wrote:
>>>
>>>> Hi Fazlan,
>>>>
>>>> Ok, now I got it. Thanks for explaining it.
>>>>
>>>> Regards,
>>>> Dilshani
>>>>
>>>> On Thu, Nov 9, 2017 at 9:21 AM, Fazlan Nazeem <fazl...@wso2.com> wrote:
>>>>
>>>>> Hi Dilshani,
>>>>>
>>>>> SAML grant does not depend on client_credentials grant being enabled,
>>>>> but in store UI when we generate keys using the Generate Keys button,
>>>>> client_credentials grant is used to generate the token. Therefore you have
>>>>> to enable client_credentials grant if you are generating keys via UI. I
>>>>> think this is what Hrasha meant.
>>>>>
>>>>> On Thu, Nov 9, 2017 at 12:20 AM, Dilshani Subasinghe <
>>>>> dilsh...@wso2.com> wrote:
>>>>>
>>>>>> Hi Harsha,
>>>>>>
>>>>>> Thanks for prompt reply. Will follow that. Hope we need to specify
>>>>>> that client_credentials grant need for enabling SAML grant in the
>>>>>> documentation.
>>>>>>
>>>>>> Regards,
>>>>>> Dilshani
>>>>>>
>>>>>> On Thu, Nov 9, 2017 at 12:08 AM, Harsha Kumara <hars...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Dilshani,
>>>>>>>
>>>>>>> If you need to generate a token using SAML2 grant you may follow
>>>>>>> [1]. In store, you need to select client_credentials grant as we used 
>>>>>>> it in
>>>>>>> the store to generate the token for an application.
>>>>>>>
>>>>>>> [1] https://docs.wso2.com/display/AM1100/Exchanging+SAML2+Be
>>>>>>> arer+Tokens+with+OAuth2+-+SAML+Extension+Grant+Type
>>>>>>>
>>>>>>> On Thu, Nov 9, 2017 at 12:01 AM, Dilshani Subasinghe <
>>>>>

Re: [Dev] [IS as Key Manager] Error when generating keys for application

[Dilshani Subasinghe]

Hi Fazlan,

Ok, now I got it. Thanks for explaining it.

Regards,
Dilshani

On Thu, Nov 9, 2017 at 9:21 AM, Fazlan Nazeem <fazl...@wso2.com> wrote:

> Hi Dilshani,
>
> SAML grant does not depend on client_credentials grant being enabled, but
> in store UI when we generate keys using the Generate Keys button,
> client_credentials grant is used to generate the token. Therefore you have
> to enable client_credentials grant if you are generating keys via UI. I
> think this is what Hrasha meant.
>
> On Thu, Nov 9, 2017 at 12:20 AM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi Harsha,
>>
>> Thanks for prompt reply. Will follow that. Hope we need to specify that
>> client_credentials grant need for enabling SAML grant in the documentation.
>>
>> Regards,
>> Dilshani
>>
>> On Thu, Nov 9, 2017 at 12:08 AM, Harsha Kumara <hars...@wso2.com> wrote:
>>
>>> Hi Dilshani,
>>>
>>> If you need to generate a token using SAML2 grant you may follow [1]. In
>>> store, you need to select client_credentials grant as we used it in the
>>> store to generate the token for an application.
>>>
>>> [1] https://docs.wso2.com/display/AM1100/Exchanging+SAML2+Be
>>> arer+Tokens+with+OAuth2+-+SAML+Extension+Grant+Type
>>>
>>> On Thu, Nov 9, 2017 at 12:01 AM, Dilshani Subasinghe <dilsh...@wso2.com>
>>> wrote:
>>>
>>>> Hi APIM/IS Team,
>>>>
>>>> I'm working with IS as Key manager setup. (APIM 2.1.0 and
>>>> wso2is-km-5.3.0). In APIM, while generating keys for Applications with
>>>> "SAML" as grant type, it may give an error as follows [1]:
>>>>
>>>> [2017-11-08 23:51:34,102] ERROR - APIUtil Error occurred while
>>>> executing SubscriberKeyMgtClient.
>>>> java.lang.RuntimeException: Error occurred while calling token
>>>> endpoint: HTTP error code : 400
>>>> at org.wso2.carbon.apimgt.impl.AMDefaultKeyManagerImpl.getNewAp
>>>> plicationAccessToken(AMDefaultKeyManagerImpl.java:367)
>>>> at org.wso2.carbon.apimgt.impl.workflow.AbstractApplicationRegi
>>>> strationWorkflowExecutor.dogenerateKeysForApplication(Abstra
>>>> ctApplicationRegistrationWorkflowExecutor.java:151)
>>>> at org.wso2.carbon.apimgt.impl.workflow.AbstractApplicationRegi
>>>> strationWorkflowExecutor.generateKeysForApplication(Abstract
>>>> ApplicationRegistrationWorkflowExecutor.java:118)
>>>> at org.wso2.carbon.apimgt.impl.workflow.ApplicationRegistration
>>>> SimpleWorkflowExecutor.complete(ApplicationRegistrationSimpl
>>>> eWorkflowExecutor.java:78)
>>>> at org.wso2.carbon.apimgt.impl.workflow.ApplicationRegistration
>>>> SimpleWorkflowExecutor.execute(ApplicationRegistrationSimple
>>>> WorkflowExecutor.java:54)
>>>> at org.wso2.carbon.apimgt.impl.APIConsumerImpl.requestApprovalF
>>>> orApplicationRegistration(APIConsumerImpl.java:2789)
>>>> at org.wso2.carbon.apimgt.impl.UserAwareAPIConsumer.requestAppr
>>>> ovalForApplicationRegistration(UserAwareAPIConsumer.java:36)
>>>> at org.wso2.carbon.apimgt.hostobjects.APIStoreHostObject.jsFunc
>>>> tion_getApplicationKey(APIStoreHostObject.java:385)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at sun.reflect.NativeMethodAccessorIm
>>>>
>>>> Any idea on the issue?
>>>>
>>>> [1] error.png
>>>>
>>>> Thanks,
>>>> Dilshani
>>>>
>>>> --
>>>>
>>>> Dilshani Subasinghe
>>>> Software Engineer - QA *|* WSO2
>>>> lean *|* enterprise *|* middleware
>>>>
>>>> Mobile : +94773375185 <+94%2077%20337%205185>
>>>> Blog: dilshani.me
>>>>
>>>> <https://wso2.com/signature>
>>>>
>>>
>>>
>>>
>>> --
>>> Harsha Kumara
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94775505618 <+94%2077%20550%205618>
>>> Blog:harshcreationz.blogspot.com
>>>
>>
>>
>>
>> --
>>
>> Dilshani Subasinghe
>> Software Engineer - QA *|* WSO2
>> lean *|* enterprise *|* middleware
>>
>> Mobile : +94773375185 <+94%2077%20337%205185>
>> Blog: dilshani.me
>>
>> <https://wso2.com/signature>
>>
>
>
>
> --
> Thanks & Regards,
>
> *Fazlan Nazeem*
> Senior Software Engineer
> WSO2 Inc
> Mobile : +94772338839
> <%2B94%20%280%29%20773%20451194>
> fazl...@wso2.com
>



-- 

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] [IS as Key Manager] Error when generating keys for application

[Dilshani Subasinghe]

Hi Harsha,

Thanks for prompt reply. Will follow that. Hope we need to specify that
client_credentials grant need for enabling SAML grant in the documentation.

Regards,
Dilshani

On Thu, Nov 9, 2017 at 12:08 AM, Harsha Kumara <hars...@wso2.com> wrote:

> Hi Dilshani,
>
> If you need to generate a token using SAML2 grant you may follow [1]. In
> store, you need to select client_credentials grant as we used it in the
> store to generate the token for an application.
>
> [1] https://docs.wso2.com/display/AM1100/Exchanging+
> SAML2+Bearer+Tokens+with+OAuth2+-+SAML+Extension+Grant+Type
>
> On Thu, Nov 9, 2017 at 12:01 AM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi APIM/IS Team,
>>
>> I'm working with IS as Key manager setup. (APIM 2.1.0 and
>> wso2is-km-5.3.0). In APIM, while generating keys for Applications with
>> "SAML" as grant type, it may give an error as follows [1]:
>>
>> [2017-11-08 23:51:34,102] ERROR - APIUtil Error occurred while executing
>> SubscriberKeyMgtClient.
>> java.lang.RuntimeException: Error occurred while calling token endpoint:
>> HTTP error code : 400
>> at org.wso2.carbon.apimgt.impl.AMDefaultKeyManagerImpl.getNewAp
>> plicationAccessToken(AMDefaultKeyManagerImpl.java:367)
>> at org.wso2.carbon.apimgt.impl.workflow.AbstractApplicationRegi
>> strationWorkflowExecutor.dogenerateKeysForApplication(Abstra
>> ctApplicationRegistrationWorkflowExecutor.java:151)
>> at org.wso2.carbon.apimgt.impl.workflow.AbstractApplicationRegi
>> strationWorkflowExecutor.generateKeysForApplication(Abstract
>> ApplicationRegistrationWorkflowExecutor.java:118)
>> at org.wso2.carbon.apimgt.impl.workflow.ApplicationRegistration
>> SimpleWorkflowExecutor.complete(ApplicationRegistrationSimpl
>> eWorkflowExecutor.java:78)
>> at org.wso2.carbon.apimgt.impl.workflow.ApplicationRegistration
>> SimpleWorkflowExecutor.execute(ApplicationRegistrationSimple
>> WorkflowExecutor.java:54)
>> at org.wso2.carbon.apimgt.impl.APIConsumerImpl.requestApprovalF
>> orApplicationRegistration(APIConsumerImpl.java:2789)
>> at org.wso2.carbon.apimgt.impl.UserAwareAPIConsumer.requestAppr
>> ovalForApplicationRegistration(UserAwareAPIConsumer.java:36)
>> at org.wso2.carbon.apimgt.hostobjects.APIStoreHostObject.jsFunc
>> tion_getApplicationKey(APIStoreHostObject.java:385)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorIm
>>
>> Any idea on the issue?
>>
>> [1] error.png
>>
>> Thanks,
>> Dilshani
>>
>> --
>>
>> Dilshani Subasinghe
>> Software Engineer - QA *|* WSO2
>> lean *|* enterprise *|* middleware
>>
>> Mobile : +94773375185 <+94%2077%20337%205185>
>> Blog: dilshani.me
>>
>> <https://wso2.com/signature>
>>
>
>
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618 <+94%2077%20550%205618>
> Blog:harshcreationz.blogspot.com
>



-- 

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] [IAM] Clarification on usage of "Single Sign On with delegated access control"

[Dilshani Subasinghe]

Hi Godwin,

Thanks for explaining the scenario. I wanted to clarify exact use case
identified with documentation [1]. According to the offline discussion we
had, identified addressing the scenario with IS as Key Manager and will
work on that. Thanks for your support on this.

[1] https://docs.wso2.com/display/IS530/SAML2+Bearer+
Assertion+Profile+for+OAuth+2.0+with+WSO2+Travelocity

Regards,
Dilshani


On Wed, Nov 8, 2017 at 10:12 AM, Godwin Shrimal <god...@wso2.com> wrote:

> Hi Dilshani,
>
> Let me explain the use case of SAML2 Bearer Assertion Profile. You have a
> webapp which communicate with IS via SAML and authenticate. Then your
> webapp need to invoke OAuth2 secured backend APIs. You can't request users
> credentials again since the user already entered while login to webapp.
> Then how to generate the OAuth2 Access Token and invoke the API? You can
> use SAML2 Bearer Grant, Once after the successful authentication, your
> webapps getting SAML response, You can pass that SAML response and generate
> the access token.
>
> Please let know if you are not clear with this.
>
> Thanks
> Godwin
>
>
> On Tue, Nov 7, 2017 at 3:59 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> I implemented 10th pattern "Single Sign On with delegated access control"
>> in this blog [1]. For that, I have followed "SAML2 Bearer Assertion Profile
>> for OAuth 2.0 with WSO2 Travelocity" [2] documentation.
>>
>> In here we have to generate "OAuth2 Access Token" at the last step. I
>> just wanna clarify the use case in this. According to the pattern
>> identified in the blog, it uses APIM gateway to verify token. I can't
>> identify exact usage of token we are generating at the end of this
>> documentation [2]. If we are going to use IS as Key manager from APIM side,
>> we can not follow the exact doc. Please correct me if I misunderstood the
>> scenario.
>>
>> Any thoughts on this? Is there any way to continue with generated token
>> while connecting to WSO2 APIM or using any other service?
>>
>> [1] https://medium.facilelogin.com/thirty-solution-patterns-
>> with-the-wso2-identity-server-16f9fd0c0389
>> [2] https://docs.wso2.com/display/IS530/SAML2+Bearer+Asserti
>> on+Profile+for+OAuth+2.0+with+WSO2+Travelocity
>>
>> Regards,
>> Dilshani
>>
>> --
>>
>> Dilshani Subasinghe
>> Software Engineer - QA *|* WSO2
>> lean *|* enterprise *|* middleware
>>
>> Mobile : +94773375185 <+94%2077%20337%205185>
>> Blog: dilshani.me
>>
>> <https://wso2.com/signature>
>>
>
>
>
> --
> *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/
> <https://www.linkedin.com/in/godwin-amila-2ba26844/>*
> twitter: https://twitter.com/godwinamila
> <http://wso2.com/signature>
>



-- 

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

[Dev] [IAM] Clarification on usage of "Single Sign On with delegated access control"

[Dilshani Subasinghe]

Hi all,

I implemented 10th pattern "Single Sign On with delegated access control"
in this blog [1]. For that, I have followed "SAML2 Bearer Assertion Profile
for OAuth 2.0 with WSO2 Travelocity" [2] documentation.

In here we have to generate "OAuth2 Access Token" at the last step. I just
wanna clarify the use case in this. According to the pattern identified in
the blog, it uses APIM gateway to verify token. I can't identify exact
usage of token we are generating at the end of this documentation [2]. If
we are going to use IS as Key manager from APIM side, we can not follow the
exact doc. Please correct me if I misunderstood the scenario.

Any thoughts on this? Is there any way to continue with generated token
while connecting to WSO2 APIM or using any other service?

[1]
https://medium.facilelogin.com/thirty-solution-patterns-with-the-wso2-identity-server-16f9fd0c0389
[2]
https://docs.wso2.com/display/IS530/SAML2+Bearer+Assertion+Profile+for+OAuth+2.0+with+WSO2+Travelocity

Regards,
Dilshani

-- 

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] SSL issue in EI while using Entitlement mediator with IS

[Dilshani Subasinghe]

Hi Tharindu,

Thanks for pointing out methods to identify root cause through SSL logs.

It was identified that EI 6.1.1 had an issue with the expired private key
and issue fixed when I use the latest pack with WUM update.

Thank you,
Dilshani

On Fri, Oct 27, 2017 at 5:23 AM, Tharindu Edirisinghe <tharin...@wso2.com>
wrote:

> By the way, shouldn't we BCC (instead of CC) the internal mailing lists
> when mailing to public mailing lists like Dev ?
>
> Hi Dilshani,
>
> Disabling hostname verification to bypass this issue would not be a good
> practice.
>
> This error message can come due to several certificate related issues.
> Therefore, to isolate the exact issue, would you be able to start EI with
> enabling SSL debug logs for handshake.
>
> -Djavax.net.debug=ssl:handshake
>
> You'll have to append the SSL debug logs to a file as it would just print
> to terminal without appending to carbon log.
>
> sh integrator.sh -Djavax.net.debug=ssl:handshake > ssl.log
>
> Once EI is running, try out the same flow and check (or share) the SSL
> debug log. Then you should be able to identify the root cause
>
> Thanks,
> TharinduE
>
>
>
>
>
>
> On Thu, Oct 26, 2017 at 10:16 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> I implemented "Fine-grained access control for SOAP services" (Refer 25th
>> pattern in this blog [1]) pattern using WSO2 EI 6.1.1 and WSO2 IS 5.3.0. I
>> was able to implement the pattern locally and tested it successfully. While
>> I'm moving to cloud setup, I got some errors while EI going to make the
>> connection with IS.
>>
>> I got an error as follows:
>>
>> [*2017-10-26 18:52:05,406] [EI-Core]  INFO - HTTPSender Unable to
>> sendViaPost to url[https://192.168.57.251/services/EntitlementService
>> <https://192.168.57.251/services/EntitlementService>]*
>> *javax.net.ssl.SSLPeerUnverifiedException: SSL peer failed hostname
>> validation for name: null*
>> * at org.opensaml.ws.soap.client.ht
>> <http://org.opensaml.ws.soap.client.ht>tp.TLSProtocolSocketFactory.ve
>> <http://tp.TLSProtocolSocketFactory.ve>rifyHostname(TLSProtocolSocketFactory.java:233)*
>> * at org.opensaml.ws.soap.client.ht
>> <http://org.opensaml.ws.soap.client.ht>tp.TLSProtocolSocketFactory.cr
>> <http://tp.TLSProtocolSocketFactory.cr>eateSocket(TLSProtocolSocketFactory.java:186)*
>> * at
>> org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)*
>>
>> After referring some docs and emails, found out we need to add following
>> property in the integrator.sh script.
>>
>> *-Dorg.opensaml.httpclient.https.disableHostnameVerification=true \*
>>
>> After adding that, again got an error as follows:
>>
>> [2017-10-26 20:19:16,448] [EI-Core]  INFO - HTTPSender Unable to
>> sendViaPost to url[https://is.dev.wso2.org/services/EntitlementService]
>> javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
>> at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessi
>> onImpl.java:431)
>> at org.apache.commons.httpclient.protocol.SSLProtocolSocketFact
>> ory.verifyHostName(SSLProtocolSocketFactory.java:259)
>> at org.apache.commons.httpclient.protocol.SSLProtocolSocketFact
>> ory.createSocket(SSLProtocolSocketFactory.java:158)
>>
>> Any idea on fixing this issue?
>>
>> [1] https://medium.facilelogin.com/thirty-solution-patterns-
>> with-the-wso2-identity-server-16f9fd0c0389
>>
>> --
>> Best Regards,
>>
>> Dilshani Subasinghe
>> Software Engineer - QA *|* WSO2
>> lean *|* enterprise *|* middleware
>>
>> Mobile : +94773375185 <+94%2077%20337%205185>
>> Blog: dilshani.me
>>
>> <https://wso2.com/signature>
>>
>
>
>
> --
>
> Tharindu Edirisinghe
> Senior Software Engineer | WSO2 Inc
> Platform Security Team
> Blog : http://tharindue.blogspot.com
> mobile : +94 775181586 <+94%2077%20518%201586>
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

[Dev] SSL issue in EI while using Entitlement mediator with IS

[Dilshani Subasinghe]

Hi all,

I implemented "Fine-grained access control for SOAP services" (Refer 25th
pattern in this blog [1]) pattern using WSO2 EI 6.1.1 and WSO2 IS 5.3.0. I
was able to implement the pattern locally and tested it successfully. While
I'm moving to cloud setup, I got some errors while EI going to make the
connection with IS.

I got an error as follows:

[*2017-10-26 18:52:05,406] [EI-Core]  INFO - HTTPSender Unable to
sendViaPost to url[https://192.168.57.251/services/EntitlementService
<https://192.168.57.251/services/EntitlementService>]*
*javax.net.ssl.SSLPeerUnverifiedException: SSL peer failed hostname
validation for name: null*
* at
org.opensaml.ws.soap.client.http.TLSProtocolSocketFactory.verifyHostname(TLSProtocolSocketFactory.java:233)*
* at
org.opensaml.ws.soap.client.http.TLSProtocolSocketFactory.createSocket(TLSProtocolSocketFactory.java:186)*
* at
org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)*

After referring some docs and emails, found out we need to add following
property in the integrator.sh script.

*-Dorg.opensaml.httpclient.https.disableHostnameVerification=true \*

After adding that, again got an error as follows:

[2017-10-26 20:19:16,448] [EI-Core]  INFO - HTTPSender Unable to
sendViaPost to url[https://is.dev.wso2.org/services/EntitlementService]
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at sun.security.ssl.SSLSessionImpl.getPeerCertificates(
SSLSessionImpl.java:431)
at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.
verifyHostName(SSLProtocolSocketFactory.java:259)
at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.
createSocket(SSLProtocolSocketFactory.java:158)

Any idea on fixing this issue?

[1]
https://medium.facilelogin.com/thirty-solution-patterns-with-the-wso2-identity-server-16f9fd0c0389

-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185 <+94%2077%20337%205185>
Blog: dilshani.me

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

Re: [Dev] WSO2 Committers += Madhawa Perera

[Dilshani Subasinghe]

Congrats Madhawa :)

On Wed, Jun 21, 2017 at 11:27 AM, Heshitha Hettihewa <heshit...@wso2.com>
wrote:

> Congratz Madhawa! :)
>
> On Wed, Jun 21, 2017 at 11:23 AM, Imesh Chandrasiri <ime...@wso2.com>
> wrote:
>
>> Congratulations madhawa.. :)
>>
>> On Tue, Jun 20, 2017 at 2:19 PM, Pasindu Jayaweera <pasin...@wso2.com>
>> wrote:
>>
>>> Congratulations Madhawa...!!
>>>
>>> On Tue, Jun 20, 2017 at 11:38 AM, Milinda Wickramasinghe <
>>> milin...@wso2.com> wrote:
>>>
>>>> Congratulations Madhawa...!
>>>>
>>>> On Tue, Jun 20, 2017 at 11:33 AM, Rasika Perera <rasi...@wso2.com>
>>>> wrote:
>>>>
>>>>> Congratulations Madhawa !!!
>>>>>
>>>>> On Mon, Jun 19, 2017 at 4:45 PM, Chathura Dilan <chathu...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> It's my pleasure to welcome Madhawa Perera as a WSO2 Committer.
>>>>>>
>>>>>> Madhawa has been a valuable contributor to the IoT team. In
>>>>>> recognition of his contribution, dedication, and commitment he has been
>>>>>> voted as a WSO2 committer.
>>>>>>
>>>>>> Madhawa, welcome aboard and keep up the good work!
>>>>>>
>>>>>> --
>>>>>> Thanks and Best Regards,
>>>>>>
>>>>>> Chatura Dilan Perera
>>>>>> *Associate Tech Lead** - WSO2 Inc.*
>>>>>> +94777266673
>>>>>> www.dilan.me
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> 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
>>>>>
>>>>> <http://wso2.com/signature>
>>>>>
>>>>> WSO2 Inc. www.wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Milinda Wickramasinghe
>>>> *Software Engineer - Platform Security Team*
>>>> Mobile : +94 (0) 777 890 864 <%2B94%20%280%29%20773%20451194>
>>>> milin...@wso2.com
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *Pasindu Jayaweera*
>>> Software Engineer | WSO2 Inc
>>> Mobile: +94 718187375 <+94%2071%20818%207375>
>>> Blog: blog.pasindujayaweera.com
>>> <http://wso2.com/signature>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Thanks and Best Regards,*
>> Imesh Ashandimal Chandrasiri
>> *Software Engineer*
>> WSO2, Inc.
>> lean . enterprise . middleware
>> *E:* ime...@wso2.com | *P:* 0716519187
>>
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, retransmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Heshitha Hettihewa
> *Software Engineer*
> Mobile : +94716866386
> <%2B94%20%280%29%20773%20451194>
> heshit...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] WSO2 Committers += Chathurika De Silva

[Dilshani Subasinghe]

Congrats :)

On Tue, Jun 13, 2017 at 10:52 PM, Menaka Jayawardena <men...@wso2.com>
wrote:

> Congratulations Chathurika.
>
> On Tue, Jun 13, 2017 at 2:33 PM, Dilini Gunatilake <dili...@wso2.com>
> wrote:
>
>> Congratulations Chathurika :)
>>
>> On Tue, Jun 13, 2017 at 11:55 AM, Anupama Pathirage <anup...@wso2.com>
>> wrote:
>>
>>> Congratulations Chathurika :)
>>>
>>> On Tue, Jun 13, 2017 at 11:34 AM, Aparna Karunarathna <apa...@wso2.com>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> It's my pleasure to announce Chathurika De Silva as a WSO2 Committer.
>>>> She is an active member of EE team and has given a great contribution
>>>> to ESB, BPS, BRS, App Factory product releases.
>>>>
>>>> Congratulations Chathurika and keep up the good work...!
>>>>
>>>> --
>>>> *Regards,*
>>>>
>>>> *Aparna Karunarathna.*
>>>>
>>>>
>>>> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
>>>>
>>>> * <http://wso2.com/signature>*
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Anupama Pathirage
>>> Associate Technical Lead
>>> WSO2, Inc.  http://wso2.com/
>>> Email: anup...@wso2.com
>>> Mobile:+94 71 8273 979
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Dilini GunatilakeSoftware Engineer - QA Team*
>> Mobile : +94771162518 <+94%2077%20116%202518>
>> dili...@wso2.com
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Menaka Jayawardena*
> *Software Engineer - WSO2 Inc*
> *Tel : 071 350 5470*
> *LinkedIn: https://lk.linkedin.com/in/menakajayawardena
> <https://lk.linkedin.com/in/menakajayawardena>*
> *Blog: https://menakamadushanka.wordpress.com/
> <https://menakamadushanka.wordpress.com/>*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] [Vote] Release WSO2 Enterprise Integrator 6.1.1 RC1

[Dilshani Subasinghe]

>>> [+] Stable - go ahead and release
>>>>>>
>>>>>> Thanks,
>>>>>> Integration Team
>>>>>>
>>>>>> --
>>>>>> Milinda Perera
>>>>>> Senior Software Engineer;
>>>>>> WSO2 Inc. http://wso2.com ,
>>>>>> Mobile: (+94) 714 115 032 <+94%2071%20411%205032>
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sasikala Kottegoda
>>>>> *Senior Software Engineer*
>>>>> WSO2 Inc., http://wso2.com/
>>>>> lean. enterprise. middleware
>>>>> Mobile: +94 774835928 <+94%2077%20483%205928>
>>>>>
>>>>> [image: https://wso2.com/signature] <https://wso2.com/signature>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Vinod Kavinda
>>>> Senior Software Engineer
>>>> *WSO2 Inc. - lean . enterprise . middleware <http://www.wso2.com>.*
>>>> Mobile : +94 (0) 712 415544
>>>> Blog : http://soatechflicks.blogspot.com/
>>>> [image: http://wso2.com/signature]
>>>> <http://wso2.com/signature>
>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Isuru Wijesinghe
>>> *Software Engineer*
>>> WSO2 inc : http://wso2.com
>>> lean.enterprise.middleware
>>> Mobile: 0710933706
>>> isur...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Heshitha Hettihewa
>> *Software Engineer*
>> Mobile : +94716866386
>> <%2B94%20%280%29%20773%20451194>
>> heshit...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Ushani Balasooriya*
> Senior Software Engineer - EE;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; +94772636796
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] [EI] omit step of adding broker client libs when configuring broker with integrator

[Dilshani Subasinghe]

Hope it will be better, not to pack broker libs with integration server. As
we provide freedom to use any broker with integration server, it will be
easy and user friendly to add relevant libraries when configure exact
broker.

Regards,
Dilshani

On Wed, Apr 5, 2017 at 1:53 PM, Nandika Jayawardana <nand...@wso2.com>
wrote:

> Can this conflict with a user who is configuring another broker with an EI
> runtime. If it is not the case, then it is fine to pack those libs.
>
> Regards
> Nandika
>
> On Wed, Apr 5, 2017 at 1:34 PM, Pamod Sylvester <pa...@wso2.com> wrote:
>
>> Hi All,
>>
>> Based on [1], as a configuration step it requires to add the client
>> libraries within one folder to the other in EI when integrating broker with
>> integrator etc.
>>
>> Since both broker and esb is packaged together, how about we add the
>> andes client-libs into the lib folder by default when we ship.
>>
>> This will reduce the step of having to copy the libs from one folder to
>> the other
>>
>> wdyt ?
>>
>> [1] https://docs.wso2.com/display/EI600/Configuring+with+
>> the+Broker+Profile
>>
>> Thanks,
>> Pamod
>>
>> --
>> *Pamod Sylvester *
>>
>> *WSO2 Inc.; http://wso2.com <http://wso2.com>*
>> cell: +94 77 7779495 <077%20777%209495>
>>
>
>
>
> --
> Nandika Jayawardana
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] Bundling JMS 2.0 API jar with integration server

[Dilshani Subasinghe]

Noted. Issue reported as [1].

[1] https://github.com/wso2/product-ei/issues/415

Thanks,
Dilshani


On Tue, Mar 28, 2017 at 7:10 PM, Nandika Jayawardana <nand...@wso2.com>
wrote:

> Shall we do this post alpha release. Please create an issue for this.
>
> Regards
> Nandika
>
> On Tue, Mar 28, 2017 at 6:33 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi EI Team,
>>
>> As I am working with JMS 2.0 scenarios with integration server, it was
>> found that we should add javax.jms-api-2.0.1.jar
>> <https://drive.google.com/a/wso2.com/file/d/0BzqPLt3PumqXbl9WclRtZHFmWTg/view>replacing
>> "geronimo-jms_1.1_spec-1.1.0.wso2v1.jar"($EI_HOME/wso2/lib/endorsed).
>>
>> As JMS 2.0 jar working fine with JMS 1.x scenarios, can we bundle the
>> integration server with only JMS 2.0 jar ? That will be more user friendly
>> as we support JMS 2.0 as inbuilt features.
>>
>> Any thoughts ?
>>
>> Thanks
>>
>> --
>> Best Regards,
>>
>> Dilshani Subasinghe
>> Software Engineer - QA *|* WSO2
>> lean *|* enterprise *|* middleware
>>
>> Mobile : +94773375185 <077%20337%205185>
>> Blog: dilshani.me
>>
>> <https://wso2.com/signature>
>>
>
>
>
> --
> Nandika Jayawardana
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

[Dev] Bundling JMS 2.0 API jar with integration server

[Dilshani Subasinghe]

Hi EI Team,

As I am working with JMS 2.0 scenarios with integration server, it was
found that we should add javax.jms-api-2.0.1.jar
<https://drive.google.com/a/wso2.com/file/d/0BzqPLt3PumqXbl9WclRtZHFmWTg/view>replacing
"geronimo-jms_1.1_spec-1.1.0.wso2v1.jar"($EI_HOME/wso2/lib/endorsed).

As JMS 2.0 jar working fine with JMS 1.x scenarios, can we bundle the
integration server with only JMS 2.0 jar ? That will be more user friendly
as we support JMS 2.0 as inbuilt features.

Any thoughts ?

Thanks

-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] [WSO2 IS] SCIM call to create a role with permissions

[Dilshani Subasinghe]

Hi Hanen,

Your cURL command use "admin" permission to make the call and not to add
permissions to your group. As u create groups with basic authentication,
you may not add different permissions via the SCIM call. Even though its
call as roles, it will be map with groups in WSO2 IS.

Reference: https://docs.wso2.com/display/IS520/SCIM+APIs

Regards,
Dilshani


On Tue, Jan 10, 2017 at 10:42 PM, Hanen Ben Rhouma <hanen...@gmail.com>
wrote:

> Hi,
>
> Is it possible to create a role with a list of permissions through SCIM ?
> I created one with this command
>
> curl -v -k --user admin:admin --data '{"displayName":
> "TenantAdmin","members": 
> [{"value":"09f55b8d-9a94-484c-9fff-09e02013167a","hanen":
> "hanen"}]}' --header "Content-Type:application/json"
> https://localhost:9443/wso2/scim/Groups
>
> but the result is stripped of any kind of permission, is it possible to
> assign them through such calls ?
>
>
> Regards,
> Hanen
>
> _______
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] WSO2 Committers += Malintha Fernando

[Dilshani Subasinghe]

Congrats Malintha :)

On Tue, Nov 8, 2016 at 1:45 PM, Heshitha Hettihewa <heshit...@wso2.com>
wrote:

> Congratz Malintha!!!
>
> On Tue, Nov 8, 2016 at 1:32 PM, Chandana Napagoda <chand...@wso2.com>
> wrote:
>
>> Hi Devs,
>>
>> It is my pleasure to welcome Malintha Fernando as a WSO2 Committer.
>> Malintha has made some great contributions to WSO2 Governance Registry and
>> WSO2 Enterprise Store products during the last few months and in
>> recognition of his commitment and contributions, he has been voted as a
>> Committer for WSO2.
>>
>> @Malintha, welcome aboard and keep up the good work.
>>
>> Best Regards,
>> Chandana
>>
>> --
>> *Chandana Napagoda*
>> Associate Technical Lead
>> WSO2 Inc. - http://wso2.org
>>
>> *Email  :  chand...@wso2.com <chand...@wso2.com>**Mobile : +94718169299
>> <%2B94718169299>*
>>
>> *Blog  :http://cnapagoda.blogspot.com <http://cnapagoda.blogspot.com>
>> | http://chandana.napagoda.com <http://chandana.napagoda.com>*
>>
>> *Linkedin : http://www.linkedin.com/in/chandananapagoda
>> <http://www.linkedin.com/in/chandananapagoda>*
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Heshitha Hettihewa
> *Software Engineer*
> Mobile : +94716866386
> <%2B94%20%280%29%20773%20451194>
> heshit...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] No available task nodes for resolving a task

[Dilshani Subasinghe]

Hi Shazni,

AFAIK this is an expected behavior. I got this issue in ESB cluster. Hope
someone in the team will provide a proper answer for that error.

Regards,
Dilshani

On Mon, Nov 7, 2016 at 4:48 PM, Shazni Nazeer <sha...@wso2.com> wrote:

> I get the following exception in the manager node when it's started first
> before worker nodes. Exception doesn't occur if the worker nodes started
> first. I have a scheduled task deployed in the setup.
>
> TID: [-1234] [] [2016-11-03 12:36:36,126] ERROR {org.wso2.carbon.mediation.
> ntask.NTaskTaskManager} - Scheduling task [[
> NTask::-1234::CalendarCleanupTask]::synapse.simple.quartz] FAILED. Error:
> No available task nodes for resolving a task l
> ocation {org.wso2.carbon.mediation.ntask.NTaskTaskManager}
> org.wso2.carbon.ntask.common.TaskException: No available task nodes for
> resolving a task location
>
> at org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.
> getTaskLocation(ClusteredTaskManager.java:232)
> at org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.
> locateMemberForTask(ClusteredTaskManager.java:209)
> at org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.
> getMemberIdFromTaskName(ClusteredTaskManager.java:283)
> at org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.
> scheduleTask(ClusteredTaskManager.java:91)
> at org.wso2.carbon.mediation.ntask.NTaskTaskManager.schedule(
> NTaskTaskManager.java:103)
> at org.wso2.carbon.mediation.ntask.NTaskTaskManager.init(NTaskT
> askManager.java:352)
> at org.wso2.carbon.mediation.ntask.NTaskTaskManager.update(NTas
> kTaskManager.java:365)
> at org.wso2.carbon.mediation.ntask.internal.NtaskService.update
> AndCleanupObservers(NtaskService.java:103)
> at org.wso2.carbon.mediation.ntask.internal.NtaskService.setCon
> figurationContextService(NtaskService.java:96)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
> ssorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
> thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.internal.ds.model.ComponentReference.bin
> d(ComponentReference.java:376)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b
> indReference(ServiceComponentProp.java:430)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b
> ind(ServiceComponentProp.java:218)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b
> uild(ServiceComponentProp.java:343)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(
> InstanceProcess.java:620)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(
> InstanceProcess.java:197)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SC
> RManager.java:222)
> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.
> serviceChanged(FilteredServiceListener.java:107)
>
>
> According to [1] this is expected. Is there a fix for this to suppress the
> exception?
>
> [1] http://bugsbydilshani.blogspot.co.uk/2016/07/wso2esbcluster-task-
> scheduling-error.html
>
> --
> Shazni Nazeer
> Associate Technical Lead | WSO2
>
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
> Blog : http://shazninazeer.blogspot.com
>
> <http://wso2.com/signature>
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] Kubernetes pod Back-off pulling image due to an authentication error

[Dilshani Subasinghe]

Thanks Irham for the explanation.

On Wed, Oct 26, 2016 at 5:18 PM, Irham Iqbal <iq...@wso2.com> wrote:

> Hi Dilshani,
>
> No you can use kubectl command to pull the image from private docker
> registry, to do that you have to create a secret in k8s as[1] and refer
> that in your yaml (i.e highlighted in [2])
>
> [1] kubectl create secret docker-registry wso2registrykey --docker-server=
> http://dockerhub.private.wso2.com/ --docker-username=x
> --docker-password=xx --docker-email=xx...@wso2.com
>
> [2]
>
> apiVersion: v1
>
> kind: ReplicationController
>
> metadata:
>
>   name: wso2am-api-key-manager
>
>   labels:
>
> name: wso2am-api-key-manager
>
> spec:
>
>   replicas: 1
>
>   selector:
>
> name: wso2am-api-key-manager
>
>   template:
>
> metadata:
>
>   labels:
>
> name: wso2am-api-key-manager
>
> spec:
>
>   containers:
>
>   -
>
> name: wso2am-api-key-manager
>
> image: dockerhub.private.wso2.com/dimuthud-wso2-am-api-
> keymanager:1.10.0
>
> env:
>
> -
>
>   name: KUBERNETES_MASTER_SKIP_SSL_VERIFICATION
>
>   value: "true"
>
> -
>
>   name: KUBERNETES_API_SERVER
>
>   value: "http://192.168.19.45:8080;
>
> ports:
>
> -
>
>   containerPort: 9763
>
>   protocol: "TCP"
>
> -
>
>   containerPort: 9443
>
>   protocol: "TCP"
>
> -
>
>   containerPort: 10397
>
>   protocol: "TCP"
>
>   imagePullSecrets:
>
>   - name: registrypullsecret
>
> Thanks,
> Iqbal
>
> On Wed, Oct 26, 2016 at 5:09 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi Irham,
>>
>> I need a clarification on this. Do we have to pull every image manually?
>> As I can see, while running the tests it will fail pulling due to
>> authentication error. But still we can pull the same image manually and
>> then it going to work.
>>
>> Any idea on fixing?
>>
>> Regards,
>> Dilshani
>>
>> On Wed, Oct 26, 2016 at 5:01 PM, Dilshani Subasinghe <dilsh...@wso2.com>
>> wrote:
>>
>>> Hi Irham,
>>>
>>> Thanks a lot for pointing out the solution. Problem solved.
>>>
>>> Regards,
>>> Dilshani
>>>
>>> On Wed, Oct 26, 2016 at 4:01 PM, Irham Iqbal <iq...@wso2.com> wrote:
>>>
>>>> Hi Dilshani,
>>>>
>>>> Since you're pulling the image from private docker registry to your k8s
>>>> node you have to configure your node refer mail[1]. Then you can check the
>>>> image pulling manually(login to that node and docker pull).
>>>>
>>>>
>>>> Thanks,
>>>> Iqbal
>>>>
>>>> [1] WSO2 Private Docker Registry
>>>>
>>>> On Wed, Oct 26, 2016 at 3:43 PM, Dilshani Subasinghe <dilsh...@wso2.com
>>>> > wrote:
>>>>
>>>>> Hi Devs,
>>>>>
>>>>> While configuring Kubernetes cluster, came up with an error in
>>>>> Kubernetes pod.
>>>>>
>>>>> For the command "kubectl get pods", it list down results as follows:
>>>>>
>>>>> NAME   READY STATUS RESTARTS   AGE
>>>>> mysql-apim-db-1viwg1/1 Running
>>>>> 2  20h
>>>>> mysql-govdb-qioee1/1 Running
>>>>> 2  20h
>>>>> mysql-userdb-l8q8c   1/1 Running
>>>>> 1  20h
>>>>> wso2am-default-813fy0/1   ImagePullBackOff  0
>>>>> 20h
>>>>>
>>>>> When find the reason for "ImagePullBackOff ", identified following
>>>>> error.
>>>>>
>>>>> Error response from daemon: Authentication is required: Get
>>>>> https://dockerhub.private.wso2.com/v2/wso2am/manifests/1.10.0:
>>>>> unauthorized: authentication required
>>>>>
>>>>> Any ideas/ suggestions to solve this error?
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>>
>>>>> Dilshani Subasinghe
>>>>> Software Engineer - QA *|* WSO2
>>>>> lean *|* enterprise *|* middleware
>>>>>
>>>>> Mobile : +94773375185
>>>>> Blog: dilshani.me
>>>>>
>>>>> <https://wso2.com/signature>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Irham Iqbal
>>>> Software Engineer
>>>> WSO2
>>>> phone: +94 777888452
>>>> <http://wso2.com/signature>
>>>>
>>>>
>>>
>>>
>>> --
>>> Best Regards,
>>>
>>> Dilshani Subasinghe
>>> Software Engineer - QA *|* WSO2
>>> lean *|* enterprise *|* middleware
>>>
>>> Mobile : +94773375185
>>> Blog: dilshani.me
>>>
>>> <https://wso2.com/signature>
>>>
>>
>>
>>
>> --
>> Best Regards,
>>
>> Dilshani Subasinghe
>> Software Engineer - QA *|* WSO2
>> lean *|* enterprise *|* middleware
>>
>> Mobile : +94773375185
>> Blog: dilshani.me
>>
>> <https://wso2.com/signature>
>>
>
>
>
> --
> Irham Iqbal
> Software Engineer
> WSO2
> phone: +94 777888452
> <http://wso2.com/signature>
>
>


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] Kubernetes pod Back-off pulling image due to an authentication error

[Dilshani Subasinghe]

Hi Irham,

I need a clarification on this. Do we have to pull every image manually? As
I can see, while running the tests it will fail pulling due to
authentication error. But still we can pull the same image manually and
then it going to work.

Any idea on fixing?

Regards,
Dilshani

On Wed, Oct 26, 2016 at 5:01 PM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:

> Hi Irham,
>
> Thanks a lot for pointing out the solution. Problem solved.
>
> Regards,
> Dilshani
>
> On Wed, Oct 26, 2016 at 4:01 PM, Irham Iqbal <iq...@wso2.com> wrote:
>
>> Hi Dilshani,
>>
>> Since you're pulling the image from private docker registry to your k8s
>> node you have to configure your node refer mail[1]. Then you can check the
>> image pulling manually(login to that node and docker pull).
>>
>>
>> Thanks,
>> Iqbal
>>
>> [1] WSO2 Private Docker Registry
>>
>> On Wed, Oct 26, 2016 at 3:43 PM, Dilshani Subasinghe <dilsh...@wso2.com>
>> wrote:
>>
>>> Hi Devs,
>>>
>>> While configuring Kubernetes cluster, came up with an error in
>>> Kubernetes pod.
>>>
>>> For the command "kubectl get pods", it list down results as follows:
>>>
>>> NAME   READY STATUS RESTARTS   AGE
>>> mysql-apim-db-1viwg1/1 Running
>>> 2  20h
>>> mysql-govdb-qioee1/1 Running
>>> 2  20h
>>> mysql-userdb-l8q8c   1/1 Running
>>> 1  20h
>>> wso2am-default-813fy0/1   ImagePullBackOff  0
>>> 20h
>>>
>>> When find the reason for "ImagePullBackOff ", identified following error.
>>>
>>> Error response from daemon: Authentication is required: Get
>>> https://dockerhub.private.wso2.com/v2/wso2am/manifests/1.10.0:
>>> unauthorized: authentication required
>>>
>>> Any ideas/ suggestions to solve this error?
>>>
>>> --
>>> Best Regards,
>>>
>>> Dilshani Subasinghe
>>> Software Engineer - QA *|* WSO2
>>> lean *|* enterprise *|* middleware
>>>
>>> Mobile : +94773375185
>>> Blog: dilshani.me
>>>
>>> <https://wso2.com/signature>
>>>
>>
>>
>>
>> --
>> Irham Iqbal
>> Software Engineer
>> WSO2
>> phone: +94 777888452
>> <http://wso2.com/signature>
>>
>>
>
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA *|* WSO2
> lean *|* enterprise *|* middleware
>
> Mobile : +94773375185
> Blog: dilshani.me
>
> <https://wso2.com/signature>
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] Kubernetes pod Back-off pulling image due to an authentication error

[Dilshani Subasinghe]

Hi Irham,

Thanks a lot for pointing out the solution. Problem solved.

Regards,
Dilshani

On Wed, Oct 26, 2016 at 4:01 PM, Irham Iqbal <iq...@wso2.com> wrote:

> Hi Dilshani,
>
> Since you're pulling the image from private docker registry to your k8s
> node you have to configure your node refer mail[1]. Then you can check the
> image pulling manually(login to that node and docker pull).
>
>
> Thanks,
> Iqbal
>
> [1] WSO2 Private Docker Registry
>
> On Wed, Oct 26, 2016 at 3:43 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi Devs,
>>
>> While configuring Kubernetes cluster, came up with an error in Kubernetes
>> pod.
>>
>> For the command "kubectl get pods", it list down results as follows:
>>
>> NAME   READY STATUS RESTARTS   AGE
>> mysql-apim-db-1viwg1/1 Running
>> 2  20h
>> mysql-govdb-qioee1/1 Running
>> 2  20h
>> mysql-userdb-l8q8c   1/1 Running
>> 1  20h
>> wso2am-default-813fy0/1   ImagePullBackOff  0  20h
>>
>> When find the reason for "ImagePullBackOff ", identified following error.
>>
>> Error response from daemon: Authentication is required: Get
>> https://dockerhub.private.wso2.com/v2/wso2am/manifests/1.10.0:
>> unauthorized: authentication required
>>
>> Any ideas/ suggestions to solve this error?
>>
>> --
>> Best Regards,
>>
>> Dilshani Subasinghe
>> Software Engineer - QA *|* WSO2
>> lean *|* enterprise *|* middleware
>>
>> Mobile : +94773375185
>> Blog: dilshani.me
>>
>> <https://wso2.com/signature>
>>
>
>
>
> --
> Irham Iqbal
> Software Engineer
> WSO2
> phone: +94 777888452
> <http://wso2.com/signature>
>
>


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

[Dev] Kubernetes pod Back-off pulling image due to an authentication error

[Dilshani Subasinghe]

Hi Devs,

While configuring Kubernetes cluster, came up with an error in Kubernetes
pod.

For the command "kubectl get pods", it list down results as follows:

NAME   READY STATUS RESTARTS   AGE
mysql-apim-db-1viwg1/1 Running   2
20h
mysql-govdb-qioee1/1 Running
2  20h
mysql-userdb-l8q8c   1/1 Running
1  20h
wso2am-default-813fy0/1   ImagePullBackOff  0  20h

When find the reason for "ImagePullBackOff ", identified following error.

Error response from daemon: Authentication is required: Get
https://dockerhub.private.wso2.com/v2/wso2am/manifests/1.10.0:
unauthorized: authentication required

Any ideas/ suggestions to solve this error?

-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] WSO2 Committers += Farasath Ahamed

[Dilshani Subasinghe]

Congrats Farasath :)

On Tue, Oct 25, 2016 at 10:36 AM, Malintha Fernando <malinth...@wso2.com>
wrote:

> Congrats Fara! :D
>
> On Mon, Oct 24, 2016 at 1:14 PM, Johann Nallathamby <joh...@wso2.com>
> wrote:
>
>> Hi All,
>>
>> It's my pleasure to announce Farasath Ahamed as a WSO2 Committer.
>> Farasath has been a valuable contributor for WSO2 Identity Server
>> product, and in recognition of his contribution to WSO2, he has been voted
>> as a WSO2 Committer.
>>
>> Farasath, congratulations and keep up the good work!
>>
>> Thanks & Regards.
>>
>> --
>> Thanks & Regards,
>>
>> *Johann Dilantha Nallathamby*
>> Technical Lead & Product Lead of WSO2 Identity Server
>> Governance Technologies Team
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - *+9476950*
>> Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Malintha Fernando
> Software Engineer
> WSO2 Inc. | http://wso2.com
> Mobile : +94 718874922
> Blog : http://blog.malintha.org
>
> Lean . Enterprise . Middleware
>
>
>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] WSO2 Committers += Kasun Thennakoon

[Dilshani Subasinghe]

Congrats Kasun :)

On Fri, Oct 21, 2016 at 9:16 AM, Heshitha Hettihewa <heshit...@wso2.com>
wrote:

> Congratz kasun!!!
>
> On Fri, Oct 21, 2016 at 9:13 AM, Chandana Napagoda <chand...@wso2.com>
> wrote:
>
>> Hi Devs,
>>
>> It is my pleasure to welcome Kasun Thennakoon as a WSO2 Committer. Kasun
>> has made some great contributions to WSO2 Enterprise Store and WSO2
>> Governance Registry products during the last few months and in recognition
>> of his commitment and contributions, he has been voted as a Committer for
>> WSO2.
>>
>> @Kasun, welcome aboard and keep up the good work.
>>
>> Best Regards,
>> Chandana
>>
>> --
>> *Chandana Napagoda*
>> Associate Technical Lead
>> WSO2 Inc. - http://wso2.org
>>
>> *Email  :  chand...@wso2.com <chand...@wso2.com>**Mobile : +94718169299
>> <%2B94718169299>*
>>
>> *Blog  :http://cnapagoda.blogspot.com <http://cnapagoda.blogspot.com>
>> | http://chandana.napagoda.com <http://chandana.napagoda.com>*
>>
>> *Linkedin : http://www.linkedin.com/in/chandananapagoda
>> <http://www.linkedin.com/in/chandananapagoda>*
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Heshitha Hettihewa
> *Software Engineer*
> Mobile : +94716866386
> <%2B94%20%280%29%20773%20451194>
> heshit...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] WSO2 Committers += Anupama Pathirage

[Dilshani Subasinghe]

Congrats :) :)

On Mon, Oct 17, 2016 at 1:35 PM, Anjana Fernando <anj...@wso2.com> wrote:

> Hi everyone,
>
> It's my pleasure to announce Anupama as a WSO2 committer. Anupama has made
> great contributions to WSO2 DSS/DAS in improving the products. In
> recognizing the work that has been done, she has been voted in as a WSO2
> committer. Anupama, welcome aboard and all the best! ..
>
> Cheers,
> Anjana.
> --
> *Anjana Fernando*
> Associate Director / Architect
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me

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

Re: [Dev] WSO2 Committers += Eranda Rajapaksha

[Dilshani Subasinghe]

Congrats Eranda :)

On Mon, Oct 10, 2016 at 6:24 PM, Chanaka Cooray <chana...@wso2.com> wrote:

> Congratz Eranda !!!
>
> On Mon, Oct 10, 2016 at 6:14 PM, Senduran Balasubramaniyam <
> sendu...@wso2.com> wrote:
>
>> Congratulations Eranda !!
>>
>> On Mon, Oct 10, 2016 at 6:11 PM, Nadeeshaan Gunasinghe <
>> nadeesh...@wso2.com> wrote:
>>
>>> Congrats Eranda !!
>>>
>>>
>>> *Nadeeshaan Gunasinghe*
>>> Software Engineer, WSO2 Inc. http://wso2.com
>>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
>>> <#m_-3850375786891945420_m_-7870931990120826241_m_-4715409582830934341_>
>>> <http://www.facebook.com/nadeeshaan.gunasinghe>
>>> <http://lk.linkedin.com/in/nadeeshaan>  <http://twitter.com/Nadeeshaan>
>>> <http://nadeeshaan.blogspot.com/>
>>> Get a signature like this: Click here!
>>> <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0==627709341532653>
>>>
>>> On Mon, Oct 10, 2016 at 6:09 PM, prabath <prabathm...@gmail.com> wrote:
>>>
>>>> Congratulation Eranda !!
>>>>
>>>> On Mon, Oct 10, 2016 at 6:07 PM, Sameera Gunarathne <samee...@wso2.com>
>>>> wrote:
>>>>
>>>>> Congrats Eranda !!!
>>>>>
>>>>> On Mon, Oct 10, 2016 at 6:03 PM, Prakhash Sivakumar <prakh...@wso2.com
>>>>> > wrote:
>>>>>
>>>>>> Congratulation Eranda !
>>>>>>
>>>>>> On Mon, Oct 10, 2016 at 5:41 PM, Chanaka Fernando <chana...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Devs,
>>>>>>>
>>>>>>> It is with great pleasure I welcome Eranda Rajapaksha as a WSO2
>>>>>>> committer. Eranda has been contributing to the WSO2 ESB 5.0 release 
>>>>>>> during
>>>>>>> past few months and showed great passion and commitment to work. In
>>>>>>> recognition of his work on ESB and Integration related development he 
>>>>>>> has
>>>>>>> been voted as a committer.
>>>>>>>
>>>>>>> Eranda, welcome aboard and keep up the good work.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Chanaka
>>>>>>>
>>>>>>> --
>>>>>>> Thank you and Best Regards,
>>>>>>> Chanaka Fernando
>>>>>>> Senior Technical Lead
>>>>>>> m: +94 773337238
>>>>>>> https://wso2.com <https://wso2.com/signature>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ___
>>>>>>> Dev mailing list
>>>>>>> Dev@wso2.org
>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Prakhash Sivakumar
>>>>>> Software Engineer | WSO2 Inc
>>>>>> Platform Security Team
>>>>>> Mobile : +94771510080
>>>>>> Blog : https://medium.com/@PrakhashS
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sameera Gunarathne
>>>>> Software Engineer, WSO2 Inc. http://wso2.com
>>>>> <http://l.facebook.com/l.php?u=http%3A%2F%2Fwso2.com=gAQEswASa>
>>>>> Email: samee...@wso2.com
>>>>> Mobile: +94714155561
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Prabath Ariyarathna.
>>>> 
>>>> --
>>>> Talk is cheap. Show me the code.
>>>> (Torvalds, Linus (2000-08-25))
>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Senduran *
>> Senior Software Engineer,
>> WSO2, Inc.;  http://wso2.com/ <http://wso2.com/>
>> Mobile: +94 77 952 6548
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Chanaka Cooray
> Software Engineer, WSO2 Inc. http://wso2.com
> Email: chana...@wso2.com
> Mobile: +94713149860
> <https://wso2.com/signature>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshanilive.blogspot.com

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

Re: [Dev] WSO2 Committers += Heshitha Hettihewa

[Dilshani Subasinghe]

Congratulations Heshitha !!!

On Mon, Sep 12, 2016 at 11:55 AM, Nandika Jayawardana <nand...@wso2.com>
wrote:

> Hi all,
>
> It is my pleasure to welcome Heshitha Hettihewa as a WSO2 Committer.
> Heshitha has been the leading contributor to Business Process Server
> tooling effort and in recognition of his contributions, he has been voted
> as a Committer.
>
> Heshitha, welcome aboard and keep up the good work.
>
> Regards,
> Nandika
>
> --
> Nandika Jayawardana
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshanilive.blogspot.com

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

Re: [Dev] Setting JMS Version gloably

[Dilshani Subasinghe]

Hi Manuranga,

According to documentation, Yes we can set that. But I notice that, it
doesn't validate through the value given globally. For example, even I set
up JMS Version as 2.0 globally, it doesn't take that value.

Within the source (ServiceTaskManager.java) it seem to hard coded.


*/** Should this service use JMS 1.1 ? (when false, defaults to 1.0.2b)
*/private boolean jmsSpec11 = true;*

@Vijitha - Hope you may explain the actual scenario ?

Regards,
Dilshani


On Wed, Jun 8, 2016 at 1:25 AM, Manuranga Perera <m...@wso2.com> wrote:

> Hi Ravindra/Dilshani,
> Can we set transport.jms.JMSSpecVersion globally (ie: via axis2.xml)?
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware
Mobile: +94773375185
Blog: dilshanilive.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 5 Beta - Shared subscriber doesn't connect

[Dilshani Subasinghe]

Hi Manuranga,

Sure, will do. I also identified similar scenarios while testing JMS
Transport service parameters.

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

Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter

[Dilshani Subasinghe]

Hi all,

Update: Issue can be reproduce with ActiveMQ Client libraries which are
having versions greater than 5.9.

Regards,
Dilshani


On Fri, May 27, 2016 at 4:26 PM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:

> Hi Nuwan,
>
> When I am going to test JMS parameters according to a given support issue,
> it was not released BETA pack and used ALPHA pack. But I tested this
> scenario again with BETA pack and still see the same issue.
>
> Reported an jira[1] with the issue.
>
> [1] https://wso2.org/jira/browse/ESBJAVA-4632
>
> Regards,
> Dilshani
>
>
> On Fri, May 27, 2016 at 2:53 PM, Nuwan Wimalasekara <nuw...@wso2.com>
> wrote:
>
>> Hi Dilshani,
>>
>> Which ESB version are you using to test this scenario. Can you please
>> check this on ESB 5.0.0-BETA pack?
>> I could not observe such a behaviour in ESB 5.0.0-BETA.
>>
>> Thanks,
>> Nuwanw
>>
>> On Thu, May 26, 2016 at 2:50 PM, Dilshani Subasinghe <dilsh...@wso2.com>
>> wrote:
>>
>>> Hi Nuwan,
>>>
>>> Thank you for your response. I tried with both
>>>
>>>
>>> *java.naming.provider.url=failover:tcp://localhost:61616, and *
>>>
>>>
>>> *java.naming.provider.url=failover:(tcp://localhost:61616).*
>>> But still missing messages.
>>>
>>> Regards,
>>> Dilshani
>>>
>>>
>>> On Thu, May 26, 2016 at 2:15 PM, Nuwan Wimalasekara <nuw...@wso2.com>
>>> wrote:
>>>
>>>> Hi Dilshani,
>>>>
>>>>
>>>> On Thu, May 26, 2016 at 1:35 PM, Dilshani Subasinghe <dilsh...@wso2.com
>>>> > wrote:
>>>>
>>>>> Hi Nuwan,
>>>>>
>>>>> Yes I configured jms url with failover. Actually I used failover
>>>>> syntax as u asked me to change
>>>>> (java.naming.provider.url=failover:(tcp://localhost:61616) or
>>>>>  java.naming.provider.url=failover:tcp://localhost:61616)
>>>>>
>>>>> Proxy config:
>>>>>
>>>>> >>>> uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>>>> *java.naming.provider.url=failover:tcp://localhost:61616*
>>>>> transport.jms.DestinationType=queuetransport.jms.SessionTransacted=truetransport.Transactionality=local"/>
>>>>>
>>>>
>>>>
>>>>>
>>>>> I'm really sorry I didn't get your suggestion. Can you point out the
>>>>> error within my config?
>>>>>
>>>> The problem in your config is , that there is no '*,*'  at the end of
>>>> the url.
>>>> It should be as bellow.
>>>>
>>>> *java.naming.provider.url=failover:tcp://localhost:61616,*
>>>>
>>>> New Config:
>>>> >>> uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>>> *java.naming.provider.url=failover:tcp://localhost:61616,*
>>>> transport.jms.DestinationType=queuetransport.jms.SessionTransacted=truetransport.Transactionality=local"/>
>>>>
>>>> Thanks,
>>>> Nuwanw
>>>>
>>>>
>>>>
>>>>> Regards,
>>>>> Dilshani
>>>>>
>>>>>
>>>>> On Thu, May 26, 2016 at 1:01 PM, Nuwan Wimalasekara <nuw...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Dilshani,
>>>>>>
>>>>>>  In your proxy config, you have defined a jms url with failover. Can
>>>>>> you please try the failover url syntax as one of bellow. I think it is 
>>>>>> due
>>>>>> to invalid url definition of failover for ActiveMQ.
>>>>>>
>>>>>> Please refer[1] for failover url syntax in ActiveMQ
>>>>>>
>>>>>> java.naming.provider.url=failover:(tcp://localhost:61616) or
>>>>>>  java.naming.provider.url=failover:tcp://localhost:61616,
>>>>>>
>>>>>> [1] http://activemq.apache.org/failover-transport-reference.html
>>>>>>
>>>>>> Thanks,
>>>>>> Nuwanw
>>>>>>
>>>>>> On Wed, May 25, 2016 at 11:51 AM, Dilshani Subasinghe <
>>>>>> dilsh...@wso2.co

Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter

[Dilshani Subasinghe]

Hi Nuwan,

When I am going to test JMS parameters according to a given support issue,
it was not released BETA pack and used ALPHA pack. But I tested this
scenario again with BETA pack and still see the same issue.

Reported an jira[1] with the issue.

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

Regards,
Dilshani


On Fri, May 27, 2016 at 2:53 PM, Nuwan Wimalasekara <nuw...@wso2.com> wrote:

> Hi Dilshani,
>
> Which ESB version are you using to test this scenario. Can you please
> check this on ESB 5.0.0-BETA pack?
> I could not observe such a behaviour in ESB 5.0.0-BETA.
>
> Thanks,
> Nuwanw
>
> On Thu, May 26, 2016 at 2:50 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi Nuwan,
>>
>> Thank you for your response. I tried with both
>>
>>
>> *java.naming.provider.url=failover:tcp://localhost:61616, and *
>>
>>
>> *java.naming.provider.url=failover:(tcp://localhost:61616).*
>> But still missing messages.
>>
>> Regards,
>> Dilshani
>>
>>
>> On Thu, May 26, 2016 at 2:15 PM, Nuwan Wimalasekara <nuw...@wso2.com>
>> wrote:
>>
>>> Hi Dilshani,
>>>
>>>
>>> On Thu, May 26, 2016 at 1:35 PM, Dilshani Subasinghe <dilsh...@wso2.com>
>>> wrote:
>>>
>>>> Hi Nuwan,
>>>>
>>>> Yes I configured jms url with failover. Actually I used failover syntax
>>>> as u asked me to change
>>>> (java.naming.provider.url=failover:(tcp://localhost:61616) or
>>>>  java.naming.provider.url=failover:tcp://localhost:61616)
>>>>
>>>> Proxy config:
>>>>
>>>> >>> uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>>> *java.naming.provider.url=failover:tcp://localhost:61616*
>>>> transport.jms.DestinationType=queuetransport.jms.SessionTransacted=truetransport.Transactionality=local"/>
>>>>
>>>
>>>
>>>>
>>>> I'm really sorry I didn't get your suggestion. Can you point out the
>>>> error within my config?
>>>>
>>> The problem in your config is , that there is no '*,*'  at the end of
>>> the url.
>>> It should be as bellow.
>>>
>>> *java.naming.provider.url=failover:tcp://localhost:61616,*
>>>
>>> New Config:
>>> >> uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>> *java.naming.provider.url=failover:tcp://localhost:61616,*
>>> transport.jms.DestinationType=queuetransport.jms.SessionTransacted=truetransport.Transactionality=local"/>
>>>
>>> Thanks,
>>> Nuwanw
>>>
>>>
>>>
>>>> Regards,
>>>> Dilshani
>>>>
>>>>
>>>> On Thu, May 26, 2016 at 1:01 PM, Nuwan Wimalasekara <nuw...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Dilshani,
>>>>>
>>>>>  In your proxy config, you have defined a jms url with failover. Can
>>>>> you please try the failover url syntax as one of bellow. I think it is due
>>>>> to invalid url definition of failover for ActiveMQ.
>>>>>
>>>>> Please refer[1] for failover url syntax in ActiveMQ
>>>>>
>>>>> java.naming.provider.url=failover:(tcp://localhost:61616) or
>>>>>  java.naming.provider.url=failover:tcp://localhost:61616,
>>>>>
>>>>> [1] http://activemq.apache.org/failover-transport-reference.html
>>>>>
>>>>> Thanks,
>>>>> Nuwanw
>>>>>
>>>>> On Wed, May 25, 2016 at 11:51 AM, Dilshani Subasinghe <
>>>>> dilsh...@wso2.com> wrote:
>>>>>
>>>>>> Hi ESB Team,
>>>>>>
>>>>>> I am testing JMS parameters and identified scenario of missing
>>>>>> messages when using "transport.Transactionality" parameter.
>>>>>>
>>>>>> Configured axis2.xml as follows;
>>>>>>
>>>>>>   >>>>> class="org.apache.axis2.transport.jms.JMSListener">
>>>>>> 
>>>>>> >>>>> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>>>>> 

Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter

[Dilshani Subasinghe]

Hi Nuwan,

Thank you for your response. I tried with both


*java.naming.provider.url=failover:tcp://localhost:61616, and *


*java.naming.provider.url=failover:(tcp://localhost:61616).*
But still missing messages.

Regards,
Dilshani


On Thu, May 26, 2016 at 2:15 PM, Nuwan Wimalasekara <nuw...@wso2.com> wrote:

> Hi Dilshani,
>
>
> On Thu, May 26, 2016 at 1:35 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi Nuwan,
>>
>> Yes I configured jms url with failover. Actually I used failover syntax
>> as u asked me to change
>> (java.naming.provider.url=failover:(tcp://localhost:61616) or
>>  java.naming.provider.url=failover:tcp://localhost:61616)
>>
>> Proxy config:
>>
>> > uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
>> *java.naming.provider.url=failover:tcp://localhost:61616*
>> transport.jms.DestinationType=queuetransport.jms.SessionTransacted=truetransport.Transactionality=local"/>
>>
>
>
>>
>> I'm really sorry I didn't get your suggestion. Can you point out the
>> error within my config?
>>
> The problem in your config is , that there is no '*,*'  at the end of the
> url.
> It should be as bellow.
>
> *java.naming.provider.url=failover:tcp://localhost:61616,*
>
> New Config:
>  uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
> *java.naming.provider.url=failover:tcp://localhost:61616,*
> transport.jms.DestinationType=queuetransport.jms.SessionTransacted=truetransport.Transactionality=local"/>
>
> Thanks,
> Nuwanw
>
>
>
>> Regards,
>> Dilshani
>>
>>
>> On Thu, May 26, 2016 at 1:01 PM, Nuwan Wimalasekara <nuw...@wso2.com>
>> wrote:
>>
>>> Hi Dilshani,
>>>
>>>  In your proxy config, you have defined a jms url with failover. Can you
>>> please try the failover url syntax as one of bellow. I think it is due to
>>> invalid url definition of failover for ActiveMQ.
>>>
>>> Please refer[1] for failover url syntax in ActiveMQ
>>>
>>> java.naming.provider.url=failover:(tcp://localhost:61616) or
>>>  java.naming.provider.url=failover:tcp://localhost:61616,
>>>
>>> [1] http://activemq.apache.org/failover-transport-reference.html
>>>
>>> Thanks,
>>> Nuwanw
>>>
>>> On Wed, May 25, 2016 at 11:51 AM, Dilshani Subasinghe <dilsh...@wso2.com
>>> > wrote:
>>>
>>>> Hi ESB Team,
>>>>
>>>> I am testing JMS parameters and identified scenario of missing messages
>>>> when using "transport.Transactionality" parameter.
>>>>
>>>> Configured axis2.xml as follows;
>>>>
>>>>   >>> class="org.apache.axis2.transport.jms.JMSListener">
>>>> 
>>>> >>> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>>> >>> locked="false">failover:tcp://localhost:61616
>>>> >>> name="transport.jms.ConnectionFactoryJNDIName"
>>>> locked="false">TopicConnectionFactory
>>>> >>> locked="false">topic
>>>> >>> locked="false">topic
>>>>
>>>> * >>> locked="false">local>>> name="transport.jms.SessionTransacted" locked="false">true*
>>>> 
>>>>
>>>> 
>>>> >>> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>>> >>> locked="false">failover:tcp://localhost:61616
>>>> >>> name="transport.jms.ConnectionFactoryJNDIName"
>>>> locked="false">QueueConnectionFactory
>>>> >>> locked="false">queue
>>>>
>>>> * >>> locked="false">local>>> name="transport.jms.SessionTransacted" locked="false">true*
>>>> 
>>>>
>>>> 
>>>> >>> locked="false">org.apache.activemq.jndi.ActiveMQInitial

Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter

[Dilshani Subasinghe]

Hi Nuwan,

Yes I configured jms url with failover. Actually I used failover syntax as
u asked me to change
(java.naming.provider.url=failover:(tcp://localhost:61616) or
 java.naming.provider.url=failover:tcp://localhost:61616)

Proxy config:



I'm really sorry I didn't get your suggestion. Can you point out the error
within my config?

Regards,
Dilshani


On Thu, May 26, 2016 at 1:01 PM, Nuwan Wimalasekara <nuw...@wso2.com> wrote:

> Hi Dilshani,
>
>  In your proxy config, you have defined a jms url with failover. Can you
> please try the failover url syntax as one of bellow. I think it is due to
> invalid url definition of failover for ActiveMQ.
>
> Please refer[1] for failover url syntax in ActiveMQ
>
> java.naming.provider.url=failover:(tcp://localhost:61616) or
>  java.naming.provider.url=failover:tcp://localhost:61616,
>
> [1] http://activemq.apache.org/failover-transport-reference.html
>
> Thanks,
> Nuwanw
>
> On Wed, May 25, 2016 at 11:51 AM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi ESB Team,
>>
>> I am testing JMS parameters and identified scenario of missing messages
>> when using "transport.Transactionality" parameter.
>>
>> Configured axis2.xml as follows;
>>
>>   > class="org.apache.axis2.transport.jms.JMSListener">
>> 
>> > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>> > locked="false">failover:tcp://localhost:61616
>> > locked="false">TopicConnectionFactory
>> > locked="false">topic
>> > locked="false">topic
>>
>> * > locked="false">local> name="transport.jms.SessionTransacted" locked="false">true*
>> 
>>
>> 
>> > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>> > locked="false">failover:tcp://localhost:61616
>> > locked="false">QueueConnectionFactory
>> > locked="false">queue
>>
>> * > locked="false">local> name="transport.jms.SessionTransacted" locked="false">true*
>> 
>>
>> 
>> > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>> > locked="false">failover:tcp://localhost:61616
>> > locked="false">TopicConnectionFactory
>> > locked="false">topic
>> > locked="false">topic
>>
>> *  > locked="false">local> name="transport.jms.SessionTransacted" locked="false">true*
>> 
>> 
>>
>> And aslo added same parameters to JMS sender too.
>>
>>   > class="org.apache.axis2.transport.jms.JMSSender">
>>
>> > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>> > locked="false">failover:tcp://localhost:61616
>> > locked="false">TopicConnectionFactory
>> > locked="false">topic
>> > locked="false">topic
>>
>> *> locked="false">local> name="transport.jms.SessionTransacted" locked="false">true*
>> 
>>
>> 
>> > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>> > locked="false">failover:tcp://localhost:61616
>> > locked="false">QueueConnectionFactory
>> > locked="false">queue
>>
>>
>> *> locked="false">local    > name="transport.jms.SessionTransacted"
>> locked="false">true*
>>  
>>
>>
>>- Used activeMQ as JMS broker
>>- I used the scenario of "ESB as Both a JMS Producer and Consumer" [1]
>>- When testing that used external publisher to send messages to JMS
>>queue
>>
>> *Results:*
>>
>>- *Messages will be missing when consuming through ESB.*(It may
>>publish 1 messages to jms queue and only get around 100 or less number

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

[Dilshani Subasinghe]

Noted and appreciate quick response.

Regards,
Dilshani

On Thu, May 19, 2016 at 11:31 AM, Nuwan Wimalasekara <nuw...@wso2.com>
wrote:

> Log is corrected as bellow when having below parameter values.
>
>  locked="false">1
>  locked="false">6
>
> [2016-05-19 11:23:20,338] ERROR - ServiceTaskManager Reconnection attempt
> : 1 for service : JmsProxy failed. Next retry in 20 seconds
>
> [2016-05-19 11:23:45,357] ERROR - ServiceTaskManager Reconnection attempt
> : 2 for service : JmsProxy failed. Next retry in 40 seconds
>
> [2016-05-19 11:24:30,378]  INFO - ServiceTaskManager
> InitialReconnectDuration reached to MaxReconnectDuration.
> [2016-05-19 11:24:30,379] ERROR - ServiceTaskManager Reconnection attempt
> : 3 for service : JmsProxy failed. Next retry in 60 seconds
>
> [2016-05-19 11:25:35,411]  INFO - ServiceTaskManager
> InitialReconnectDuration reached to MaxReconnectDuration.
> [2016-05-19 11:25:35,411] ERROR - ServiceTaskManager Reconnection attempt
> : 4 for service : JmsProxy failed. Next retry in 60 seconds
>
> Thanks,
> Nuwanw
>
>
> On Thu, May 19, 2016 at 11:11 AM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Noted and reported a jira [1] to cover up fixing the issue.
>>
>> [1] https://wso2.org/jira/browse/ESBJAVA-4625
>>
>> Regards,
>> Dilshani
>>
>>
>> On Thu, May 19, 2016 at 10:47 AM, Nuwan Wimalasekara <nuw...@wso2.com>
>> wrote:
>>
>>> HI Dilshani,
>>>
>>> On Wed, May 18, 2016 at 6:27 PM, Dilshani Subasinghe <dilsh...@wso2.com>
>>> wrote:
>>>
>>>> Hi Nuwan,
>>>>
>>>> Thanks a lot for your clarification. But need more explanation on your
>>>> comments.
>>>>
>>>> 1. *if the user define only transport.jms.InitialReconnectDuration, It
>>>> will always be multiplied by the transport.jms.ReconnectProgressFactor
>>>> until it reach to transport.jms.MaxReconnectDuration. *
>>>>
>>>> We can define "transport.jms.MaxReconnectDuration" as 30 seconds and
>>>> shut down the jms broker. It may increase retry time interval by
>>>> ReconnectProgressFactor and doesn't consider about
>>>> MaxReconnectDuration.
>>>>
>>>
>>> The log is not correct. It waits for MaxReconnectDuration. But logs
>>> show incorrect value. Thanks for reporting the issue. Will fix the logs.
>>>
>>>
>>>>
>>>> As I know MaxReconnectDuration is used to define upper level of
>>>> reconnect time limit. I don't understand exact relationship between "
>>>> ReconnectProgressFactor" and "MaxReconnectDuration". Can you verify it
>>>> further?
>>>>
>>>> When include ">>> locked="false">3" and testing with exact scenario you can
>>>> find logs as follows:
>>>>
>>>> [2016-05-18 18:01:21,257] ERROR - ServiceTaskManager Reconnection
>>>> attempt : 1 for service : QueueProxy failed. Next retry in 20 seconds
>>>> [2016-05-18 18:01:21,258] ERROR - ServiceTaskManager Reconnection
>>>> attempt : 1 for service : TopicProxy failed. Next retry in 20 seconds
>>>> [2016-05-18 18:01:51,262] ERROR - ServiceTaskManager Reconnection
>>>> attempt : 2 for service : QueueProxy failed. Next retry in 40 seconds
>>>> [2016-05-18 18:01:51,263] ERROR - ServiceTaskManager Reconnection
>>>> attempt : 2 for service : TopicProxy failed. Next retry in 40 seconds
>>>> [2016-05-18 18:02:31,269] ERROR - ServiceTaskManager Reconnection
>>>> attempt : 3 for service : QueueProxy failed. Next retry in 60 seconds
>>>> [2016-05-18 18:02:31,271] ERROR - ServiceTaskManager Reconnection
>>>> attempt : 3 for service : TopicProxy failed. Next retry in 60 seconds
>>>>
>>>>  2.
>>>>
>>>>
>>>> *if the user define only transport.jms.InitialReconnectDuration, It
>>>> will always be multiplied by the transport.jms.ReconnectProgressFactor
>>>> until it reach to transport.jms.MaxReconnectDuration. *
>>>> I also tried above scenario while adding both InitialReconnectDuration
>>>> and MaxReconnectDuration. What do you mean by "*It will always be
>>>> multiplied by the transport.jms.ReconnectProgressFactor until it reach
>>>> to transport.jms.MaxReconnectDuration.*"
>>>>
>>>> When I am testing got the same result as above scenario:
>>>>
>

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

[Dilshani Subasinghe]

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

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

Regards,
Dilshani


On Thu, May 19, 2016 at 10:47 AM, Nuwan Wimalasekara <nuw...@wso2.com>
wrote:

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

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

[Dilshani Subasinghe]

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

1.


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


Regards,
Dilshani


On Wed, May 18, 2016 at 6:27 PM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:

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

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

[Dilshani Subasinghe]

Hi Nuwan,

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

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

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

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

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

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

 2.


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

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

1
3

Logs:

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

Hope you will clarify more on these factors.

Regards,
Dilshani


On Wed, May 18, 2016 at 5:53 PM, Nuwan Wimalasekara <nuw...@wso2.com> wrote:

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

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

[Dilshani Subasinghe]

Hi ESB Team,

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

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

ServiceTaskManager.java class will handle above function as follows:

   i









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


There are two facts to clarify with above situation.

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

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

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

*1*

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

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





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


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

Thank you.

-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware
Mobile: +94773375185
Blog: dilshanilive.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Dilshani Subasinghe]

Adding Chanaka

On Mon, May 16, 2016 at 8:55 AM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:

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



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware
Mobile: +94773375185
Blog: dilshanilive.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Dilshani Subasinghe]

Hi all,

Currently I am testing JMS transport parameters of ESB 5.0.0 alpha pack
with MB 3.1.0 as the broker. While testing that, identified following
factors:

   - As the JMS receiver, ESB can use proxy and inbound endpoints.
   - While using jms transport within proxy, that will always pick up
   default parameters defined with in axis2.xml.

While enabling jms transport for ESB, have to uncomment following fragments:



org.wso2.andes.jndi.PropertiesFileInitialContextFactory
repository/conf/jndi.properties
TopicConnectionFactory parameter>
topic



org.wso2.andes.jndi.PropertiesFileInitialContextFactory
repository/conf/jndi.properties
QueueConnectionFactory
   queue







*org.wso2.andes.jndi.PropertiesFileInitialContextFactory
repository/conf/jndi.properties
QueueConnectionFactoryqueue*


But enabling jms transaction only consider about "default" parameters.

   - With above scenario, *user may cannot listen to topic and queue within
   one ESB instance.*
   - As a further identification, found the article [2] which will address
   above scenario with a proper solution. Within that article, user have to
   add extra parameters to override default configurations.


 
 contentType
 application/xml
 
 
 myQueueConnectionFactory
 myQueue
 queue

   - With these configuration, it can successfully achieve the use case of
   listening to both topic and queue within one ESB instance.

1. Is there any other method to fulfill above user requirement ?

2. When considering documentation noticed following bugs and improvements:

   - Docs were not clearly identified enabling jms transport in proxy [1]
   - Docs didn't mention about way of addressing above scenario and the
   need of adding exact parameters for axis2.xml [4]

If above mention method is the only one to achieve the scenario, it may
have to update docs properly. Added document jira for required
modifications [5].

@ESB/MB Team - Please correct me if I have any misunderstanding about the
flow or functionality of features.
[1] https://docs.wso2.com/display/ESB500/JMS+Transport
[2]
http://wso2.com/library/articles/2013/03/configuring-wso2-esb-wso2-message-broker/
[3] https://docs.wso2.com/display/ESB470/Proxy+Services
[4] https://docs.wso2.com/display/ESB500/Configure+with+WSO2+Message+Broker

Thank you.

-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware
Mobile: +94773375185
Blog: dilshanilive.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB][JMS] What is the usage and behavior of "transport.jms.ConnectionFactoryType" parameter ?

[Dilshani Subasinghe]

There are some typos in previous mail and please find correct configuration
as follows. Sorry for the inconvenience made.

*ESB Configuration in axis2.xml should be as follows:*



org.wso2.andes.jndi.PropertiesFileInitialContextFactory
repository/conf/jndi.properties
   TopicConnectionFactory
   
*queue*



org.wso2.andes.jndi.PropertiesFileInitialContextFactory
repository/conf/jndi.properties
 QueueConnectionFactory
*topic*




org.wso2.andes.jndi.PropertiesFileInitialContextFactory
repository/conf/jndi.properties
 QueueConnectionFactory
*topic*





*Warning coming from ESB console not from MB*




On Thu, May 12, 2016 at 3:04 PM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:

> Hi Devs,
>
> I am testing JMS transport parameters in ESB and using MB as the broker. I
> am little bit confused about the parameter
> "transport.jms.ConnectionFactoryType" with its' behavior.
>
> I used the JMS use case of "ESB as both JMS producer and consumer"
>
>- In ESB, I configured receiver with incorrect value for
>"transport.jms.ConnectionFactoryType=topic" as follows:
>
>   class="org.apache.axis2.transport.jms.JMSListener">
> 
>  locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory
>  locked="false">repository/conf/jndi.properties
> locked="false">TopicConnectionFactory
>
> *queue*
> 
>
> 
>  locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory
>  locked="false">repository/conf/jndi.properties
>   locked="false">TopicConnectionFactory
> 
> *topic*
> 
>
> 
>  locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory
>  locked="false">repository/conf/jndi.properties
>   locked="false">TopicConnectionFactory
> 
> *topic*
> 
> 
>
>
>- And created a proxy as follows:
>
> http://ws.apache.org/ns/synapse;
>name="JMSProxy"
>transports="jms"
>statistics="disable"
>trace="disable"
>startOnLoad="true">
>
>   
>  
>  
> 
> uri="jms:/JMSMS?transport.jms.ConnectionFactoryJNDIName=
> *QueueConnectionFactory*
> java.naming.factory.initial=org.wso2.andes.jndi.PropertiesFileInitialContextFactoryjava.naming.provider.url=repository/conf/jndi.propertiestransport.jms.ConnectionFactoryType=
> *topic*"/>
> 
>  
>   
>
>
> 
>
> Within JMS sender (JMS endpoint) also given incorrect value for
> "transport.jms.ConnectionFactoryType". But still it may create queue in MB
> without considering *Connection Factory Type*.  (Both JMSProxy and JMSMS
> are queues)
>
> When publishing messages, there is a warning from MB side as follows
> (Warning is printing per message):
>
> *WARN - AMQConnectionDelegate_8_0 Loading keystore and truststore from
> system properties*
>
> Can someone help to understand this behavior ? Is it correct, not to
> identify connection factory type ?
>
> Thank you.
>
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
> lean.enterprise.middleware
> Mobile: +94773375185
> Blog: dilshanilive.blogspot.com
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware
Mobile: +94773375185
Blog: dilshanilive.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB][JMS] What is the usage and behavior of "transport.jms.ConnectionFactoryType" parameter ?

[Dilshani Subasinghe]

Hi Devs,

I am testing JMS transport parameters in ESB and using MB as the broker. I
am little bit confused about the parameter
"transport.jms.ConnectionFactoryType" with its' behavior.

I used the JMS use case of "ESB as both JMS producer and consumer"

   - In ESB, I configured receiver with incorrect value for
   "transport.jms.ConnectionFactoryType=topic" as follows:

 

org.wso2.andes.jndi.PropertiesFileInitialContextFactory
repository/conf/jndi.properties
   TopicConnectionFactory
   
*queue*



org.wso2.andes.jndi.PropertiesFileInitialContextFactory
repository/conf/jndi.properties
 TopicConnectionFactory
*topic*




org.wso2.andes.jndi.PropertiesFileInitialContextFactory
repository/conf/jndi.properties
 TopicConnectionFactory
*topic*





   - And created a proxy as follows:

http://ws.apache.org/ns/synapse;
   name="JMSProxy"
   transports="jms"
   statistics="disable"
   trace="disable"
   startOnLoad="true">
   
  
 
 

   

 
  
   
   


Within JMS sender (JMS endpoint) also given incorrect value for
"transport.jms.ConnectionFactoryType". But still it may create queue in MB
without considering *Connection Factory Type*.  (Both JMSProxy and JMSMS
are queues)

When publishing messages, there is a warning from MB side as follows
(Warning is printing per message):

*WARN - AMQConnectionDelegate_8_0 Loading keystore and truststore from
system properties*

Can someone help to understand this behavior ? Is it correct, not to
identify connection factory type ?

Thank you.


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware
Mobile: +94773375185
Blog: dilshanilive.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB 5.0.0][Mediation Debugger]After restarting debug process, it will not take previous debug points

[Dilshani Subasinghe]

Hi Chanaka,

Added a jira [1] and +1 for fixing it with this release.

[1] https://wso2.org/jira/browse/DEVTOOLESB-208

Regards,
Dilshani


On Mon, May 9, 2016 at 1:00 PM, Nuwan Pallewela <nuw...@wso2.com> wrote:

> Hi Chanaka,
>
> This is not reported as a public JIRA yet.
>
> Thanks,
> Nuwan
>
> On Mon, May 9, 2016 at 12:51 PM, Chanaka Fernando <chana...@wso2.com>
> wrote:
>
>> Is there any public JIRA already created?
>>
>> On Mon, May 9, 2016 at 12:46 PM, Isabelle Mauny <isabe...@wso2.com>
>> wrote:
>>
>>> +1 - Can we fix this in 5.0.0 …
>>> __
>>>
>>> Isabelle Mauny
>>> VP, Product Management; WSO2, Inc.;  http://wso2.com/
>>>
>>> On May 9, 2016, at 9:05 AM, Chathurika De Silva <chathuri...@wso2.com>
>>> wrote:
>>>
>>> Hi ESB Team
>>>
>>> Addition to dilshani' and nuwan's feedback, from user's perspective,
>>> when debug points are set and if the artifact is not changed, the need for
>>> him to resend debug point information is an additional task. Ideally it's
>>> better to give the same feel to a developer who is using this tool after
>>> using the general eclipse debugging (since we are based on eclipse). It's
>>> understandable that resend is needed when the artifact has changed, but if
>>> doesn't the developer should be able to start debugging without any extra
>>> effort from the tooling side. So is there any possibility in getting this
>>> fixed with this release rather than marking it as an improvement?
>>>
>>> Thank You
>>> Erandi
>>>
>>> On Mon, May 9, 2016 at 12:09 PM, Dilshani Subasinghe <dilsh...@wso2.com>
>>>  wrote:
>>>
>>>> Hi ESB Team,
>>>>
>>>> After restarting debug process, it may not identify previously added
>>>> debug points. But newly added ESB points will be added to debug process
>>>> successfully.
>>>>
>>>> When we using the option "*Resend ESB Debug Points*", it may send
>>>> previous debug points too.
>>>>
>>>> As Far As I Feel, this is bit of misleading and I also took much time
>>>> to identify relevant option.
>>>>
>>>> What is the improvement you can do about that ?
>>>>
>>>> @Nisrin/Praneesha - As I seen in the blog post (
>>>> https://nuwanpallewela.wordpress.com/2016/04/10/how-to-debug-wso2-esb-mediation-flow/),
>>>> "*Resend ESB Debug Points*" will be useful when we changing the
>>>> artifact. But in documentation it may just give explanation like "Sends
>>>> all registered debugging points to the ESB Server".
>>>>
>>>> Hope it will be better to be more descriptive with relevant
>>>> functionalities (Ex: When to use). Because user may confuse with exact
>>>> options as they are having similar functionalities.
>>>>
>>>> Thank you
>>>>
>>>> --
>>>> Best Regards,
>>>>
>>>> Dilshani Subasinghe
>>>> Software Engineer - QA
>>>> WSO2, Inc.;http://wso2.com/
>>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
>>>> lean.enterprise.middleware
>>>> Mobile: +94773375185
>>>> Blog: dilshanilive.blogspot.com
>>>>
>>>
>>>
>>>
>>> --
>>> *Chathurika Erandi*
>>> Software Engineer,
>>> WSO2 Inc.
>>>
>>> *E-mail:* chathuri...@wso2.com
>>> *Mobile: *+94714 328 612
>>> *Blog*: chathurikaerandi.blogspot.com
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "WSO2 Documentation Group" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to documentation+unsubscr...@wso2.com.
>>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>>
>>>
>>>
>>
>>
>> --
>> Thank you and Best Regards,
>> Chanaka Fernando
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 773337238
>> Blog : http://soatutorials.blogspot.com
>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>> Twitter:https://twitter.com/chanakaudaya
>>
>>
>>
>>
>>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com <nuw...@wso2.com>*
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware
Mobile: +94773375185
Blog: dilshanilive.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB 5.0.0][Mediation Debugger]After restarting debug process, it will not take previous debug points

[Dilshani Subasinghe]

Hi ESB Team,

After restarting debug process, it may not identify previously added debug
points. But newly added ESB points will be added to debug process
successfully.

When we using the option "*Resend ESB Debug Points*", it may send previous
debug points too.

As Far As I Feel, this is bit of misleading and I also took much time to
identify relevant option.

What is the improvement you can do about that ?

@Nisrin/Praneesha - As I seen in the blog post (
https://nuwanpallewela.wordpress.com/2016/04/10/how-to-debug-wso2-esb-mediation-flow/),
"*Resend ESB Debug Points*" will be useful when we changing the artifact.
But in documentation it may just give explanation like "Sends all
registered debugging points to the ESB Server".

Hope it will be better to be more descriptive with relevant functionalities
(Ex: When to use). Because user may confuse with exact options as they are
having similar functionalities.

Thank you

-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware
Mobile: +94773375185
Blog: dilshanilive.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB]Blocking option of Call mediator

[Dilshani Subasinghe]

Hi Malintha and Senduran,

Thank you for your clarifications and I understood the real process through
that. It was really helpful.

Regards,
Dilshani

On Fri, Apr 1, 2016 at 12:25 PM, Malintha Amarasinghe <malint...@wso2.com>
wrote:

> Sorry.. resending with some of the typos corrected :)
>
> --
>
> I and Prabath (from ESB team) had a similar discussion about this before. 
> Blocking
> false in a call mediator is intended for a different behavior and it is not
> same as send mediator.
>
> AFAIU a call mediator with call-blocking=false is not same as
> blocking=true although it seems to be same at first glance. This is
> executed differently in thread level.
>
> Say you have a config like below.
>
> 
> 
> 
> ..
>
> In thread level this will be executed like below when there's a call
> mediator with blocking false.
>
>  ---  executed by thread T1 and it
> will end after registering a call back to process the response.
>--- response is received by a different thread  T2 via
> callback. After that T2 takes care of executing mediators after that.
>  --- executed by T2
>
> With blocking true :
>
>  ---  executed by thread T1 and the
> same thread will wait till it get the response.
>--- response is received and same thread T1 takes care
> of executing mediators after that.
>  --- executed by T1
>
> Hope this helps you to understand the difference.
>
> When blocking false, there are no waiting threads till receiving responses
> that consumes resources like blocking true.
>
> Prabath, can you please correct if anything need to be changed.
>
> -
>
> Thanks!
>
> On Fri, Apr 1, 2016 at 12:17 PM, Malintha Amarasinghe <malint...@wso2.com>
> wrote:
>
>> Hi Dilshani,
>>
>> I and Prabath (from ESB team) had a similar discussion about this before.
>> AFAIU a call mediator without call-blocking=true (which is default) is not
>> same as send mediator. This is executed differently in thread level.
>>
>> Say you have a config like below.
>>
>> 
>> 
>> 
>> ..
>>
>> In thread level this will be executed like below when there's a call
>> mediator with blocking true.
>>
>>  ---  executed by thread T1 and it
>> will end after registering a call back to process the response.
>>--- response is received by a different thread  T2 via
>> callback. After that T2 takes care of executing mediators after that.
>>  --- executed by T2
>>
>> With blocking false :
>>
>>  ---  executed by thread T1 and the
>> same thread will wait till it get the response.
>>--- response is received and same thread T1 takes care
>> of executing mediators after that.
>>  --- executed by T1
>>
>> Hope this helps you to understand the difference.
>>
>> When blocking false, there are no waiting threads till receiving
>> responses that consumes resources like blocking true.
>>
>> Prabath, can you please correct if anything need to be changed.
>>
>> Thanks,
>> Malintha
>>
>> On Fri, Apr 1, 2016 at 11:53 AM, Dilshani Subasinghe <dilsh...@wso2.com>
>> wrote:
>>
>>> Hi Kathees,
>>>
>>> Thank you for the response.
>>>
>>> If it is, When blocking disabled call mediator should work as just like
>>> send mediator. Right ? (Correct me If I am wrong) Because call mediator
>>> will send message to endpoint and do not wait for response.
>>>
>>> But it doesn't work in that manner. Any clarification ?
>>>
>>> Regards,
>>> Dilshani
>>>
>>>
>>> On Fri, Apr 1, 2016 at 11:47 AM, Kathees Rajendram <kath...@wso2.com>
>>> wrote:
>>>
>>>> Hi Dilshani,
>>>>
>>>> Call mediator blocking functionality [1] is similar to the Callout
>>>> mediator.
>>>>
>>>> When invoked in a asynchronous manner, the Call mediator performs a
>>>> blocking external service invocation during mediation. So when you send the
>>>> call to backend with blocking functionality (blocking=true), It will wait
>>>> for the response. When you send the call with non blocking, It will work in
>>>> a synchronous manner without waiting for the response.
>>>>
>>>> [1] - https://docs.wso2.com/display/ESB490/Call+Mediator
>>>>
>>>>
>>>> Thanks,
>>>> Kathees
>>>>
>>>> On Fri, Apr 1, 2016 at 11:20 AM, Dilshani Subasinghe <dilsh...@wso2.com
>>>> > wrote:
>>>>
>>>>>

Re: [Dev] [ESB]Blocking option of Call mediator

[Dilshani Subasinghe]

Hi Kathees,

Thank you for the response.

If it is, When blocking disabled call mediator should work as just like
send mediator. Right ? (Correct me If I am wrong) Because call mediator
will send message to endpoint and do not wait for response.

But it doesn't work in that manner. Any clarification ?

Regards,
Dilshani


On Fri, Apr 1, 2016 at 11:47 AM, Kathees Rajendram <kath...@wso2.com> wrote:

> Hi Dilshani,
>
> Call mediator blocking functionality [1] is similar to the Callout
> mediator.
>
> When invoked in a asynchronous manner, the Call mediator performs a
> blocking external service invocation during mediation. So when you send the
> call to backend with blocking functionality (blocking=true), It will wait
> for the response. When you send the call with non blocking, It will work in
> a synchronous manner without waiting for the response.
>
> [1] - https://docs.wso2.com/display/ESB490/Call+Mediator
>
>
> Thanks,
> Kathees
>
> On Fri, Apr 1, 2016 at 11:20 AM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi ESB team,
>>
>> In call mediator, there is a separate option called "Blocking". AFAIK
>> call mediator having default functionality of blocking mediation.
>>
>> What will be the different behavior can have through Enabling Blocking
>> rather than in-built blocking feature ? Even though Blocking disabled, it
>> may not act as send mediator.
>>
>> Can someone help to figure out this ?
>>
>> Thank you.
>>
>> --
>> Best Regards,
>>
>> Dilshani Subasinghe
>> Software Engineer - QA
>> WSO2, Inc.;http://wso2.com/
>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
>> lean.enterprise.middleware
>>
>> Mobile: +94773375185
>>
>> _______
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Kathees
> Software Engineer,
> email: kath...@wso2.com
> mobile: +94772596173
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware

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

[Dev] [ESB]Blocking option of Call mediator

[Dilshani Subasinghe]

Hi ESB team,

In call mediator, there is a separate option called "Blocking". AFAIK call
mediator having default functionality of blocking mediation.

What will be the different behavior can have through Enabling Blocking
rather than in-built blocking feature ? Even though Blocking disabled, it
may not act as send mediator.

Can someone help to figure out this ?

Thank you.

-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware

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

Re: [Dev] [ESB500]Error in Clustering Mode - JMS 2.0 Feature:Shared Topic Subscription

[Dilshani Subasinghe]

Hi all,

Any updates on issue?

Regards,
Dilshani


On Thu, Feb 25, 2016 at 10:31 AM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:

> Hi Ravindra,
>
> Yes I doubled checked libraries and It will work properly when
> "Clustering" mode disabled.
>
> Yes, it will be giving an error regarding libraries and jars. But same
> error pop up when it can not process with HornetQ. Previously I experienced
> that. When HornetQ cannot bind its' host name, it must modify its "run.sh"
> script. With that issue also, ESB giving same error with misleading error
> message about broker jars [1].
>
>
> [1]-https://wso2.org/jira/browse/ESBJAVA-4438
>
> Regards,
> Dilshani
>
>
> On Thu, Feb 25, 2016 at 10:20 AM, Ravindra Ranwala <ravin...@wso2.com>
> wrote:
>
>> Hi Dilshani,
>>
>> AFAIK there's no special configuration for this in ESB side. Have you
>> copied all the libraries to the workers properly? If so we have to debug
>> and see the root cause of the issue.
>>
>>
>> Thanks & Regards,
>>
>> On Thu, Feb 25, 2016 at 8:14 AM, Dilshani Subasinghe <dilsh...@wso2.com>
>> wrote:
>>
>>> Hi Malaka,
>>>
>>> This issue about clustering. Multiple subscribers do not affect to the
>>> error.
>>>
>>> Yes, I am using M2 pack.
>>>
>>> Regards,
>>> Dilshani
>>>
>>>
>>> On Wed, Feb 24, 2016 at 8:38 PM, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> Hi Dilshani,
>>>>
>>>> Just to be clear is this issue related to clustering or issue persist
>>>> when there are multiple subscribers?
>>>>
>>>> Also you must be using esb 5 milestone pack?
>>>>
>>>> On Wed, Feb 24, 2016 at 7:09 PM, Dilshani Subasinghe <dilsh...@wso2.com
>>>> > wrote:
>>>>
>>>>> Hi ESB Team,
>>>>>
>>>>> I am testing new fearure called "JMS 2.0.0 Support"[1] and found an
>>>>> error in "JMS 2.0 Feature:Shared Topic Subscription". Feature will
>>>>> successfully functioning in Standalone mode. But it clustering mode, it
>>>>> will provide an error as follows;
>>>>>
>>>>>  TID: [-1234] [] [2016-02-24 15:30:13,451]  WARN
>>>>> {org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer} -
>>>>> Inbound JMS endpoint unable to get a connection.
>>>>> {org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer}
>>>>> TID: [-1234] [] [2016-02-24 15:30:14,451] ERROR
>>>>> {org.wso2.carbon.inbound.endpoint.protocol.jms.factory.JMSConnectionFactory}
>>>>> -  Connection cannot bb establish to the broke. Plese check the broker 
>>>>> libs
>>>>> provided.
>>>>> {org.wso2.carbon.inbound.endpoint.protocol.jms.factory.JMSConnectionFactory}
>>>>>
>>>>> This error will pop up from worker nodes. When clustering mode
>>>>> disabled, it will work properly.
>>>>>
>>>>> Is there any special configuration for HornetQ when ESB in clustering
>>>>> mode?
>>>>>
>>>>> As I found out, HornetQ "run.sh" script must modify to bind its' host
>>>>> name. Likewise is there any special configurations for ESB cluster ?
>>>>>
>>>>> Thank you in advance.
>>>>>
>>>>> [1] - https://redmine.wso2.com/issues/4121
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>>
>>>>> Software Engineer - QA
>>>>> WSO2, Inc.;http://wso2.com/
>>>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
>>>>> lean.enterprise.middleware
>>>>>
>>>>> Mobile: +94773375185
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Best Regards,
>>>>
>>>> Malaka Silva
>>>> Senior Tech Lead
>>>> M: +94 777 219 791
>>>> Tel : 94 11 214 5345
>>>> Fax :94 11 2145300
>>>> Skype : malaka.sampath.silva
>>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>>> Blog : http://mrmalakasilva.blogspot.com/
>>>>
>>>> WSO2, Inc.
>>>> lean . enterprise . middleware
>>>> http://www.wso2.com/
>>>> http://www.wso2.com/a

Re: [Dev] [ESB] Can we use sequence + endpoint at the same time within clone mediator ?

[Dilshani Subasinghe]

Identified this as invalid use case.

Thread closed.

Regards,
Dilshani

On Wed, Mar 23, 2016 at 6:21 PM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:

> Hi Malaka,
>
> Thanks for clarification. There was an old test case for $subject and I am
> checking validity of that. When I am implementing following sequences, it
> doesn't give an exact error. But it also do not send to back end. Is there
> any exact reason for that?
>
> 
> 
> 
> 
> http://localhost:9001/services/SimpleStockQuoteService/"/>
> 
> 
> 
> 
> 
>
> 
> 
>  xmlns:ns="http://org.apache.synapse/xsd;
> xmlns:ser="http://services.samples;
> xpath="concat(//ser:symbol/text(),'1')"/>
> 
> 
> 
>  type="property"/>
> http://org.apache.synapse/xsd;
> xmlns:ser="http://services.samples; xpath="//ser:symbol/text()"/>
> 
> 
>
> PS: Sample test case of above scenario is available at:
> https://testlink.wso2.com/linkto.php?tprojectPrefix=ESB=testcase=ESB-2254
>
> Thank you and Regards,
> Dilshani
>
>
>
> On Wed, Mar 23, 2016 at 6:14 PM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Hi Dilshani,
>>
>> Yes we can. But this does not make sense. What is the use case you are
>> trying to implement?
>>
>> On Wed, Mar 23, 2016 at 5:11 PM, Dilshani Subasinghe <dilsh...@wso2.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> Any ideas or comments on $subject?
>>>
>>> Regards,
>>> Dilshani
>>>
>>> --
>>> Best Regards,
>>>
>>> Dilshani Subasinghe
>>> Software Engineer - QA
>>> WSO2, Inc.;http://wso2.com/
>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94773375185
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> <http://wso2.com/about/team/malaka-silva/>
>> https://store.wso2.com/store/
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>
>
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
> lean.enterprise.middleware
>
> Mobile: +94773375185
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware

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

Re: [Dev] [ESB] Can we use sequence + endpoint at the same time within clone mediator ?

[Dilshani Subasinghe]

Hi Malaka,

Thanks for clarification. There was an old test case for $subject and I am
checking validity of that. When I am implementing following sequences, it
doesn't give an exact error. But it also do not send to back end. Is there
any exact reason for that?





http://localhost:9001/services/SimpleStockQuoteService/"/>








http://org.apache.synapse/xsd;
xmlns:ser="http://services.samples;
xpath="concat(//ser:symbol/text(),'1')"/>




http://org.apache.synapse/xsd;
xmlns:ser="http://services.samples; xpath="//ser:symbol/text()"/>



PS: Sample test case of above scenario is available at:
https://testlink.wso2.com/linkto.php?tprojectPrefix=ESB=testcase=ESB-2254

Thank you and Regards,
Dilshani



On Wed, Mar 23, 2016 at 6:14 PM, Malaka Silva <mal...@wso2.com> wrote:

> Hi Dilshani,
>
> Yes we can. But this does not make sense. What is the use case you are
> trying to implement?
>
> On Wed, Mar 23, 2016 at 5:11 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> Any ideas or comments on $subject?
>>
>> Regards,
>> Dilshani
>>
>> --
>> Best Regards,
>>
>> Dilshani Subasinghe
>> Software Engineer - QA
>> WSO2, Inc.;http://wso2.com/
>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
>> lean.enterprise.middleware
>>
>> Mobile: +94773375185
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> <http://wso2.com/about/team/malaka-silva/>
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware

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

[Dev] [ESB] Can we use sequence + endpoint at the same time within clone mediator ?

[Dilshani Subasinghe]

Hi all,

Any ideas or comments on $subject?

Regards,
Dilshani

-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware

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

Re: [Dev] [ESB] Error message when adding a datasource

[Dilshani Subasinghe]

Hi Ravindi,

When testing same configs with ESB 5.0.0 m2 pack [1], it doesn't give exact
error. You can try out. It may be fixed the issue through new pack.

[1] -
https://svn.wso2.org/repos/wso2/scratch/ESB/packs/5.0.0-Releases/5.0.0-M2/wso2esb-5.0.0-M2.zip

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

Re: [Dev] [ESB500] JMS Inbound Endpoint behavior with Session Acknowledgement

[Dilshani Subasinghe]

Hi all,

Any updates on issue?

Regards,
Dilshani

On Wed, Mar 2, 2016 at 3:18 PM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:

> Hi Malaka,
>
> Thank you and will try to proceed with that in mind. Still ESB having
> different behavior rather than normal JMS Client (Even though having same
> configurations). Will check on that.
>
> Regards,
> Dilshani
>
>
> On Wed, Mar 2, 2016 at 3:08 PM, Malaka Silva <mal...@wso2.com> wrote:
>
>>
>>
>> On Wed, Mar 2, 2016 at 2:55 PM, Dilshani Subasinghe <dilsh...@wso2.com>
>> wrote:
>>
>>> Hi Malaka,
>>>
>>> Thank you for explanations. I checked configurations and updated
>>> accordingly. And also there is a small point to clarify.
>>>
>>> When creating JMS Client use following function to create a session:
>>>
>>> *Session session = connection.createSession(false,
>>> Session.CLIENT_ACKNOWLEDGE);*
>>>
>>> JMS Inbound Endpoint will be using following parameter:
>>>
>>>
>>>
>>> *transport.jms.SessionAcknowledgement*
>>> Do both parameters refer same function of JMS ? Do ESB having special
>>> characteristics rather than normal JMS client ?
>>>
>> ​It's same.
>>
>> protected Session createSession(Connection connection) {
>> try {
>> if (jmsSpec11) {
>> return connection.createSession(transactedSession,
>> sessionAckMode);
>> } else {
>> if
>> (this.destinationType.equals(JMSConstants.JMSDestinationType.QUEUE)) {
>> return (QueueSession) ((QueueConnection)
>> (connection)).createQueueSession(
>> transactedSession, sessionAckMode);
>> } else if
>> (this.destinationType.equals(JMSConstants.JMSDestinationType.TOPIC)) {
>> return (TopicSession) ((TopicConnection)
>> (connection)).createTopicSession(
>> transactedSession, sessionAckMode);
>> }
>> }
>> } catch (JMSException e) {
>> logger.error("JMS Exception while obtaining session for
>> factory '"
>> + this.connectionFactoryString + "' " +
>> e.getMessage());
>> }
>>
>> return null;
>> }​
>>
>>
>>>
>>> Your support is highly appreciated.
>>>
>>> Regards,
>>> Dilshani
>>>
>>>
>>> On Tue, Mar 1, 2016 at 5:58 PM, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> Hi Dilshani,
>>>>
>>>> Flow is very simple except following exceptions. Take message ->
>>>> execute mediation (sequence) -> ack the broker.
>>>>
>>>> If you want to rollback set SET_ROLLBACK_ONLY mc property to true in
>>>> fault sequence.
>>>>
>>>> Also in mediation flow non-blocking mediator should be used. eg:-
>>>> callout mediator not send mediator.
>>>>
>>>> On Tue, Mar 1, 2016 at 3:34 PM, Dilshani Subasinghe <dilsh...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Malaka,
>>>>>
>>>>> In ESB, JMS Inbound endpoint can configure Acknowledgement Type with
>>>>> "transport.jms.SessionAcknowledgement". When it set as
>>>>> "Client_Acknowledge" , What will be the behavior of ESB ? Does it behave
>>>>> like normal JMS Client which enabled "Client_Acknowledgement" ?
>>>>>
>>>>> I'm using separate JMS Client with "Client_Acknowledge" mode and using
>>>>> it to test JMSX Delivery Count. But ESB Inbound endpoint doesn't behave
>>>>> like particular JMS Client (With "Client_Acknowledge" mode).
>>>>>
>>>>> Can you explain ESB behavior within the particular scenario ?
>>>>>
>>>>> Thank you.
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>>
>>>>> Dilshani Subasinghe
>>>>> Software Engineer - QA
>>>>> WSO2, Inc.;http://wso2.com/
>>>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
>>>>> lean.enterprise.middleware
>>>>>
>>>>> Mobile: +94773375185
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>

Re: [Dev] [ESB] Message processors support to On Store Sequence

[Dilshani Subasinghe]

Hi all,

Found the solution for particular issue. Error indicating about failing to
connect deactivate sequence.



* WARN - ForwardingService Failed to send the message through the
deactivate sequence. Sequence name does not Exist.*
According to configuration, after maximum delivery attempts, it will find
the deactivate sequence. But in this scenario, "Deactivate sequence" not
given.

So Configured "Drop message after maximum delivery attempts" as "Enabled".

This redelivery process going on because of back-end service is not alive
or processor can't find endpoint.

In this scenario, it was given direct endpoint (
http://127.0.0.1:9000/services/SimpleStockQuoteService) rather than giving
previously created endpoint. So it also cause for the issue.

Configuring those parameters, solved the issue. Hope this will be helpful
to someone.

Regards,
Dilshani.


On Thu, Mar 10, 2016 at 8:14 AM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:

> Hi ESB Team,
>
> When I am configuring Store mediator, I created an On Store Sequence.
>
>
>
> *http://ws.apache.org/ns/synapse
> <http://ws.apache.org/ns/synapse>"> sequence="conf:/registrySeq"
> xmlns:axis2ns17="http://ws.apache.org/ns/synapse
> <http://ws.apache.org/ns/synapse>"/>*
>
> Then I created another sequence with a store mediator (Store mediator used
> On Store Sequence)
>
>
>
>
>
> * sequence="conf:/registrySeq"/>  *
> Created a proxy and invoked it using axis2Client.
>
>
>
>
> * transports="http https"> inSequence="onstoreSeq"/>*
>
> Then I tried to add a Scheduled Message Forwarding Processor to send
> messages in the message store. As I used Store mediator through On Store
> Sequence, processor will automatically deactivate:
>
>
>
>
>
>
>
>
>
>
>
>
>
> *ForwardingService Deactivating the message processor
> [storeProce]java.lang.NullPointerExceptionat
> org.apache.synapse.message.processor.impl.forwarder.ForwardingService.dispatch(ForwardingService.java:431)
> at
> org.apache.synapse.message.processor.impl.forwarder.ForwardingService.execute(ForwardingService.java:204)
> at
> org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(NTaskAdapter.java:90)
> at
> org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:67)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)[2016-03-09 23:58:51,712]  WARN -
> ForwardingService Failed to send the message through the deactivate
> sequence. Sequence name does not Exist.*
>
>
> *Issue*: Can we implement message processor which have connection to On
> Store Sequence as it not including in synapse ? Why message processor do
> not identify On Store Sequence?
>
> Any clarification on this ? Any help will be highly appreciated.
>
> PS: Attached Synapse Configuration XML.
>
> Thank you.
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
> lean.enterprise.middleware
>
> Mobile: +94773375185
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware

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

Re: [Dev] [ESB500][Error]- Delivery Delay property in Cluster Setup

[Dilshani Subasinghe]

Hi all,

Added a jira issue[1] for particular error.

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

Regards,
Dilshani

On Mon, Mar 7, 2016 at 2:06 PM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:

> Hi all,
>
> When testing the feature "JMS 2.0:Delivery Delay" [1] in a cluster setup,
> it gave the following error.
>
> Any idea about error or how to solve that ?
>
> Any support is highly appreciated.
>
> ERROR - Axis2Sender Unexpected error during sending message out
> javax.jms.JMSRuntimeException: HQ129012: The property name {0} is not a
> valid java identifier.
> at
> org.hornetq.jms.client.HornetQMessage.checkProperty(HornetQMessage.java:1113)
> at
> org.hornetq.jms.client.HornetQMessage.setStringProperty(HornetQMessage.java:797)
> at
> org.apache.axis2.transport.jms.JMSUtils.setTransportHeaders(JMSUtils.java:322)
> at
> org.apache.axis2.transport.jms.JMSSender.createJMSMessage(JMSSender.java:482)
> at
> org.apache.axis2.transport.jms.JMSSender.sendOverJMS(JMSSender.java:187)
> at
> org.apache.axis2.transport.jms.JMSSender.sendMessage(JMSSender.java:169)
> at
> org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at
> org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:297)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:558)
> at
> org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:79)
> at
> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:551)
> at
> org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:387)
> at
> org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:65)
> at
> org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:111)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:86)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:49)
> at
> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:163)
> at
> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:211)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at
> org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:395)
> at
> org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
> 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:745)
>
>
>
> [1] -
> https://docs.google.com/document/d/19vEMJEYBo_iSgo3GoRJ5s4cNtcHvLJmd3G6QnldiGrs/edit
>
> Thank you,
>
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
> lean.enterprise.middleware
>
> Mobile: +94773375185
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware

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

[Dev] [ESB] Message processors support to On Store Sequence

[Dilshani Subasinghe]

Hi ESB Team,

When I am configuring Store mediator, I created an On Store Sequence.



*http://ws.apache.org/ns/synapse
<http://ws.apache.org/ns/synapse>">http://ws.apache.org/ns/synapse
<http://ws.apache.org/ns/synapse>"/>*

Then I created another sequence with a store mediator (Store mediator used
On Store Sequence)





*  *
Created a proxy and invoked it using axis2Client.




*
*

Then I tried to add a Scheduled Message Forwarding Processor to send
messages in the message store. As I used Store mediator through On Store
Sequence, processor will automatically deactivate:













*ForwardingService Deactivating the message processor
[storeProce]java.lang.NullPointerExceptionat
org.apache.synapse.message.processor.impl.forwarder.ForwardingService.dispatch(ForwardingService.java:431)
at
org.apache.synapse.message.processor.impl.forwarder.ForwardingService.execute(ForwardingService.java:204)
at
org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(NTaskAdapter.java:90)
at
org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:67)
at org.quartz.core.JobRunShell.run(JobRunShell.java:213)at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)[2016-03-09 23:58:51,712]  WARN -
ForwardingService Failed to send the message through the deactivate
sequence. Sequence name does not Exist.*


*Issue*: Can we implement message processor which have connection to On
Store Sequence as it not including in synapse ? Why message processor do
not identify On Store Sequence?

Any clarification on this ? Any help will be highly appreciated.

PS: Attached Synapse Configuration XML.

Thank you.

-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware

Mobile: +94773375185

http://ws.apache.org/ns/synapse;>

15000























http://localhost:9000.*; source="get-property('To')">







The main sequence for the message mediation


http://127.0.0.1:9000/services/SimpleStockQuoteService;>
1000
false
4
1
Disabled
1000
true
http://127.0.0.1:9000/services/SimpleStockQuoteService


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

[Dev] [ESB500][Error]- Delivery Delay property in Cluster Setup

[Dilshani Subasinghe]

Hi all,

When testing the feature "JMS 2.0:Delivery Delay" [1] in a cluster setup,
it gave the following error.

Any idea about error or how to solve that ?

Any support is highly appreciated.

ERROR - Axis2Sender Unexpected error during sending message out
javax.jms.JMSRuntimeException: HQ129012: The property name {0} is not a
valid java identifier.
at
org.hornetq.jms.client.HornetQMessage.checkProperty(HornetQMessage.java:1113)
at
org.hornetq.jms.client.HornetQMessage.setStringProperty(HornetQMessage.java:797)
at
org.apache.axis2.transport.jms.JMSUtils.setTransportHeaders(JMSUtils.java:322)
at
org.apache.axis2.transport.jms.JMSSender.createJMSMessage(JMSSender.java:482)
at
org.apache.axis2.transport.jms.JMSSender.sendOverJMS(JMSSender.java:187)
at
org.apache.axis2.transport.jms.JMSSender.sendMessage(JMSSender.java:169)
at
org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:297)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:558)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:79)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:551)
at
org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:387)
at
org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:65)
at
org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:111)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:86)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:49)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:163)
at
org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:211)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:395)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
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:745)



[1] -
https://docs.google.com/document/d/19vEMJEYBo_iSgo3GoRJ5s4cNtcHvLJmd3G6QnldiGrs/edit

Thank you,


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware

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

Re: [Dev] [ESB500] JMS Inbound Endpoint behavior with Session Acknowledgement

[Dilshani Subasinghe]

Hi Malaka,

Thank you and will try to proceed with that in mind. Still ESB having
different behavior rather than normal JMS Client (Even though having same
configurations). Will check on that.

Regards,
Dilshani


On Wed, Mar 2, 2016 at 3:08 PM, Malaka Silva <mal...@wso2.com> wrote:

>
>
> On Wed, Mar 2, 2016 at 2:55 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi Malaka,
>>
>> Thank you for explanations. I checked configurations and updated
>> accordingly. And also there is a small point to clarify.
>>
>> When creating JMS Client use following function to create a session:
>>
>> *Session session = connection.createSession(false,
>> Session.CLIENT_ACKNOWLEDGE);*
>>
>> JMS Inbound Endpoint will be using following parameter:
>>
>>
>>
>> *transport.jms.SessionAcknowledgement*
>> Do both parameters refer same function of JMS ? Do ESB having special
>> characteristics rather than normal JMS client ?
>>
> ​It's same.
>
> protected Session createSession(Connection connection) {
> try {
> if (jmsSpec11) {
> return connection.createSession(transactedSession,
> sessionAckMode);
> } else {
> if
> (this.destinationType.equals(JMSConstants.JMSDestinationType.QUEUE)) {
> return (QueueSession) ((QueueConnection)
> (connection)).createQueueSession(
> transactedSession, sessionAckMode);
> } else if
> (this.destinationType.equals(JMSConstants.JMSDestinationType.TOPIC)) {
> return (TopicSession) ((TopicConnection)
> (connection)).createTopicSession(
> transactedSession, sessionAckMode);
> }
> }
> } catch (JMSException e) {
> logger.error("JMS Exception while obtaining session for
> factory '"
> + this.connectionFactoryString + "' " +
> e.getMessage());
> }
>
> return null;
> }​
>
>
>>
>> Your support is highly appreciated.
>>
>> Regards,
>> Dilshani
>>
>>
>> On Tue, Mar 1, 2016 at 5:58 PM, Malaka Silva <mal...@wso2.com> wrote:
>>
>>> Hi Dilshani,
>>>
>>> Flow is very simple except following exceptions. Take message -> execute
>>> mediation (sequence) -> ack the broker.
>>>
>>> If you want to rollback set SET_ROLLBACK_ONLY mc property to true in
>>> fault sequence.
>>>
>>> Also in mediation flow non-blocking mediator should be used. eg:-
>>> callout mediator not send mediator.
>>>
>>> On Tue, Mar 1, 2016 at 3:34 PM, Dilshani Subasinghe <dilsh...@wso2.com>
>>> wrote:
>>>
>>>> Hi Malaka,
>>>>
>>>> In ESB, JMS Inbound endpoint can configure Acknowledgement Type with
>>>> "transport.jms.SessionAcknowledgement". When it set as
>>>> "Client_Acknowledge" , What will be the behavior of ESB ? Does it behave
>>>> like normal JMS Client which enabled "Client_Acknowledgement" ?
>>>>
>>>> I'm using separate JMS Client with "Client_Acknowledge" mode and using
>>>> it to test JMSX Delivery Count. But ESB Inbound endpoint doesn't behave
>>>> like particular JMS Client (With "Client_Acknowledge" mode).
>>>>
>>>> Can you explain ESB behavior within the particular scenario ?
>>>>
>>>> Thank you.
>>>>
>>>> --
>>>> Best Regards,
>>>>
>>>> Dilshani Subasinghe
>>>> Software Engineer - QA
>>>> WSO2, Inc.;http://wso2.com/
>>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
>>>> lean.enterprise.middleware
>>>>
>>>> Mobile: +94773375185
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>> Malaka Silva
>>> Senior Tech Lead
>>> M: +94 777 219 791
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>> Skype : malaka.sampath.silva
>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>> Blog : http://mrmalakasilva.blogspot.com/
>>>
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> http://www.wso2.com/
>>> http://www.wso2.com/about/team/malaka-silva/
>>> <http://wso2.com/about/team/malaka-silva/>
>>> https://store.wso2.co

Re: [Dev] [ESB500] JMS Inbound Endpoint behavior with Session Acknowledgement

[Dilshani Subasinghe]

Hi Malaka,

Thank you for explanations. I checked configurations and updated
accordingly. And also there is a small point to clarify.

When creating JMS Client use following function to create a session:

*Session session = connection.createSession(false,
Session.CLIENT_ACKNOWLEDGE);*

JMS Inbound Endpoint will be using following parameter:



*transport.jms.SessionAcknowledgement*
Do both parameters refer same function of JMS ? Do ESB having special
characteristics rather than normal JMS client ?

Your support is highly appreciated.

Regards,
Dilshani


On Tue, Mar 1, 2016 at 5:58 PM, Malaka Silva <mal...@wso2.com> wrote:

> Hi Dilshani,
>
> Flow is very simple except following exceptions. Take message -> execute
> mediation (sequence) -> ack the broker.
>
> If you want to rollback set SET_ROLLBACK_ONLY mc property to true in fault
> sequence.
>
> Also in mediation flow non-blocking mediator should be used. eg:- callout
> mediator not send mediator.
>
> On Tue, Mar 1, 2016 at 3:34 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi Malaka,
>>
>> In ESB, JMS Inbound endpoint can configure Acknowledgement Type with
>> "transport.jms.SessionAcknowledgement". When it set as
>> "Client_Acknowledge" , What will be the behavior of ESB ? Does it behave
>> like normal JMS Client which enabled "Client_Acknowledgement" ?
>>
>> I'm using separate JMS Client with "Client_Acknowledge" mode and using it
>> to test JMSX Delivery Count. But ESB Inbound endpoint doesn't behave like
>> particular JMS Client (With "Client_Acknowledge" mode).
>>
>> Can you explain ESB behavior within the particular scenario ?
>>
>> Thank you.
>>
>> --
>> Best Regards,
>>
>> Dilshani Subasinghe
>> Software Engineer - QA
>> WSO2, Inc.;http://wso2.com/
>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
>> lean.enterprise.middleware
>>
>> Mobile: +94773375185
>>
>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> <http://wso2.com/about/team/malaka-silva/>
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware

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

[Dev] [ESB500] JMS Inbound Endpoint behavior with Session Acknowledgement

[Dilshani Subasinghe]

Hi Malaka,

In ESB, JMS Inbound endpoint can configure Acknowledgement Type with
"transport.jms.SessionAcknowledgement". When it set as "Client_Acknowledge"
, What will be the behavior of ESB ? Does it behave like normal JMS Client
which enabled "Client_Acknowledgement" ?

I'm using separate JMS Client with "Client_Acknowledge" mode and using it
to test JMSX Delivery Count. But ESB Inbound endpoint doesn't behave like
particular JMS Client (With "Client_Acknowledge" mode).

Can you explain ESB behavior within the particular scenario ?

Thank you.

-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware

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

Re: [Dev] [ESB500]Error in Clustering Mode - JMS 2.0 Feature:Shared Topic Subscription

[Dilshani Subasinghe]

Hi Ravindra,

Yes I doubled checked libraries and It will work properly when "Clustering"
mode disabled.

Yes, it will be giving an error regarding libraries and jars. But same
error pop up when it can not process with HornetQ. Previously I experienced
that. When HornetQ cannot bind its' host name, it must modify its "run.sh"
script. With that issue also, ESB giving same error with misleading error
message about broker jars [1].


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

Regards,
Dilshani


On Thu, Feb 25, 2016 at 10:20 AM, Ravindra Ranwala <ravin...@wso2.com>
wrote:

> Hi Dilshani,
>
> AFAIK there's no special configuration for this in ESB side. Have you
> copied all the libraries to the workers properly? If so we have to debug
> and see the root cause of the issue.
>
>
> Thanks & Regards,
>
> On Thu, Feb 25, 2016 at 8:14 AM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi Malaka,
>>
>> This issue about clustering. Multiple subscribers do not affect to the
>> error.
>>
>> Yes, I am using M2 pack.
>>
>> Regards,
>> Dilshani
>>
>>
>> On Wed, Feb 24, 2016 at 8:38 PM, Malaka Silva <mal...@wso2.com> wrote:
>>
>>> Hi Dilshani,
>>>
>>> Just to be clear is this issue related to clustering or issue persist
>>> when there are multiple subscribers?
>>>
>>> Also you must be using esb 5 milestone pack?
>>>
>>> On Wed, Feb 24, 2016 at 7:09 PM, Dilshani Subasinghe <dilsh...@wso2.com>
>>> wrote:
>>>
>>>> Hi ESB Team,
>>>>
>>>> I am testing new fearure called "JMS 2.0.0 Support"[1] and found an
>>>> error in "JMS 2.0 Feature:Shared Topic Subscription". Feature will
>>>> successfully functioning in Standalone mode. But it clustering mode, it
>>>> will provide an error as follows;
>>>>
>>>>  TID: [-1234] [] [2016-02-24 15:30:13,451]  WARN
>>>> {org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer} -
>>>> Inbound JMS endpoint unable to get a connection.
>>>> {org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer}
>>>> TID: [-1234] [] [2016-02-24 15:30:14,451] ERROR
>>>> {org.wso2.carbon.inbound.endpoint.protocol.jms.factory.JMSConnectionFactory}
>>>> -  Connection cannot bb establish to the broke. Plese check the broker libs
>>>> provided.
>>>> {org.wso2.carbon.inbound.endpoint.protocol.jms.factory.JMSConnectionFactory}
>>>>
>>>> This error will pop up from worker nodes. When clustering mode
>>>> disabled, it will work properly.
>>>>
>>>> Is there any special configuration for HornetQ when ESB in clustering
>>>> mode?
>>>>
>>>> As I found out, HornetQ "run.sh" script must modify to bind its' host
>>>> name. Likewise is there any special configurations for ESB cluster ?
>>>>
>>>> Thank you in advance.
>>>>
>>>> [1] - https://redmine.wso2.com/issues/4121
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>>
>>>> Software Engineer - QA
>>>> WSO2, Inc.;http://wso2.com/
>>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
>>>> lean.enterprise.middleware
>>>>
>>>> Mobile: +94773375185
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>> Malaka Silva
>>> Senior Tech Lead
>>> M: +94 777 219 791
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>> Skype : malaka.sampath.silva
>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>> Blog : http://mrmalakasilva.blogspot.com/
>>>
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> http://www.wso2.com/
>>> http://www.wso2.com/about/team/malaka-silva/
>>> <http://wso2.com/about/team/malaka-silva/>
>>> https://store.wso2.com/store/
>>>
>>> Save a tree -Conserve nature & Save the world for your future. Print
>>> this email only if it is absolutely necessary.
>>>
>>
>>
>>
>> --
>> Best Regards,
>>
>> Dilshani Subasinghe
>> Software Engineer - QA
>> WSO2, Inc.;http://wso2.com/
>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
>> lean.enterprise.middleware
>>
>> Mobile: +94773375185
>>
>
>
>
> --
> Ravindra Ranwala
> Software Engineer
> WSO2, Inc: http://wso2.com
> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com=D=1=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
> Mobile: +94714198770
>
>


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware

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

Re: [Dev] [ESB500]Error in Clustering Mode - JMS 2.0 Feature:Shared Topic Subscription

[Dilshani Subasinghe]

Hi Malaka,

This issue about clustering. Multiple subscribers do not affect to the
error.

Yes, I am using M2 pack.

Regards,
Dilshani


On Wed, Feb 24, 2016 at 8:38 PM, Malaka Silva <mal...@wso2.com> wrote:

> Hi Dilshani,
>
> Just to be clear is this issue related to clustering or issue persist when
> there are multiple subscribers?
>
> Also you must be using esb 5 milestone pack?
>
> On Wed, Feb 24, 2016 at 7:09 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi ESB Team,
>>
>> I am testing new fearure called "JMS 2.0.0 Support"[1] and found an error
>> in "JMS 2.0 Feature:Shared Topic Subscription". Feature will successfully
>> functioning in Standalone mode. But it clustering mode, it will provide an
>> error as follows;
>>
>>  TID: [-1234] [] [2016-02-24 15:30:13,451]  WARN
>> {org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer} -
>> Inbound JMS endpoint unable to get a connection.
>> {org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer}
>> TID: [-1234] [] [2016-02-24 15:30:14,451] ERROR
>> {org.wso2.carbon.inbound.endpoint.protocol.jms.factory.JMSConnectionFactory}
>> -  Connection cannot bb establish to the broke. Plese check the broker libs
>> provided.
>> {org.wso2.carbon.inbound.endpoint.protocol.jms.factory.JMSConnectionFactory}
>>
>> This error will pop up from worker nodes. When clustering mode disabled,
>> it will work properly.
>>
>> Is there any special configuration for HornetQ when ESB in clustering
>> mode?
>>
>> As I found out, HornetQ "run.sh" script must modify to bind its' host
>> name. Likewise is there any special configurations for ESB cluster ?
>>
>> Thank you in advance.
>>
>> [1] - https://redmine.wso2.com/issues/4121
>>
>>
>> --
>> Best Regards,
>>
>> Software Engineer - QA
>> WSO2, Inc.;http://wso2.com/
>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
>> lean.enterprise.middleware
>>
>> Mobile: +94773375185
>>
>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> <http://wso2.com/about/team/malaka-silva/>
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware

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

[Dev] [ESB500]Error in Clustering Mode - JMS 2.0 Feature:Shared Topic Subscription

[Dilshani Subasinghe]

Hi ESB Team,

I am testing new fearure called "JMS 2.0.0 Support"[1] and found an error
in "JMS 2.0 Feature:Shared Topic Subscription". Feature will successfully
functioning in Standalone mode. But it clustering mode, it will provide an
error as follows;

 TID: [-1234] [] [2016-02-24 15:30:13,451]  WARN
{org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer} -
Inbound JMS endpoint unable to get a connection.
{org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer}
TID: [-1234] [] [2016-02-24 15:30:14,451] ERROR
{org.wso2.carbon.inbound.endpoint.protocol.jms.factory.JMSConnectionFactory}
-  Connection cannot bb establish to the broke. Plese check the broker libs
provided.
{org.wso2.carbon.inbound.endpoint.protocol.jms.factory.JMSConnectionFactory}

This error will pop up from worker nodes. When clustering mode disabled, it
will work properly.

Is there any special configuration for HornetQ when ESB in clustering mode?

As I found out, HornetQ "run.sh" script must modify to bind its' host name.
Likewise is there any special configurations for ESB cluster ?

Thank you in advance.

[1] - https://redmine.wso2.com/issues/4121


-- 
Best Regards,

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

lean.enterprise.middleware

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

Re: [Dev] [ESB] [Redmine] Feature #4055 -JMS Transaction support for Store Mediator

[Dilshani Subasinghe]

Hi Malaka and Prabath,

Noted. Thanks for clearing conflicting points.

Regards,
Dilshani

On Wed, Feb 17, 2016 at 5:34 PM, Prabath Ariyarathna <prabat...@wso2.com>
wrote:

> Hi Dilshani.
>
> Yes, title is little bit confusing. This feature was
> implemented for adding guaranteed delivery capability to the store
> mediator. We achieved this by using "Failover Message Store and Scheduled
> Failover Message Forwarding Processor".
>
> Can someone please help in understanding how this scenario relate to JMS
> Transactions ?
> We added JMS transaction between store mediator and message broker for the
> gurenteed delivery scenarios. This is only effect to the JMS message store.
>
> Is this "Guaranteed Delivery with Failover Message Store and Scheduled
> Failover Message Forwarding Processor" scenario limited to JMS message
> stores?
> This is not limited to the JMS message store.
>
>
> Thanks.
>
>
> On Wed, Feb 17, 2016 at 1:30 PM, Malaka Silva <mal...@wso2.com> wrote:
>
>> You can do this with JMS transport. [1] [2]
>>
>> But in your mediation flow only blocking calls needs to be implemented.
>> AFAIK MSMP does not support transactions.
>>
>> [1] https://docs.wso2.com/display/ESB490/JMS+Inbound+Protocol
>> [2] https://docs.wso2.com/display/ESB490/JMS+FAQ
>>
>> On Wed, Feb 17, 2016 at 12:00 PM, Dilshani Subasinghe <dilsh...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I am working with $subject[1] in QA perspectives and identified relevant
>>> scenarios through given documentations. But that feature titled as " JMS
>>> Transaction support for Store Mediator" and Feature will introduce
>>> "Scheduled Failover Message Forwarding Processor".
>>>
>>> Little bit confused with the title and the new processor introduced with
>>> this redmine. Can someone please help in understanding how this scenario
>>> relate to JMS Transactions ?
>>>
>>> Given sample scenario[2] will indicating that, we can choose JMS message
>>> store to create original message store. Hope this scenario not limited to
>>> JMS message stores.
>>>
>>> Is this "Guaranteed Delivery with Failover Message Store and Scheduled
>>> Failover Message Forwarding Processor" scenario limited to JMS message
>>> stores?
>>>
>>>
>>> [1] - https://redmine.wso2.com/issues/4055
>>> [2] -
>>> https://docs.wso2.com/display/ESB490/Guaranteed+Delivery+with+Failover+Message+Store+and+Scheduled+Failover+Message+Forwarding+Processor
>>>
>>> Thank you
>>>
>>> --
>>> Best Regards,
>>>
>>> Software Engineer - QA
>>> WSO2, Inc.;http://wso2.com/
>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94773375185
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> <http://wso2.com/about/team/malaka-silva/>
>> https://store.wso2.com/store/
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>
>
>
> --
>
> *Prabath Ariyarathna*
>
> *Associate Technical Lead*
>
> *WSO2, Inc. *
>
> *lean . enterprise . middleware *
>
>
> *Email: prabat...@wso2.com <prabat...@wso2.com>*
>
> *Blog: http://prabu-lk.blogspot.com <http://prabu-lk.blogspot.com>*
>
> *Flicker : https://www.flickr.com/photos/47759189@N08
> <https://www.flickr.com/photos/47759189@N08>*
>
> *Mobile: +94 77 699 4730 *
>
>
>
>
>
>


-- 
Best Regards,

Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware

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

[Dev] [ESB] [Redmine] Feature #4055 -JMS Transaction support for Store Mediator

[Dilshani Subasinghe]

Hi,

I am working with $subject[1] in QA perspectives and identified relevant
scenarios through given documentations. But that feature titled as " JMS
Transaction support for Store Mediator" and Feature will introduce
"Scheduled Failover Message Forwarding Processor".

Little bit confused with the title and the new processor introduced with
this redmine. Can someone please help in understanding how this scenario
relate to JMS Transactions ?

Given sample scenario[2] will indicating that, we can choose JMS message
store to create original message store. Hope this scenario not limited to
JMS message stores.

Is this "Guaranteed Delivery with Failover Message Store and Scheduled
Failover Message Forwarding Processor" scenario limited to JMS message
stores?


[1] - https://redmine.wso2.com/issues/4055
[2] -
https://docs.wso2.com/display/ESB490/Guaranteed+Delivery+with+Failover+Message+Store+and+Scheduled+Failover+Message+Forwarding+Processor

Thank you

-- 
Best Regards,

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

lean.enterprise.middleware

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