We have discovered a major issue with WSO2 API Manager 1.3 and it's integration into the WSO2 BAM 2.0.1 analytics product and I'm wondering if anyone out there has worked around this issue?
Details
After 100 calls trying to log API data to the BAM server all further calls will fail and in some cases this will stop the API Manager server from service API requests also.
The problem occurs in the DataPublisher.java class that acquires a permit from one semaphore and then releases the permit on the wrong semaphore.
Mentioned in the JIRA issue at https://wso2.org/jira/browse/APIMANAGER-992
This is obviously a blocker for us in using API Manager as we can no longer show clients any API analytics - hoping someone out there has had a similar problem and fingers crossed a work around.
We have done some major improvements to API Manager's Data publisher. These fixes will be included in 1.4.0 release, which will be ready by end of April.
We are planning to push preview releases from this week on wards. I am not particularly sure if the mentioned issue is fixed by now. However We have made this a blocker for 1.4.0 release. Hence, if not fixed by now it will be taken up soon. We will be updating the JIRA issue with progress.
Related
I am trying to utilise multitenancy feature in WSO2 by using github releases(https://github.com/wso2/product-is/releases/tag/v5.11.0). I just wanted to understand if there are any limitations for the same between enterprise version downloaded from wso2 site and github releases.
Thanks
WSO2 doesn't have an Enterprise Version of the product. Everybody uses the same base release and if you have a subscription you will be receiving product updates for bug fixes, improvements, security issues etc. Other than that there are no hidden features or limitations in the Opensource version.(Rarely some features are introduced as updates, in these cases you may not receive them) The subscription is for getting updates and getting support from WSO2.
You can read more about WSO2 subscription from here.
Adding to #YCR answer, yes, multi tenancy is supported in IS 5.11.0 and IS 6.0.0 and it was supported throughout IS 5.x series. Please see Tenant Management on WSO2 documentation.
I'm using WSO2's API Manager version 2.5.0 (https://github.com/wso2/product-apim/tree/v2.5.0).
Problem:
I create a REST API then create a SOAP API. When I edit the REST API looking at the first page (Design), it shows a SOAP endpoint instead of the REST endpoints. If I then create a websocket API and view the design page of the REST and SOAP APIs, the endpoints aren't shown indicating they are now websocket APIs. If I then create another REST API, viewing the design page of the other APIs shows they are now back to normal.
Question:
What is causing this to happen? Is there a fix for it? Does anyone have information about this? I've done extensive research looking through their docs, their github, stackoverflow, and google searches with no luck.
This is a known issue in 2.5.0 and fixed in 2.6.0.
Edit: My bad. It seems it's fixed after 2.6.0 release.
You can use the development branch[1].
[1] https://github.com/wso2/product-apim/tree/2.x
Kinda new to WSO products. Installed WSO DSS 3.5.0 and created a simple test data service following all the instructions on WSO documentation. it is working fine except I can not find out how to implement the security for data service as mentioned in the documentation :
https://docs.wso2.com/display/DSS350/Filtering+Content+to+Specific+User+Roles
The problem is that Quality Of Service Configuration Panel is empty in my web console and no menu exists there for security or anything else except the edit data service menu as you can see :
Spending a full day reading docs searching googling etc for the solution I have not found any..
Anyone else facing this same issue? should I activate it in features somehow or is there another product needed to be installed together with DSS for this to work?
WSO2 DSS 3.5.0 is carbon kernel 4.4.x based product. From kernel 4.4.x on wards QoS features are removed from the kernel.
You have to use WSO2 Developer Studio to implemnet QoS for the requirement.
This is regarding wso2 APM
Is there a getting started guide for those who wanted to start contributing to WSO2 API Manager.
Any feature request page where I can see community voted new features on which contribution is required ?
Thanks.
To get an understanding about the jaggery application structure in the API manager (The UI parts) you can read following tutorials
http://wso2.com/library/tutorials/2012/09/customizing-api-store-publisher-part1/
http://wso2.com/library/tutorials/2013/08/customizing-api-storepublisher-jaggery-applicationspart2/
this is the structure followed in api manager store, publisher and admin-dashboard jaggery application.
You can read http://wso2.com/library/tutorials/writing-custom-hostobject/ to see how the jaggery application is connected with the java code.
These will give you a basic understanding about the code base of the api manager.
Is there a getting started guide for those who wanted to start
contributing to WSO2 API Manager.
WSO2 API Manager is 100% open source API Management solution. You can find the component source code in github, component repo and product repo
Any feature request page where I can see community voted new features
on which contribution is required ?
You can find those information in the following mailing list
dev#wso2.org is a mailing list to discuss about all WSO2 products.
I am trying to register WSO2 as a identity provider for PingOne. After configuring both PingOne and WSO2 PingOne would complain about not being able to process WSO2's SAML response.
After working with Ping technical support, we discovered that the WSO2 compresses SAML when sending it using the SAML POST binding which is a violation of the SAML specification.
I dug around on the web and it seems that the WSO2 team is already aware of this issue and it is fixed in version 4.1.1. Unfortunately, there does not seem to be a 4.1.1 download on the WSO2 page.
If the WSO2 support team monitoring stack overflow could please recommend how I should proceed to work around this issue I would greatly appreciate it.
There was such issue and it has been fixed in 4.5.0. Actually, there was a plan to release 4.1.1. But due to new features, finally it has been renamed as 4.5.0. Please download 4.5.0 from official website http://wso2.com/products/identity-server and try out it.