Thanks for fixing the doc, Chanaka.
On Thu, Apr 17, 2014 at 11:47 PM, Chathurika Mahaarachchi < chathur...@wso2.com> wrote: > Thanks Chanaka for updating the document by adding correct configuration. > > Regards, > Chathurika > > > On Thu, Apr 17, 2014 at 8:07 PM, Chanaka Fernando <chana...@wso2.com>wrote: > >> Hi Sajini/Chathurika, >> >> This error occurred due to the invalid configuration in the proxy service >> as pointed out by Harsha in the previous reply. What happened here was that >> we are using a <send/> mediator in the <inSequence> without specifying the >> actual endpoint which the message needs to be sent. But in the <target> >> section, we have already defined the actual endpoint. Resolution would be >> to remove the <send/> mediator from the <inSequence>. Final correct >> configuration should be as follows. >> >> <definitions >> xmlns="http://ws.apache.org/ns/synapse";<http://ws.apache.org/ns/synapse> >> > >> <proxy >> xmlns="http://ws.apache.org/ns/synapse";<http://ws.apache.org/ns/synapse> >> name="MessageExpirationProxy" transports="https,http" statistics= >> "disable" trace="disable" startOnLoad="true"> >> <target> >> <inSequence onError="LogAndDropMessageFault"> >> <log level="full"/> >> </inSequence> >> <outSequence onError="fault"> >> <log level="full"/> >> <send/> >> </outSequence> >> <endpoint name="TimeoutEndpoint"> >> <address uri=" >> http://localhost:9000/services/SimpleStockQuoteService";<http://localhost:9000/services/SimpleStockQuoteService> >> > >> <timeout> >> <duration>30000</duration> >> <responseAction>fault</responseAction> >> </timeout> >> </address> >> </endpoint> >> </target> >> <description></description> >> </proxy> >> <sequence name="LogAndDropMessageFault"> >> <log level="full"> >> <property name="MESSAGE" value="Executing default "fault" >> sequence"/> >> <property name="ERROR_CODE" expression="get-property('ERROR_CODE')" >> /> >> <property name="ERROR_MESSAGE" expression= >> "get-property('ERROR_MESSAGE')"/> >> </log> >> <drop/> >> </sequence> >> </definitions> >> >> @Nirdesha: I have corrected the documentation link. >> >> https://docs.wso2.org/display/IntegrationPatterns/Message+Expiration >> >> Thanks, >> Chanaka >> >> >> >> >> >> On Thu, Apr 17, 2014 at 5:50 PM, Chathurika Mahaarachchi < >> chathur...@wso2.com> wrote: >> >>> I also got the same issue when running the above sample and used [1] to >>> correct the proxy service >>> >>> @ Nirdesha : Could you please update the EIP guide accordingly >>> >>> >>> [1] >>> http://charithaka.blogspot.com/2014/02/common-mistakes-to-avoid-in-wso2-esb-1.html >>> >>> >>> On Thu, Apr 17, 2014 at 5:23 PM, Harsha Kumara <hars...@wso2.com> wrote: >>> >>>> Hi Sajini, >>>> According to [1] this error cause due to having below configuration in >>>> the synapse xml. >>>> >>>> <inSequence> >>>> * <send/>* >>>> </inSequence> >>>> >>>> >>>> The error cab be avoided by adding endpoint inside send mediator as >>>> follows. >>>> >>>> <inSequence> >>>> *<send> >>>> <endpoint name="TimeoutEndpoint"> >>>> <address >>>> uri="http://localhost:9000/services/SimpleStockQuoteService >>>> <http://localhost:9000/services/SimpleStockQuoteService>"> >>>> <timeout> >>>> <duration>8000</duration> >>>> <responseAction>fault</responseAction> >>>> </timeout> >>>> </address> >>>> </endpoint> >>>> </send>* >>>> </inSequence> >>>> >>>> Seems worked fine for me. >>>> >>>> If one from ESB team can confirm this as the solution then document >>>> needs to be updated. >>>> >>>> [1]- >>>> http://charithaka.blogspot.com/2014/02/common-mistakes-to-avoid-in-wso2-esb-1.html >>>> >>>> Thanks, >>>> Harsha >>>> >>>> On Thu, Apr 17, 2014 at 4:42 PM, Sajini De Silva <saj...@wso2.com>wrote: >>>> >>>>> Hi, >>>>> >>>>> I tried out example scenario in [1] and it gave me the following >>>>> error. >>>>> >>>>> [2014-04-17 16:40:13,395] ERROR - ClientUtils The system cannot infer >>>>> the transport information from the /services/MessageExpirationProxy URL. >>>>> [2014-04-17 16:40:13,396] ERROR - Axis2Sender Unexpected error during >>>>> sending message out >>>>> org.apache.axis2.AxisFault: The system cannot infer the transport >>>>> information from the /services/MessageExpirationProxy URL. >>>>> at >>>>> org.apache.axis2.description.ClientUtils.inferOutTransport(ClientUtils.java:81) >>>>> at >>>>> org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:115) >>>>> at >>>>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149) >>>>> at >>>>> org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:482) >>>>> at >>>>> org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:59) >>>>> at >>>>> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:338) >>>>> at >>>>> org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:94) >>>>> at >>>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77) >>>>> at >>>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47) >>>>> at >>>>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131) >>>>> at >>>>> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:166) >>>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) >>>>> at >>>>> org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411) >>>>> at >>>>> org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183) >>>>> at >>>>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) >>>>> at java.lang.Thread.run(Thread.java:662) >>>>> >>>>> What could be the issue here? >>>>> >>>>> >>>>> [1] >>>>> https://docs.wso2.org/display/IntegrationPatterns/Message+Expiration >>>>> >>>>> Thank you >>>>> Sajini. >>>>> -- >>>>> Sajini De SIlva >>>>> Software Engineer; WSO2 Inc.; http://wso2.com , >>>>> Email: saj...@wso2.com >>>>> Blog: http://sajinid.blogspot.com/ >>>>> Git hub profile: https://github.com/sajinidesilva >>>>> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Harsha Kumara >>>> Software Engineer, WSO2 Inc. >>>> Mobile: +94775505618 >>>> Blog:harshcreationz.blogspot.com >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Chathurika Mahaarachchi* >>> Software Engineer, QA. >>> WSO2 Inc.: http://wso2.com/ >>> lean.enterprise.middleware >>> Mobile: +94718223950 >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> -- >> Chanaka Fernando >> Technical Lead >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> mobile: +94 773337238 >> Blog : http://soatutorials.blogspot.com >> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 >> Twitter:https://twitter.com/chanakaudaya >> Wordpress:http://chanakaudaya.wordpress.com >> >> >> >> > > > -- > *Chathurika Mahaarachchi* > Software Engineer, QA. > WSO2 Inc.: http://wso2.com/ > lean.enterprise.middleware > Mobile: +94718223950 > -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
