Hi Aliosha, The issue is ESB cannot recognize the endpoint from your proxy. Please have a look in the following blog post.
http://charithaka.blogspot.com/2014/02/common-mistakes-to-avoid-in-wso2-esb-1.html Thank you, Kesavan Yogarajah Associate Software Engineer WSO2 Inc. Mob: +94 779758021 On Mon, Mar 16, 2015 at 9:21 AM, Sriashalya Srivathsan <[email protected]> wrote: > Hi Aliosha, > For ESB 4.8.1 Script mediator is working perfectly with out any > problem.Your proxy also seems fine.If you can compare, the headers with > direct call and ESB call.I think some headers may be missed in the ESB. In > that case you want to add those additionally. > > you can go with following links > > > http://stackoverflow.com/questions/17469516/adding-user-defined-headers-in-wso2-esb-custom-proxy > > https://docs.wso2.com/display/ESB480/Sample+351%3A+Inline+script+mediation+with+JavaScript > https://docs.wso2.com/display/ESB480/Script+Mediator > > > Thank you, > Rgds, > > On Fri, Mar 13, 2015 at 8:03 PM, Aliosha <[email protected]> wrote: > >> For sake of precision about my previous email i have to say that in the >> out sequence of my proxy there is this script: >> <script language="js">var endpoint = mc.getProperty('last_endpoint'); >> >> mc.setProperty('used_endpoint',endpoint.toString());</script> >> >> suggested from you in order to trace the response IP to client requests. >> When i delete the mediator the response go fine. >> Regards. >> Alessio >> >> >> >> >> >> >> >> >> ---------- Forwarded message ---------- >> From: Aliosha <[email protected]> >> Date: 2015-03-13 14:41 GMT+01:00 >> Subject: WSO2 large JSON Parsing error >> To: [email protected], WSO2 Developers' List <[email protected]> >> >> >> Hi >> >> I'm wokring on WSO2 ESB 4.8.1. My service on application server responses >> with a 10Kb json. The json is sent serialized into bytes. The client >> request accept:application/json response. Without ESB in the middle request >> and response went fine, but when they pass throughout one ESB proxy (who >> made some operation on the jason i get this exception) >> >> TID: [0] [ESB] [2015-03-13 14:18:48,695] ERROR >> {org.apache.axis2.description.ClientUtils} - The system cannot infer the >> transport information from the xxxx URL. >> {org.apache.axis2.description.ClientUtils} >> TID: [0] [ESB] [2015-03-13 14:18:48,697] ERROR >> {org.apache.synapse.core.axis2.Axis2Sender} - Unexpected error during >> sending message out {org.apache.synapse.core.axis2.Axis2Sender} >> org.apache.axis2.AxisFault: The system cannot infer the transport >> information from XXXX 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.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:333) >> at >> org.apache.synapse.endpoints.DefaultEndpoint.send(DefaultEndpoint.java:75) >> at >> org.apache.synapse.endpoints.LoadbalanceEndpoint.send(LoadbalanceEndpoint.java:143) >> at >> org.apache.synapse.endpoints.IndirectEndpoint.send(IndirectEndpoint.java:54) >> at >> org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:97) >> 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.mediators.base.SequenceMediator.mediate(SequenceMediator.java:196) >> 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.processNonEntityEnclosingRESTHandler(ServerWorker.java:344) >> at >> org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:168) >> at >> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >> at java.lang.Thread.run(Thread.java:744) >> >> What about the library which gives this error? Is it a bug or is there a >> way to set the memory used by formatter and builder? >> >> regards. >> >> Alessio Orlando >> >> > > > -- > S.Sriashalya, > Associate Software Engineer, > WSO2. >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
