Re: [Dev] Getting "SignatureDoesNotMatch" error with deleteBucketReplication operation in Amazon s3 connector

[Biruntha Gnaneswaran]

Sender I/O
dispatcher-1 << "[\r][\n]"
[2018-11-08 09:12:12,744] [EI-Core] DEBUG - wire HTTP-Sender I/O
dispatcher-1 >> "HTTP/1.1 400 Bad Request[\r][\n]"
[2018-11-08 09:12:12,745] [EI-Core] DEBUG - wire HTTP-Sender I/O
dispatcher-1 >> "x-amz-request-id: B6F5E938580BA667[\r][\n]"
[2018-11-08 09:12:12,746] [EI-Core] DEBUG - wire HTTP-Sender I/O
dispatcher-1 >> "x-amz-id-2: r6uXD7k9kVwqCAPd44EnDB6xm80XtQ
jBQpGW1NY+ozg/UIgajRw2ZZmD/u+gGJy5e3ypGBli1U0=[\r][\n]"
[2018-11-08 09:12:12,746] [EI-Core] DEBUG - wire HTTP-Sender I/O
dispatcher-1 >> "Content-Type: application/xml[\r][\n]"
[2018-11-08 09:12:12,746] [EI-Core] DEBUG - wire HTTP-Sender I/O
dispatcher-1 >> "Transfer-Encoding: chunked[\r][\n]"
[2018-11-08 09:12:12,747] [EI-Core] DEBUG - wire HTTP-Sender I/O
dispatcher-1 >> "Date: Thu, 08 Nov 2018 03:42:13 GMT[\r][\n]"
[2018-11-08 09:12:12,747] [EI-Core] DEBUG - wire HTTP-Sender I/O
dispatcher-1 >> "Connection: close[\r][\n]"
[2018-11-08 09:12:12,748] [EI-Core] DEBUG - wire HTTP-Sender I/O
dispatcher-1 >> "Server: AmazonS3[\r][\n]"
[2018-11-08 09:12:12,748] [EI-Core] DEBUG - wire HTTP-Sender I/O
dispatcher-1 >> "[\r][\n]"
[2018-11-08 09:12:12,748] [EI-Core] DEBUG - wire HTTP-Sender I/O
dispatcher-1 >> "168[\r][\n]"
[2018-11-08 09:12:12,748] [EI-Core] DEBUG - wire HTTP-Sender I/O
dispatcher-1 >> "[\n]"
[2018-11-08 09:12:12,749] [EI-Core] DEBUG - wire HTTP-Sender I/O
dispatcher-1 >> "RequestTimeoutYour socket
connection to the server was not read from or written to within the timeout
period. Idle connections will be closed.
B6F5E938580BA667r6uXD7k9kVwqCAPd44EnDB6xm80XtQ
jBQpGW1NY+ozg/UIgajRw2ZZmD/u+gGJy5e3ypGBli1U0=[\r][\n]"
[2018-11-08 09:12:12,749] [EI-Core] DEBUG - wire HTTP-Sender I/O
dispatcher-1 >> "0[\r][\n]"
[2018-11-08 09:12:12,749] [EI-Core] DEBUG - wire HTTP-Sender I/O
dispatcher-1 >> "[\r][\n]"
[2018-11-08 09:12:12,755] [EI-Core] DEBUG - headers http-outgoing-1 <<
HTTP/1.1 400 Bad Request
[2018-11-08 09:12:12,755] [EI-Core] DEBUG - headers http-outgoing-1 <<
x-amz-request-id: B6F5E938580BA667
[2018-11-08 09:12:12,756] [EI-Core] DEBUG - headers http-outgoing-1 <<
x-amz-id-2: r6uXD7k9kVwqCAPd44EnDB6xm80XtQjBQpGW1NY+ozg/UIgajRw2ZZmD/u+
gGJy5e3ypGBli1U0=
[2018-11-08 09:12:12,756] [EI-Core] DEBUG - headers http-outgoing-1 <<
Content-Type: application/xml
[2018-11-08 09:12:12,757] [EI-Core] DEBUG - headers http-outgoing-1 <<
Transfer-Encoding: chunked
[2018-11-08 09:12:12,758] [EI-Core] DEBUG - headers http-outgoing-1 <<
Date: Thu, 08 Nov 2018 03:42:13 GMT
[2018-11-08 09:12:12,758] [EI-Core] DEBUG - headers http-outgoing-1 <<
Connection: close
[2018-11-08 09:12:12,758] [EI-Core] DEBUG - headers http-outgoing-1 <<
Server: AmazonS3
[2018-11-08 09:12:12,794] [EI-Core]  WARN - SequenceMediator onError
handler : faultHandlerSeq for sequence : null cannot be found
[2018-11-08 09:12:12,802] [EI-Core] DEBUG - headers http-incoming-1 <<
HTTP/1.1 400 Bad Request
[2018-11-08 09:12:12,802] [EI-Core] DEBUG - headers http-incoming-1 <<
Content-Type: application/xml
[2018-11-08 09:12:12,802] [EI-Core] DEBUG - headers http-incoming-1 <<
Date: Thu, 08 Nov 2018 03:42:12 GMT
[2018-11-08 09:12:12,802] [EI-Core] DEBUG - headers http-incoming-1 <<
Transfer-Encoding: chunked
[2018-11-08 09:12:12,802] [EI-Core] DEBUG - headers http-incoming-1 <<
Connection: Close
[2018-11-08 09:12:12,803] [EI-Core] DEBUG - wire HTTP-Listener I/O
dispatcher-1 << "HTTP/1.1 400 Bad Request[\r][\n]"
[2018-11-08 09:12:12,804] [EI-Core] DEBUG - wire HTTP-Listener I/O
dispatcher-1 << "Content-Type: application/xml[\r][\n]"
[2018-11-08 09:12:12,804] [EI-Core] DEBUG - wire HTTP-Listener I/O
dispatcher-1 << "Date: Thu, 08 Nov 2018 03:42:12 GMT[\r][\n]"
[2018-11-08 09:12:12,804] [EI-Core] DEBUG - wire HTTP-Listener I/O
dispatcher-1 << "Transfer-Encoding: chunked[\r][\n]"
[2018-11-08 09:12:12,804] [EI-Core] DEBUG - wire HTTP-Listener I/O
dispatcher-1 << "Connection: Close[\r][\n]"
[2018-11-08 09:12:12,804] [EI-Core] DEBUG - wire HTTP-Listener I/O
dispatcher-1 << "[\r][\n]"
[2018-11-08 09:12:12,804] [EI-Core] DEBUG - wire HTTP-Listener I/O
dispatcher-1 << "168[\r][\n]"
[2018-11-08 09:12:12,804] [EI-Core] DEBUG - wire HTTP-Listener I/O
dispatcher-1 << "[\n]"
[2018-11-08 09:12:12,804] [EI-Core] DEBUG - wire HTTP-Listener I/O
dispatcher-1 << "RequestTimeoutYour socket
connection to the server was not read from or written to within the timeout
period. Idle connections will be closed.
B6F5E938580BA667r6uXD7k9kVwqCAPd44EnDB6xm80XtQ
jBQpGW1NY+ozg/UIgajRw2ZZmD/u+gGJy5e3ypGBli1U0=[\r][\n]"
[2018-11-08 09:12:12,8

Re: [Dev] Delay in sending SMS from ESB SMPP connector

[Biruntha Gnaneswaran]

Hi Gayan,

No we can't specify scheduled delivery time as null. Here in [1], we
specify delivery time as current time (new Date()) for immediate deliver of
the SMS.

[1] https://github.com/wso2-extensions/esb-connector-smpp/
blob/master/src/main/java/org/wso2/carbon/esb/connector/SendSMS.java#L127


On Thu, Oct 25, 2018 at 2:29 PM, gayan gunawardana 
wrote:

> Hi Team,
>
> Can we set scheduled delivery time to *null* in [1] to immediately
> deliver the SMS ? Currently I'm observing some delay due to time zone gap
> between SMS gatway and ESB.
>
> [1] https://github.com/wso2-extensions/esb-connector-smpp/
> blob/master/src/main/java/org/wso2/carbon/esb/connector/SendSMS.java#L127
> 
>
> --
> Gayan
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Biruntha

Software Engineer
WSO2
Email: birun...@wso2.com
LinkedIn: https://lk.linkedin.com/in/biruntha
Mobile : +94773718986
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting "SignatureDoesNotMatch" error with deleteBucketReplication operation in Amazon s3 connector

[Biruntha Gnaneswaran]

Hi Shakila,

I have tried as you mentioned but still I'm getting "SignatureDoesNotMatch"
error. So, I have posted stackoverflow question regarding this [1].

[1]
https://stackoverflow.com/questions/52714250/getting-signaturedoesnotmatch-error-with-delete-bucket-replication-operation-i

Thanks,

On Mon, Oct 8, 2018 at 1:56 PM, Shakila Sasikaran  wrote:

> Hi Biruntha,
>
> As per the API documentation [1], I think the bucket URL should be like
> /. Could you please try with 
> *http://testbuckkkbiru.s3-us-east-2.amazonaws.com
> <http://testbuckkkbiru.s3-us-east-2.amazonaws.com>*?
>
> [1] https://docs.aws.amazon.com/AmazonS3/latest/API/
> RESTBucketDELETEreplication.html
>
> Thanks
>
> On Fri, Oct 5, 2018 at 3:00 PM Biruntha Gnaneswaran 
> wrote:
>
>> Hi All,
>>
>> I'm trying to use deleteBucketReplication operation in amazon s3
>> connector [1] & [2]. But I'm getting "SignatureDoesNotMatch" error with the
>> sample request [3] & [4].  When I try this method with host and bucketUrl
>> as in [5], I'm getting error as in [6]. Am I missed anything? Appreciate
>> your input on this.
>>
>>
>> [1] https://docs.aws.amazon.com/AmazonS3/latest/API/
>> RESTBucketDELETEreplication.html
>> [2] https://docs.wso2.com/display/ESBCONNECTORS/Working+with+
>> Buckets+in+Amazon+S3#WorkingwithBucketsinAmazonS3-deleteBucketReplication
>> [3]
>> 
>> xx
>> xx
>> DELETE
>> application/xml
>> true
>> http://testbuckkkbiru.s3.amazonaws.com
>> 
>> 
>> us-east-2
>> testbuckkkbiru
>> s3.amazonaws.com
>> 
>> 
>> public-read
>> 
>> [4]
>> 
>> http://ws.apache.org/ns/synapse";
>>name="amazons3_deleteBucketReplication"
>>startOnLoad="true"
>>statistics="disable"
>>trace="disable"
>>transports="http,https">
>>
>>   
>>  
>>  > name="secretAccessKey"/>
>>  
>>  
>>  
>>  
>>  
>>  
>>  > name="xAmzSecurityToken"/>
>>  
>>  
>>  > name="contentLength"/>
>>  
>>  
>>  
>> {$ctx:accessKeyId}
>> {$ctx:secretAccessKey}
>> {$ctx:methodType}
>> {$ctx:contentType}
>> {$ctx:bucketName}
>> {$ctx:isXAmzDate}
>> {$ctx:contentMD5}
>> {$ctx:xAmzSecurityToken}> xAmzSecurityToken>
>> {$ctx:region}
>> {$ctx:host}
>> {$ctx:expect}
>> {$ctx:contentLength}
>> {$ctx:xAmzMfa}
>>  
>>  
>> {$ctx:bucketUrl}
>>  
>>  
>>   
>>   
>>  
>>   
>>
>>
>> 
>>
>> [5]
>> s3-us-east-2.amazonaws.com
>> http://s3-us-east-2.amazonaws.com/testbuckkkbiru
>>
>> [6]
>> RequestTimeoutYour socket connection to the
>> server was not read from or written to within the timeout period. Idle
>> connections will be closed.
>> DEEACD868FB28742zVKD6i4XzrWD7Dh8htoqPrlDypGClg
>> B4SjdCD+4IQz7IkrqP1D7Xt4l+R9DhfsUSEefqZzlZoXo=
>>
>> Thanks,
>> --
>> Biruntha
>>
>> Software Engineer
>> WSO2
>> Email: birun...@wso2.com
>> LinkedIn: https://lk.linkedin.com/in/biruntha
>> Mobile : +94773718986
>>
>
>
> --
> Shakila Sasikaran
> Software Engineer
> Mobile :+94 (0) 77 526 6848
> shak...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
>



-- 
Biruntha

Software Engineer
WSO2
Email: birun...@wso2.com
LinkedIn: https://lk.linkedin.com/in/biruntha
Mobile : +94773718986
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Getting "SignatureDoesNotMatch" error with deleteBucketReplication operation in Amazon s3 connector

[Biruntha Gnaneswaran]

Hi All,

I'm trying to use deleteBucketReplication operation in amazon s3 connector
[1] & [2]. But I'm getting "SignatureDoesNotMatch" error with the sample
request [3] & [4].  When I try this method with host and bucketUrl as in
[5], I'm getting error as in [6]. Am I missed anything? Appreciate your
input on this.


[1]
https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketDELETEreplication.html
[2]
https://docs.wso2.com/display/ESBCONNECTORS/Working+with+Buckets+in+Amazon+S3#WorkingwithBucketsinAmazonS3-deleteBucketReplication
[3]

xx
xx
DELETE
application/xml
true
http://testbuckkkbiru.s3.amazonaws.com


us-east-2
testbuckkkbiru
s3.amazonaws.com


public-read

[4]

http://ws.apache.org/ns/synapse";
   name="amazons3_deleteBucketReplication"
   startOnLoad="true"
   statistics="disable"
   trace="disable"
   transports="http,https">
   
  
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
{$ctx:accessKeyId}
{$ctx:secretAccessKey}
{$ctx:methodType}
{$ctx:contentType}
{$ctx:bucketName}
{$ctx:isXAmzDate}
{$ctx:contentMD5}
{$ctx:xAmzSecurityToken}
{$ctx:region}
{$ctx:host}
{$ctx:expect}
{$ctx:contentLength}
{$ctx:xAmzMfa}
 
 
{$ctx:bucketUrl}
 
 
  
  
 
  
   
   


[5]
s3-us-east-2.amazonaws.com
http://s3-us-east-2.amazonaws.com/testbuckkkbiru

[6]
RequestTimeoutYour socket connection to the
server was not read from or written to within the timeout period. Idle
connections will be
closed.DEEACD868FB28742zVKD6i4XzrWD7Dh8htoqPrlDypGClgB4SjdCD+4IQz7IkrqP1D7Xt4l+R9DhfsUSEefqZzlZoXo=

Thanks,
-- 
Biruntha

Software Engineer
WSO2
Email: birun...@wso2.com
LinkedIn: https://lk.linkedin.com/in/biruntha
Mobile : +94773718986
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Deprecating Mepin Authenticator

[Biruntha Gnaneswaran]

Hi Omindu,

We have tried to use the new MePIN endpoint for API version 4 . But we
got error
from Mepin back end as {"status":"error","status_text":"Service plan does
not permit requested action. Please contact supp...@meontrust.com"}.

Seems we need a commercial account for the Mepin API access. So, If we get
an account then we can update the Mepin authenticator.

Thanks,

On Tue, Jul 24, 2018 at 8:53 PM, Omindu Rathnaweera  wrote:

> Hi Biruntha,
>
> Are there any plans to update the connector with the new APIs ?
>
> Thanks,
> Omindu.
>
> On Tue, Jul 24, 2018 at 11:04 AM Biruntha Gnaneswaran 
> wrote:
>
>> Hi All,
>>
>> We are planning to deprecate Mepin authenticator[1] from the store[2]. In
>> our Mepin authenticator, we are using the Mepin simple_api endpoint [3] to
>> authenticate and retrieve user information. Since this endpoint has been
>> deprecated recently and giving 502 Bad Gateway error, we are planning to
>> deprecate.
>>
>> Please let us know if there are any concerns.
>>
>> [1] https://docs.wso2.com/display/ISCONNECTORS/MePIN+Authenticator
>> [2] https://store.wso2.com/store/assets/isconnector/details/
>> 00902cc7-5efc-4b8f-aae7-930e999f8058
>> [3] https://api.mepin.com/simple_api/
>>
>> Thanks,
>> --
>> Biruntha
>>
>> Software Engineer
>> WSO2
>> Email: birun...@wso2.com
>> LinkedIn: https://lk.linkedin.com/in/biruntha
>> Mobile : +94773718986
>>
>
>
> --
> Omindu Rathnaweera
> Senior Software Engineer, WSO2 Inc.
> Mobile: +94 771 197 211
>



-- 
Biruntha

Software Engineer
WSO2
Email: birun...@wso2.com
LinkedIn: https://lk.linkedin.com/in/biruntha
Mobile : +94773718986
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Deprecating Mepin Authenticator

[Biruntha Gnaneswaran]

Hi All,

We are planning to deprecate Mepin authenticator[1] from the store[2]. In
our Mepin authenticator, we are using the Mepin simple_api endpoint [3] to
authenticate and retrieve user information. Since this endpoint has been
deprecated recently and giving 502 Bad Gateway error, we are planning to
deprecate.

Please let us know if there are any concerns.

[1] https://docs.wso2.com/display/ISCONNECTORS/MePIN+Authenticator
[2]
https://store.wso2.com/store/assets/isconnector/details/00902cc7-5efc-4b8f-aae7-930e999f8058
[3] https://api.mepin.com/simple_api/

Thanks,
-- 
Biruntha

Software Engineer
WSO2
Email: birun...@wso2.com
LinkedIn: https://lk.linkedin.com/in/biruntha
Mobile : +94773718986
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release of WSO2 API Manager 2.5.0 RC4

[Biruntha Gnaneswaran]

Hi all,

I have tested following and no issues found when "hashing access tokens,
refresh tokens, client secrets, and authorization codes" feature enabled.

   - Application creation.
   - Regenerating consumer secret from store UI.
   - Regenerating consumer secret using REST API.

[+] - Stable - go ahead and release.

Thanks,

On Fri, Jun 22, 2018 at 8:07 PM, Vithursa Mahendrarajah 
wrote:

> Hi all,
>
> I have tested following and no issues found.
>
>- Basic API Flow - API creation, publishing and invocation
>- Creating users and roles
>- Application attributes
>- API Documentation
>- API Properties
>
> [+] - Stable - go ahead and release.
>
> Thanks,
> Vithursa.
>
> On Fri, Jun 22, 2018 at 6:57 PM Dushani Wellappili 
> wrote:
>
>> Hi all,
>>
>> Test the following APIM RC4. No issues found
>>
>> 1. Basic API creation, publishing and invocation.
>> 2. Enabling and disabling self signup in API store.
>> 3. Configuring workflow extensions including application creation, api
>> subscription, user signup and api state change for both tenant and super
>> tenant.
>> 4. Password recovery, account locking by failed login attempts and
>> account locking by an administrative user for API Store.
>>
>>
>> [+] -  Stable - go ahead and release
>>
>>
>> *Dushani Wellappili*
>> Software Engineer - WSO2
>>
>> Email : dusha...@wso2.com
>> Mobile : +94779367571
>> Web : https://wso2.com/
>>
>>
>>
>>
>> On Fri, Jun 22, 2018 at 5:28 PM Dinusha Dissanayake 
>> wrote:
>>
>>> Hi all,
>>>
>>> Tested APIM with APIM analytics.
>>> 1. Created different users with different roles.
>>> 2. Created API, publisher, subscriber, key generated and invoked the
>>> APIs.
>>> 3. Stat could be seen in publisher and store web apps.
>>> 4. Invoked and API with faulty back-end and check faulty invocation stat.
>>> 5. Invoked an API with backend returning 500 and check health
>>> availability alerts and alert suppression.
>>>
>>> No blockers found.
>>> [+] - Stable - go ahead and release
>>>
>>>
>>> On Fri, Jun 22, 2018 at 12:35 PM, Tharika Madurapperuma <
>>> thar...@wso2.com> wrote:
>>>
 Hi,

   Tested the following in API Manager RC4. No issues found.

 1. Basic API and Application flow
 - API Creation, Publishing, Key generation, Subscription and
 Invocation.
 2. Creating New API Version
 3. Deploy and invoke Prototyped APIs
 4. Customizing API LifeCycle
 5. API Documentation
 6. Publishing to multiple External API Stores
 7. Create and Publish SOAP APIs

 [+] - Stable - go ahead and release

 Thanks,
 Tharika.

 On Fri, Jun 22, 2018 at 12:24 PM Chamalee De Silva 
 wrote:

> Hi,
> I tested following in API Manager RC4.
>
> 1. Basic API flow
> - API creation, publishing, invocation etc.
> 2. Creating users and roles, and user permissions.
> 3. API documentation
> 4. Forums in API Store
>
> 5. Single Sign On with WSO2 Idnetity Server (WSO2 IS 5.6.0 RC3)
>  - SP init and IDP init SSO
>  - Assertion Encryption
>  - Single logout on/off
>  -  SAML request singning in store and publisher.
>
> 6. Installing SCIM identity feature in API Manager 2.5.0
> 7. API Properties
> 8. SDK generation feature
>
>
> [+] -  Stable - go ahead and release
>
>
> Thanks,
> Chamalee
>
>
> On Fri, Jun 22, 2018 at 12:16 PM, Chamin Dias 
> wrote:
>
>> Hi,
>>
>> Tested following (for both super tenat and tenat) and no issues found.
>>
>> a) Label creation/update
>> b) Attaching/removing labels to/from APIs
>> c) Displaying label information in Publisher and Store
>>
>> [+] Stable - go ahead and release
>>
>> Thanks.
>>
>> On Fri, Jun 22, 2018 at 12:15 PM, Krishan Wijesena > > wrote:
>>
>>> Hi,
>>> I have tested following and no issues found.
>>>
>>> 1. Basic API flow
>>> - API creation, publishing, invocation.
>>> 2. Admin REST API
>>> 3. Adding new Throttling policies
>>> - Advanced policies
>>> - Subscription policies
>>> - Application policies
>>> - Block list policies
>>> 4. Microgateway label add/update REST API
>>> 5. Test with browser IE 11
>>>  - basic flow (Super tenant/tenant)
>>>  - Label add/update
>>>
>>> [+]Stable - go ahead and release
>>>
>>> Thanks,
>>> krishan.
>>>
>>>
>>>
>>> On Thu, Jun 21, 2018 at 10:36 PM, Chamin Dias 
>>> wrote:
>>>
 Hi all,

 We are pleased to announce the fourth release candidate of WSO2 API
 Manager 2.5.0.

 This release fixes the following issues.
 Fixes : carbon-apimgt
 
 Fixes : product-a

Re: [Dev] [Architecture] [VOTE] Release of WSO2 Identity Server 5.6.0 RC3

[Biruntha Gnaneswaran]

Hi All,

I have tested the following,

Create service provider and tested OAuth flow with playground when hashing
access tokens, refresh tokens, client secrets, and authorization codes
feature enabled.

No blocking issues found.

[+] Stable - go ahead and release

Thanks,

On Tue, Jun 19, 2018 at 4:52 PM, Nadeeshani Pathirennehelage <
nadeesha...@wso2.com> wrote:

> Hi All,
>
> +1 from Platform Security Team.
>
> Thank You,
> Nadeeshani.
>
> On Tue, Jun 19, 2018 at 4:42 PM, Ashen Weerathunga  wrote:
>
>> Hi All,
>>
>> I have tested the following and found no issues.
>>
>>- Consent Management for Self Sign Up.
>>- Creating Users with the Ask Password Option.
>>- Password pattern validation.
>>- SAML SSO with Consent Management.
>>
>> [+] Stable - go ahead and release
>>
>> Thanks,
>> Ashen
>>
>>
>> On Tue, Jun 19, 2018 at 3:59 PM Ishara Karunarathna 
>> wrote:
>>
>>> Hi All,
>>>
>>> Tested the IS 5.6.0-RC3 integration with IS-Analytics-5.6.0
>>> And check the session analytics reports.
>>>
>>>
>>> No blocking issues found.
>>> [+] Stable
>>>
>>> Thanks,
>>> Ishara
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Jun 19, 2018 at 3:48 PM Isuri Anuradha  wrote:
>>>
 Hi all,

 I've tested following scenarios on the IS 5.6.0-RC3 pack.

- SAML to SAML federation flow.
- Publish and Update XACML policies.
- OAuth token revocation.

 No blocking issues found.

 [+] Stable

 Thanks
 Isuri.

 On Tue, Jun 19, 2018 at 3:34 PM, Omindu Rathnaweera 
 wrote:

> Hi All,
>
> Tested SCIM 2.0 basic operations. No blocking issues found
>
> [+] Stable - Go ahead and release
>
> Regards,
> Omindu.
>
>
>
>
>
> On Tue, Jun 19, 2018 at 3:14 PM Nipuni Bhagya 
> wrote:
>
>> Hi all,
>>
>> I've tested following scenarios on the IS 5.6.0-RC3 pack.
>>
>>- Configuring Single-Sign-On with SAML2
>>- Configuring Single-Sign-On with OIDC
>>- Configuring Multi-Factor Authentication
>>- Configuring Twitter as a Federated Authenticator
>>- Setting up Self-Signup
>>- Creating a workflow
>>- Tested Consent management API (Add/Retrieve purposes,
>>Add/revoke consents.)
>>
>> No blocking issues found.
>>
>> [+] Stable
>>
>> Thanks,
>>
>>
>> On Tue, Jun 19, 2018 at 2:38 AM Pulasthi Mahawithana <
>> pulast...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> Tested SSO with Multi step/multi option authentication, Google
>>> and Twitter authenticators
>>>
>>> No blocking issues found.
>>>
>>> [+] Stable - Go ahead and release
>>>
>>>
>>> On Tue, Jun 19, 2018 at 2:59 PM Hasanthi Purnima Dissanayake <
>>> hasan...@wso2.com> wrote:
>>>
 Hi,

 Tested below scenarios on IS 5.6.0-RC3 pack,

 - Register a service provider
 - Obtain an access token using JWT grant type
 - Invoke user info endpoint using the token.

 No blocking issues found.

 [+] Stable - Go ahead and release

 Thanks,
 Hasanthi

 On Tue, Jun 19, 2018 at 2:44 PM, Dewni Weeraman 
 wrote:

> Hi,
>
> Tested below scenarios on IS 5.6.0-RC3 pack,
>
>- Invoke the OAuth Introspection Endpoint.
>- OAuth token revocation.
>- Entitlement policy creation using write policy in xml and
>publishing.
>- Using REST APIs via XACML to manage entitlement.
>- Create, update, get, delete an OAuth app using Dynamic
>Client Registration endpoint.
>
>
> No blocking issues found.
>
> [+] Stable - Go ahead and release
>
> Thanks,
> Dewni
>
> On Tue, Jun 19, 2018 at 1:43 PM, Sathya Bandara 
> wrote:
>
>> Hi all,
>>
>> I've tested following scenarios on the IS 5.6.0-RC3 pack.
>>
>> User management (add/update/remove users).
>> User management in secondary userstores (Read-Write LDAP).
>> Consent Management in SAML SSO.
>> SAML to SAML federation.
>> Creating workflows definitions for primary userstore users.
>> Engaging/Disabling workflows on user-store operations.
>> Enable role based authorization using XACML for service providers.
>> Tenant creation/update/disabling.
>>
>> No blocking issues are found.
>>
>> [+] Stable - go ahead and release.
>>
>> Thanks,
>> Sathya
>>
>>
>> On Tue, Jun 19, 2018 at 12:26 PM, Vihanga Liyanage <
>> viha...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> I've tested following scenarios on the IS 5.6.0-RC3 pack with
>>> defa

[Dev] [DEV] Problem While using For each mediator within iterate mediator

[Biruntha Gnaneswaran]

Hi All,

I have $subject issue while doing github to spreadsheet integration
scenario. For that, I have tried the sample sequence as below [1]. After
calling fist call mediator, I'm getting the response for the first call
mediator. But the remain highlighted code segment is not executing. Is
there any way to resolve this issue? or Is this an expected behavior?

But when I replace the for each mediator with iterate mediator There are no
issues.

[1]


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

{"repo" : ["repo_1"]}

http://org.apache.synapse/xsd";>




https://api.github.com

application/vnd.github+json


Biruntha
{$ctx:repository}








https://www.googleapis.com/oauth2/v1/tokeninfo?access_token=ya29.Glu_BNInVSEO-bM3sJaYoN8m-k6w91j_WKg8mKraTu3E6_AKvbQmzJFMVDZ9q6HsfYDjT2enY5jjEy8p3ce9UJFwk7uhduKB8imoAi725i27toW0mwRs_LevZUvR
"/>








{"values":[['repo_2','1st issue for repo_2']]}




https://sheets.googleapis.com/v4/spreadsheets/14PJALKcIXLr75rJWXlHhVjOt7z0Nby7AvcKXJGhMN2s/values/Scenario!A1:append?valueInputOption=RAW
"/>










Thanks,
-- 
Biruntha

Software Engineer
WSO2
Email: birun...@wso2.com
LinkedIn: https://lk.linkedin.com/in/biruntha
Mobile : +94773718986
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Kanapriya Kuleswararajan

[Biruntha Gnaneswaran]

Congratulations Kanapriya

Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com
Linkedin : https://lk.linkedin.com/in/biruntha
Mobile : +94773718986

On Tue, Dec 6, 2016 at 3:49 PM, Yashothara Shanmugarajah <
yashoth...@wso2.com> wrote:

> Congratulations Kanapriya :)
>
> Best Regards,
> Yashothara.S
> Software Engineer
> WSO2
> http://wso2.com
> https://wso2.com/signature
> 
>
> On Tue, Dec 6, 2016 at 3:44 PM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> Congratulations Kanapriya :)
>>
>> On Tue, Dec 6, 2016 at 3:22 PM, Malaka Silva  wrote:
>>
>>> Hi Devs,
>>>
>>> Its my pleasure to welcome Kanapriya Kuleswararajan as a WSO2 Committer.
>>>
>>> She has been working with the WSO2 Platform Extensions Team for a while
>>> and has contributed to  ESB and IS product extensions,
>>>
>>> Kanapriya, welcome aboard and keep up the good work.
>>>
>>> Best Regards,
>>>
>>> Malaka Silva
>>> Senior Technical Lead
>>> M: +94 777 219 791 <+94%2077%20721%209791>
>>> 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
>>> https://wso2.com/signature
>>> http://www.wso2.com/about/team/malaka-silva/
>>> 
>>> https://store.wso2.com/store/
>>>
>>> Don't make Trees rare, we should keep them with care
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanuja Uruththirakodeeswaran
>> Software Engineer
>> WSO2 Inc.;http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 774363167 <+94%2077%20436%203167>
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Megala Uthayakumar

[Biruntha Gnaneswaran]

Congratulations Megala.

Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com
Linkedin : https://lk.linkedin.com/in/biruntha
Mobile : +94773718986

On Wed, Nov 2, 2016 at 10:50 AM, Prabushi Samarakoon 
wrote:

> Congratulations Megala :)
>
> On Wed, Nov 2, 2016 at 10:29 AM, Fathima Dilhasha 
> wrote:
>
>> Congratz Megala :D
>>
>> On Tue, Nov 1, 2016 at 2:21 PM, Sinthuja Ragendran 
>> wrote:
>>
>>> Hi all,
>>>
>>> It's my pleasure to announce Megala Uthayakumar as a WSO2 Committer.
>>> Megala had been a valuable contributor for Dashboard Server product, and
>>> now for EMM/IoT Products. And in recognition of her contribution to WSO2,
>>> she has been voted as a WSO2 Committer.
>>>
>>> Megala, Keep up the good work and wish you all the best for your future
>>> endeavors!
>>>
>>> Thanks,
>>> Sinthuja.
>>>
>>> --
>>> *Sinthuja Rajendran*
>>> Technical Lead
>>> WSO2, Inc.:http://wso2.com
>>>
>>> Blog: http://sinthu-rajan.blogspot.com/
>>> Mobile: +94774273955
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Fathima Dilhasha
>> *Software Engineer*
>> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
>> <%2B94%20%280%29%20773%20451194>
>> dilha...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Prabushi Samarakoon*
> Software Engineer
> Mobile: +94715434580
> Email: prabus...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] NtaskTaskManager Error : No available task nodes for resolving a task location

[Biruntha Gnaneswaran]

Hi,

I changed Enabled property of DeploymentSynchronizer as true. Now it’s
working fine.

Thank you for your response Rajith.


Thanks,

Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com
Linkedin : https://lk.linkedin.com/in/biruntha
Mobile : +94773718986

On Mon, Sep 26, 2016 at 11:39 AM, Rajith Vitharana  wrote:

> Hi,
>
> Can you see Member Joined logs as well? AFAIK Member joined logs are the
> ones which indicates cluster is correctly  connected.
>
> Thanks,
>
> On 26 September 2016 at 11:36, Biruntha Gnaneswaran 
> wrote:
>
>> Hi Rajith,
>>
>> Yes I started worker node with -DworkerNode=true parameter.
>>
>> From manager :
>> [2016-09-26 11:08:54,170]  INFO - MemberUtils Added member: Host:
>> esb.wso2.com, Remote Host:null, Port: 4200, HTTP:-1, HTTPS:-1, Domain:
>> null, Sub-domain:null, Active:true
>>
>> From the worker :
>> [2016-09-26 09:10:11,345]  INFO - MemberUtils Added member: Host:
>> mgt.esb.wso2.com, Remote Host:null, Port: 4100, HTTP:-1, HTTPS:-1,
>> Domain: null, Sub-domain:null, Active:true
>>
>>
>> Biruntha
>>
>> Associate Software Engineer
>> WSO2
>> Email : birun...@wso2.com
>> Linkedin : https://lk.linkedin.com/in/biruntha
>> Mobile : +94773718986
>>
>> On Mon, Sep 26, 2016 at 11:21 AM, Rajith Vitharana 
>> wrote:
>>
>>> Hi,
>>>
>>> Have you started worker node with -DworkerNode=true parameter? does the
>>> cluster connects correctly? (means can you see node joining logs in both
>>> nodes?)
>>>
>>> Thanks,
>>>
>>> On 26 September 2016 at 11:05, Biruntha Gnaneswaran 
>>> wrote:
>>>
>>>> Hi Malaka/Rajith,
>>>>
>>>> I followed as you suggested.
>>>>
>>>> When I specify taskServerCount as 2, I couldn’t access the management
>>>> console. But when I specify taskServerCount as 1, I’m able to access the
>>>> management console. But still I got the same error [2].
>>>>
>>>> [2] -
>>>> at org.apache.catalina.core.StandardWrapper.load(StandardWrappe
>>>> r.java:1085)
>>>> at org.apache.catalina.core.StandardContext.loadOnStartup(Stand
>>>> ardContext.java:5318)
>>>> at org.apache.catalina.core.StandardContext.startInternal(Stand
>>>> ardContext.java:5610)
>>>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.j
>>>> ava:147)
>>>> at org.apache.catalina.core.ContainerBase$StartChild.call(Conta
>>>> inerBase.java:1572)
>>>> at org.apache.catalina.core.ContainerBase$StartChild.call(Conta
>>>> inerBase.java:1562)
>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>>>> Executor.java:1145)
>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>>>> lExecutor.java:615)
>>>> at java.lang.Thread.run(Thread.java:745)
>>>> [2016-09-26 10:52:11,284]  INFO - ClusterGroupCommunicator Waiting for
>>>> 1 [registryTasks] task executor nodes...
>>>> [2016-09-26 10:52:11,284]  INFO - ClusterGroupCommunicator All task
>>>> servers activated for [registryTasks].
>>>> [2016-09-26 10:52:11,309]  INFO - JMXServerManager JMX Service URL  :
>>>> service:jmx:rmi://localhost:2/jndi/rmi://localhost:1/jmxrmi
>>>> [2016-09-26 10:52:11,313]  INFO - StartupFinalizerServiceComponent
>>>> Server   :  WSO2 Enterprise Service Bus-5.0.0
>>>> [2016-09-26 10:52:11,314]  INFO - StartupFinalizerServiceComponent
>>>> WSO2 Carbon started in 21 sec
>>>> [2016-09-26 10:52:11,508]  INFO - CarbonUIServiceComponent Mgt Console
>>>> URL  : https://mgt.esb.wso2.com:443/carbon/
>>>>
>>>> Thanks,
>>>>
>>>> Biruntha
>>>>
>>>> Associate Software Engineer
>>>> WSO2
>>>> Email : birun...@wso2.com
>>>> Linkedin : https://lk.linkedin.com/in/biruntha
>>>> Mobile : +94773718986
>>>>
>>>> On Mon, Sep 26, 2016 at 10:33 AM, Rajith Vitharana 
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> That error comes when you start a *non* task node(in this case
>>>>> manager node) without starting a task node(worker node). (task node count
>>>>> specified in tasks-config.xml). So if you follow below steps, this
>>>>> shouldn't happen.
>>>>>
>>>>> 1) specify task server count(1) as
>>>>> 1 in task-config.xml
>>>>> 2) start worker and then manager. (if worker correctly connects to the
>>>>> manger through cluster, this error message shouldn't come)
>>>>>
>>>>> Thanks,
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Rajith Vitharana
>>>
>>> Senior Software Engineer,
>>> WSO2 Inc. : wso2.com
>>> Mobile : +94715883223
>>> Blog : http://lankavitharana.blogspot.com/
>>> <http://wso2.com/signature>
>>>
>>
>>
>
>
> --
> Rajith Vitharana
>
> Senior Software Engineer,
> WSO2 Inc. : wso2.com
> Mobile : +94715883223
> Blog : http://lankavitharana.blogspot.com/
> <http://wso2.com/signature>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] NtaskTaskManager Error : No available task nodes for resolving a task location

[Biruntha Gnaneswaran]

Hi Rajith,

Yes I started worker node with -DworkerNode=true parameter.

>From manager :
[2016-09-26 11:08:54,170]  INFO - MemberUtils Added member: Host:
esb.wso2.com, Remote Host:null, Port: 4200, HTTP:-1, HTTPS:-1, Domain:
null, Sub-domain:null, Active:true

>From the worker :
[2016-09-26 09:10:11,345]  INFO - MemberUtils Added member: Host:
mgt.esb.wso2.com, Remote Host:null, Port: 4100, HTTP:-1, HTTPS:-1, Domain:
null, Sub-domain:null, Active:true


Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com
Linkedin : https://lk.linkedin.com/in/biruntha
Mobile : +94773718986

On Mon, Sep 26, 2016 at 11:21 AM, Rajith Vitharana  wrote:

> Hi,
>
> Have you started worker node with -DworkerNode=true parameter? does the
> cluster connects correctly? (means can you see node joining logs in both
> nodes?)
>
> Thanks,
>
> On 26 September 2016 at 11:05, Biruntha Gnaneswaran 
> wrote:
>
>> Hi Malaka/Rajith,
>>
>> I followed as you suggested.
>>
>> When I specify taskServerCount as 2, I couldn’t access the management
>> console. But when I specify taskServerCount as 1, I’m able to access the
>> management console. But still I got the same error [2].
>>
>> [2] -
>> at org.apache.catalina.core.StandardWrapper.load(StandardWrappe
>> r.java:1085)
>> at org.apache.catalina.core.StandardContext.loadOnStartup(Stand
>> ardContext.java:5318)
>> at org.apache.catalina.core.StandardContext.startInternal(Stand
>> ardContext.java:5610)
>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.
>> java:147)
>> at org.apache.catalina.core.ContainerBase$StartChild.call(Conta
>> inerBase.java:1572)
>> at org.apache.catalina.core.ContainerBase$StartChild.call(Conta
>> inerBase.java:1562)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1145)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:745)
>> [2016-09-26 10:52:11,284]  INFO - ClusterGroupCommunicator Waiting for 1
>> [registryTasks] task executor nodes...
>> [2016-09-26 10:52:11,284]  INFO - ClusterGroupCommunicator All task
>> servers activated for [registryTasks].
>> [2016-09-26 10:52:11,309]  INFO - JMXServerManager JMX Service URL  :
>> service:jmx:rmi://localhost:2/jndi/rmi://localhost:1/jmxrmi
>> [2016-09-26 10:52:11,313]  INFO - StartupFinalizerServiceComponent
>> Server   :  WSO2 Enterprise Service Bus-5.0.0
>> [2016-09-26 10:52:11,314]  INFO - StartupFinalizerServiceComponent WSO2
>> Carbon started in 21 sec
>> [2016-09-26 10:52:11,508]  INFO - CarbonUIServiceComponent Mgt Console
>> URL  : https://mgt.esb.wso2.com:443/carbon/
>>
>> Thanks,
>>
>> Biruntha
>>
>> Associate Software Engineer
>> WSO2
>> Email : birun...@wso2.com
>> Linkedin : https://lk.linkedin.com/in/biruntha
>> Mobile : +94773718986
>>
>> On Mon, Sep 26, 2016 at 10:33 AM, Rajith Vitharana 
>> wrote:
>>
>>> Hi,
>>>
>>> That error comes when you start a *non* task node(in this case manager
>>> node) without starting a task node(worker node). (task node count specified
>>> in tasks-config.xml). So if you follow below steps, this shouldn't happen.
>>>
>>> 1) specify task server count(1) as 1
>>> in task-config.xml
>>> 2) start worker and then manager. (if worker correctly connects to the
>>> manger through cluster, this error message shouldn't come)
>>>
>>> Thanks,
>>>
>>
>>
>
>
> --
> Rajith Vitharana
>
> Senior Software Engineer,
> WSO2 Inc. : wso2.com
> Mobile : +94715883223
> Blog : http://lankavitharana.blogspot.com/
> <http://wso2.com/signature>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] NtaskTaskManager Error : No available task nodes for resolving a task location

[Biruntha Gnaneswaran]

Hi Malaka/Rajith,

I followed as you suggested.

When I specify taskServerCount as 2, I couldn’t access the management
console. But when I specify taskServerCount as 1, I’m able to access the
management console. But still I got the same error [2].

[2] -
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1085)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5318)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5610)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1572)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1562)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[2016-09-26 10:52:11,284]  INFO - ClusterGroupCommunicator Waiting for 1
[registryTasks] task executor nodes...
[2016-09-26 10:52:11,284]  INFO - ClusterGroupCommunicator All task servers
activated for [registryTasks].
[2016-09-26 10:52:11,309]  INFO - JMXServerManager JMX Service URL  :
service:jmx:rmi://localhost:2/jndi/rmi://localhost:1/jmxrmi
[2016-09-26 10:52:11,313]  INFO - StartupFinalizerServiceComponent
Server   :  WSO2 Enterprise Service Bus-5.0.0
[2016-09-26 10:52:11,314]  INFO - StartupFinalizerServiceComponent WSO2
Carbon started in 21 sec
[2016-09-26 10:52:11,508]  INFO - CarbonUIServiceComponent Mgt Console URL
: https://mgt.esb.wso2.com:443/carbon/

Thanks,

Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com
Linkedin : https://lk.linkedin.com/in/biruntha
Mobile : +94773718986

On Mon, Sep 26, 2016 at 10:33 AM, Rajith Vitharana  wrote:

> Hi,
>
> That error comes when you start a *non* task node(in this case manager
> node) without starting a task node(worker node). (task node count specified
> in tasks-config.xml). So if you follow below steps, this shouldn't happen.
>
> 1) specify task server count(1) as 1
> in task-config.xml
> 2) start worker and then manager. (if worker correctly connects to the
> manger through cluster, this error message shouldn't come)
>
> Thanks,
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] NtaskTaskManager Error : No available task nodes for resolving a task location

[Biruntha Gnaneswaran]

Hi All,

I tested AmazonSQS inbound in esb cluster mode. For that I follow [1] to
setup the manager and worker nodes. When I start the manger node I am
getting following error [2].

In addition to that, I tried to solve this by

   -

   configure *ESB_HOME/repository/conf/etc/tasks-config.xml* file with
the below parameter.


2


   -

   start the manager node after starting the worker nodes

but still I’m getting the same error. Is there any way to achieve this?

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

#

[2] -

[2016-09-26 10:21:44,913]  INFO - NTaskTaskManager Initialized task
manager. Tenant [-1234]
[2016-09-26 10:21:44,944] ERROR - NTaskTaskManager Scheduling task
[[NTask::-1234::amazon-CLASS--SYNAPSE_INBOUND_ENDPOINT]::CLASS--SYNAPSE_INBOUND_ENDPOINT]
FAILED. Error: No available task nodes for resolving a task location
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:106)
at
org.wso2.carbon.mediation.ntask.NTaskTaskManager.init(NTaskTaskManager.java:351)
at
org.wso2.carbon.mediation.ntask.NTaskTaskManager.update(NTaskTaskManager.java:406)
at
org.wso2.carbon.mediation.ntask.internal.NtaskService.updateAndCleanupObservers(NtaskService.java:103)
at
org.wso2.carbon.mediation.ntask.internal.NtaskService.setConfigurationContextService(NtaskService.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:376)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:430)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bind(ServiceComponentProp.java:218)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(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(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.ntask.core.internal.TasksDSComponent.activate(TasksDSComponent.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
at
org.eclipse.equinox.internal.ds.InstanceProcess.b

Re: [Dev] WSO2 Committers += Hariprasath Thanarajah

[Biruntha Gnaneswaran]

Hi Hariprasath,
Congratulations

Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com
Linkedin : https://lk.linkedin.com/in/biruntha
Mobile : +94773718986

On Thu, Sep 1, 2016 at 10:02 AM, Yashothara Shanmugarajah <
yashoth...@wso2.com> wrote:

> Congratulations Hariprasath.
>
> / Best Regards,
> Yashothara.S
> Software Engineer
> WSO2
> http://wso2.com
>
> On Thu, Sep 1, 2016 at 9:31 AM, Malaka Silva  wrote:
>
>> Hi Devs,
>>
>> Its my pleasure to welcome Hariprasath Thanarajah as a WSO2 Committer.
>>
>> He has been working with the WSO2 Platform Extensions Team and has
>> contributed immensely to  ESB and IS product extensions, He is a very
>> dedicated, passionate and committed individual who is ready to
>> take challengers.
>>
>> Hariprasath, welcome aboard and keep up the good work.
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Technical 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
>> ​​
>>
>> https://wso2.com/signature
>> http://www.wso2.com/about/team/malaka-silva/
>> 
>> https://store.wso2.com/store/
>>
>> Don't make Trees rare, we should keep them with care
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [Mepin Authenticator] Problem while sending URL parameters using POST method

[Biruntha Gnaneswaran]

Hi Kasun,

I test my use-case with [1]. It works fine.

[1] - http://maven.wso2.org/nexus/content/repositories/
snapshots/org/wso2/is/wso2is/5.2.0-SNAPSHOT/

Thanks,

Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com
Linkedin : https://lk.linkedin.com/in/biruntha
Mobile : +94773718986

On Tue, Aug 23, 2016 at 6:27 PM, Kasun Bandara  wrote:

> Hi Biruntha,
>
> This issue has been already fixed in the public branch [1]. You can verify
> your use-case with the latest pack available in [2]
>
> Thanks,
> Kasun.
>
> [1] https://github.com/wso2-extensions/identity-inbound-
> auth-saml/blob/master/components/org.wso2.carbon.
> identity.sso.saml/src/main/java/org/wso2/carbon/identity/sso/saml/servlet/
> SAMLSSOProviderServlet.java
>
> [2] http://maven.wso2.org/nexus/content/repositories/
> snapshots/org/wso2/is/wso2is/5.2.0-SNAPSHOT/
>
> Thanks,
> Kasun
>
> On Tue, Aug 23, 2016 at 5:43 PM, Kasun Bandara  wrote:
>
>> Hi Biruntha,
>>
>> Thanks for fixing the issue. Can you please send the relevant PR to [1]
>> extension. We don't use the carbon-identity repository now.
>>
>> Thanks,
>> Kasun.
>>
>> [1] https://github.com/wso2-extensions/identity-inbound-auth-
>> saml/blob/master/components/org.wso2.carbon.identity.sso.
>> saml/src/main/java/org/wso2/carbon/identity/sso/saml/
>> servlet/SAMLSSOProviderServlet.java
>>
>> On Tue, Aug 23, 2016 at 4:48 PM, Johann Nallathamby 
>> wrote:
>>
>>>
>>>
>>> On Tue, Aug 23, 2016 at 4:14 PM, Biruntha Gnaneswaran >> > wrote:
>>>
>>>> Hi,
>>>>
>>>> I created jira [1] and fixed in [2].
>>>>
>>>> @ IS team please verify and merge.
>>>>
>>>> [1] - https://wso2.org/jira/browse/IDENTITY-5027
>>>>
>>>> [2] - https://github.com/wso2/carbon-identity/pull/1748
>>>>
>>>> Thanks,
>>>>
>>>> Biruntha
>>>>
>>>> Associate Software Engineer
>>>> WSO2
>>>> Email : birun...@wso2.com
>>>> Linkedin : https://lk.linkedin.com/in/biruntha
>>>> Mobile : +94773718986
>>>>
>>>> On Tue, Aug 23, 2016 at 6:05 AM, Malaka Silva  wrote:
>>>>
>>>>> Hi Biruntha,
>>>>>
>>>>> Good investigation on this matter. However we are not sure the impact
>>>>> of this change. Can you create a jira [1] and add the PR so that IS team
>>>>> can verify this in coming releases?
>>>>>
>>>>> [1] https://wso2.org/jira/browse/IDENTITY
>>>>>
>>>>> On Mon, Aug 22, 2016 at 6:04 PM, Biruntha Gnaneswaran <
>>>>> birun...@wso2.com> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> While posting a form from Mepin Authenticator to Authentication
>>>>>> endpoint, [1] will be executed. So it goes to [2]. From that method, it
>>>>>> only support for url redirecting not support for form posting. So, I
>>>>>> replace the logic [3] by [4]. Now it is working fine .So, To support post
>>>>>> request in authentication endpoint, we need to modify sso-saml module.
>>>>>>
>>>>>> [1] - https://github.com/wso2/carbon-identity/blob/master/componen
>>>>>> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/
>>>>>> org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderSer
>>>>>> vlet.java#L157-#L161
>>>>>>
>>>>>> [2] - https://github.com/wso2/carbon-identity/blob/master/componen
>>>>>> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/
>>>>>> org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderSer
>>>>>> vlet.java#L980
>>>>>>
>>>>>> [3] - https://github.com/wso2/carbon-identity/blob/master/componen
>>>>>> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/
>>>>>> org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderSer
>>>>>> vlet.java#L992
>>>>>>
>>>>>> [4] - https://github.com/wso2/carbon-identity/blob/master/componen
>>>>>> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/
>>>>>> org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderSer
>>>>>> vlet.java#L1031-#L1035
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>

Re: [Dev] [DEV] [Mepin Authenticator] Problem while sending URL parameters using POST method

[Biruntha Gnaneswaran]

Hi,

I created jira [1] and fixed in [2].

@ IS team please verify and merge.

[1] - https://wso2.org/jira/browse/IDENTITY-5027

[2] - https://github.com/wso2/carbon-identity/pull/1748

Thanks,

Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com
Linkedin : https://lk.linkedin.com/in/biruntha
Mobile : +94773718986

On Tue, Aug 23, 2016 at 6:05 AM, Malaka Silva  wrote:

> Hi Biruntha,
>
> Good investigation on this matter. However we are not sure the impact of
> this change. Can you create a jira [1] and add the PR so that IS team can
> verify this in coming releases?
>
> [1] https://wso2.org/jira/browse/IDENTITY
>
> On Mon, Aug 22, 2016 at 6:04 PM, Biruntha Gnaneswaran 
> wrote:
>
>> Hi All,
>>
>> While posting a form from Mepin Authenticator to Authentication endpoint,
>> [1] will be executed. So it goes to [2]. From that method, it only support
>> for url redirecting not support for form posting. So, I replace the logic
>> [3] by [4]. Now it is working fine .So, To support post request in
>> authentication endpoint, we need to modify sso-saml module.
>>
>> [1] - https://github.com/wso2/carbon-identity/blob/master/componen
>> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/
>> java/org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProvid
>> erServlet.java#L157-#L161
>>
>> [2] - https://github.com/wso2/carbon-identity/blob/master/componen
>> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/
>> java/org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProvid
>> erServlet.java#L980
>>
>> [3] - https://github.com/wso2/carbon-identity/blob/master/componen
>> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/
>> java/org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProvid
>> erServlet.java#L992
>>
>> [4] - https://github.com/wso2/carbon-identity/blob/master/componen
>> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/
>> java/org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProvid
>> erServlet.java#L1031-#L1035
>>
>>
>> Thanks,
>>
>> Biruntha
>>
>> Associate Software Engineer
>> WSO2
>> Email : birun...@wso2.com
>> Linkedin : https://lk.linkedin.com/in/biruntha
>> Mobile : +94773718986
>>
>> On Fri, Aug 12, 2016 at 10:18 PM, Biruntha Gnaneswaran > > wrote:
>>
>>> Hi All,
>>>
>>>
>>> To solve the issue in $subject, i tried to post a html form from
>>> Authenticator to mepin.jsp using [1]. But still i couldn't solve that
>>> issue. It's again redirected to [2].
>>> Can anyone help me to solve this issue?
>>>
>>> [1]
>>>
>>> response.setContentType(*"text/html"*);java.io.PrintWriter out = 
>>> response.getWriter();
>>> out.println(*""*);out.println(*""*);out.println(*">>  name=**\"**loginform**\"* *method=**\"**post**\"* 
>>> *action=**\"**/mepinauthenticationendpoint/mepin.jsp**\"**>"*);out.println(*">>  type=**\"**hidden**\"* *id=**\"**param1**\"* *name=**\"**param1**\"* 
>>> *value=**\"**"*+param1+*"**\"**/>"*);out.println(*">> type=**\"**hidden**\"* *id=**\"**param2**\"* *name=**\"**param2**\"* 
>>> *value=**\"**"*+param2+*"**\"**/>"*);out.println(*""*);
>>>
>>> [2] https://localhost:9443/samlsso
>>>
>>> Thanks,
>>>
>>> Biruntha
>>>
>>> Associate Software Engineer
>>> WSO2
>>> Email : birun...@wso2.com
>>> Linkedin : https://lk.linkedin.com/in/biruntha
>>> Mobile : +94773718986
>>>
>>> On Fri, Jul 29, 2016 at 11:46 PM, Biruntha Gnaneswaran <
>>> birun...@wso2.com> wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> In Mepin authenticator, some URL parameters are send to Mepin UI page
>>>> using GET method [1]. When I try to send these parameters via POST method
>>>> using HttpURLConnection class [2], it redirects to [3] not to the
>>>> actual Mepin UI page. While I try, I got the following Log .
>>>>
>>>> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
>>>> ication.authentication.framework.handler.request.impl.DefaultAuthenticationRequestHandler}
>>>> - In authentication flow
>>>>
>>>> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
>>>> ication.auth

Re: [Dev] [DEV] [Mepin Authenticator] Problem while sending URL parameters using POST method

[Biruntha Gnaneswaran]

Hi All,

While posting a form from Mepin Authenticator to Authentication endpoint,
[1] will be executed. So it goes to [2]. From that method, it only support
for url redirecting not support for form posting. So, I replace the logic
[3] by [4]. Now it is working fine .So, To support post request in
authentication endpoint, we need to modify sso-saml module.

[1] -
https://github.com/wso2/carbon-identity/blob/master/components/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderServlet.java#L157-#L161

[2] -
https://github.com/wso2/carbon-identity/blob/master/components/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderServlet.java#L980

[3] -
https://github.com/wso2/carbon-identity/blob/master/components/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderServlet.java#L992

[4] -
https://github.com/wso2/carbon-identity/blob/master/components/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderServlet.java#L1031-#L1035


Thanks,

Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com
Linkedin : https://lk.linkedin.com/in/biruntha
Mobile : +94773718986

On Fri, Aug 12, 2016 at 10:18 PM, Biruntha Gnaneswaran 
wrote:

> Hi All,
>
>
> To solve the issue in $subject, i tried to post a html form from
> Authenticator to mepin.jsp using [1]. But still i couldn't solve that
> issue. It's again redirected to [2].
> Can anyone help me to solve this issue?
>
> [1]
>
> response.setContentType(*"text/html"*);java.io.PrintWriter out = 
> response.getWriter();
> out.println(*""*);out.println(*""*);out.println(*"  name=**\"**loginform**\"* *method=**\"**post**\"* 
> *action=**\"**/mepinauthenticationendpoint/mepin.jsp**\"**>"*);out.println(*"  type=**\"**hidden**\"* *id=**\"**param1**\"* *name=**\"**param1**\"* 
> *value=**\"**"*+param1+*"**\"**/>"*);out.println(*" type=**\"**hidden**\"* *id=**\"**param2**\"* *name=**\"**param2**\"* 
> *value=**\"**"*+param2+*"**\"**/>"*);out.println(*""*);
>
> [2] https://localhost:9443/samlsso
>
> Thanks,
>
> Biruntha
>
> Associate Software Engineer
> WSO2
> Email : birun...@wso2.com
> Linkedin : https://lk.linkedin.com/in/biruntha
> Mobile : +94773718986
>
> On Fri, Jul 29, 2016 at 11:46 PM, Biruntha Gnaneswaran 
> wrote:
>
>> Hi Devs,
>>
>> In Mepin authenticator, some URL parameters are send to Mepin UI page
>> using GET method [1]. When I try to send these parameters via POST method
>> using HttpURLConnection class [2], it redirects to [3] not to the actual
>> Mepin UI page. While I try, I got the following Log .
>>
>> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
>> ication.authentication.framework.handler.request.impl.DefaultAuthenticationRequestHandler}
>> - In authentication flow
>>
>> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
>> ication.authentication.framework.handler.sequence.impl.DefaultStepBasedSequenceHandler}
>> - Executing the Step Based Authentication...
>>
>> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
>> ication.authentication.framework.handler.sequence.impl.DefaultStepBasedSequenceHandler}
>> - Starting Step: 1
>>
>> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
>> ication.authentication.framework.util.FrameworkUtils} - Finding already
>> authenticated IdPs of the Step
>>
>> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
>> ication.authentication.framework.handler.step.impl.DefaultStepHandler} -
>> Receive a response from the external party
>>
>> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
>> ication.authentication.framework.handler.step.impl.DefaultStepHandler} -
>> BasicAuthenticator can handle the request.
>>
>> [2016-07-29 23:30:00,929] DEBUG {org.wso2.carbon.identity.appl
>> ication.authentication.framework.handler.step.impl.DefaultStepHandler} -
>> BasicAuthenticator returned: SUCCESS_COMPLETED
>>
>> [2016-07-29 23:30:00,930] DEBUG {org.wso2.carbon.identity.appl
>> ication.authentication.framework.handler.sequence.impl.DefaultStepBasedSequenceHandler}
>> - Step 1 is completed. Going to get the next one.
>>
>> [2016-07-29 23:30:00,930] DEBUG {org.wso2.carbon.identity.appl
>> ication.authentication.framework.handler.sequence.impl.DefaultSte

Re: [Dev] [DEV] [Mepin Authenticator] Problem while sending URL parameters using POST method

[Biruntha Gnaneswaran]

Hi All,


To solve the issue in $subject, i tried to post a html form from
Authenticator to mepin.jsp using [1]. But still i couldn't solve that
issue. It's again redirected to [2].
Can anyone help me to solve this issue?

[1]

response.setContentType(*"text/html"*);java.io.PrintWriter out =
response.getWriter();
out.println(*""*);out.println(*""*);out.println(*""*);out.println(*""*);out.println(*""*);out.println(*""*);

[2] https://localhost:9443/samlsso

Thanks,

Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com
Linkedin : https://lk.linkedin.com/in/biruntha
Mobile : +94773718986

On Fri, Jul 29, 2016 at 11:46 PM, Biruntha Gnaneswaran 
wrote:

> Hi Devs,
>
> In Mepin authenticator, some URL parameters are send to Mepin UI page
> using GET method [1]. When I try to send these parameters via POST method
> using HttpURLConnection class [2], it redirects to [3] not to the actual
> Mepin UI page. While I try, I got the following Log .
>
> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.
> application.authentication.framework.handler.request.impl.
> DefaultAuthenticationRequestHandler} - In authentication flow
>
> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.
> application.authentication.framework.handler.sequence.impl.
> DefaultStepBasedSequenceHandler} - Executing the Step Based
> Authentication...
>
> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.
> application.authentication.framework.handler.sequence.impl.
> DefaultStepBasedSequenceHandler} - Starting Step: 1
>
> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.
> application.authentication.framework.util.FrameworkUtils} - Finding
> already authenticated IdPs of the Step
>
> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.
> application.authentication.framework.handler.step.impl.DefaultStepHandler}
> - Receive a response from the external party
>
> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.
> application.authentication.framework.handler.step.impl.DefaultStepHandler}
> - BasicAuthenticator can handle the request.
>
> [2016-07-29 23:30:00,929] DEBUG {org.wso2.carbon.identity.
> application.authentication.framework.handler.step.impl.DefaultStepHandler}
> - BasicAuthenticator returned: SUCCESS_COMPLETED
>
> [2016-07-29 23:30:00,930] DEBUG {org.wso2.carbon.identity.
> application.authentication.framework.handler.sequence.impl.
> DefaultStepBasedSequenceHandler} - Step 1 is completed. Going to get the
> next one.
>
> [2016-07-29 23:30:00,930] DEBUG {org.wso2.carbon.identity.
> application.authentication.framework.handler.sequence.impl.
> DefaultStepBasedSequenceHandler} - Starting Step: 2
>
> [2016-07-29 23:30:00,930] DEBUG {org.wso2.carbon.identity.
> application.authentication.framework.util.FrameworkUtils} - Finding
> already authenticated IdPs of the Step
>
> [2016-07-29 23:30:00,930] DEBUG {org.wso2.carbon.identity.
> application.authentication.framework.handler.step.impl.DefaultStepHandler}
> - Step contains only a single IdP. Going to call it directly
>
> [2016-07-29 23:30:00,930] DEBUG {org.wso2.carbon.identity.
> application.authentication.framework.config.ConfigurationFacade} - Trying
> to find the IdP for name: mepin
>
> [2016-07-29 23:30:00,934] DEBUG {org.wso2.carbon.identity.
> application.authentication.framework.config.ConfigurationFacade} - A
> registered IdP was found
>
> [2016-07-29 23:30:03,520] DEBUG {org.wso2.carbon.identity.
> application.authentication.framework.handler.step.impl.DefaultStepHandler}
> - MePINAuthenticator returned: INCOMPLETE
>
> [2016-07-29 23:30:03,521] DEBUG {org.wso2.carbon.identity.
> application.authentication.framework.handler.step.impl.DefaultStepHandler}
> - MePINAuthenticator is redirecting
>
> [2016-07-29 23:30:03,521] DEBUG {org.wso2.carbon.identity.
> application.authentication.framework.handler.sequence.impl.
> DefaultStepBasedSequenceHandler} - Step is not complete yet. Redirecting
> to outside.
>
>
> So, I had offline chat with Dulanja. He said that it is not a direct
> method when using POST method. POST method is not really needed. Because,
> even facebook authenticator uses GET method to send URL parameters. And
> also he give some suggestion,
>
>-
>
>For example, To send parameter called username, instead of using
>username as a name we can use “a” or “A” so from outside it can’t be
>guess.
>-
>
>From java class , send as HTML body. While on submitting, need to get
>url parameters.
>
> @ Dulanja, Please add If I miss anything.
>
>
> Your comments and suggestions are highly appreciated.
>
> [1]
> *https://github.com/wso

[Dev] [DEV] [Mepin Authenticator] Problem while sending URL parameters using POST method

[Biruntha Gnaneswaran]

Hi Devs,

In Mepin authenticator, some URL parameters are send to Mepin UI page using
GET method [1]. When I try to send these parameters via POST method
using HttpURLConnection
class [2], it redirects to [3] not to the actual Mepin UI page. While I
try, I got the following Log .

[2016-07-29 23:30:00,903] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultAuthenticationRequestHandler}
- In authentication flow

[2016-07-29 23:30:00,903] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.handler.sequence.impl.DefaultStepBasedSequenceHandler}
- Executing the Step Based Authentication...

[2016-07-29 23:30:00,903] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.handler.sequence.impl.DefaultStepBasedSequenceHandler}
- Starting Step: 1

[2016-07-29 23:30:00,903] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.util.FrameworkUtils}
- Finding already authenticated IdPs of the Step

[2016-07-29 23:30:00,903] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.handler.step.impl.DefaultStepHandler}
- Receive a response from the external party

[2016-07-29 23:30:00,903] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.handler.step.impl.DefaultStepHandler}
- BasicAuthenticator can handle the request.

[2016-07-29 23:30:00,929] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.handler.step.impl.DefaultStepHandler}
- BasicAuthenticator returned: SUCCESS_COMPLETED

[2016-07-29 23:30:00,930] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.handler.sequence.impl.DefaultStepBasedSequenceHandler}
- Step 1 is completed. Going to get the next one.

[2016-07-29 23:30:00,930] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.handler.sequence.impl.DefaultStepBasedSequenceHandler}
- Starting Step: 2

[2016-07-29 23:30:00,930] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.util.FrameworkUtils}
- Finding already authenticated IdPs of the Step

[2016-07-29 23:30:00,930] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.handler.step.impl.DefaultStepHandler}
- Step contains only a single IdP. Going to call it directly

[2016-07-29 23:30:00,930] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.config.ConfigurationFacade}
- Trying to find the IdP for name: mepin

[2016-07-29 23:30:00,934] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.config.ConfigurationFacade}
- A registered IdP was found

[2016-07-29 23:30:03,520] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.handler.step.impl.DefaultStepHandler}
- MePINAuthenticator returned: INCOMPLETE

[2016-07-29 23:30:03,521] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.handler.step.impl.DefaultStepHandler}
- MePINAuthenticator is redirecting

[2016-07-29 23:30:03,521] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.handler.sequence.impl.DefaultStepBasedSequenceHandler}
- Step is not complete yet. Redirecting to outside.


So, I had offline chat with Dulanja. He said that it is not a direct method
when using POST method. POST method is not really needed. Because, even
facebook authenticator uses GET method to send URL parameters. And also he
give some suggestion,

   -

   For example, To send parameter called username, instead of using
   username as a name we can use “a” or “A” so from outside it can’t be
   guess.
   -

   From java class , send as HTML body. While on submitting, need to get
   url parameters.

@ Dulanja, Please add If I miss anything.


Your comments and suggestions are highly appreciated.

[1]
*https://github.com/wso2-extensions/identity-outbound-auth-mepin/blob/master/component/authenticator/src/main/java/org/wso2/carbon/identity/authenticator/mepin/MepinAuthenticator.java#L112-#L116*


[2]
http://stackoverflow.com/questions/4205980/java-sending-http-parameters-via-post-method-easily

[3] https://localhost:9443/samlsso


Thanks,


Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com
Linkedin : https://lk.linkedin.com/in/biruntha
Mobile : +94773718986
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [SMS Transport] Problem with Exception Handling

[Biruntha Gnaneswaran]

Hi malaka,

I will do ...

Thankyou

Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com

On Mon, Jun 13, 2016 at 9:32 AM, Malaka Silva  wrote:

> Hi Biruntha,
>
> These are the exact fixes we need to improve with the connector. Otherwise
> no pointing implementing the same thing. We need to have a better version
> of existing transport with connector.
>
> Axis2 transport is something for you to get an idea. We need to have a
> better version for connector.
>
> With connector not an good idea to depend on axis2 modules, better to
> implement logic within the connector itself.
>
> On Sat, Jun 11, 2016 at 8:32 PM, Biruntha Gnaneswaran 
> wrote:
>
>> Hi Rajjaz,
>>
>> The above problem is not for the case “without specifying "system Id" or
>> "password" ".  This is for the " wrong "system Id" or "password" ".
>>
>> Thankyou
>>
>> Biruntha
>>
>> Associate Software Engineer
>> WSO2
>> Email : birun...@wso2.com
>>
>> On Sat, Jun 11, 2016 at 3:47 PM, Biruntha Gnaneswaran 
>> wrote:
>>
>>> Hi Rajjaz,
>>>
>>> Yes SMSMesage  throws AxisFault.
>>> I try without general exception. but i'm facing the same problem.
>>> because sentInfo() is different.
>>>
>>> for example i try this without specifying "system Id" or "password". so, 
>>> this
>>> was checked [getSystemId(),getPassword()] under sendSMS() method in
>>> SMPPImplManager class. So only i’m getting *"Unable to Connect "* error
>>> message in *log*.
>>>
>>> Thankyou
>>>
>>> Biruntha
>>>
>>> Associate Software Engineer
>>> WSO2
>>> Email : birun...@wso2.com
>>>
>>> On Sat, Jun 11, 2016 at 3:22 PM, Rajjaz Mohammed 
>>> wrote:
>>>
>>>> Hi Biruntha,
>>>>
>>>> Why do you want to catch a general exception here?
>>>>
>>>> You can simply catch AxisFault since SMSMesage uses axis2 transport and
>>>> throws AxisFault.
>>>>
>>>> try {
>>>> smsMessage = new SMSMessage(SMPPConstants.SENDER, phoneNo, message, 
>>>> SMSMessage.OUT_MESSAGE);
>>>> manager.sentInfo(smsMessage);
>>>> } catch (AxisFault axisFault) {
>>>> handleException("Error while sending SMS: " + axisFault.getMessage(), 
>>>> messageContext);
>>>> }
>>>>
>>>>
>>>> On Fri, Jun 10, 2016 at 4:04 PM, Biruntha Gnaneswaran <
>>>> birun...@wso2.com> wrote:
>>>>
>>>>> Hi Devs,
>>>>>
>>>>> I want to send SMS using axis2 SMS Transport [1] . I try with below
>>>>> code. It works fine in normal case. Here sentInfo() is used to send
>>>>> SMS. But if there is an exception in sentInfo() method, I couldn’t
>>>>> catch that exception from my code. Because sendSMS() method in
>>>>> SMPPImplManager class didn’t throw any exception.
>>>>>
>>>>> Is there any way to solve this problem?
>>>>>
>>>>> *try *{smsMessage = *new *SMSMessage(sender,phoneNo,message,*2*);
>>>>> manager.sentInfo(smsMessage);*log*.info(*"Successfully completed 
>>>>> sending SMS"*);} *catch *(Exception e){handleException(*"Error while 
>>>>> sending SMS: " *+ e.getMessage(), e, messageContext);}
>>>>>
>>>>> [1]
>>>>> https://github.com/wso2/wso2-axis2-transports/tree/master/modules/sms/src/main/java/org/apache/axis2/transport/sms
>>>>>
>>>>> Thankyou,
>>>>>
>>>>> Biruntha
>>>>>
>>>>> Associate Software Engineer
>>>>> WSO2
>>>>> Email : birun...@wso2.com
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thank you
>>>> Best Regards
>>>>
>>>> *Rajjaz HM*
>>>> Associate Software Engineer
>>>> Platform Extension Team
>>>> WSO2 Inc. <http://wso2.com/>
>>>> lean | enterprise | middleware
>>>> Mobile | +94752833834|+94777226874
>>>> Email   | raj...@wso2.com
>>>> LinkedIn <https://lk.linkedin.com/in/hmohammedrajjaz> | Blogger
>>>> <http://rajjazhm.blogspot.com/> | WSO2 Profile
>>>> <http://wso2.com/about/team/mohammer-rajjaz/>
>>>>
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Technical 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.
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [SMS Transport] Problem with Exception Handling

[Biruntha Gnaneswaran]

Hi Rajjaz,

The above problem is not for the case “without specifying "system Id" or
"password" ".  This is for the " wrong "system Id" or "password" ".

Thankyou

Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com

On Sat, Jun 11, 2016 at 3:47 PM, Biruntha Gnaneswaran 
wrote:

> Hi Rajjaz,
>
> Yes SMSMesage  throws AxisFault.
> I try without general exception. but i'm facing the same problem. because 
> sentInfo()
> is different.
>
> for example i try this without specifying "system Id" or "password". so, this
> was checked [getSystemId(),getPassword()] under sendSMS() method in
> SMPPImplManager class. So only i’m getting *"Unable to Connect "* error
> message in *log*.
>
> Thankyou
>
> Biruntha
>
> Associate Software Engineer
> WSO2
> Email : birun...@wso2.com
>
> On Sat, Jun 11, 2016 at 3:22 PM, Rajjaz Mohammed  wrote:
>
>> Hi Biruntha,
>>
>> Why do you want to catch a general exception here?
>>
>> You can simply catch AxisFault since SMSMesage uses axis2 transport and
>> throws AxisFault.
>>
>> try {
>> smsMessage = new SMSMessage(SMPPConstants.SENDER, phoneNo, message, 
>> SMSMessage.OUT_MESSAGE);
>>     manager.sentInfo(smsMessage);
>> } catch (AxisFault axisFault) {
>> handleException("Error while sending SMS: " + axisFault.getMessage(), 
>> messageContext);
>> }
>>
>>
>> On Fri, Jun 10, 2016 at 4:04 PM, Biruntha Gnaneswaran 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> I want to send SMS using axis2 SMS Transport [1] . I try with below
>>> code. It works fine in normal case. Here sentInfo() is used to send
>>> SMS. But if there is an exception in sentInfo() method, I couldn’t
>>> catch that exception from my code. Because sendSMS() method in
>>> SMPPImplManager class didn’t throw any exception.
>>>
>>> Is there any way to solve this problem?
>>>
>>> *try *{smsMessage = *new *SMSMessage(sender,phoneNo,message,*2*);
>>> manager.sentInfo(smsMessage);*log*.info(*"Successfully completed 
>>> sending SMS"*);} *catch *(Exception e){handleException(*"Error while 
>>> sending SMS: " *+ e.getMessage(), e, messageContext);}
>>>
>>> [1]
>>> https://github.com/wso2/wso2-axis2-transports/tree/master/modules/sms/src/main/java/org/apache/axis2/transport/sms
>>>
>>> Thankyou,
>>>
>>> Biruntha
>>>
>>> Associate Software Engineer
>>> WSO2
>>> Email : birun...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thank you
>> Best Regards
>>
>> *Rajjaz HM*
>> Associate Software Engineer
>> Platform Extension Team
>> WSO2 Inc. <http://wso2.com/>
>> lean | enterprise | middleware
>> Mobile | +94752833834|+94777226874
>> Email   | raj...@wso2.com
>> LinkedIn <https://lk.linkedin.com/in/hmohammedrajjaz> | Blogger
>> <http://rajjazhm.blogspot.com/> | WSO2 Profile
>> <http://wso2.com/about/team/mohammer-rajjaz/>
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [SMS Transport] Problem with Exception Handling

[Biruntha Gnaneswaran]

Hi Rajjaz,

Yes SMSMesage  throws AxisFault.
I try without general exception. but i'm facing the same problem.
because sentInfo()
is different.

for example i try this without specifying "system Id" or "password". so, this
was checked [getSystemId(),getPassword()] under sendSMS() method in
SMPPImplManager class. So only i’m getting *"Unable to Connect "* error
message in *log*.

Thankyou

Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com

On Sat, Jun 11, 2016 at 3:22 PM, Rajjaz Mohammed  wrote:

> Hi Biruntha,
>
> Why do you want to catch a general exception here?
>
> You can simply catch AxisFault since SMSMesage uses axis2 transport and
> throws AxisFault.
>
> try {
> smsMessage = new SMSMessage(SMPPConstants.SENDER, phoneNo, message, 
> SMSMessage.OUT_MESSAGE);
> manager.sentInfo(smsMessage);
> } catch (AxisFault axisFault) {
> handleException("Error while sending SMS: " + axisFault.getMessage(), 
> messageContext);
> }
>
>
> On Fri, Jun 10, 2016 at 4:04 PM, Biruntha Gnaneswaran 
> wrote:
>
>> Hi Devs,
>>
>> I want to send SMS using axis2 SMS Transport [1] . I try with below code.
>> It works fine in normal case. Here sentInfo() is used to send SMS. But
>> if there is an exception in sentInfo() method, I couldn’t catch that
>> exception from my code. Because sendSMS() method in SMPPImplManager class
>> didn’t throw any exception.
>>
>> Is there any way to solve this problem?
>>
>> *try *{smsMessage = *new *SMSMessage(sender,phoneNo,message,*2*);
>> manager.sentInfo(smsMessage);*log*.info(*"Successfully completed sending 
>> SMS"*);} *catch *(Exception e){handleException(*"Error while sending 
>> SMS: " *+ e.getMessage(), e, messageContext);}
>>
>> [1]
>> https://github.com/wso2/wso2-axis2-transports/tree/master/modules/sms/src/main/java/org/apache/axis2/transport/sms
>>
>> Thankyou,
>>
>> Biruntha
>>
>> Associate Software Engineer
>> WSO2
>> Email : birun...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thank you
> Best Regards
>
> *Rajjaz HM*
> Associate Software Engineer
> Platform Extension Team
> WSO2 Inc. <http://wso2.com/>
> lean | enterprise | middleware
> Mobile | +94752833834|+94777226874
> Email   | raj...@wso2.com
> LinkedIn <https://lk.linkedin.com/in/hmohammedrajjaz> | Blogger
> <http://rajjazhm.blogspot.com/> | WSO2 Profile
> <http://wso2.com/about/team/mohammer-rajjaz/>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] [SMS Transport] Problem with Exception Handling

[Biruntha Gnaneswaran]

Hi Devs,

I want to send SMS using axis2 SMS Transport [1] . I try with below code.
It works fine in normal case. Here sentInfo() is used to send SMS. But if
there is an exception in sentInfo() method, I couldn’t catch that exception
from my code. Because sendSMS() method in SMPPImplManager class didn’t
throw any exception.

Is there any way to solve this problem?

*try *{smsMessage = *new *SMSMessage(sender,phoneNo,message,*2*);
  manager.sentInfo(smsMessage);*log*.info(*"Successfully completed
sending SMS"*);} *catch *(Exception e){handleException(*"Error
while sending SMS: " *+ e.getMessage(), e, messageContext);}

[1]
https://github.com/wso2/wso2-axis2-transports/tree/master/modules/sms/src/main/java/org/apache/axis2/transport/sms

Thankyou,

Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [ESB] [SMPP Transport] Unable to send message

[Biruntha Gnaneswaran]

Hi Malaka,

I will try to debug. but i already tried with some information from [1] and
[2]. but the same error is coming.

[1] http://stackoverflow.com/questions/18721246/smpp-using-wso2
[2]
http://mytecheye.blogspot.com/2013/01/wso2-esb-sending-sms-alerts-for-failures.html

Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com

On Wed, Jun 1, 2016 at 11:19 AM, Malaka Silva  wrote:

> Hi Biruntha,
>
> Try debugging [1] and you may also find some info in [2]
>
> [1]
> http://svn.apache.org/repos/asf/axis/axis2/java/transports/branches/transport/1.0.0/modules/sms/
>
> [2]
> http://mytecheye.blogspot.com/2013/01/wso2-esb-sending-sms-alerts-for-failures.html
>
> On Tue, May 31, 2016 at 7:18 PM, Biruntha Gnaneswaran 
> wrote:
>
>> Hi Devs,
>>
>> I follow [1] to send a message from SMSC simulator to ESB using SMPP
>> Transport. When I try to send, in ESB logs I got the following error.
>>
>> ERROR - AxisEngine The service cannot be found for the endpoint reference
>> (EPR)
>>
>> org.apache.axis2.AxisFault: The service cannot be found for the endpoint
>> reference (EPR)
>>
>> at
>> org.apache.axis2.engine.DispatchPhase.validateTransport(DispatchPhase.java:251)
>>
>> at
>> org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:109)
>>
>> at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
>>
>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>>
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>>
>> at
>> org.apache.axis2.transport.sms.SMSManager.dispatchToAxis2(SMSManager.java:162)
>>
>> at
>> org.apache.axis2.transport.sms.smpp.SMPPDispatcher.dispatch(SMPPDispatcher.java:46)
>>
>> at
>> org.apache.axis2.transport.sms.smpp.SMPPListener.onAcceptDeliverSm(SMPPListener.java:85)
>>
>> at org.jsmpp.session.SMPPSession.fireAcceptDeliverSm(SMPPSession.java:445)
>>
>> at org.jsmpp.session.SMPPSession.access$0(SMPPSession.java:443)
>>
>> at
>> org.jsmpp.session.SMPPSession$ResponseHandlerImpl.processDeliverSm(SMPPSession.java:462)
>>
>> at
>> org.jsmpp.session.state.SMPPSessionBoundRX.processDeliverSm0(SMPPSessionBoundRX.java:109)
>>
>> at
>> org.jsmpp.session.state.SMPPSessionBoundRX.processDeliverSm(SMPPSessionBoundRX.java:51)
>>
>> at org.jsmpp.session.PDUProcessTask.run(PDUProcessTask.java:81)
>>
>> 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://gayanlggd.wordpress.com/2014/12/19/sending-a-message-from-smsc-simulator-to-wso2-esb-using-smpp-transport/
>>
>>
>> Biruntha
>>
>> Associate Software Engineer
>> WSO2
>> Email : birun...@wso2.com
>>
>> ___
>> 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.
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] [ESB] [SMPP Transport] Unable to send message

[Biruntha Gnaneswaran]

Hi Devs,

I follow [1] to send a message from SMSC simulator to ESB using SMPP
Transport. When I try to send, in ESB logs I got the following error.

ERROR - AxisEngine The service cannot be found for the endpoint reference
(EPR)

org.apache.axis2.AxisFault: The service cannot be found for the endpoint
reference (EPR)

at
org.apache.axis2.engine.DispatchPhase.validateTransport(DispatchPhase.java:251)

at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:109)

at org.apache.axis2.engine.Phase.invoke(Phase.java:329)

at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)

at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)

at
org.apache.axis2.transport.sms.SMSManager.dispatchToAxis2(SMSManager.java:162)

at
org.apache.axis2.transport.sms.smpp.SMPPDispatcher.dispatch(SMPPDispatcher.java:46)

at
org.apache.axis2.transport.sms.smpp.SMPPListener.onAcceptDeliverSm(SMPPListener.java:85)

at org.jsmpp.session.SMPPSession.fireAcceptDeliverSm(SMPPSession.java:445)

at org.jsmpp.session.SMPPSession.access$0(SMPPSession.java:443)

at
org.jsmpp.session.SMPPSession$ResponseHandlerImpl.processDeliverSm(SMPPSession.java:462)

at
org.jsmpp.session.state.SMPPSessionBoundRX.processDeliverSm0(SMPPSessionBoundRX.java:109)

at
org.jsmpp.session.state.SMPPSessionBoundRX.processDeliverSm(SMPPSessionBoundRX.java:51)

at org.jsmpp.session.PDUProcessTask.run(PDUProcessTask.java:81)

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://gayanlggd.wordpress.com/2014/12/19/sending-a-message-from-smsc-simulator-to-wso2-esb-using-smpp-transport/


Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev