Re: [Dev] API-Proxy for Single Page Application

[Thilina Madumal]

Hi Youcef,

This is not a replacement for APIM Gateway. APIM Gateway and this are two
different things.
This is an implementation of the security pattern no. 17 described in blog
1.

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

Regards,
Thilina.

On Tue, Dec 12, 2017 at 12:48 AM, Youcef HILEM 
wrote:

> Hi Thilina,
>
> Could you please explain why APIM Gateway is not suitable?
> How to integrate this feature in WSO2 APIM?
> In our distributed architecture, we already have enough components and
> adding another seems inappropriate.
>
> Thanks
> Youcef HILEM
>
>
>
> --
> Sent from: http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-
> Development-f3.html
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
*Thilina Madumal*
*Software Engineer | **WSO2*
Email: thilina...@wso2.com
Mobile: *+ <+94%2077%20767%201807>94 774553167*
Web:  http://wso2.com


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

[Dev] [XACML] Entitlement with APIs - Inconsistent Information Against with Docs

[Chaminda Jayawardena]

Hi All,

I am trying to add a policy(addPolicy) using Identity Server 5.4.0
Entitlement API as described in*[1]*. When compare the API with the
document it has many differences, so raised the doc Jira*[2]*.

But while having further look on this, I have a doubt whether this API is
correct since the content has lastModifiedTime, lastModifiedUser kind of
fields which are unnecessary for the request as I believe.
So I tried with the request content as mentioned in the document replacing
the actual one and it worked.
*Is this a bug in admin service?* what is the correct request for
*addPolicy?*

Below is the *addPolicy* operation according to the IS5.4.0 admin service

*http://schemas.xmlsoap.org/soap/envelope/
"
xmlns:xsd="http://org.apache.axis2/xsd "
xmlns:xsd1="http://dto.entitlement.identity.carbon.wso2.org/xsd
">*
**
**
*   *
*  *
*  *
* *
* ?*
* *
* *
**
*?*
**
*?*
**
*?*
**
*?*
* *
* *
* ?*
* *
* ?*
* *
* ?*
* *
* ?*
* *
* ?*
* *
* ?*
* *
* ?*
* *
* ?*
* *
* ?*
* *
* ?*
* *
* ?*
* *
* ?*
*  *
*   *
**
* *

[1] https://docs.wso2.com/display/IS540/Entitlement+with+APIs
[2] https://wso2.org/jira/browse/DOCUMENTATION-7322

-- 
Thanks & Regards

*Chaminda Jayawardena*
Associate Technical Lead - QA
WSO2 Inc. - http://wso2.com
+94-77-7725234
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error while configuring email notification in WSO2 DSS

[Chanika Geeganage]

Since this is an authentication failure, this might be because of gmail
account protection. To avoid that, you have to make your gmail account less
secure. You can do that from following link

https://www.google.com/settings/security/lesssecureapps

On Wed, Dec 13, 2017 at 12:11 PM, Piriya Sivalingam  wrote:

> Hi,
>
> I am trying to configure email notification scenario in WSO2 DSS. I have
> generated a data service in DSS for exposing data in a database, and when a
> request to that data service triggers an event the subscribers to that
> event should receive an email notification. The use case is when I invoke
> the data service the data should be added to the database and at the same
> time the respective subscribers should receive a mail notification.
>
> The steps I followed are:
>
>- I configured the mailto transport sender in axis2_Client.xml file
>located in /repository/conf/axis2 folder.
>- In the insert query I added an event for identifying an
>event_trigger used in the data service.
>- I configured the Xpath accordingly for the response message, and
>when this evaluation becomes true the event will be triggered.
>- I configured the Event sink URL as well.
>
> When I invoke the service I found the following exception logged in the
> console:
>
> ERROR {org.apache.axis2.transport.mail.MailTransportSender} -  Error
> creating mail message or sending it to the configured server
> {org.apache.axis2.transport.mail.MailTransportSender}
> javax.mail.AuthenticationFailedException
>
> Can you please suggest whether there is anything wrong with my
> configuration?
> The document I referred is [1].
>
> [1] https://docs.wso2.com/display/DSS351/Receiving+
> Notifications+from+Data+Services
>
> Thanks,
> Piriya
>
> Regards,
>
> *Piriya Sivalingam*
>
> *Software Engineer - Support Team*
>
> *WSO2*
> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>
> [image: http://wso2.com/signature] 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards..

Chanika Geeganage
+94773522586
WSO2, Inc.; http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error while configuring email notification in WSO2 DSS

[Dilusha Alphonso]

Hi Piriya,

I followed the same documentation for email generation in DSS. But I
encountered another exception while configuring. I believe the steps you
followed here is correct but if I am not wrong you may be missed to select
the input event which you created. If so could you please select that event
and save it. I feel this instruction is missing in the document. So can you
try this out and let me know whether it works or not.

Thanks,
Dilusha.



On Wed, Dec 13, 2017 at 12:11 PM, Piriya Sivalingam  wrote:

> Hi,
>
> I am trying to configure email notification scenario in WSO2 DSS. I have
> generated a data service in DSS for exposing data in a database, and when a
> request to that data service triggers an event the subscribers to that
> event should receive an email notification. The use case is when I invoke
> the data service the data should be added to the database and at the same
> time the respective subscribers should receive a mail notification.
>
> The steps I followed are:
>
>- I configured the mailto transport sender in axis2_Client.xml file
>located in /repository/conf/axis2 folder.
>- In the insert query I added an event for identifying an
>event_trigger used in the data service.
>- I configured the Xpath accordingly for the response message, and
>when this evaluation becomes true the event will be triggered.
>- I configured the Event sink URL as well.
>
> When I invoke the service I found the following exception logged in the
> console:
>
> ERROR {org.apache.axis2.transport.mail.MailTransportSender} -  Error
> creating mail message or sending it to the configured server
> {org.apache.axis2.transport.mail.MailTransportSender}
> javax.mail.AuthenticationFailedException
>
> Can you please suggest whether there is anything wrong with my
> configuration?
> The document I referred is [1].
>
> [1] https://docs.wso2.com/display/DSS351/Receiving+
> Notifications+from+Data+Services
>
> Thanks,
> Piriya
>
> Regards,
>
> *Piriya Sivalingam*
>
> *Software Engineer - Support Team*
>
> *WSO2*
> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>
> [image: http://wso2.com/signature] 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 


*Best Regards,Dilusha Alphonso*

*Software Engineer - Support Team*


*WSO2*
*Mobile : *

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

[Dev] Error while configuring email notification in WSO2 DSS

[Piriya Sivalingam]

Hi,

I am trying to configure email notification scenario in WSO2 DSS. I have
generated a data service in DSS for exposing data in a database, and when a
request to that data service triggers an event the subscribers to that
event should receive an email notification. The use case is when I invoke
the data service the data should be added to the database and at the same
time the respective subscribers should receive a mail notification.

The steps I followed are:

   - I configured the mailto transport sender in axis2_Client.xml file
   located in /repository/conf/axis2 folder.
   - In the insert query I added an event for identifying an event_trigger
   used in the data service.
   - I configured the Xpath accordingly for the response message, and when
   this evaluation becomes true the event will be triggered.
   - I configured the Event sink URL as well.

When I invoke the service I found the following exception logged in the
console:

ERROR {org.apache.axis2.transport.mail.MailTransportSender} -  Error
creating mail message or sending it to the configured server
{org.apache.axis2.transport.mail.MailTransportSender}
javax.mail.AuthenticationFailedException

Can you please suggest whether there is anything wrong with my
configuration?
The document I referred is [1].

[1]
https://docs.wso2.com/display/DSS351/Receiving+Notifications+from+Data+Services

Thanks,
Piriya

Regards,

*Piriya Sivalingam*

*Software Engineer - Support Team*

*WSO2*
*Mobile : +94 77 8462039*

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

Re: [Dev] Federated authenticators - Connectors and protocols

[Shavindri Dissanayake]

Thak you! Created a doc JIRA for it.

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

Thanks & Regards
Shavindri Dissanayake
Senior Technical Writer

WSO2 Inc.
lean.enterprise.middleware

On Wed, Dec 13, 2017 at 10:17 AM, Isuru Uyanage  wrote:

> Hi Shavindri,
> Yes, that is the exact requirement.
>
>
> Thanks
> Isuru
>
> *Thanks and Best Regards,*
>
> *Isuru Uyanage*
> *Software Engineer - QA | WSO2*
> *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
> *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
> *
>
>
>
>
> On Wed, Dec 13, 2017 at 9:56 AM, Shavindri Dissanayake  > wrote:
>
>> Hi Isuru, Godwin, and Hasanthi,
>>
>> Thank you, for the info.
>> To ensure I have got the requirement clear: We need to update docs for
>> each connector in [1] and mention the underlying protocol they use?
>>
>> [1] https://docs.wso2.com/display/ISCONNECTORS/Authenticator
>> s+and+Connectors
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Federated authenticators - Connectors and protocols

[Isuru Uyanage]

Hi Shavindri,
Yes, that is the exact requirement.


Thanks
Isuru

*Thanks and Best Regards,*

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




On Wed, Dec 13, 2017 at 9:56 AM, Shavindri Dissanayake 
wrote:

> Hi Isuru, Godwin, and Hasanthi,
>
> Thank you, for the info.
> To ensure I have got the requirement clear: We need to update docs for
> each connector in [1] and mention the underlying protocol they use?
>
> [1] https://docs.wso2.com/display/ISCONNECTORS/
> Authenticators+and+Connectors
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Federated authenticators - Connectors and protocols

[Shavindri Dissanayake]

Hi Isuru, Godwin, and Hasanthi,

Thank you, for the info.
To ensure I have got the requirement clear: We need to update docs for each
connector in [1] and mention the underlying protocol they use?

[1] https://docs.wso2.com/display/ISCONNECTORS/Authenticators+and+Connectors
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] Error occurred while connecting to back end

[Viduranga Gunarathne]

Hi,

Please find the link below

https://stackoverflow.com/questions/23322676/javax-net-ssl-sslhandshakeexception-sun-security-validator-validatorexception

Thanks,
Viduranga

On Tue, Dec 12, 2017 at 9:35 PM, Senuwan Withana  wrote:

> Thank Guys, I will look into it.
>
> *Senuwan Withana*
> Software Engineer - Support Team | WSO2
>
> Email : senu...@wso2.com
> Mobile: 94773212853
> Web: http://www.wso2.com
>
>
>
> On Tue, Dec 12, 2017 at 7:23 PM, Godwin Shrimal  wrote:
>
>> Hi Senuwan,
>>
>> Check the validity period of the certificate of the ESB. Maybe it's
>> expired.
>>
>> Thanks
>> Godwin
>>
>> On Tue, Dec 12, 2017 at 6:41 PM, Senuwan Withana 
>> wrote:
>>
>>> Hi Abimaran,
>>>
>>> Well, I did not generate any certificate. What I did was, tried to
>>> create an API using WSO2 API Manager, Publisher. When I was adding
>>> Production Endpoint that mentioned error was popping up.
>>>
>>> Thanks.
>>> *Senuwan Withana*
>>> Software Engineer - Support Team | WSO2
>>>
>>> Email : senu...@wso2.com
>>> Mobile: 94773212853
>>> Web: http://www.wso2.com
>>>
>>>
>>>
>>> On Tue, Dec 12, 2017 at 5:06 PM, Abimaran Kugathasan 
>>> wrote:
>>>
 Hi Senuwan,

 By checking your exception, it says, your certificate is expired. You
 have to generate a new certificate.

 Caused by: java.security.cert.CertificateExpiredException: NotAfter:
 Mon Jun 19 14:43:07 IST 2017

 On Tue, Dec 12, 2017 at 4:41 PM, Senuwan Withana 
 wrote:

> Hi Team,
>
> I got below error when I'm trying to connect my ESB proxy into the API
> Manager.  Any suggestion to solve this error?
>
>
> [2017-12-12 16:38:56,137] ERROR - APIProviderHostObject Error occurred
> while connecting to backend : https://localhost:8243/service
> s/EmailSender, reason : sun.security.validator.ValidatorException:
> PKIX path validation failed: 
> java.security.cert.CertPathValidatorException:
> timestamp check failed
> javax.net.ssl.SSLHandshakeException: 
> sun.security.validator.ValidatorException:
> PKIX path validation failed: 
> java.security.cert.CertPathValidatorException:
> timestamp check failed
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHa
> ndshaker.java:1514)
> at sun.security.ssl.ClientHandshaker.processMessage(ClientHands
> haker.java:216)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1026)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:961)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSo
> cketImpl.java:1375)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.
> java:1403)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.
> java:1387)
> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS
> ocketFactory.java:533)
> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS
> ocketFactory.java:401)
> at org.apache.http.impl.conn.DefaultClientConnectionOperator.op
> enConnection(DefaultClientConnectionOperator.java:178)
> at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(M
> anagedClientConnectionImpl.java:304)
> at org.apache.http.impl.client.DefaultRequestDirector.tryConnec
> t(DefaultRequestDirector.java:610)
> at org.apache.http.impl.client.DefaultRequestDirector.execute(D
> efaultRequestDirector.java:445)
> at org.apache.http.impl.client.AbstractHttpClient.doExecute(Abs
> tractHttpClient.java:863)
> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
> eableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
> eableHttpClient.java:106)
> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
> eableHttpClient.java:57)
> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.sen
> dHttpHEADRequest(APIProviderHostObject.java:4781)
> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.jsF
> unction_isURLValid(APIProviderHostObject.java:4173)
> at sun.reflect.GeneratedMethodAccessor117.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
> thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
> at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386)
> at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime
> 

Re: [Dev] [EI] Change number of pages

[Shazni Nazeer]

Issue for  is created in [1]

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

It's vital have search than the number of tabs. Godwin's query for tab was
because the search is not available. Thus if dynamic endpoint search is
fixed there's no need to configure the default number of tabs (which is not
an issue in the first place)



On Tue, Dec 12, 2017 at 7:43 PM, Milinda Perera  wrote:

> Hi,
>
> Please create issues related to EI/ESB in [1].
>
> When you click next, does 1,2,3,next,last get updated to 2,3,4,next,last ?
> If so that is fine.
> I think fixing search feature is more important and useful than fixing the
> number of pages shown. Anyway, we have to fix to honor "ItemsPerPage" in
> carbon.xml
>
> [1] https://github.com/wso2/product-ei/issues
>
> Thanks,
> Milinda
>
> On Wed, Dec 13, 2017 at 5:50 AM, Shazni Nazeer  wrote:
>
>> Hi Chandana,
>>
>> Yes. Looks like sequences, endpoints pages do not take that into account.
>> I have create an issue [1] for that. Thanks for pointing it out.
>>
>> [1] https://github.com/wso2/carbon-mediation/issues/929
>>
>> However, the question raised above is not about the number of entries in
>> a single page. Instead it's about configuring default numbered tabs shown.
>> Even if you have 100s of artifacts what is available are the tabs with
>> label 1, 2, 3 and then 'next' and 'last'. Question was if there's a way to
>> have more numbers tabs, say 5 and have 1, 2, 3, 4, 5 and then 'next' and
>> 'last'.
>>
>> On Tue, Dec 12, 2017 at 5:39 PM, Chandana Napagoda 
>> wrote:
>>
>>> Hi,
>>>
>>> I think this is a bug/ implementation limitation in the ESB/EI UIs.
>>> Because other pages such as user management pages honour the 'ItemsPerPage'
>>> value in the carbon.xml
>>>
>>> Regards,
>>> Chandana
>>>
>>> Blog: http://blog.napagoda.com
>>> Linkedin: https://www.linkedin.com/in/chandananapagoda/
>>>
>>> On 12 December 2017 at 12:24, Shazni Nazeer  wrote:
>>>
 Yes Godwin. I too have felt the same. It is tough to look for the
 endpoint when there are many. Quickly navigating and to have a quick peek
 at it requires many clicks. Search option would help in this case.

 On Mon, Dec 11, 2017 at 7:51 PM, Godwin Shrimal 
 wrote:

> Thanks for the response Shazni, This is really important specially for
> dynamic endpoints. Since searching functionality is not working with
> dynamic endpoint, think we need to find an endpoint start from letter "P"
> while we are having many no of endpoints in the system. We have to click
> next, next many times to find the exact endpoint. Extending the no of 
> pages
> will not solve the exact problem here, but up to some level. I think
> Implementing search feature for dynamic endpoint is the best solution as
> discussed in [1].
>
> [1] [EI] Cant search dynamic endpoints
>
> Thanks
> Godwin
>
>
> On Tue, Dec 12, 2017 at 7:25 AM, Shazni Nazeer 
> wrote:
>
>> I don't think this is possible with any configuration. If you want
>> you will have to tweak all the jsp's related to sequences, templates etc.
>> See [1]. I don't think it's a good option.
>>
>> [1] https://github.com/wso2/carbon-mediation/blob/master/compone
>> nts/mediation-ui/org.wso2.carbon.sequences.ui/src/main/resou
>> rces/web/sequences/list_sequences.jsp
>>
>> On Mon, Dec 11, 2017 at 6:34 AM, Godwin Shrimal 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> Can we change the number of pages shows in Proxy services, sequence,
>>> endpoints etc?  By default it shows only 3 pages, next and last
>>>
>>>
>>> Thank
>>> Godwin
>>>
>>> --
>>> *Godwin Amila Shrimal*
>>> Associate Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94772264165*
>>> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
>>> *
>>> twitter: https://twitter.com/godwinamila
>>> 
>>>
>>
>>
>>
>> --
>> Shazni Nazeer
>>
>> Mob : +94 37331
>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>>
>> Blogs :
>>
>> https://medium.com/@mshazninazeer
>> http://shazninazeer.blogspot.com
>>
>> 
>>
>
>
>
> --
> *Godwin Amila Shrimal*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
> *
> twitter: https://twitter.com/godwinamila
> 
>



 --
 Shazni Nazeer

 Mob : +94 37331
 

Re: [Dev] [EI] Change number of pages

[Milinda Perera]

Hi,

Please create issues related to EI/ESB in [1].

When you click next, does 1,2,3,next,last get updated to 2,3,4,next,last ?
If so that is fine.
I think fixing search feature is more important and useful than fixing the
number of pages shown. Anyway, we have to fix to honor "ItemsPerPage" in
carbon.xml

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

Thanks,
Milinda

On Wed, Dec 13, 2017 at 5:50 AM, Shazni Nazeer  wrote:

> Hi Chandana,
>
> Yes. Looks like sequences, endpoints pages do not take that into account.
> I have create an issue [1] for that. Thanks for pointing it out.
>
> [1] https://github.com/wso2/carbon-mediation/issues/929
>
> However, the question raised above is not about the number of entries in a
> single page. Instead it's about configuring default numbered tabs shown.
> Even if you have 100s of artifacts what is available are the tabs with
> label 1, 2, 3 and then 'next' and 'last'. Question was if there's a way to
> have more numbers tabs, say 5 and have 1, 2, 3, 4, 5 and then 'next' and
> 'last'.
>
> On Tue, Dec 12, 2017 at 5:39 PM, Chandana Napagoda 
> wrote:
>
>> Hi,
>>
>> I think this is a bug/ implementation limitation in the ESB/EI UIs.
>> Because other pages such as user management pages honour the 'ItemsPerPage'
>> value in the carbon.xml
>>
>> Regards,
>> Chandana
>>
>> Blog: http://blog.napagoda.com
>> Linkedin: https://www.linkedin.com/in/chandananapagoda/
>>
>> On 12 December 2017 at 12:24, Shazni Nazeer  wrote:
>>
>>> Yes Godwin. I too have felt the same. It is tough to look for the
>>> endpoint when there are many. Quickly navigating and to have a quick peek
>>> at it requires many clicks. Search option would help in this case.
>>>
>>> On Mon, Dec 11, 2017 at 7:51 PM, Godwin Shrimal  wrote:
>>>
 Thanks for the response Shazni, This is really important specially for
 dynamic endpoints. Since searching functionality is not working with
 dynamic endpoint, think we need to find an endpoint start from letter "P"
 while we are having many no of endpoints in the system. We have to click
 next, next many times to find the exact endpoint. Extending the no of pages
 will not solve the exact problem here, but up to some level. I think
 Implementing search feature for dynamic endpoint is the best solution as
 discussed in [1].

 [1] [EI] Cant search dynamic endpoints

 Thanks
 Godwin


 On Tue, Dec 12, 2017 at 7:25 AM, Shazni Nazeer  wrote:

> I don't think this is possible with any configuration. If you want you
> will have to tweak all the jsp's related to sequences, templates etc. See
> [1]. I don't think it's a good option.
>
> [1] https://github.com/wso2/carbon-mediation/blob/master/compone
> nts/mediation-ui/org.wso2.carbon.sequences.ui/src/main/resou
> rces/web/sequences/list_sequences.jsp
>
> On Mon, Dec 11, 2017 at 6:34 AM, Godwin Shrimal 
> wrote:
>
>> Hi Devs,
>>
>> Can we change the number of pages shows in Proxy services, sequence,
>> endpoints etc?  By default it shows only 3 pages, next and last
>>
>>
>> Thank
>> Godwin
>>
>> --
>> *Godwin Amila Shrimal*
>> Associate Technical Lead
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
>> *
>> twitter: https://twitter.com/godwinamila
>> 
>>
>
>
>
> --
> Shazni Nazeer
>
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>
> Blogs :
>
> https://medium.com/@mshazninazeer
> http://shazninazeer.blogspot.com
>
> 
>



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

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

>>>
>>>
>>>
>>> --
>>> Shazni Nazeer
>>>
>>> Mob : +94 37331
>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>>>
>>> Blogs :
>>>
>>> https://medium.com/@mshazninazeer
>>> http://shazninazeer.blogspot.com
>>>
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Blog: http://blog.napagoda.com
>> Linkedin: https://www.linkedin.com/in/chandananapagoda/
>>
>>
>
>
> --
> Shazni Nazeer
>
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>
> Blogs :
>
> 

Re: [Dev] [EI] Change number of pages

[Shazni Nazeer]

Hi Chandana,

Yes. Looks like sequences, endpoints pages do not take that into account. I
have create an issue [1] for that. Thanks for pointing it out.

[1] https://github.com/wso2/carbon-mediation/issues/929

However, the question raised above is not about the number of entries in a
single page. Instead it's about configuring default numbered tabs shown.
Even if you have 100s of artifacts what is available are the tabs with
label 1, 2, 3 and then 'next' and 'last'. Question was if there's a way to
have more numbers tabs, say 5 and have 1, 2, 3, 4, 5 and then 'next' and
'last'.

On Tue, Dec 12, 2017 at 5:39 PM, Chandana Napagoda 
wrote:

> Hi,
>
> I think this is a bug/ implementation limitation in the ESB/EI UIs.
> Because other pages such as user management pages honour the 'ItemsPerPage'
> value in the carbon.xml
>
> Regards,
> Chandana
>
> Blog: http://blog.napagoda.com
> Linkedin: https://www.linkedin.com/in/chandananapagoda/
>
> On 12 December 2017 at 12:24, Shazni Nazeer  wrote:
>
>> Yes Godwin. I too have felt the same. It is tough to look for the
>> endpoint when there are many. Quickly navigating and to have a quick peek
>> at it requires many clicks. Search option would help in this case.
>>
>> On Mon, Dec 11, 2017 at 7:51 PM, Godwin Shrimal  wrote:
>>
>>> Thanks for the response Shazni, This is really important specially for
>>> dynamic endpoints. Since searching functionality is not working with
>>> dynamic endpoint, think we need to find an endpoint start from letter "P"
>>> while we are having many no of endpoints in the system. We have to click
>>> next, next many times to find the exact endpoint. Extending the no of pages
>>> will not solve the exact problem here, but up to some level. I think
>>> Implementing search feature for dynamic endpoint is the best solution as
>>> discussed in [1].
>>>
>>> [1] [EI] Cant search dynamic endpoints
>>>
>>> Thanks
>>> Godwin
>>>
>>>
>>> On Tue, Dec 12, 2017 at 7:25 AM, Shazni Nazeer  wrote:
>>>
 I don't think this is possible with any configuration. If you want you
 will have to tweak all the jsp's related to sequences, templates etc. See
 [1]. I don't think it's a good option.

 [1] https://github.com/wso2/carbon-mediation/blob/master/compone
 nts/mediation-ui/org.wso2.carbon.sequences.ui/src/main/resou
 rces/web/sequences/list_sequences.jsp

 On Mon, Dec 11, 2017 at 6:34 AM, Godwin Shrimal 
 wrote:

> Hi Devs,
>
> Can we change the number of pages shows in Proxy services, sequence,
> endpoints etc?  By default it shows only 3 pages, next and last
>
>
> Thank
> Godwin
>
> --
> *Godwin Amila Shrimal*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
> *
> twitter: https://twitter.com/godwinamila
> 
>



 --
 Shazni Nazeer

 Mob : +94 37331
 LinkedIn : http://lk.linkedin.com/in/shazninazeer

 Blogs :

 https://medium.com/@mshazninazeer
 http://shazninazeer.blogspot.com

 

>>>
>>>
>>>
>>> --
>>> *Godwin Amila Shrimal*
>>> Associate Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94772264165*
>>> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
>>> *
>>> twitter: https://twitter.com/godwinamila
>>> 
>>>
>>
>>
>>
>> --
>> Shazni Nazeer
>>
>> Mob : +94 37331
>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>>
>> Blogs :
>>
>> https://medium.com/@mshazninazeer
>> http://shazninazeer.blogspot.com
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Blog: http://blog.napagoda.com
> Linkedin: https://www.linkedin.com/in/chandananapagoda/
>
>


-- 
Shazni Nazeer

Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer

Blogs :

https://medium.com/@mshazninazeer
http://shazninazeer.blogspot.com


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

Re: [Dev] [EI] Change number of pages

[Chandana Napagoda]

Hi,

I think this is a bug/ implementation limitation in the ESB/EI UIs. Because
other pages such as user management pages honour the 'ItemsPerPage' value
in the carbon.xml

Regards,
Chandana

Blog: http://blog.napagoda.com
Linkedin: https://www.linkedin.com/in/chandananapagoda/

On 12 December 2017 at 12:24, Shazni Nazeer  wrote:

> Yes Godwin. I too have felt the same. It is tough to look for the endpoint
> when there are many. Quickly navigating and to have a quick peek at it
> requires many clicks. Search option would help in this case.
>
> On Mon, Dec 11, 2017 at 7:51 PM, Godwin Shrimal  wrote:
>
>> Thanks for the response Shazni, This is really important specially for
>> dynamic endpoints. Since searching functionality is not working with
>> dynamic endpoint, think we need to find an endpoint start from letter "P"
>> while we are having many no of endpoints in the system. We have to click
>> next, next many times to find the exact endpoint. Extending the no of pages
>> will not solve the exact problem here, but up to some level. I think
>> Implementing search feature for dynamic endpoint is the best solution as
>> discussed in [1].
>>
>> [1] [EI] Cant search dynamic endpoints
>>
>> Thanks
>> Godwin
>>
>>
>> On Tue, Dec 12, 2017 at 7:25 AM, Shazni Nazeer  wrote:
>>
>>> I don't think this is possible with any configuration. If you want you
>>> will have to tweak all the jsp's related to sequences, templates etc. See
>>> [1]. I don't think it's a good option.
>>>
>>> [1] https://github.com/wso2/carbon-mediation/blob/master/compone
>>> nts/mediation-ui/org.wso2.carbon.sequences.ui/src/main/resou
>>> rces/web/sequences/list_sequences.jsp
>>>
>>> On Mon, Dec 11, 2017 at 6:34 AM, Godwin Shrimal  wrote:
>>>
 Hi Devs,

 Can we change the number of pages shows in Proxy services, sequence,
 endpoints etc?  By default it shows only 3 pages, next and last


 Thank
 Godwin

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

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

>>>
>>>
>>>
>>> --
>>> Shazni Nazeer
>>>
>>> Mob : +94 37331
>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>>>
>>> Blogs :
>>>
>>> https://medium.com/@mshazninazeer
>>> http://shazninazeer.blogspot.com
>>>
>>> 
>>>
>>
>>
>>
>> --
>> *Godwin Amila Shrimal*
>> Associate Technical Lead
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
>> *
>> twitter: https://twitter.com/godwinamila
>> 
>>
>
>
>
> --
> Shazni Nazeer
>
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>
> Blogs :
>
> https://medium.com/@mshazninazeer
> http://shazninazeer.blogspot.com
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Blog: http://blog.napagoda.com
Linkedin: https://www.linkedin.com/in/chandananapagoda/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] SourceHandler I/O error

[Senuwan Withana]

Thanks, I will check on it.

*Senuwan Withana*
Software Engineer - Support Team | WSO2

Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com



On Tue, Dec 12, 2017 at 8:14 PM, Dinusha Dissanayake 
wrote:

> Hi Senuwa,
>
> The reason for this is the certifiacte has not been approved from the
> browser. So I think this could be fixed when certificate is accepted from
> browser. Please check if logging to EI from a new tab and trust the cert
> from the browser would solve this issue
>
> Thanks,
> DinushaD.
>
> On Tue, Dec 12, 2017 at 5:33 PM, Dilusha Alphonso 
> wrote:
>
>> Hi Senuwan,
>>
>> This looks like certificate error.I think this exception is happening
>> when invoking API in EI. Could you tell how to use curl command when
>> invoking API?
>>
>> Thanks
>> Dilusha
>>
>> On Tue, Dec 12, 2017 at 4:36 PM, Senuwan Withana 
>> wrote:
>>
>>> Hi Team,
>>>
>>> I got below error in EI Console. I would like to know why this error is
>>> happened?
>>>
>>>
>>> [2017-12-12 16:32:11,766] [EI-Core] ERROR - SourceHandler I/O error:
>>> Received fatal alert: certificate_unknown
>>> javax.net.ssl.SSLException: Received fatal alert: certificate_unknown
>>> at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
>>> at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1666)
>>> at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1634)
>>> at sun.security.ssl.SSLEngineImpl.recvAlert(SSLEngineImpl.java:1800)
>>> at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1083)
>>> at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:907)
>>> at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
>>> at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
>>> at org.apache.http.nio.reactor.ssl.SSLIOSession.doUnwrap(SSLIOS
>>> ession.java:245)
>>> at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSL
>>> IOSession.java:280)
>>> at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady
>>> (SSLIOSession.java:410)
>>> at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputRea
>>> dy(AbstractIODispatch.java:119)
>>> at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(Base
>>> IOReactor.java:159)
>>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEv
>>> ent(AbstractIOReactor.java:338)
>>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEv
>>> ents(AbstractIOReactor.java:316)
>>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(A
>>> bstractIOReactor.java:277)
>>> at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseI
>>> OReactor.java:105)
>>> at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReacto
>>> r$Worker.run(AbstractMultiworkerIOReactor.java:586)
>>> at java.lang.Thread.run(Thread.java:748)
>>>
>>>
>>> Regards,
>>>
>>> *Senuwan Withana*
>>> Software Engineer - Support Team | WSO2
>>>
>>> Email : senu...@wso2.com
>>> Mobile: 94773212853
>>> Web: http://www.wso2.com
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>>
>> *Best Regards,Dilusha Alphonso*
>>
>> *Software Engineer - Support Team*
>>
>>
>> *WSO2*
>> *Mobile : *
>>
>> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Dinusha Dissanayake
> Software Engineer
> WSO2 Inc
> Mobile: +94712939439 <+94%2071%20293%209439>
> 
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] Error occurred while connecting to back end

[Senuwan Withana]

Thank Guys, I will look into it.

*Senuwan Withana*
Software Engineer - Support Team | WSO2

Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com



On Tue, Dec 12, 2017 at 7:23 PM, Godwin Shrimal  wrote:

> Hi Senuwan,
>
> Check the validity period of the certificate of the ESB. Maybe it's
> expired.
>
> Thanks
> Godwin
>
> On Tue, Dec 12, 2017 at 6:41 PM, Senuwan Withana  wrote:
>
>> Hi Abimaran,
>>
>> Well, I did not generate any certificate. What I did was, tried to create
>> an API using WSO2 API Manager, Publisher. When I was adding Production
>> Endpoint that mentioned error was popping up.
>>
>> Thanks.
>> *Senuwan Withana*
>> Software Engineer - Support Team | WSO2
>>
>> Email : senu...@wso2.com
>> Mobile: 94773212853
>> Web: http://www.wso2.com
>>
>>
>>
>> On Tue, Dec 12, 2017 at 5:06 PM, Abimaran Kugathasan 
>> wrote:
>>
>>> Hi Senuwan,
>>>
>>> By checking your exception, it says, your certificate is expired. You
>>> have to generate a new certificate.
>>>
>>> Caused by: java.security.cert.CertificateExpiredException: NotAfter:
>>> Mon Jun 19 14:43:07 IST 2017
>>>
>>> On Tue, Dec 12, 2017 at 4:41 PM, Senuwan Withana 
>>> wrote:
>>>
 Hi Team,

 I got below error when I'm trying to connect my ESB proxy into the API
 Manager.  Any suggestion to solve this error?


 [2017-12-12 16:38:56,137] ERROR - APIProviderHostObject Error occurred
 while connecting to backend : https://localhost:8243/service
 s/EmailSender, reason : sun.security.validator.ValidatorException:
 PKIX path validation failed: java.security.cert.CertPathValidatorException:
 timestamp check failed
 javax.net.ssl.SSLHandshakeException: 
 sun.security.validator.ValidatorException:
 PKIX path validation failed: java.security.cert.CertPathValidatorException:
 timestamp check failed
 at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
 at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
 at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
 at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
 at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHa
 ndshaker.java:1514)
 at sun.security.ssl.ClientHandshaker.processMessage(ClientHands
 haker.java:216)
 at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1026)
 at sun.security.ssl.Handshaker.process_record(Handshaker.java:961)
 at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
 at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSo
 cketImpl.java:1375)
 at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.
 java:1403)
 at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.
 java:1387)
 at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS
 ocketFactory.java:533)
 at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS
 ocketFactory.java:401)
 at org.apache.http.impl.conn.DefaultClientConnectionOperator.op
 enConnection(DefaultClientConnectionOperator.java:178)
 at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(M
 anagedClientConnectionImpl.java:304)
 at org.apache.http.impl.client.DefaultRequestDirector.tryConnec
 t(DefaultRequestDirector.java:610)
 at org.apache.http.impl.client.DefaultRequestDirector.execute(D
 efaultRequestDirector.java:445)
 at org.apache.http.impl.client.AbstractHttpClient.doExecute(Abs
 tractHttpClient.java:863)
 at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
 eableHttpClient.java:82)
 at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
 eableHttpClient.java:106)
 at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
 eableHttpClient.java:57)
 at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.sen
 dHttpHEADRequest(APIProviderHostObject.java:4781)
 at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.jsF
 unction_isURLValid(APIProviderHostObject.java:4173)
 at sun.reflect.GeneratedMethodAccessor117.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
 thodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
 at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386)
 at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime
 .java:52)
 at org.jaggeryjs.rhino.publisher.modules.api.c3._c_anonymous_10
 (/publisher/modules/api/add.jag:225)
 at org.jaggeryjs.rhino.publisher.modules.api.c3.call(/publisher
 /modules/api/add.jag)
 at org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRunti
 me.java:2430)
 at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.
 java:269)
 at 

Re: [Dev] [ESB] SourceHandler I/O error

[Dinusha Dissanayake]

Hi Senuwa,

The reason for this is the certifiacte has not been approved from the
browser. So I think this could be fixed when certificate is accepted from
browser. Please check if logging to EI from a new tab and trust the cert
from the browser would solve this issue

Thanks,
DinushaD.

On Tue, Dec 12, 2017 at 5:33 PM, Dilusha Alphonso  wrote:

> Hi Senuwan,
>
> This looks like certificate error.I think this exception is happening when
> invoking API in EI. Could you tell how to use curl command when invoking
> API?
>
> Thanks
> Dilusha
>
> On Tue, Dec 12, 2017 at 4:36 PM, Senuwan Withana  wrote:
>
>> Hi Team,
>>
>> I got below error in EI Console. I would like to know why this error is
>> happened?
>>
>>
>> [2017-12-12 16:32:11,766] [EI-Core] ERROR - SourceHandler I/O error:
>> Received fatal alert: certificate_unknown
>> javax.net.ssl.SSLException: Received fatal alert: certificate_unknown
>> at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
>> at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1666)
>> at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1634)
>> at sun.security.ssl.SSLEngineImpl.recvAlert(SSLEngineImpl.java:1800)
>> at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1083)
>> at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:907)
>> at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
>> at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
>> at org.apache.http.nio.reactor.ssl.SSLIOSession.doUnwrap(SSLIOS
>> ession.java:245)
>> at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSL
>> IOSession.java:280)
>> at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady
>> (SSLIOSession.java:410)
>> at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputRea
>> dy(AbstractIODispatch.java:119)
>> at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(Base
>> IOReactor.java:159)
>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEv
>> ent(AbstractIOReactor.java:338)
>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEv
>> ents(AbstractIOReactor.java:316)
>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(A
>> bstractIOReactor.java:277)
>> at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseI
>> OReactor.java:105)
>> at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReacto
>> r$Worker.run(AbstractMultiworkerIOReactor.java:586)
>> at java.lang.Thread.run(Thread.java:748)
>>
>>
>> Regards,
>>
>> *Senuwan Withana*
>> Software Engineer - Support Team | WSO2
>>
>> Email : senu...@wso2.com
>> Mobile: 94773212853
>> Web: http://www.wso2.com
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
>
> *Best Regards,Dilusha Alphonso*
>
> *Software Engineer - Support Team*
>
>
> *WSO2*
> *Mobile : *
>
> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dinusha Dissanayake
Software Engineer
WSO2 Inc
Mobile: +94712939439 <+94%2071%20293%209439>

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

Re: [Dev] [APIM] Error occurred while connecting to back end

[Godwin Shrimal]

Hi Senuwan,

Check the validity period of the certificate of the ESB. Maybe it's
expired.

Thanks
Godwin

On Tue, Dec 12, 2017 at 6:41 PM, Senuwan Withana  wrote:

> Hi Abimaran,
>
> Well, I did not generate any certificate. What I did was, tried to create
> an API using WSO2 API Manager, Publisher. When I was adding Production
> Endpoint that mentioned error was popping up.
>
> Thanks.
> *Senuwan Withana*
> Software Engineer - Support Team | WSO2
>
> Email : senu...@wso2.com
> Mobile: 94773212853
> Web: http://www.wso2.com
>
>
>
> On Tue, Dec 12, 2017 at 5:06 PM, Abimaran Kugathasan 
> wrote:
>
>> Hi Senuwan,
>>
>> By checking your exception, it says, your certificate is expired. You
>> have to generate a new certificate.
>>
>> Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon
>> Jun 19 14:43:07 IST 2017
>>
>> On Tue, Dec 12, 2017 at 4:41 PM, Senuwan Withana 
>> wrote:
>>
>>> Hi Team,
>>>
>>> I got below error when I'm trying to connect my ESB proxy into the API
>>> Manager.  Any suggestion to solve this error?
>>>
>>>
>>> [2017-12-12 16:38:56,137] ERROR - APIProviderHostObject Error occurred
>>> while connecting to backend : https://localhost:8243/service
>>> s/EmailSender, reason : sun.security.validator.ValidatorException: PKIX
>>> path validation failed: java.security.cert.CertPathValidatorException:
>>> timestamp check failed
>>> javax.net.ssl.SSLHandshakeException: 
>>> sun.security.validator.ValidatorException:
>>> PKIX path validation failed: java.security.cert.CertPathValidatorException:
>>> timestamp check failed
>>> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
>>> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
>>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
>>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
>>> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHa
>>> ndshaker.java:1514)
>>> at sun.security.ssl.ClientHandshaker.processMessage(ClientHands
>>> haker.java:216)
>>> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1026)
>>> at sun.security.ssl.Handshaker.process_record(Handshaker.java:961)
>>> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
>>> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSo
>>> cketImpl.java:1375)
>>> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.
>>> java:1403)
>>> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.
>>> java:1387)
>>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS
>>> ocketFactory.java:533)
>>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS
>>> ocketFactory.java:401)
>>> at org.apache.http.impl.conn.DefaultClientConnectionOperator.op
>>> enConnection(DefaultClientConnectionOperator.java:178)
>>> at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(M
>>> anagedClientConnectionImpl.java:304)
>>> at org.apache.http.impl.client.DefaultRequestDirector.tryConnec
>>> t(DefaultRequestDirector.java:610)
>>> at org.apache.http.impl.client.DefaultRequestDirector.execute(D
>>> efaultRequestDirector.java:445)
>>> at org.apache.http.impl.client.AbstractHttpClient.doExecute(Abs
>>> tractHttpClient.java:863)
>>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>>> eableHttpClient.java:82)
>>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>>> eableHttpClient.java:106)
>>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>>> eableHttpClient.java:57)
>>> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.sen
>>> dHttpHEADRequest(APIProviderHostObject.java:4781)
>>> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.jsF
>>> unction_isURLValid(APIProviderHostObject.java:4173)
>>> at sun.reflect.GeneratedMethodAccessor117.invoke(Unknown Source)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>>> thodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
>>> at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386)
>>> at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
>>> at org.jaggeryjs.rhino.publisher.modules.api.c3._c_anonymous_10
>>> (/publisher/modules/api/add.jag:225)
>>> at org.jaggeryjs.rhino.publisher.modules.api.c3.call(/publisher
>>> /modules/api/add.jag)
>>> at org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRunti
>>> me.java:2430)
>>> at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
>>> at org.mozilla.javascript.IdFunctionObject.call(IdFunctionObjec
>>> t.java:97)
>>> at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
>>> at org.jaggeryjs.rhino.publisher.modules.api.c0._c_anonymous_5(
>>> /publisher/modules/api/module.jag:18)
>>> at org.jaggeryjs.rhino.publisher.modules.api.c0.call(/publisher
>>> /modules/api/module.jag)
>>> at 

Re: [Dev] Expose the data as webservices

[Godwin Shrimal]

Did you test the connectivity of the data source? You can click Test
Connection button under data source.



Thanks
Godwin


On Tue, Dec 12, 2017 at 6:58 PM, Dilusha Alphonso  wrote:

> I didn't see any errors. Service is not working.
>
> Thanks
> Dilusha
>
> On Tue, Dec 12, 2017 at 4:59 PM, Chanika Geeganage 
> wrote:
>
>> What do you mean by 'unable to access data from database'? Do you see any
>> errors in the logs?
>>
>> On Tue, Dec 12, 2017 at 4:53 PM, Dilusha Alphonso 
>> wrote:
>>
>>> Hi All,
>>>
>>> I followed [1] this step of the link. My service is working fine. I am
>>> unable to access the data from the database. But when I followed that [2]
>>> this link, my service is not working. I could not connect to the data
>>> source.I have attached the screenshot also.
>>>
>>>
>>> [1].https://wso2.com/library/tutorials/2015/05/tutorial-host
>>> ing-restful-web-services-using-oauth-with-the-wso2-platform-0/
>>> [2]..https://wso2.com/library/articles/2015/02/how-to-write-
>>> a-web-application-backed-by-wso2-middleware-part-1/
>>>
>>> Thanks
>>> Dilusha
>>>
>>>
>>>
>>> On Fri, Dec 8, 2017 at 4:26 PM, Piriya Sivalingam 
>>> wrote:
>>>
 Hi Dilusha,

 Since it is not mentioned in the document that you attached, have you
 copied the MySQL connector jar to /repository/components/lib/
 directory. If not could you please do it.
 And I have tried exposing RDBMS as a dataservice using WSO2 DSS using
 the below documentation and it works fine.

 [1] https://wso2.com/library/tutorials/2015/05/tutorial-host
 ing-restful-web-services-using-oauth-with-the-wso2-platform-0/

 Regards,
 Piriya

 On Fri, Dec 8, 2017 at 11:47 AM, Samitha Chathuranga 
 wrote:

> Hi Dilusha,
>
> On Fri, Dec 8, 2017 at 10:03 AM, Dilusha Alphonso 
> wrote:
>
>> Hi All,
>>
>> According to my scenario, I have the database. I have to expose that
>> data as web services. For that, I am using WSO2 DSS ( Data Service 
>> Server)
>> and followed that step of this document [1].
>>
>
>
>> But I could not deploy service on the server.
>>
> What do you mean by that you couldn't? Any alert displayed? Or after
> which step you stuck?
>
>>
>>  Can anyone please help on this or suggest If I am doing wrong.
>>
>> [1].https://wso2.com/library/articles/2015/02/how-to-write-a
>> -web-application-backed-by-wso2-middleware-part-1/
>>
>>
>> Thanks
>> Dilusha
>>
>>
>>
>>
>> *Best Regards,Dilusha Alphonso*
>>
>> *Software Engineer - Support Team*
>>
>>
>> *WSO2*
>> *Mobile : *
>>
>> *+94766837098 <+94%2076%20683%207098>[image:
>> http://wso2.com/signature] *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Samitha Chathuranga
> Software Engineer, WSO2 Inc.
> lean.enterprise.middleware
> Mobile: +94715123761
>
> [image: http://wso2.com/signature] 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Regards,

 *Piriya Sivalingam*

 *Software Engineer - Support Team*

 *WSO2*
 *Mobile : +94 77 8462039 <+94%2077%20846%202039>*

 [image: http://wso2.com/signature] 


>>>
>>>
>>> --
>>>
>>>
>>> *Best Regards,Dilusha Alphonso*
>>>
>>> *Software Engineer - Support Team*
>>>
>>>
>>> *WSO2*
>>> *Mobile : *
>>>
>>> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
>>> *
>>>
>>
>>
>>
>> --
>> Best Regards..
>>
>> Chanika Geeganage
>> +94773522586 <+94%2077%20352%202586>
>> WSO2, Inc.; http://wso2.com
>>
>>
>
>
> --
>
>
> *Best Regards,Dilusha Alphonso*
>
> *Software Engineer - Support Team*
>
>
> *WSO2*
> *Mobile : *
>
> *+94766837098[image: http://wso2.com/signature]
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

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

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

Re: [Dev] generate the email (auto-generation )when storing the data in the database

[Irham Iqbal]

Hi Dilusha,

As far as I can remember we need to do some configurations in gmail
settings.
Can you try with the same synapse files with the same gmail account in this
path[1]. We used this for test mailto transport.

[1]
https://github.com/irham0019/product-esb/tree/master/modules/integration/tests-integration/tests-transport/src/test/resources/artifacts/ESB/mailTransport

Thanks,
Iqbal

On Tue, Dec 12, 2017 at 5:14 PM, Dilusha Alphonso  wrote:

> Hi,n
> I enabled this configuration in my Gmail. But I could not generate the
> mail. Anything else I missed in my configuration.
>
> Thanks
> Dilusha
>
>
>
> On Tue, Dec 12, 2017 at 4:43 PM, Vinod Kavinda  wrote:
>
>> Hi Dilusha,
>> This is an authentication failure. Did you authorized your Gmail account
>> to be accessed by the unsecured apps? You need to enable this in Gmail
>> settings. This may be the reason for your error.
>>
>> Regards,
>> Vinod
>>
>> On Tue, Dec 12, 2017 at 4:38 PM, Dilusha Alphonso 
>> wrote:
>>
>>> Hi All,
>>>
>>> I am trying to generate the email (auto-generation )when storing the
>>> data in the database. In my scenario, My backend service deploys on the DSS
>>> server. I am trying to post the data using api in ESB 5.0.0.
>>>
>>> For email generation, I followed the below steps.
>>>
>>> 1. uncommented  the transport sender in axis2.xml  in the ESB
>>>
>>>  
>>> smtp.gmail.com
>>> 587
>>> true
>>> true
>>> esbadmin
>>> *
>>> mym...@gmail.com
>>> 
>>>
>>> 2.configured the endpoint in the API in ESB 5.0.0.
>>> 
>>>  mailto:dilu...@wso2.com"/>
>>>   
>>>
>>>
>>> but I noticed below exception.
>>>
>>> javax.mail.AuthenticationFailedException
>>> at javax.mail.Service.connect(Service.java:306)
>>> at javax.mail.Service.connect(Service.java:156)
>>> at javax.mail.Service.connect(Service.java:105)
>>> at javax.mail.Transport.send0(Transport.java:168)
>>> at javax.mail.Transport.send(Transport.java:98)
>>> at org.apache.axis2.transport.mail.MailTransportSender.sendMail
>>> (MailTransportSender.java:501)
>>> at org.apache.axis2.transport.mail.MailTransportSender.sendMess
>>> age(MailTransportSender.java:182)
>>> at org.apache.axis2.transport.base.AbstractTransportSender.invo
>>> ke(AbstractTransportSender.java:112)
>>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>>> at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOp
>>> erationClient.send(DynamicAxisOperation.java:185)
>>> at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOp
>>> erationClient.executeImpl(DynamicAxisOperation.java:167)
>>> at org.apache.axis2.client.OperationClient.execute(OperationCli
>>> ent.java:149)
>>> at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Ax
>>> is2FlexibleMEPClient.java:581)
>>> at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:78)
>>> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(A
>>> xis2SynapseEnvironment.java:548)
>>> at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractE
>>> ndpoint.java:382)
>>> at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEnd
>>> point.java:65)
>>> at org.apache.synapse.endpoints.RecipientListEndpoint.sendToEnd
>>> pointList(RecipientListEndpoint.java:185)
>>> at org.apache.synapse.endpoints.RecipientListEndpoint.sendMessa
>>> ge(RecipientListEndpoint.java:137)
>>> at org.apache.synapse.endpoints.RecipientListEndpoint.send(Reci
>>> pientListEndpoint.java:116)
>>> at org.apache.synapse.mediators.builtin.CallMediator.handleNonB
>>> lockingCall(CallMediator.java:221)
>>> at org.apache.synapse.mediators.builtin.CallMediator.mediate(Ca
>>> llMediator.java:99)
>>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>>> stractListMediator.java:97)
>>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>>> stractListMediator.java:59)
>>> at org.apache.synapse.mediators.base.SequenceMediator.mediate(S
>>> equenceMediator.java:158)
>>> at org.apache.synapse.rest.Resource.process(Resource.java:343)
>>> at org.apache.synapse.rest.API.process(API.java:399)
>>> at org.apache.synapse.rest.RESTRequestHandler.apiProcess(RESTRe
>>> questHandler.java:123)
>>> at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RES
>>> TRequestHandler.java:101)
>>> at org.apache.synapse.rest.RESTRequestHandler.process(RESTReque
>>> stHandler.java:69)
>>> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.inject
>>> Message(Axis2SynapseEnvironment.java:304)
>>> at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive
>>> (SynapseMessageReceiver.java:75)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>> at org.apache.synapse.transport.passthru.ServerWorker.processNo
>>> nEntityEnclosingRESTHandler(ServerWorker.java:325)
>>> at org.apache.synapse.transport.passthru.ServerWorker.processEn
>>> 

Re: [Dev] [ESB] SourceHandler I/O error

[Dilusha Alphonso]

Hi Senuwan,

This looks like certificate error.I think this exception is happening when
invoking API in EI. Could you tell how to use curl command when invoking
API?

Thanks
Dilusha

On Tue, Dec 12, 2017 at 4:36 PM, Senuwan Withana  wrote:

> Hi Team,
>
> I got below error in EI Console. I would like to know why this error is
> happened?
>
>
> [2017-12-12 16:32:11,766] [EI-Core] ERROR - SourceHandler I/O error:
> Received fatal alert: certificate_unknown
> javax.net.ssl.SSLException: Received fatal alert: certificate_unknown
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
> at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1666)
> at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1634)
> at sun.security.ssl.SSLEngineImpl.recvAlert(SSLEngineImpl.java:1800)
> at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1083)
> at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:907)
> at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
> at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
> at org.apache.http.nio.reactor.ssl.SSLIOSession.doUnwrap(
> SSLIOSession.java:245)
> at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(
> SSLIOSession.java:280)
> at org.apache.http.nio.reactor.ssl.SSLIOSession.
> isAppInputReady(SSLIOSession.java:410)
> at org.apache.http.impl.nio.reactor.AbstractIODispatch.
> inputReady(AbstractIODispatch.java:119)
> at org.apache.http.impl.nio.reactor.BaseIOReactor.
> readable(BaseIOReactor.java:159)
> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(
> AbstractIOReactor.java:338)
> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(
> AbstractIOReactor.java:316)
> at org.apache.http.impl.nio.reactor.AbstractIOReactor.
> execute(AbstractIOReactor.java:277)
> at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(
> BaseIOReactor.java:105)
> at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$
> Worker.run(AbstractMultiworkerIOReactor.java:586)
> at java.lang.Thread.run(Thread.java:748)
>
>
> Regards,
>
> *Senuwan Withana*
> Software Engineer - Support Team | WSO2
>
> Email : senu...@wso2.com
> Mobile: 94773212853
> Web: http://www.wso2.com
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 


*Best Regards,Dilusha Alphonso*

*Software Engineer - Support Team*


*WSO2*
*Mobile : *

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

Re: [Dev] Expose the data as webservices

[Dilusha Alphonso]

I didn't see any errors. Service is not working.

Thanks
Dilusha

On Tue, Dec 12, 2017 at 4:59 PM, Chanika Geeganage  wrote:

> What do you mean by 'unable to access data from database'? Do you see any
> errors in the logs?
>
> On Tue, Dec 12, 2017 at 4:53 PM, Dilusha Alphonso 
> wrote:
>
>> Hi All,
>>
>> I followed [1] this step of the link. My service is working fine. I am
>> unable to access the data from the database. But when I followed that [2]
>> this link, my service is not working. I could not connect to the data
>> source.I have attached the screenshot also.
>>
>>
>> [1].https://wso2.com/library/tutorials/2015/05/tutorial-host
>> ing-restful-web-services-using-oauth-with-the-wso2-platform-0/
>> [2]..https://wso2.com/library/articles/2015/02/how-to-write-
>> a-web-application-backed-by-wso2-middleware-part-1/
>>
>> Thanks
>> Dilusha
>>
>>
>>
>> On Fri, Dec 8, 2017 at 4:26 PM, Piriya Sivalingam 
>> wrote:
>>
>>> Hi Dilusha,
>>>
>>> Since it is not mentioned in the document that you attached, have you
>>> copied the MySQL connector jar to /repository/components/lib/
>>> directory. If not could you please do it.
>>> And I have tried exposing RDBMS as a dataservice using WSO2 DSS using
>>> the below documentation and it works fine.
>>>
>>> [1] https://wso2.com/library/tutorials/2015/05/tutorial-host
>>> ing-restful-web-services-using-oauth-with-the-wso2-platform-0/
>>>
>>> Regards,
>>> Piriya
>>>
>>> On Fri, Dec 8, 2017 at 11:47 AM, Samitha Chathuranga 
>>> wrote:
>>>
 Hi Dilusha,

 On Fri, Dec 8, 2017 at 10:03 AM, Dilusha Alphonso 
 wrote:

> Hi All,
>
> According to my scenario, I have the database. I have to expose that
> data as web services. For that, I am using WSO2 DSS ( Data Service Server)
> and followed that step of this document [1].
>


> But I could not deploy service on the server.
>
 What do you mean by that you couldn't? Any alert displayed? Or after
 which step you stuck?

>
>  Can anyone please help on this or suggest If I am doing wrong.
>
> [1].https://wso2.com/library/articles/2015/02/how-to-write-a
> -web-application-backed-by-wso2-middleware-part-1/
>
>
> Thanks
> Dilusha
>
>
>
>
> *Best Regards,Dilusha Alphonso*
>
> *Software Engineer - Support Team*
>
>
> *WSO2*
> *Mobile : *
>
> *+94766837098 <+94%2076%20683%207098>[image:
> http://wso2.com/signature] *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

 [image: http://wso2.com/signature] 

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


>>>
>>>
>>> --
>>> Regards,
>>>
>>> *Piriya Sivalingam*
>>>
>>> *Software Engineer - Support Team*
>>>
>>> *WSO2*
>>> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>>>
>>> [image: http://wso2.com/signature] 
>>>
>>>
>>
>>
>> --
>>
>>
>> *Best Regards,Dilusha Alphonso*
>>
>> *Software Engineer - Support Team*
>>
>>
>> *WSO2*
>> *Mobile : *
>>
>> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
>> *
>>
>
>
>
> --
> Best Regards..
>
> Chanika Geeganage
> +94773522586 <+94%2077%20352%202586>
> WSO2, Inc.; http://wso2.com
>
>


-- 


*Best Regards,Dilusha Alphonso*

*Software Engineer - Support Team*


*WSO2*
*Mobile : *

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

Re: [Dev] generate the email (auto-generation )when storing the data in the database

[Dilusha Alphonso]

Hi,n
I enabled this configuration in my Gmail. But I could not generate the
mail. Anything else I missed in my configuration.

Thanks
Dilusha



On Tue, Dec 12, 2017 at 4:43 PM, Vinod Kavinda  wrote:

> Hi Dilusha,
> This is an authentication failure. Did you authorized your Gmail account
> to be accessed by the unsecured apps? You need to enable this in Gmail
> settings. This may be the reason for your error.
>
> Regards,
> Vinod
>
> On Tue, Dec 12, 2017 at 4:38 PM, Dilusha Alphonso 
> wrote:
>
>> Hi All,
>>
>> I am trying to generate the email (auto-generation )when storing the
>> data in the database. In my scenario, My backend service deploys on the DSS
>> server. I am trying to post the data using api in ESB 5.0.0.
>>
>> For email generation, I followed the below steps.
>>
>> 1. uncommented  the transport sender in axis2.xml  in the ESB
>>
>>  
>> smtp.gmail.com
>> 587
>> true
>> true
>> esbadmin
>> *
>> mym...@gmail.com
>> 
>>
>> 2.configured the endpoint in the API in ESB 5.0.0.
>> 
>>  mailto:dilu...@wso2.com"/>
>>   
>>
>>
>> but I noticed below exception.
>>
>> javax.mail.AuthenticationFailedException
>> at javax.mail.Service.connect(Service.java:306)
>> at javax.mail.Service.connect(Service.java:156)
>> at javax.mail.Service.connect(Service.java:105)
>> at javax.mail.Transport.send0(Transport.java:168)
>> at javax.mail.Transport.send(Transport.java:98)
>> at org.apache.axis2.transport.mail.MailTransportSender.sendMail
>> (MailTransportSender.java:501)
>> at org.apache.axis2.transport.mail.MailTransportSender.sendMess
>> age(MailTransportSender.java:182)
>> at org.apache.axis2.transport.base.AbstractTransportSender.invo
>> ke(AbstractTransportSender.java:112)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOp
>> erationClient.send(DynamicAxisOperation.java:185)
>> at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOp
>> erationClient.executeImpl(DynamicAxisOperation.java:167)
>> at org.apache.axis2.client.OperationClient.execute(OperationCli
>> ent.java:149)
>> at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Ax
>> is2FlexibleMEPClient.java:581)
>> at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:78)
>> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(A
>> xis2SynapseEnvironment.java:548)
>> at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractE
>> ndpoint.java:382)
>> at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEnd
>> point.java:65)
>> at org.apache.synapse.endpoints.RecipientListEndpoint.sendToEnd
>> pointList(RecipientListEndpoint.java:185)
>> at org.apache.synapse.endpoints.RecipientListEndpoint.sendMessa
>> ge(RecipientListEndpoint.java:137)
>> at org.apache.synapse.endpoints.RecipientListEndpoint.send(Reci
>> pientListEndpoint.java:116)
>> at org.apache.synapse.mediators.builtin.CallMediator.handleNonB
>> lockingCall(CallMediator.java:221)
>> at org.apache.synapse.mediators.builtin.CallMediator.mediate(Ca
>> llMediator.java:99)
>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>> stractListMediator.java:97)
>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>> stractListMediator.java:59)
>> at org.apache.synapse.mediators.base.SequenceMediator.mediate(S
>> equenceMediator.java:158)
>> at org.apache.synapse.rest.Resource.process(Resource.java:343)
>> at org.apache.synapse.rest.API.process(API.java:399)
>> at org.apache.synapse.rest.RESTRequestHandler.apiProcess(RESTRe
>> questHandler.java:123)
>> at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RES
>> TRequestHandler.java:101)
>> at org.apache.synapse.rest.RESTRequestHandler.process(RESTReque
>> stHandler.java:69)
>> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.inject
>> Message(Axis2SynapseEnvironment.java:304)
>> at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive
>> (SynapseMessageReceiver.java:75)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at org.apache.synapse.transport.passthru.ServerWorker.processNo
>> nEntityEnclosingRESTHandler(ServerWorker.java:325)
>> at org.apache.synapse.transport.passthru.ServerWorker.processEn
>> tityEnclosingRequest(ServerWorker.java:371)
>> at org.apache.synapse.transport.passthru.ServerWorker.run(Serve
>> rWorker.java:151)
>> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.
>> run(NativeWorkerPool.java:172)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:748)
>> [2017-12-12 15:17:22,297] ERROR - MailTransportSender Error generating
>> mail message
>> org.apache.axis2.AxisFault: Error creating mail message or sending 

Re: [Dev] [APIM] Error occurred while connecting to back end

[Senuwan Withana]

Hi Abimaran,

Well, I did not generate any certificate. What I did was, tried to create
an API using WSO2 API Manager, Publisher. When I was adding Production
Endpoint that mentioned error was popping up.

Thanks.
*Senuwan Withana*
Software Engineer - Support Team | WSO2

Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com



On Tue, Dec 12, 2017 at 5:06 PM, Abimaran Kugathasan 
wrote:

> Hi Senuwan,
>
> By checking your exception, it says, your certificate is expired. You have
> to generate a new certificate.
>
> Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon
> Jun 19 14:43:07 IST 2017
>
> On Tue, Dec 12, 2017 at 4:41 PM, Senuwan Withana  wrote:
>
>> Hi Team,
>>
>> I got below error when I'm trying to connect my ESB proxy into the API
>> Manager.  Any suggestion to solve this error?
>>
>>
>> [2017-12-12 16:38:56,137] ERROR - APIProviderHostObject Error occurred
>> while connecting to backend : https://localhost:8243/services/EmailSender,
>> reason : sun.security.validator.ValidatorException: PKIX path validation
>> failed: java.security.cert.CertPathValidatorException: timestamp check
>> failed
>> javax.net.ssl.SSLHandshakeException: 
>> sun.security.validator.ValidatorException:
>> PKIX path validation failed: java.security.cert.CertPathValidatorException:
>> timestamp check failed
>> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
>> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
>> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHa
>> ndshaker.java:1514)
>> at sun.security.ssl.ClientHandshaker.processMessage(ClientHands
>> haker.java:216)
>> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1026)
>> at sun.security.ssl.Handshaker.process_record(Handshaker.java:961)
>> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
>> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSo
>> cketImpl.java:1375)
>> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
>> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS
>> ocketFactory.java:533)
>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS
>> ocketFactory.java:401)
>> at org.apache.http.impl.conn.DefaultClientConnectionOperator.
>> openConnection(DefaultClientConnectionOperator.java:178)
>> at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(M
>> anagedClientConnectionImpl.java:304)
>> at org.apache.http.impl.client.DefaultRequestDirector.tryConnec
>> t(DefaultRequestDirector.java:610)
>> at org.apache.http.impl.client.DefaultRequestDirector.execute(D
>> efaultRequestDirector.java:445)
>> at org.apache.http.impl.client.AbstractHttpClient.doExecute(Abs
>> tractHttpClient.java:863)
>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>> eableHttpClient.java:82)
>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>> eableHttpClient.java:106)
>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>> eableHttpClient.java:57)
>> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.sen
>> dHttpHEADRequest(APIProviderHostObject.java:4781)
>> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.jsF
>> unction_isURLValid(APIProviderHostObject.java:4173)
>> at sun.reflect.GeneratedMethodAccessor117.invoke(Unknown Source)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
>> at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386)
>> at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
>> at org.jaggeryjs.rhino.publisher.modules.api.c3._c_anonymous_10
>> (/publisher/modules/api/add.jag:225)
>> at org.jaggeryjs.rhino.publisher.modules.api.c3.call(/publisher
>> /modules/api/add.jag)
>> at org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRunti
>> me.java:2430)
>> at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
>> at org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97)
>> at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
>> at org.jaggeryjs.rhino.publisher.modules.api.c0._c_anonymous_5(
>> /publisher/modules/api/module.jag:18)
>> at org.jaggeryjs.rhino.publisher.modules.api.c0.call(/publisher
>> /modules/api/module.jag)
>> at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
>> at org.jaggeryjs.rhino.publisher.site.blocks.item_add.ajax.c0._
>> c_anonymous_2(/publisher/site/blocks/item-add/ajax/add.jag:233)
>> at org.jaggeryjs.rhino.publisher.site.blocks.item_add.ajax.c0.c
>> 

Re: [Dev] [APIM] Error occurred while connecting to back end

[Abimaran Kugathasan]

Hi Senuwan,

By checking your exception, it says, your certificate is expired. You have
to generate a new certificate.

Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon
Jun 19 14:43:07 IST 2017

On Tue, Dec 12, 2017 at 4:41 PM, Senuwan Withana  wrote:

> Hi Team,
>
> I got below error when I'm trying to connect my ESB proxy into the API
> Manager.  Any suggestion to solve this error?
>
>
> [2017-12-12 16:38:56,137] ERROR - APIProviderHostObject Error occurred
> while connecting to backend : https://localhost:8243/services/EmailSender,
> reason : sun.security.validator.ValidatorException: PKIX path validation
> failed: java.security.cert.CertPathValidatorException: timestamp check
> failed
> javax.net.ssl.SSLHandshakeException: 
> sun.security.validator.ValidatorException:
> PKIX path validation failed: java.security.cert.CertPathValidatorException:
> timestamp check failed
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
> at sun.security.ssl.ClientHandshaker.serverCertificate(
> ClientHandshaker.java:1514)
> at sun.security.ssl.ClientHandshaker.processMessage(
> ClientHandshaker.java:216)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1026)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:961)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(
> SSLSocketImpl.java:1375)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(
> SSLSocketFactory.java:533)
> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(
> SSLSocketFactory.java:401)
> at org.apache.http.impl.conn.DefaultClientConnectionOperato
> r.openConnection(DefaultClientConnectionOperator.java:178)
> at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(
> ManagedClientConnectionImpl.java:304)
> at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(
> DefaultRequestDirector.java:610)
> at org.apache.http.impl.client.DefaultRequestDirector.execute(
> DefaultRequestDirector.java:445)
> at org.apache.http.impl.client.AbstractHttpClient.doExecute(
> AbstractHttpClient.java:863)
> at org.apache.http.impl.client.CloseableHttpClient.execute(
> CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(
> CloseableHttpClient.java:106)
> at org.apache.http.impl.client.CloseableHttpClient.execute(
> CloseableHttpClient.java:57)
> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.
> sendHttpHEADRequest(APIProviderHostObject.java:4781)
> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.
> jsFunction_isURLValid(APIProviderHostObject.java:4173)
> at sun.reflect.GeneratedMethodAccessor117.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
> at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386)
> at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
> at org.jaggeryjs.rhino.publisher.modules.api.c3._c_anonymous_
> 10(/publisher/modules/api/add.jag:225)
> at org.jaggeryjs.rhino.publisher.modules.api.c3.call(/
> publisher/modules/api/add.jag)
> at org.mozilla.javascript.ScriptRuntime.applyOrCall(
> ScriptRuntime.java:2430)
> at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
> at org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97)
> at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
> at org.jaggeryjs.rhino.publisher.modules.api.c0._c_anonymous_5(
> /publisher/modules/api/module.jag:18)
> at org.jaggeryjs.rhino.publisher.modules.api.c0.call(/
> publisher/modules/api/module.jag)
> at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
> at org.jaggeryjs.rhino.publisher.site.blocks.item_add.ajax.c0._
> c_anonymous_2(/publisher/site/blocks/item-add/ajax/add.jag:233)
> at org.jaggeryjs.rhino.publisher.site.blocks.item_add.ajax.c0.
> call(/publisher/site/blocks/item-add/ajax/add.jag)
> at org.mozilla.javascript.optimizer.OptRuntime.call0(OptRuntime.java:23)
> at org.jaggeryjs.rhino.publisher.site.blocks.item_add.ajax.c0._
> c_script_0(/publisher/site/blocks/item-add/ajax/add.jag:9)
> at org.jaggeryjs.rhino.publisher.site.blocks.item_add.ajax.c0.
> call(/publisher/site/blocks/item-add/ajax/add.jag)
> at org.mozilla.javascript.ContextFactory.doTopCall(
> ContextFactory.java:394)
> at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)
> at 

Re: [Dev] Giving proxy service as API End point causes an error

[Firzhan Naqash]

Hi Buddhima,

Since timeout has happened, which means the server/machine couldn't resolve
the hostname. Can you change your hostname to localhost
from buddhimala-ThinkPad-X1-Carbon-5th, and try the scenario again?



Regards,
Firzhan


email: firz...@wso2.com
mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
blog: http://firzhanblogger.blogspot.com/
  *
*twitter: https://twitter.com/firzhan007  |
linked-in: **https://www.linkedin.com/in/firzhan
*

On Tue, Dec 12, 2017 at 4:44 PM, Buddhimala Ranasinghe 
wrote:

> Hi All,
>
> I have a deployement where I have an API in APIM and a proxy service in
> EI. I'm creating an API to have this proxy service as API EP. But when I
> tried to give the url of the proxy service that I have created, I'm getting
> the following error.
>
> [2017-12-12 16:36:57,951] ERROR - APIProviderHostObject Error occurred
> while connecting to backend : http://buddhimala-ThinkPad-X1-
> Carbon-5th:8280/services/ViewOrderDetailsproxy, reason : Read timed out
> java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
> at java.net.SocketInputStream.read(SocketInputStream.java:171)
> at java.net.SocketInputStream.read(SocketInputStream.java:141)
> at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(
> AbstractSessionInputBuffer.java:160)
> at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(
> SocketInputBuffer.java:84)
> at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(
> AbstractSessionInputBuffer.java:273)
> at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(
> DefaultHttpResponseParser.java:140)
> at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(
> DefaultHttpResponseParser.java:57)
> at org.apache.http.impl.io.AbstractMessageParser.parse(
> AbstractMessageParser.java:260)
> at org.apache.http.impl.AbstractHttpClientConnection.
> receiveResponseHeader(AbstractHttpClientConnection.java:283)
> at org.apache.http.impl.conn.DefaultClientConnection.
> receiveResponseHeader(DefaultClientConnection.java:251)
> at org.apache.http.impl.conn.ManagedClientConnectionImpl.
> receiveResponseHeader(ManagedClientConnectionImpl.java:197)
> at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(
> HttpRequestExecutor.java:271)
> at org.apache.http.protocol.HttpRequestExecutor.execute(
> HttpRequestExecutor.java:123)
> at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(
> DefaultRequestDirector.java:682)
> at org.apache.http.impl.client.DefaultRequestDirector.execute(
> DefaultRequestDirector.java:486)
> at org.apache.http.impl.client.AbstractHttpClient.doExecute(
> AbstractHttpClient.java:863)
> at org.apache.http.impl.client.CloseableHttpClient.execute(
> CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(
> CloseableHttpClient.java:106)
> at org.apache.http.impl.client.CloseableHttpClient.execute(
> CloseableHttpClient.java:57)
> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.
> sendHttpHEADRequest(APIProviderHostObject.java:4781)
> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.
> jsFunction_isURLValid(APIProviderHostObject.java:4178)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
> at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386)
> at org.mozilla.javascript.optimizer.OptRuntime.callN(
> OptRuntime.java:52)
> at org.jaggeryjs.rhino.publisher.modules.api.c3._c_anonymous_
> 10(/publisher/modules/api/add.jag:225)
> at org.jaggeryjs.rhino.publisher.modules.api.c3.call(/
> publisher/modules/api/add.jag)
> at org.mozilla.javascript.ScriptRuntime.applyOrCall(
> ScriptRuntime.java:2430)
> at org.mozilla.javascript.BaseFunction.execIdCall(
> BaseFunction.java:269)
> at org.mozilla.javascript.IdFunctionObject.call(
> IdFunctionObject.java:97)
> at org.mozilla.javascript.optimizer.OptRuntime.call2(
> OptRuntime.java:42)
> at org.jaggeryjs.rhino.publisher.modules.api.c0._c_anonymous_5(
> /publisher/modules/api/module.jag:18)
> at org.jaggeryjs.rhino.publisher.modules.api.c0.call(/
> publisher/modules/api/module.jag)
> at org.mozilla.javascript.optimizer.OptRuntime.callN(
> OptRuntime.java:52)
> at org.jaggeryjs.rhino.publisher.site.blocks.item_add.ajax.c0._
> 

Re: [Dev] Expose the data as webservices

[Chanika Geeganage]

What do you mean by 'unable to access data from database'? Do you see any
errors in the logs?

On Tue, Dec 12, 2017 at 4:53 PM, Dilusha Alphonso  wrote:

> Hi All,
>
> I followed [1] this step of the link. My service is working fine. I am
> unable to access the data from the database. But when I followed that [2]
> this link, my service is not working. I could not connect to the data
> source.I have attached the screenshot also.
>
>
> [1].https://wso2.com/library/tutorials/2015/05/tutorial-host
> ing-restful-web-services-using-oauth-with-the-wso2-platform-0/
> [2]..https://wso2.com/library/articles/2015/02/how-to-write-
> a-web-application-backed-by-wso2-middleware-part-1/
>
> Thanks
> Dilusha
>
>
>
> On Fri, Dec 8, 2017 at 4:26 PM, Piriya Sivalingam  wrote:
>
>> Hi Dilusha,
>>
>> Since it is not mentioned in the document that you attached, have you
>> copied the MySQL connector jar to /repository/components/lib/
>> directory. If not could you please do it.
>> And I have tried exposing RDBMS as a dataservice using WSO2 DSS using the
>> below documentation and it works fine.
>>
>> [1] https://wso2.com/library/tutorials/2015/05/tutorial-host
>> ing-restful-web-services-using-oauth-with-the-wso2-platform-0/
>>
>> Regards,
>> Piriya
>>
>> On Fri, Dec 8, 2017 at 11:47 AM, Samitha Chathuranga 
>> wrote:
>>
>>> Hi Dilusha,
>>>
>>> On Fri, Dec 8, 2017 at 10:03 AM, Dilusha Alphonso 
>>> wrote:
>>>
 Hi All,

 According to my scenario, I have the database. I have to expose that
 data as web services. For that, I am using WSO2 DSS ( Data Service Server)
 and followed that step of this document [1].

>>>
>>>
 But I could not deploy service on the server.

>>> What do you mean by that you couldn't? Any alert displayed? Or after
>>> which step you stuck?
>>>

  Can anyone please help on this or suggest If I am doing wrong.

 [1].https://wso2.com/library/articles/2015/02/how-to-write-a
 -web-application-backed-by-wso2-middleware-part-1/


 Thanks
 Dilusha




 *Best Regards,Dilusha Alphonso*

 *Software Engineer - Support Team*


 *WSO2*
 *Mobile : *

 *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
 *

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


>>>
>>>
>>> --
>>> Samitha Chathuranga
>>> Software Engineer, WSO2 Inc.
>>> lean.enterprise.middleware
>>> Mobile: +94715123761
>>>
>>> [image: http://wso2.com/signature] 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> *Piriya Sivalingam*
>>
>> *Software Engineer - Support Team*
>>
>> *WSO2*
>> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>>
>> [image: http://wso2.com/signature] 
>>
>>
>
>
> --
>
>
> *Best Regards,Dilusha Alphonso*
>
> *Software Engineer - Support Team*
>
>
> *WSO2*
> *Mobile : *
>
> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
> *
>



-- 
Best Regards..

Chanika Geeganage
+94773522586
WSO2, Inc.; http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] generate the email (auto-generation )when storing the data in the database

[Vinod Kavinda]

Hi Dilusha,
This is an authentication failure. Did you authorized your Gmail account to
be accessed by the unsecured apps? You need to enable this in Gmail
settings. This may be the reason for your error.

Regards,
Vinod

On Tue, Dec 12, 2017 at 4:38 PM, Dilusha Alphonso  wrote:

> Hi All,
>
> I am trying to generate the email (auto-generation )when storing the data
> in the database. In my scenario, My backend service deploys on the DSS
> server. I am trying to post the data using api in ESB 5.0.0.
>
> For email generation, I followed the below steps.
>
> 1. uncommented  the transport sender in axis2.xml  in the ESB
>
>  
> smtp.gmail.com
> 587
> true
> true
> esbadmin
> *
> mym...@gmail.com
> 
>
> 2.configured the endpoint in the API in ESB 5.0.0.
> 
>  mailto:dilu...@wso2.com"/>
>   
>
>
> but I noticed below exception.
>
> javax.mail.AuthenticationFailedException
> at javax.mail.Service.connect(Service.java:306)
> at javax.mail.Service.connect(Service.java:156)
> at javax.mail.Service.connect(Service.java:105)
> at javax.mail.Transport.send0(Transport.java:168)
> at javax.mail.Transport.send(Transport.java:98)
> at org.apache.axis2.transport.mail.MailTransportSender.
> sendMail(MailTransportSender.java:501)
> at org.apache.axis2.transport.mail.MailTransportSender.sendMessage(
> MailTransportSender.java:182)
> at org.apache.axis2.transport.base.AbstractTransportSender.invoke(
> AbstractTransportSender.java:112)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at org.apache.synapse.core.axis2.DynamicAxisOperation$
> DynamicOperationClient.send(DynamicAxisOperation.java:185)
> at org.apache.synapse.core.axis2.DynamicAxisOperation$
> DynamicOperationClient.executeImpl(DynamicAxisOperation.java:167)
> at org.apache.axis2.client.OperationClient.execute(
> OperationClient.java:149)
> at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(
> Axis2FlexibleMEPClient.java:581)
> at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:78)
> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(
> Axis2SynapseEnvironment.java:548)
> at org.apache.synapse.endpoints.AbstractEndpoint.send(
> AbstractEndpoint.java:382)
> at org.apache.synapse.endpoints.AddressEndpoint.send(
> AddressEndpoint.java:65)
> at org.apache.synapse.endpoints.RecipientListEndpoint.sendToEndpointList(
> RecipientListEndpoint.java:185)
> at org.apache.synapse.endpoints.RecipientListEndpoint.sendMessage(
> RecipientListEndpoint.java:137)
> at org.apache.synapse.endpoints.RecipientListEndpoint.send(
> RecipientListEndpoint.java:116)
> at org.apache.synapse.mediators.builtin.CallMediator.
> handleNonBlockingCall(CallMediator.java:221)
> at org.apache.synapse.mediators.builtin.CallMediator.mediate(
> CallMediator.java:99)
> at org.apache.synapse.mediators.AbstractListMediator.mediate(
> AbstractListMediator.java:97)
> at org.apache.synapse.mediators.AbstractListMediator.mediate(
> AbstractListMediator.java:59)
> at org.apache.synapse.mediators.base.SequenceMediator.mediate(
> SequenceMediator.java:158)
> at org.apache.synapse.rest.Resource.process(Resource.java:343)
> at org.apache.synapse.rest.API.process(API.java:399)
> at org.apache.synapse.rest.RESTRequestHandler.apiProcess(
> RESTRequestHandler.java:123)
> at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(
> RESTRequestHandler.java:101)
> at org.apache.synapse.rest.RESTRequestHandler.process(
> RESTRequestHandler.java:69)
> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(
> Axis2SynapseEnvironment.java:304)
> at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(
> SynapseMessageReceiver.java:75)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at org.apache.synapse.transport.passthru.ServerWorker.
> processNonEntityEnclosingRESTHandler(ServerWorker.java:325)
> at org.apache.synapse.transport.passthru.ServerWorker.
> processEntityEnclosingRequest(ServerWorker.java:371)
> at org.apache.synapse.transport.passthru.ServerWorker.run(
> ServerWorker.java:151)
> at org.apache.axis2.transport.base.threads.NativeWorkerPool$
> 1.run(NativeWorkerPool.java:172)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> [2017-12-12 15:17:22,297] ERROR - MailTransportSender Error generating
> mail message
> org.apache.axis2.AxisFault: Error creating mail message or sending it to
> the configured server
> at org.apache.axis2.transport.base.AbstractTransportSender.
> handleException(AbstractTransportSender.java:226)
> at org.apache.axis2.transport.mail.MailTransportSender.
> sendMail(MailTransportSender.java:512)
> at org.apache.axis2.transport.mail.MailTransportSender.sendMessage(
> 

[Dev] [APIM] Error occurred while connecting to back end

[Senuwan Withana]

Hi Team,

I got below error when I'm trying to connect my ESB proxy into the API
Manager.  Any suggestion to solve this error?


[2017-12-12 16:38:56,137] ERROR - APIProviderHostObject Error occurred
while connecting to backend : https://localhost:8243/services/EmailSender,
reason : sun.security.validator.ValidatorException: PKIX path validation
failed: java.security.cert.CertPathValidatorException: timestamp check
failed
javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path validation failed:
java.security.cert.CertPathValidatorException: timestamp check failed
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
at
sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1514)
at
sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1026)
at sun.security.ssl.Handshaker.process_record(Handshaker.java:961)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
at
sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
at
org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:533)
at
org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:401)
at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:178)
at
org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
at
org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610)
at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445)
at
org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
at
org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.sendHttpHEADRequest(APIProviderHostObject.java:4781)
at
org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.jsFunction_isURLValid(APIProviderHostObject.java:4173)
at sun.reflect.GeneratedMethodAccessor117.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386)
at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
at
org.jaggeryjs.rhino.publisher.modules.api.c3._c_anonymous_10(/publisher/modules/api/add.jag:225)
at
org.jaggeryjs.rhino.publisher.modules.api.c3.call(/publisher/modules/api/add.jag)
at org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2430)
at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
at org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97)
at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.modules.api.c0._c_anonymous_5(/publisher/modules/api/module.jag:18)
at
org.jaggeryjs.rhino.publisher.modules.api.c0.call(/publisher/modules/api/module.jag)
at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
at
org.jaggeryjs.rhino.publisher.site.blocks.item_add.ajax.c0._c_anonymous_2(/publisher/site/blocks/item-add/ajax/add.jag:233)
at
org.jaggeryjs.rhino.publisher.site.blocks.item_add.ajax.c0.call(/publisher/site/blocks/item-add/ajax/add.jag)
at org.mozilla.javascript.optimizer.OptRuntime.call0(OptRuntime.java:23)
at
org.jaggeryjs.rhino.publisher.site.blocks.item_add.ajax.c0._c_script_0(/publisher/site/blocks/item-add/ajax/add.jag:9)
at
org.jaggeryjs.rhino.publisher.site.blocks.item_add.ajax.c0.call(/publisher/site/blocks/item-add/ajax/add.jag)
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)
at
org.jaggeryjs.rhino.publisher.site.blocks.item_add.ajax.c0.call(/publisher/site/blocks/item-add/ajax/add.jag)
at
org.jaggeryjs.rhino.publisher.site.blocks.item_add.ajax.c0.exec(/publisher/site/blocks/item-add/ajax/add.jag)
at
org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:567)
at org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273)
at
org.jaggeryjs.jaggery.core.manager.WebAppManager.exec(WebAppManager.java:588)
at

[Dev] generate the email (auto-generation )when storing the data in the database

[Dilusha Alphonso]

Hi All,

I am trying to generate the email (auto-generation )when storing the data
in the database. In my scenario, My backend service deploys on the DSS
server. I am trying to post the data using api in ESB 5.0.0.

For email generation, I followed the below steps.

1. uncommented  the transport sender in axis2.xml  in the ESB

 
smtp.gmail.com
587
true
true
esbadmin
*
mym...@gmail.com


2.configured the endpoint in the API in ESB 5.0.0.

 mailto:dilu...@wso2.com"/>
  


but I noticed below exception.

javax.mail.AuthenticationFailedException
at javax.mail.Service.connect(Service.java:306)
at javax.mail.Service.connect(Service.java:156)
at javax.mail.Service.connect(Service.java:105)
at javax.mail.Transport.send0(Transport.java:168)
at javax.mail.Transport.send(Transport.java:98)
at
org.apache.axis2.transport.mail.MailTransportSender.sendMail(MailTransportSender.java:501)
at
org.apache.axis2.transport.mail.MailTransportSender.sendMessage(MailTransportSender.java:182)
at
org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.send(DynamicAxisOperation.java:185)
at
org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:167)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:581)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:78)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:548)
at
org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:382)
at
org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:65)
at
org.apache.synapse.endpoints.RecipientListEndpoint.sendToEndpointList(RecipientListEndpoint.java:185)
at
org.apache.synapse.endpoints.RecipientListEndpoint.sendMessage(RecipientListEndpoint.java:137)
at
org.apache.synapse.endpoints.RecipientListEndpoint.send(RecipientListEndpoint.java:116)
at
org.apache.synapse.mediators.builtin.CallMediator.handleNonBlockingCall(CallMediator.java:221)
at
org.apache.synapse.mediators.builtin.CallMediator.mediate(CallMediator.java:99)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:59)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
at org.apache.synapse.rest.Resource.process(Resource.java:343)
at org.apache.synapse.rest.API.process(API.java:399)
at
org.apache.synapse.rest.RESTRequestHandler.apiProcess(RESTRequestHandler.java:123)
at
org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:101)
at
org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:69)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:304)
at
org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:75)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:325)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:371)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:151)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
[2017-12-12 15:17:22,297] ERROR - MailTransportSender Error generating mail
message
org.apache.axis2.AxisFault: Error creating mail message or sending it to
the configured server
at
org.apache.axis2.transport.base.AbstractTransportSender.handleException(AbstractTransportSender.java:226)
at
org.apache.axis2.transport.mail.MailTransportSender.sendMail(MailTransportSender.java:512)
at
org.apache.axis2.transport.mail.MailTransportSender.sendMessage(MailTransportSender.java:182)
at
org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.send(DynamicAxisOperation.java:185)
at
org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:167)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at

[Dev] [ESB] SourceHandler I/O error

[Senuwan Withana]

Hi Team,

I got below error in EI Console. I would like to know why this error is
happened?


[2017-12-12 16:32:11,766] [EI-Core] ERROR - SourceHandler I/O error:
Received fatal alert: certificate_unknown
javax.net.ssl.SSLException: Received fatal alert: certificate_unknown
at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1666)
at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1634)
at sun.security.ssl.SSLEngineImpl.recvAlert(SSLEngineImpl.java:1800)
at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1083)
at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:907)
at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
at
org.apache.http.nio.reactor.ssl.SSLIOSession.doUnwrap(SSLIOSession.java:245)
at
org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:280)
at
org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:410)
at
org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:119)
at
org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
at
org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
at
org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:586)
at java.lang.Thread.run(Thread.java:748)


Regards,

*Senuwan Withana*
Software Engineer - Support Team | WSO2

Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev