I am working with WSO2 EI 6.6 and I am testing the "Generate API" feature from a Swagger definition. I found out that the generation success using the swagger 2.0 spec but if I convert to OpenAPI 3, the generation fails.
The error shown is the following:
TID: [-1234] [] [2020-01-15 14:12:18,653] ERROR {org.wso2.carbon.rest.api.service.RestApiAdmin} - Error occurred while generating API :: The "basePath" of the swagger definition is mandatory for API generation org.wso2.carbon.mediation.commons.rest.api.swagger.APIGenException: The "basePath" of the swagger definition is mandatory for API generation
at org.wso2.carbon.mediation.commons.rest.api.swagger.APIGenerator.generateSynapseAPI(APIGenerator.java:76)
It looks like the WSO2 EI 6.6 autogeneration tool only supports swagger 2.0 since it is missing a field that I think it is not present in OpenAPI 3
Any help? Is not there support for OpenAPI 3?
Cheers
Related
I have upgraded wso2 server from wso2 IS 5.10.0 to IS 5.11.0. I understand that there has been change in CORS, I have removed CORS filter from web.xml and added configuration to deployment.toml. I still see below two errors in logs of wso2.
ERROR {org.wso2.carbon.identity.authz.service.handler.AuthorizationHandler} - Error occurred while trying to authorize, Operation is not supported.
ERROR {org.wso2.carbon.identity.cors.valve.CORSValve} - CORS management service error when intercepting an HTTP request. org.wso2.carbon.identity.cors.mgt.core.exception.CORSManagementServiceServerException
Please guide me how to fix this errors
I use WSO2 ESB 5.0.0 and WSO2 EI 6.6.0. The WSO2 carbon generates a lot of wso2carbon.log log files daily and they eat up a lot of server hard disc space over time.
How can I set/configure WSO2 ESB 5.0.0 and WSO2 EI 6.6.0 so that it automatically deletes log files after a certain period of time (for example, after 1 month)?
Thanks.
You can follow this Log management documentation. https://docs.wso2.com/display/EI660/Managing+Log+Growth
You can limit the size of the /repository/logs/wso2carbon.log file by following the steps given below.
Configure the following two properties for CARBON_LOGFILE appender:
appender.CARBON_LOGFILE.policies.size.size=10MB
appender.CARBON_LOGFILE.strategy.max = 20
I just want to know that does WSO2 ESB by default support on soap 1.1? How to make it work on soap 1.2? Is there any global property by which I can change all the deployed services to make it work on soap 1.2?
Thanks in Advance
Regards,
Shri
Hi Thanks for your response. but I get below error when try 1.2 Soap request from the SOAP UI.
[2016-08-10 10:53:41,744] ERROR - NativeWorkerPool [msg_id=urn:uuid:4abc1b45-c6a8-4f92-9559-169d3dab403f] Uncaught exception
org.apache.axiom.om.impl.exception.OMBuilderException: detail unsupported element in SOAPFault element
at org.apache.axiom.soap.impl.builder.SOAP12BuilderHelper.handleEvent(SOAP12BuilderHelper.java:175)
at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(StAXSOAPModelBuilder.java:428)
WSO2 ESB supports both by default. For example, when you create a proxy service in ESB, it exposes both SOAP 1.1 and SOAP 1.2 endpoints.
It seems that this error happens when using SOAP 1.2 while communicating between .Net applications and Axis2. So far the only solution I have seen is to force the use of SOAP 1.1.
See also:
Mention of error
Apparently the definition of the SOAPfault changed slightly between versions, most importantly the capitalisation of certain elements, including the detail element. The error suggests that the received message includes the element, which is in accordance with SOAP 1.1, while in SOAP 1.2 it should be a element. For more detail, check this site
Using WSO2 API Manager 1.3 and WSO2 BAM 2.0.
I followed the instructions found in the README.txt in /statistics.
I am getting the following error when starting API Manager:
TID: [0] [AM] [2013-05-02 11:42:44,239] ERROR
{org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
- Error initializing APIMgtUsageDataBridgeDataPublisher {org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
org.wso2.carbon.databridge.agent.thrift.exception.AgentException:
Error when finding event stream definition for :
org.wso2.apimgt.statistics.request 1.0.0
Any suggestions on where to start looking for the issue?
It looks like you have not properly configured WSO2 API Manager 1.3 to work with WSO2 BAM.
For proper configuration follow the official docs[1]
This issue might also occur When you set an offset to BAM by 1 as described in the README.txt, as it needs its Cassandra DB configurations to be changed for the offset by 1 at BAM_HOME/repository/conf/etc/cassandra-component.xml. Therefore follow the like provided[1] where we change the API Manager's offset.
Suho
[1]http://docs.wso2.org/wiki/display/AM130/Monitoring+and+Statistics
I got the following error when runnning WSO2 API Manager 1.3.1 to use the WSO2 BAM Server 2.0.1.
TID: [0] [AM] [2013-05-02 18:58:40,609] ERROR
{org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
- Error initializing APIMgtUsageDataBridgeDataPublisher {org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
org.wso2.carbon.databridge.agent.thrift.exception.AgentException:
Error when finding event stream definition for :
org.wso2.apimgt.statistics.request 1.0.0
Both API Manager and BAM are running on the same machine and I changed offset to 1 in /home/jtao/api/wso2bam-2.0.1/repository/conf/carbon.xml based on Monetization of API Usage.
I also checked that BAM_HOME/repository/conf/etc/cassandra-component.xml doesn't exist in BAM 2.0.1. as someone suggested in the answer of another question "Configuring WSO2 API Manager to use the WSO2 BAM Server"
Any ideas?
I ran the same scenario described in guide and it works without any error. May be your have missed a part in the configuration guide? Make sure BAM_HOME is set correctly and BAM server is started before the AM server.
The following guide too can be used to integrate AM 1.3.1 with BAM 2.0.1
http://docs.wso2.org/wiki/display/AM131/Monitoring+and+Statistics
Ishara