Re: [Dev] One Specific API not responding

[alapan . sur]

Hello Team,

 

Any idea on the below ?

 


Best regards


Alapan Sur


Project Manager - SD


ValueLabs - 'inspired by potential'


Desk: +91-40-6623-9000 | Ext: 32112


Mobile: +91-7799681717


This e-mail may contain information that is proprietary, confidential or
otherwise protected from disclosure and is sent for the intended
recipient(s) only. For email disclaimer details, please visit:
http://www.valuelabs.com/terms-of-use/

 

From: alapan@valuelabs.com [mailto:alapan@valuelabs.com] 
Sent: Thursday, April 19, 2018 1:24 PM
To: 'dev@wso2.org' 
Subject: One Specific API not responding

 

Hello Team,

 

We are facing an issue file working with WSO2 API Manager 2.1.0. 

 

There is one request for a specific endpoint is continuously failing for
some reason and as a result, this specific API is getting down and we are
not getting an response from WSO2 APIM gateway  although we are receiving
the response from backend API before the socket time out error.  Please
find the below error we are getting :

 

TID: [-1] [] [2018-04-19 04:54:24,294] WARN
{org.apache.synapse.transport.passthru.SourceHandler} - Connection time
out after request is read: http-incoming-106261 Socket Timeout : 6
Remote Address : /

10.138.120.228:36754 {org.apache.synapse.transport.passthru.SourceHandler}

 
 
Is there any threshold configuration which is configured to handle the
multiple API failure and WSO2 skips suspend the end point ?

 

Can anyone help in this regard ?


Best regards


Alapan Sur


Project Manager - SD


ValueLabs - 'inspired by potential'


Desk: +91-40-6623-9000 | Ext: 32112


Mobile: +91-7799681717


This e-mail may contain information that is proprietary, confidential or
otherwise protected from disclosure and is sent for the intended
recipient(s) only. For email disclaimer details, please visit:
http://www.valuelabs.com/terms-of-use/

 

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

Re: [Dev] [APIM 2.1.0] No CORS headers received for OPTIONS http method

[Gayan Yalpathwala]

Thanks for the response Tharindu.

You're right! When I add "*Access-Control-Request-Method: GET*" header in
the request, I am seeing following behavior.

   1. When OPTIONS method is defined for a resource in API, I am getting
   all HTTP methods supported by the back-end + NO
   "Access-Control-Allow-Headers".
   This is because the back-end does not support CORS.

   2. When OPTIONS method is NOT defined for a resource in API, I am
   getting HTTP methods supported by the API (on gateway) +
   "Access-Control-Allow-Headers".
   This request is catered by the gateway itself, rather than passing thru
   to the back-end.

Thanks for the clarification.


On Thu, Apr 19, 2018 at 10:08 PM, Tharindu Dharmarathna 
wrote:

> Hi Gayan,
> Did you Add the OPTIONS resource to API ?. Then OPTION call will be going
> to the backend. If you not specifying OPTION Resource you need to send 
> *Access-Control-Request-Method
> *header.
>
>
> Thanks
> Tharindu
>
>
> On Fri, Apr 20, 2018 at 4:23 AM, Gayan Yalpathwala 
> wrote:
>
>> Hi team,
>>
>> Let me explain this using Pizzashack sample API. I have added OPTIONS
>> method for "/menu" resource on top of the sample.
>>
>> For GET method, I am receiving "Access-Control-Allow-Headers" whereas for
>> OPTIONS, I am not getting it. See below.
>>
>> curl -k -X GET --header 'Accept: application/json' --header
>> 'Authorization: Bearer x' 'https://mylocal:8243/pizzashack/1.0.0/menu'
>> -v
>> < HTTP/1.1 200 OK
>> < Access-Control-Allow-Origin: *
>> < Access-Control-Allow-Methods: GET
>> < Access-Control-Allow-Headers: authorization,Access-Control-A
>> llow-Origin,Content-Type,SOAPAction
>>
>> curl -k -X OPTIONS --header 'Accept: application/json' --header
>> 'Authorization: Bearer x' 'https://mylocal:8243/pizzashack/1.0.0/menu'
>> -v
>> < HTTP/1.1 200 OK
>> < Allow: DELETE,POST,GET,PUT,OPTIONS,HEAD
>>
>> I am expecting CORS headers for OPTIONS call as well.
>>
>> Thanks,
>>
>> --
>> *Gayan Kaushalya Yalpathwala*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> LK: +94 71 868 2704
>> US: (408) 386-7521
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Tharindu Dharmarathna*Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94779109091*
>



-- 
*Gayan Kaushalya Yalpathwala*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

LK: +94 71 868 2704
US: (408) 386-7521


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

Re: [Dev] [APIM 2.1.0] No CORS headers received for OPTIONS http method

[Tharindu Dharmarathna]

Hi Gayan,
Did you Add the OPTIONS resource to API ?. Then OPTION call will be going
to the backend. If you not specifying OPTION Resource you need to send
*Access-Control-Request-Method
*header.


Thanks
Tharindu


On Fri, Apr 20, 2018 at 4:23 AM, Gayan Yalpathwala  wrote:

> Hi team,
>
> Let me explain this using Pizzashack sample API. I have added OPTIONS
> method for "/menu" resource on top of the sample.
>
> For GET method, I am receiving "Access-Control-Allow-Headers" whereas for
> OPTIONS, I am not getting it. See below.
>
> curl -k -X GET --header 'Accept: application/json' --header
> 'Authorization: Bearer x' 'https://mylocal:8243/pizzashack/1.0.0/menu'
> -v
> < HTTP/1.1 200 OK
> < Access-Control-Allow-Origin: *
> < Access-Control-Allow-Methods: GET
> < Access-Control-Allow-Headers: authorization,Access-Control-
> Allow-Origin,Content-Type,SOAPAction
>
> curl -k -X OPTIONS --header 'Accept: application/json' --header
> 'Authorization: Bearer x' 'https://mylocal:8243/pizzashack/1.0.0/menu'
> -v
> < HTTP/1.1 200 OK
> < Allow: DELETE,POST,GET,PUT,OPTIONS,HEAD
>
> I am expecting CORS headers for OPTIONS call as well.
>
> Thanks,
>
> --
> *Gayan Kaushalya Yalpathwala*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> LK: +94 71 868 2704
> US: (408) 386-7521
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

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

Re: [Dev] [DAS] Inferring actual table name from the table's encoded name

[Fazlan Nazeem]

Hi all,

Was this implemented? if so can someone point me to the documentation? I
need to find the actual table name using the encoded name. If there is any
other alternative please let me know.

On Thu, Jan 11, 2018 at 8:21 AM, Sajith Ravindra  wrote:

> Have to agree with Sinthuja on this.
>
> IMO this is a simple utility function. People will be mostly using this
> while debugging an issue to get the actual table name. Having script makes
> things much easy and simple IMO.
>
> Thanks
> *,Sajith Ravindra*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 77 2273550
> blog: http://sajithr.blogspot.com/
> 
>
> On Thu, Jan 11, 2018 at 12:21 AM, Sinthuja Rajendran 
> wrote:
>
>> Hi Gokul,
>>
>> On Thu, Jan 11, 2018 at 11:41 AM, Gokul Balakrishnan 
>> wrote:
>>
>>> Hi Sinthuja,
>>>
>>> Agree with your point. However, a new script will come with its own
>>> complexities such as segregating permissions and preventing users from
>>> retrieving names of tables not belonging to their tenant.
>>>
>>
>> Anyhow, this is devops/advanced user related work, and not a general user
>> related operation. Because inorder to get the encoded table name, the user
>> should have the access to the database and knowing the table name/schema
>> will not impose any security threat. So I don't think having shell script
>> will reveal any additional security threat, given that the user who will be
>> using this feature will be already having the db level access.
>>
>>
>>> In addition, we already have a REST API operation for doing it the other
>>> way (human-readable name to encoded name) already, hence the decision to
>>> add this to the REST API too.
>>>
>>
>> Hmm.. Ok..
>>
>> Thanks,
>> Sinthuja.
>>
>> Best,
>>>
>>> On 11 January 2018 at 11:17, Sinthuja Rajendran 
>>> wrote:
>>>
 Hi Gokul,

 +1 to have a feature which returns the actual table name from the
 encoded table name that exists in the data storage.

 But IMHO, having REST API for this is not a correct way of doing,
 because REST APIs are intended to integrate this with external systems, and
 hence core analytics data operations need to be exposed via the REST API.
 But this feature is kind of a utility operation for debugging and not meant
 to be used by the users for normal table operations and also AFAIR it's
 applicable for RDBMS analytics data sources, not for others such as HBase.

 Therefore I propose, we'll have a utility shell script like a tool,
 which will take the encoded table name, and the data source type as params,
 and prompt the user-defined table name.

 Thanks,
 Sinthuja.

 On Thu, Jan 11, 2018 at 11:01 AM, Gokul Balakrishnan 
 wrote:

> Hi,
>
> We have come across many cases where DAS tables stored in the EVENT or
> PROCESSED stores (which have encoded names to comply with DB vendor
> limitations) cannot be identified as representing which actual table just
> by looking at them. This is a very useful functionality to have, 
> especially
> when debugging issues.
>
> In order to address this, I've implemented a DAS REST API operation
> which will simply examine the calling user's tables and print out the name
> of the actual table if a match is found.
>
> The usage will be as follows:
>
> GET (with auth) https://:9443/analyt
> ics/tables//actualName
>
> Example cURL command:
>
> curl -k -H "Authorization: Basic YWRtaW46YWRtaW4="
> https://localhost:9443/analytics/tables/ANX___7Lleafa0_/actualName
>
> We're planning to release this as a WUM update for DAS 3.1.0 and
> related products.
>
> --
> Gokul Balakrishnan
> Senior Software Engineer,
> WSO2, Inc. http://wso2.com
> M +94 77 5935 789 | +44 7563 570502 <+44%207563%20570502>
>
>


 --
 *Sinthuja Rajendran*
 Senior Technical Lead
 WSO2, Inc.:http://wso2.com

 Blog: http://sinthu-rajan.blogspot.com/
 Mobile: +94774273955 <+94%2077%20427%203955>



>>>
>>>
>>> --
>>> Gokul Balakrishnan
>>> Senior Software Engineer,
>>> WSO2, Inc. http://wso2.com
>>> M +94 77 5935 789 | +44 7563 570502 <+44%207563%20570502>
>>>
>>>
>>
>>
>> --
>> *Sinthuja Rajendran*
>> Senior Technical Lead
>> WSO2, Inc.:http://wso2.com
>>
>> Blog: http://sinthu-rajan.blogspot.com/
>> Mobile: +94774273955 <+94%2077%20427%203955>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Fazlan Nazeem*
Senior Software Engineer
WSO2 Inc

[Dev] [APIM 2.1.0] No CORS headers received for OPTIONS http method

[Gayan Yalpathwala]

Hi team,

Let me explain this using Pizzashack sample API. I have added OPTIONS
method for "/menu" resource on top of the sample.

For GET method, I am receiving "Access-Control-Allow-Headers" whereas for
OPTIONS, I am not getting it. See below.

curl -k -X GET --header 'Accept: application/json' --header 'Authorization:
Bearer x' 'https://mylocal:8243/pizzashack/1.0.0/menu' -v
< HTTP/1.1 200 OK
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Methods: GET
< Access-Control-Allow-Headers:
authorization,Access-Control-Allow-Origin,Content-Type,SOAPAction

curl -k -X OPTIONS --header 'Accept: application/json' --header
'Authorization: Bearer x' 'https://mylocal:8243/pizzashack/1.0.0/menu'
-v
< HTTP/1.1 200 OK
< Allow: DELETE,POST,GET,PUT,OPTIONS,HEAD

I am expecting CORS headers for OPTIONS call as well.

Thanks,

-- 
*Gayan Kaushalya Yalpathwala*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

LK: +94 71 868 2704
US: (408) 386-7521


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

[Dev] Missing JSESSION cookie

[Ciprian Sabolovits]

Hi Everyone,

Having a problem with WSO2 IS 5.5.0. For some reason IS does not set the cookie 
JSESSIONID and hence the log out functionality with OpenID is broken. Any idea 
why? Do we need to do anything special in configuration to get the cookies set?

Thanks,
Ciprian

CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole 
use of the intended recipient(s) and may contain confidential information of 
Cognosante Holdings, LLC and/or its subsidiaries, including Cognosante, LLC, 
Cognosante Consulting, LLC, and Cognosante MVH, LLC and is protected by law. If 
you have received this in error, please reply to the sender and delete it from 
your system. If you are the intended recipient, you may use the information 
contained in this message and any files attached only as authorized.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EXTERNAL SENDER] WSO2 Identity Server 5.6.0-M5 Released!

[Ciprian Sabolovits]

Hi Everyone,

Having a problem with WSO2 IS 5.5.0. For some reason IS does not set the cookie 
JSESSIONID and hence the log out functionality with OpenID is broken. Any idea 
why? Do we need to do anything special in configuration to get the cookies set?

Thanks,
Ciprian



CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole 
use of the intended recipient(s) and may contain confidential information of 
Cognosante Holdings, LLC and/or its subsidiaries, including Cognosante, LLC, 
Cognosante Consulting, LLC, and Cognosante MVH, LLC and is protected by law. If 
you have received this in error, please reply to the sender and delete it from 
your system. If you are the intended recipient, you may use the information 
contained in this message and any files attached only as authorized.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Identity Server 5.6.0-M5 Released!

[Madawa Soysa]

*WSO2 Identity and Access Management team is pleased to announce the
release of Identity Server 5.6.0 M5!DownloadYou can download WSO2 Identity
Server 5.6.0 M5 from here
.How
to run 1. Extract the downloaded zip file. 2. Go to the bin directory in
the extracted folder. 3. Run the wso2server.sh file if you are on a
Linux/Mac OS or run the wso2server.bat file if you are on a Windows OS. 4.
Optionally, if you need to start the OSGi console with the server, use the
-DosgiConsole property when starting the server.What's new in WSO2 Identity
Server 5.6.0 M5*


*A list of all the new features and bug fixes shipped with this release can
be found here *














*Known IssuesAll the open issues pertaining to WSO2 Identity Server are
reported at the following location: - IS Runtime
How You Can ContributeMailing
ListsJoin our mailing list and correspond with the developers directly.
Developer list: dev@wso2.org  | Subscribe | Mail Archive
 User forum: StackOverflow
Reporting IssuesWe
encourage you to report issues, improvements, documentation faults, and
feature requests regarding WSO2 Identity Server through WSO2 Identity
Server GIT Issues .For more
information about WSO2 Identity Server, please see
https://wso2.com/identity-and-access-management
 or visit the WSO2 Oxygen
Tank  developer portal for additional resources.~
The WSO2 Identity and Access Management Team ~*

-- 

Madawa Soysa / Software Engineer
mada...@wso2.com / +94714616050

*WSO2 Inc.*
lean.enterprise.middleware

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

[Dev] WSO2 Enterprise Integrator Kubernetes Resources v6.2.0.1 Released!

[Chiranga Alwis]

WSO2 Installation Experience team is pleased to announce the initial
release of WSO2 Kubernetes resources for WSO2 Enterprise Integrator 6.2.0.

*Features*

   1. Deployment controller for WSO2 Enterprise Integrator's Integrator
   profile, to easily manage corresponding pods.
   2. MySQL Deployment controller for database access to test out an
   out-of-the-box scalable deployment.
   3. Service level separation for mediation gateway and management console
   access to optimize request load.
   4. NGINX Ingress controller to publicly expose Integration services
   easily.
   5. Configmaps in managing pattern specific configurations to simplify
   rolling out of updates.
   6. Dockerfiles for building required base images from the scratch.
   7. Helper scripts for deploying and undeploying pattern-1 in one go.

*Fixed issues*

   - Migrate Kubernetes resource implementations from version 6.1.1 to
   version 6.2.x 
   - Remove custom MySQL Docker image build implementation
   
   - Remove existing Kubernetes resource deployment management scripts
   
   - Refine Docker resources for Integrator profile
   
   - Refine Docker resources for Analytics profile
   

*Supported Versions*

   - Kubernetes: v1.6.0 or later
   - Docker: v17.09.0 or later

*How You Can Contribute*
Join our mailing list and correspond with the developers directly.

   - Developer List: dev@wso2.org
   - User List: u...@wso2.org

*Reporting Issues*
We encourage you to report issues and documentation faults regarding WSO2
Kubernetes resources for WSO2 Enterprise Integrator 6.2.0 by creating issues
.

Thank you!
WSO2 Installation Experience Team

-- 
Yours sincerely,

*Chiranga Alwis*
Software Engineer | WSO2

*Mobile : *+94775930497
*Email: *chirangaal...@gmail.com
*LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9
*Medium:* https://medium.com/@chirangaalwis


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

[Dev] [Architecture] [Announce] WSO2 API Manager 3.0.0-M27 Released!

[Tharindu Dharmarathna]

The WSO2 API Manager team is pleased to announce the release of API Manager
3.0.0-M27. It's now available to download.


## Distribution

- [wso2apim-3.0.0-M27](
https://github.com/wso2/product-apim/releases/download/v3.0.0-m27/wso2apim-3.0.0-m27.zip
)
- [wso2apim-gateway-3.0.0-M27](
https://github.com/wso2/product-apim/releases/download/v3.0.0-m27/wso2apim-gateway-3.0.0-m27.zip
)

## Documentation

- [WSO2 API Manager 3.0.0](https://docs.wso2.com/display/AM300/)

Following list contains all the features, improvements and bug fixes
available with this milestone.


## Bug Fixes

- [Product-APIM Bug fixses](
https://github.com/wso2/product-apim/issues?q=is%3Aissue+milestone%3A3.0.0-m27+is%3Aclosed
)


## List of Open Issues

- Open Issues for [Product-APIM](
https://github.com/wso2/product-apim/issues?q=is%3Aopen+is%3Aissue+label%3A3.0.0+label%3AType%2FBug
)

## How To Contribute

Your feedback is most welcome!


## Mailing Lists
```
Join our mailing list and collaborate with the developers directly.
```
Developer List : dev@wso2.org | Subscribe | [Mail Archive](
http://mail.wso2.org/mailarchive/dev/)

- User Forum : [StackOverflow](
https://stackoverflow.com/questions/tagged/wso2-am)

Reporting Issues

We encourage you to report issues, improvements and feature requests
regarding WSO2 API Manager through [WSO2 API Manager GIT Issues](
https://github.com/wso2/product-apim/issues).

~ WSO2 API Manager Team ~

Thanks


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

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

Re: [Dev] WSO2 EI - org.apache.cxf.jaxws.spi.ProviderImpl not found

[Júnior]

Hi Shakila,

Actually I am not building the jar file, it is a third-party jar. I am just
including the jar file into the lib folder. Also, don't know why it is
using cxf as jaxws implementation, I think WSO2 uses it by default I think.

I am still trying to find a fix for that.

I will let you know when I find it.

Thanks,

2018-04-19 1:19 GMT-03:00 Shakila Sasikaran :

> Hi,
>
> Can you try by excluding the other cxf-bundle while adding the dependency?
>
> 
>   x
>   x
>   
>   compile
>   
> 
>   y
>   y
> 
>   
> 
>
> Thanks
>
> On Thu, Apr 19, 2018 at 1:24 AM, Júnior  wrote:
>
>> I found tha there is a bundle provided by wso2:
>> cxf-bundle-2.6.1.wso2v2.jar
>>
>> Using it I am getting another problem:
>>
>> java.lang.LinkageError: loader constraint violation: when resolving
>> method "org.apache.ws.commons.schema.XmlSchemaCollection.getNamespa
>> ceContext()Lorg/apache/ws/commons/schema/utils/NamespacePrefixList;" the
>> class loader (instance of 
>> org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader)
>> of the current class, org/apache/cxf/common/xmlschema/SchemaCollection,
>> and the class loader (instance of 
>> org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader)
>> for the method's defining class, 
>> org/apache/ws/commons/schema/XmlSchemaCollection,
>> have different Class objects for the type 
>> org/apache/ws/commons/schema/utils/NamespacePrefixList
>> used in the signature
>>
>>
>> As I could see, there is a bundle exporting this package in a different
>> version. Have you seen this error before?
>>
>> Thanks,
>>
>>
>>
>> 2018-04-17 19:25 GMT-03:00 Júnior :
>>
>>> I tried adding the cxf-bundle:cxf-bundle-2.2.5.jar
>>>
>>> And I am receiving this error:
>>>
>>> gogo: BundleException: The bundle "org.apache.cxf.bundle_2.2.5 [172]"
>>> could not be resolved. Reason: Missing Constraint: Import-Package:
>>> javax.activation; version="[1.1.0,2.0.0)"
>>> osgi>
>>>
>>> Do you know hwo to add this dependency?
>>>
>>> Thanks,
>>>
>>> 2018-04-17 6:16 GMT-03:00 Júnior :
>>>
 Hi Shakila,

 I am not building the jar, it is a third party jar. As I could see, It
 has no reference tô cxf, but only jax-ws.

 I am trying to add the required jars to the dropins folder, this is
 still in progress.

 Getting the jars from wso2/lib/runtimes/cxf

 Thanks

 Em ter, 17 de abr de 2018 00:32, Shakila Sasikaran 
 escreveu:

> Hi,
>
> I hope you are building this jar from a maven project. Could you
> please share the pom file of this application? Could you please import the
> relevant package (org.apache.cxf.jaxws.spi) with correct version and
> try?
>
> Thanks
>
> On Tue, Apr 17, 2018 at 5:12 AM, Júnior  wrote:
>
>> Hi,
>>
>> I am adding a jar file that uses a JAX-WS client to invoke a web
>> service. When I am trying to execute the code, I am getting this error:
>>
>> javax.xml.ws.spi.FactoryFinder$ConfigurationError: Provider
>> org.apache.cxf.jaxws.spi.ProviderImpl not found
>>
>> Caused by: javax.xml.ws.spi.FactoryFinder$ConfigurationError:
>> Provider org.apache.cxf.jaxws.spi.ProviderImpl not found
>> at javax.xml.ws.spi.FactoryFinder$2.run(FactoryFinder.java:130)
>> at javax.xml.ws.spi.FactoryFinder.doPrivileged(FactoryFinder.ja
>> va:220)
>> at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:124)
>> at javax.xml.ws.spi.FactoryFinder.access$200(FactoryFinder.java:44)
>> at javax.xml.ws.spi.FactoryFinder$3.run(FactoryFinder.java:211)
>> at javax.xml.ws.spi.FactoryFinder.doPrivileged(FactoryFinder.ja
>> va:220)
>> at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:160)
>> at javax.xml.ws.spi.Provider.provider(Provider.java:43)
>> at javax.xml.ws.Service.(Service.java:35)
>>
>>
>> Do you know how to overcome this error?
>>
>> Thanks,
>>
>> --
>> Francisco Ribeiro
>> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Shakila Sasikaran
> Software Engineer
> Mobile :+94 (0) 77 526 6848
> shak...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
>

>>>
>>>
>>> --
>>> Francisco Ribeiro
>>> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>>>
>>
>>
>>
>> --
>> Francisco Ribeiro
>> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>>
>
>
>
> --
> Shakila Sasikaran
> Software Engineer
> Mobile :+94 (0) 77 526 6848
> shak...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
>



-- 
Francisco Ribeiro

Re: [Dev] Update Binary attribute in Active directory via wso2 ldap Connector

[Shakila Sasikaran]

Hi Chathura,

Since this is an attribute, can you add a JSON entry with the key
*thumbnailPhoto* and add the byte array as the value into the *attribute*
object and try? You can refer the documentation [1] for more information
about the update entry operation.

[1] https://docs.wso2.com/display/ESBCONNECTORS/Working+with+
CRUD+operations+in+LDAP#WorkingwithCRUDoperationsinLDAP-updateEntry

Thanks

On Thu, Apr 19, 2018 at 4:05 PM, chathura prasad amarathunga <
drchath...@gmail.com> wrote:

> Hi Team,
> Is it possible to update binary attribute in the Active Directory ( like
> update Profile Image ). by using the Wso2 LDAP Connector.
>
> Cheers!
> Chathura
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Shakila Sasikaran
Software Engineer
Mobile :+94 (0) 77 526 6848
shak...@wso2.com
WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Update Binary attribute in Active directory via wso2 ldap Connector

[chathura prasad amarathunga]

Hi Team,
Is it possible to update binary attribute in the Active Directory ( like
update Profile Image ). by using the Wso2 LDAP Connector.

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

[Dev] WSO2 API Manager 2.2.0-update2 Released!

[Naduni Pamudika]

The WSO2 API Manager team is pleased to announce the release of version
2.2.0-update2 of API Manager.

WSO2 API Manager is a platform for creating, managing, consuming and
monitoring APIs. It employs proven SOA best practices to solve a wide range
of API management challenges such as API provisioning, API governance, API
security and API monitoring. It combines some of the most powerful and
mature components of the WSO2's state-of-the-art Carbon platform to deliver
a smooth and end-to-end API management experience while catering to both
API publisher and API consumer requirements.

WSO2 API Manager is comprised of several modules.

   - API Provider: Define new APIs and manage them
   - API Store: Browse published APIs and subscribe to them
   - API Gateway: The underlying API runtime based on WSO2 ESB
   - API Key Manager: Performs Key Generation and Key Validation
   functionalities
   - API Traffic Manager: Performs Rate Limiting of API Requests

For more information on WSO2 API Manager please visit
http://wso2.com/products/api-manager. Also, take a look at the online
product documentation
.

Distributions
wso2am-2.2.0-update2.zip

ws02am-micro-gw-2.2.0-update2.zip


wso2am-analytics-2.2.0-update1.zip


How to Run

   1. Extract the downloaded zip
   2. Go to the bin directory in the extracted folder
   3. Run the wso2server.sh or wso2server.bat as appropriate
   4. Launch a web browser and navigate to https://localhost:9443/publisher to
   access the API publisher webapp
   5. Navigate to https://localhost:9443/store to access the API store
   6. Navigate to https://localhost:9443/admin to access Admin Portal
   7. Use "admin", "admin" as the username and password to login as an admin

Bug Fixes And Improvements in 2.2.0-update2

   - JIRA 
   - GitHub (Product-apim
   ), (
   Carbon-apimgt
   )

Known Issues

All the open issues pertaining to WSO2 API Manager are reported at the
following location:

   - JIRA 
   - GitHub (Product-apim
   
),
   (Carbon-apimgt
   
),
   (Analytics-apim
   )

How You Can ContributeMailing Lists

Join our mailing list and correspond with the developers directly.

   -

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

   User List: u...@wso2.org | Subscribe | Mail Archive

Reporting Issues

We encourage you to report issues, documentation faults, and feature
requests regarding WSO2 API Manager through the public API Manager Git Repo
.

-- The WSO2 API Manager Team --

*Naduni Pamudika*
Software Engineer | WSO2
Mobile: +94 719 143658 <+94%2071%20914%203658>
[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] One Specific API not responding

[Menaka Jayawardena]

Hi Alapan Sur,

You can change the timeout configurations. Please refer the documentation
[1] and [2] for detailed information.

[1] https://docs.wso2.com/display/AM210/Prevent+API+Suspension
[2]
https://docs.wso2.com/display/AM210/Tuning+Performance#TuningPerformance-TimeoutconfigurationsforanAPIcall

Thank and Regards,
Menaka

On Thu, Apr 19, 2018 at 1:24 PM,  wrote:

> Hello Team,
>
>
>
> We are facing an issue file working with WSO2 API Manager 2.1.0.
>
>
>
> There is one request for a specific endpoint is continuously failing for
> some reason and as a result, this specific API is getting down and we are
> not getting an response from WSO2 APIM gateway  although we are receiving
> the response from backend API before the socket time out error.  Please
> find the below error we are getting :
>
>
>
> TID: [-1] [] [2018-04-19 04:54:24,294] WARN 
> {org.apache.synapse.transport.passthru.SourceHandler}
> - Connection time out after request is read: http-incoming-106261 Socket
> Timeout : 6 Remote Address : /10.138.120.228:36754
> 
> {org.apache.synapse.transport.passthru.SourceHandler}
>
>
> 
>
>
> Is there any threshold configuration which is configured to handle the
> multiple API failure and WSO2 skips suspend the end point ?
> 
>
>
>
> Can anyone help in this regard ?
>
> Best regards
>
> *Alapan Sur*
>
> Project Manager - SD
>
> ValueLabs - *'inspired by potential'*
>
> Desk: +91-40-6623-9000 | Ext: 32112
>
> Mobile: +91-7799681717
>
> This e-mail may contain information that is proprietary, confidential or
> otherwise protected from disclosure and is sent for the intended
> recipient(s) only. For email disclaimer details, please visit:
>  http://www.valuelabs.com/terms-of-use/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
Software Engineer
WSO2 Inc.

Phone: +94 71 350 5470
LinkedIn : https://lk.linkedin.com/in/menakajayawardena
Blog   : https://menakamadushanka.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] One Specific API not responding

[alapan . sur]

Hello Team,

 

We are facing an issue file working with WSO2 API Manager 2.1.0. 

 

There is one request for a specific endpoint is continuously failing for
some reason and as a result, this specific API is getting down and we are
not getting an response from WSO2 APIM gateway  although we are receiving
the response from backend API before the socket time out error.  Please
find the below error we are getting :

 

TID: [-1] [] [2018-04-19 04:54:24,294] WARN
{org.apache.synapse.transport.passthru.SourceHandler} - Connection time
out after request is read: http-incoming-106261 Socket Timeout : 6
Remote Address : /

10.138.120.228:36754 {org.apache.synapse.transport.passthru.SourceHandler}

 
 

 
 
Is there any threshold configuration which is configured to handle the
multiple API failure and WSO2 skips suspend the end point ?

 

Can anyone help in this regard ?


Best regards


Alapan Sur


Project Manager - SD


ValueLabs - 'inspired by potential'


Desk: +91-40-6623-9000 | Ext: 32112


Mobile: +91-7799681717


This e-mail may contain information that is proprietary, confidential or
otherwise protected from disclosure and is sent for the intended
recipient(s) only. For email disclaimer details, please visit:
http://www.valuelabs.com/terms-of-use/

 

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

[Dev] WSO2 Enterprise Integrator 6.3.0-M5 Released!

[Chanika Geeganage]

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

.

*Tasks/Bug Fixes and Improvements*

   - https://github.com/wso2/product-ei/milestone/37?closed=1


*Issues*

   - https://github.com/wso2/product-ei/issues?q=is%3Aopen+is%3Aissue
   - https://github.com/wso2/devstudio-tooling-ei/issues?q=is%
   3Aopen+is%3Aissue
   - https://wso2.org/jira/issues/?filter=13994


*Documentation*

   - https://docs.wso2.com/display/EI620/WSO2+Enterprise+Integrat
   or+Documentation


*How To Contribute*
Your feedback is most welcome!

*Reporting Issues​*

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

*Mailing Lists*

Join our mailing lists and correspond with the developers directly.

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


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

User Forum : StackOverflow 

~ The WSO2 Integration Team ~


-- 
Best Regards..

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