wso2

问题 I have treed as below <iterate xmlns:oag="http://www.openapplications.org/oagis/10" xmlns:fn="http://www.w3.org/2005/xpath-functions" continueParent="true" preservePayload="true" attachPath="//ProcessCredit/DataArea" expression="//ProcessCredit/DataArea/Credit sequential="true"> ..... <property xmlns:ns="http://org.apache.synapse/xsd" xmlns:oa="http://www.openapplications.org/oagis/10" name="ChargeTransactionKey" expression="concat(get-property('operation','ChargeTransactionKey'),//Extension

问题 Can WSO2 ELB automatically start another instance of ESB when the limit is reached? If yes can I get a miniature example with a limit as 2 or 3? 回答1: Yes. WSO2 ELB can automatically spawn instances using the configured cartridges. However, WSO2 ELB is no longer recommended and it has been discontinued. We recommend WSO2 Private PaaS if you need an auto-scaling platform with WSO2 products. With WSO2 Private PaaS, you can use auto-scaling policies. 来源： https://stackoverflow.com/questions

问题 After continuous time of the endpoint we are getting the message connection timeout after request is read and esb will stop responding. we need to restart the wso2 services again. i had increase the socket time out as suggested. 回答1: Time out in the esb is defined in three levels. endpoint timeout < socket timeout < synapse timeout.check[1] If you have defined enpoint timeout for your endpoint you can increase it up to the timeout value of socket timeout. and you can in crease the socket time

问题 We are using WSO2 Is 5.0 sp1. We are using the session persistence feature where we have given the following config <SessionDataPersist> <Enable>true</Enable> <RememberMePeriod>30</RememberMePeriod> <CleanUp> <Enable>true</Enable> <Period>5</Period> <TimeOut>35</TimeOut> </CleanUp> <Temporary>false</Temporary> </SessionDataPersist> Our observation is that after 15 min of session inactivity wso2 IS time-outs. This means that even after specifying session persistence of higher value the session

问题 I have followed the instructions here for building IS 4.6.0, in summary: SVN Checkout from: https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk06 Commented out APIMGT in $CARBON_SRC/product-releases/chunk-06/products/pom.xml Commented out SS in $CARBON_SRC/product-releases/chunk-06/products/pom.xml Run mvn clean install on $CARBON_SRC/product-releases/chunk-06/products/pom.xml Run mvn eclipse:eclipse on $CARBON_SRC/product-releases/chunk-06/products/pom.xml NOTE: I scripted

问题 configuration: WSO2ESB 4.8.0\4.8.1 OS: Linux\FreeBSD CLIENT <-> ESB <-> BACKEND here is my problem: if i create the simplest pass-through proxy to the sample service which responses with a delay of > 60 sec . i get an error when esb closes connection with the client without any response. By the way, according to the soap tracer logs ESB receives data from the backend, but connection "CLIENT <-> ESB" is already closed at that time. i tried to set these values: repository/conf/axis2/axis2

问题 A REST API has been defined ESB. What we have observed is if the json format (invalid json), the request is hanging and the server doesn't give any response. Ideally it should throw some error at least and it should not hang. 回答1: I had the same situation in WSO2 4.8.1. Try to change JsonStreamBuilder in your axis2.xml to JsonBuilder from ( org.apache.synapse.commons.json ) or use your own implementation. 来源： https://stackoverflow.com/questions/22817554/wso2-esb-server-4-7-hangs-when-an

问题 How can i configure @sink to call a soap based web api? where can i specify the soap action? reference i found online aren't working properly? @sink(type='http',publisher.url='http://localhost:8009/foo', method='{POST}',headers="'content-type:xml','content-length:94'", client.bootstrap.configuration="'client.bootstrap.socket.timeout:20', 'client.bootstrap.worker.group.size:10'", client.pool.configuration="'client.connection.pool.count:10','client.max.active.connections.per.pool:1'", @map(type

问题 The release matrix for the wso2 platform is here: http://wso2.com/products/carbon/release-matrix/ If I want to build Identity Server 4.0.0 it seems that I need carbon 4.0.3. Question 1. Will Identity Server only build on carbon 4.0.3, or will it build on 4.0.3+? I have checked out the source from: https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0 https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0 https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0 However, when

问题 I've created a pass through proxy service on top on a endpoint and selected Specify Source URL in publish wsdl options. The endpoint references to xsd's in the wsdl definition. The proxy web service generated fines, but when trying to load this web service from a client (SOAP UI), it throws an error because of the way the xsd is referenced in the proxy service wsdl URL. Sample of Actual web service with an xsd definition <types> <xsd:schema> <xsd:import namespace="http://service.example.com/"