Service Callout on Response Pipeline

I know that having Service Callouts in a response pipeline is not recommended as a general rule. We have what I think is a special case.
We have situations where we would like to callout to a local proxy containing only xquery transformation steps (no business service calls, database calls, or other callouts), from the response pipeline.
In simple unit tests it works, but before we roll out this concept widely and move to production, it would be nice to know if we're likely to run into problems.
Are there any cautions from BEA about using Service Callouts on a Response Pipeline in this fashion?
Thank you,
Meghan

This is not a problem. The use of the response pipeline is only discouraged when you are using transactions.
Gregory Haardt
ALSB Prg. Manager
[email protected]

Similar Messages

  • BEA-382501- OSB Service Callout action received an unrecognized response

    Hi,
    I am getting the above response while executing the proxy service which is based on http protocol.
    I am able to get the proper response through the business service, but the same i am not able to get in proxy service.
    For this I have configured one business service based on below parameters.
    Service Type Any XML Service
    Transport Configuration
    Protocol http
    Load Balancing Algorithm round-robin
    Endpoint URI http://01hw146484:8080/SpringFileUpload/testservlet?name=pratik
    Retry Count 0
    Retry Iteration Interval 30
    Retry Application Errors Yes
    HTTP Transport Configuration
    Read Timeout 0
    Connection Timeout 0
    HTTP Request Method GET
    Authentication None
    Proxy Server
    Follow HTTP redirects Disabled
    Use Chunked Streaming Mode Enabled
    Proxy service on below parameters:
    Service Type Any XML Service
    Transport Configuration
    Protocol http
    Endpoint URI /SMSProxy/PS_SMS_BasedOnBS
    Get All Headers No
    Headers
    HTTP Transport Configuration
    HTTPS required No
    Authentication None
    Message Handling Configuration
    Transaction Required Disabled
    Same Transaction For Response Disabled
    Content Streaming Disabled
    XOP/MTOM Support Disabled
    Page Attachments to Disk No
    I am using service call out to call the business service, but not able to get the any response using the proxy. my business service is working properly.
    Please let me know where i am doing mistake.
    Edited by: truptipatil on Jan 12, 2012 3:07 PM

    Hi,
    even if I am adding a service error handler, I am getting the same error, I don't why proxy is not able to get the proper response.
    I am getting the below error.
    <BEA-000000> < [PipelinePairNode1, PipelinePairNode1_request, stage1, ERROR] <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
    <con:errorCode>BEA-382501</con:errorCode>
    <con:reason>OSB Service Callout action received an unrecognized response</con:reason>
    <con:details>
    <con1:UnrecognizedResponseDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
    <con1:http-response-code>200</con1:http-response-code>
    </con1:UnrecognizedResponseDetail>
    </con:details>
    <con:location>
    <con:node>PipelinePairNode1</con:node>
    <con:pipeline>PipelinePairNode1_request</con:pipeline>
    <con:stage>stage1</con:stage>
    <con:path>request-pipeline</con:path>
    </con:location>
    </con:fault>>
    Any help in this regards, is highly appreciated.

  • BEA-382501: ALSB Service Callout action received an unrecognized response

    I have a proxy service A, in the response pipeline it has a stage that makes a service callout to another proxy B.
    The proxy B also has a pipeline pair. If the response pipeline is empty (no actions) then I get the following error when I invoke proxy A:
    BEA-382501: ALSB Service Callout action received an unrecognized response
    If I add any action to proxy B's response pipeline (eg. log, report) everything works fine.
    Any ideas to explain this?

    Hi dear,
    I think Response of Proxy Service A is not matching with the Response of Proxy Service B. if u will leave empty Response of Proxy Service B then it will not match with the response of Proxy A.

  • BEA-382502 -- OSB Service Callout action received an error response

    Hi,
    I am trying to develope a simple application with two proxy services and Business services. The first proxy sevice communicates with the second one which in turn communicates with Business service.
    I am receving this error during the communication between the proxy services.
    I have tried enabling both "configure Soap body" and "configure payload document" to pass the request from one proxy service to other. In either case am receving the same error. Can you please help me here.
    Thanks in Advance,
    Mahi
    Edited by: Mahidhara on Sep 23, 2009 12:33 AM

    Hey all,
    I have solved problem with help of one my friend..Actually its possible through routing the service. I agree its a different approach than service callout but it acts as a quick fix.
    The key issue is to map :
    1. Request in format of Proxy service schema to Request of Business service (Legacy service-In this case Siebel)
    2. Response in format of Proxy service schema to Response of Business service (Legacy service-In this case Siebel)
    This is possible using XQuery transformation.
    Steps to achieve this::
    1. Create a XQuery by mapping proxy service schema and business service schema.
    2. Now Create message flow as following: Proxy service-->Pipeline Pair-->Stage1-->Route to business service.
    3. Now in stage1, choose Add an action-->Message processing-->Replace.
    4. In replace, do this - Replace ./* in variable body by Xquery which you created in 1.
    This will work smoothly.
    If any problems, let me know. If any insights on above, please comment.
    Will update this thread whenever I get info about service callout working. Meanwhile anybody searching for quick fix, can use this.
    Thanks and Regards,
    Swapnil Kharwadkar.

  • BEA-382500: ALSB Service Callout action received SOAP Fault response

    Hi Friends...
    <BR>
    <BR>
    <BR>
    During the implementation of TUTORIAL: 2 Loan Example of AquaLogic Service Bus 2.1,
    I am getting fault response when testing the Proxy Service. Please help me in the following....
    <BR>
    <BR>
    <BR>
    <b>BEA-382500: ALSB Service Callout action received SOAP Fault response</b>
    <BR>
    <BR>
    <BR>
    <b>error: failed to load java type corresponding to t=LoanStruct@java:normal.client</b>
    <BR>
    at
    <BR>
    <BR>
    <BR>
    <BR>
    com.bea.staxb.runtime.internal.FailFastErrorHandler.add(FailFastErrorHandler.java:45)
    at com.bea.staxb.runtime.internal.MarshalStreamUtils.addError(MarshalStreamUtils.java:274)
    at com.bea.staxb.runtime.internal.MarshalStreamUtils.addError(MarshalStreamUtils.java:249)
    at com.bea.staxb.runtime.internal.UnmarshalResult.addError(UnmarshalResult.java:140)
    at com.bea.staxb.runtime.internal.UnmarshalResult.addError(UnmarshalResult.java:124)
    at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:327)
    at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoTypeFromXsiType(UnmarshalResult.java:310)
    at com.bea.staxb.runtime.internal.RuntimeBindingType.determineActualRuntimeType(RuntimeBindingType.java:256)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalType(UnmarshalResult.java:210)
    at com.bea.staxb.runtime.internal.SoapUnmarshallerImpl.unmarshalType(SoapUnmarshallerImpl.java:93)
    at weblogic.wsee.bind.runtime.internal.EncodedDeserializerContext.unmarshalType(EncodedDeserializerContext.java:66)
    at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.internalDeserializeType(BaseDeserializerContext.java:170)
    at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeType(BaseDeserializerContext.java:87)
    at weblogic.wsee.codec.soap11.SoapDecoder.decodePart(SoapDecoder.java:401)
    at weblogic.wsee.codec.soap11.SoapDecoder.decodeParams(SoapDecoder.java:236)
    at weblogic.wsee.codec.soap11.SoapDecoder.decodeParts(SoapDecoder.java:163)
    at weblogic.wsee.codec.soap11.SoapDecoder.decode(SoapDecoder.java:116)
    at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:136)
    at weblogic.wsee.ws.dispatch.server.CodecHandler.decode(CodecHandler.java:138)
    at weblogic.wsee.ws.dispatch.server.CodecHandler.handleRequest(CodecHandler.java:39)
    at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:127)
    at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:85)
    at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
    at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
    at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
    at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:165)
    at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:84)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3214)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    <BR>
    Message was edited by:
    alwaysvaghu
    Message was edited by:
    alwaysvaghu

    I've been getting this problem as well. However, the thing that confuses me is that if I use the command-line client (as described in the tutorial), everything seems to work fine. However, if I use the test console, it fails to work (giving the fault described in an ancestor of this post).
    I've tried added a 'Rename' operation, but I just get the java1 namespace as well.
    If the problem was just the namespace issue as stated, wouldn't the command-line client have a similar problem?

  • Getting "OSB Service Callout action received SOAP Fault response" on trying to invoke a service using service callout

    I'm trying to invoke a search service using service callout . However on trying to test it , I'm getting this response
    <con:fault  xmlns:con="http://www.bea.com/wli/sb/context">
    <con:errorCode>BEA-382500</con:errorCode>
    <con:reason>
    OSB Service Callout action received SOAP Fault response
    </con:reason>
    <con:details>
    <con1:ReceivedFaultDetail  xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
    <con1:faultcode  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">soapenv:Client</con1:faultcode>
    <con1:faultstring>Cannot find dispatch method for {}</con1:faultstring>
    <con1:http-response-code>500</con1:http-response-code>
    </con1:ReceivedFaultDetail>
    Please help in resolving this error.
    Thanks,
    Rohit

    you are calling wrong  the Service.
    ¿what kind of service do you have? RPC? Document?
    ir your target service its document, I recommend this:
    1. Test target service with OSB
    2. copy XML request and XML response from the test.
    3. use XML request format that you got at Step 2 in your source service and using it at your "Service Callout".

  • What's the difference between Routing and Service Callout in ALSB?

    I am puzzled by that.
    what's the difference between them.
    Or what's the situation should use Routing, and that of service callout?

    There is little difference between routing and service callout.
    Routing is symbolizes the transition of request thread to a response thread starts. (in OSB every invocation of proxy is undertaken by different request and response threads ). So by this definition, there can be only one route node in a pipeline.
    Service call out is also used for similar actions as route node , but in pipeline. So service callout can be either in request pipeline (request thread) or in response pipeline (response thread ) . So in a proxy you can have multiple ServiceCallouts but only one route node.
    There are some other slight differences.
    Manoj

  • How to do service callout with the incoming JMS message in OSB 11g

    Hello All,
    I have a specific requirement for which I am creating a kind of POC where I need some help in OSB, however am new to OSB.
    My Environment:
    1> I have a request queue (deployed on a WLS domain) - WFReq_WS
    2> I have a response queue (deployed on a WLS domain) - WFRes_WS
    3> I have created a ProxyService (request/response type) in OSB 11g which is simply mapping the incoming message in WFReq_WS to WFRes_WS
    4> I have a WebService (it is currently a simple hello WebService for testing) which takes a string and returns the same string with an added 'Hi' in front of it (e.g. If you send Jack, it will return 'Hi Jack')
    My Requirement:
    1> I have to do some mechanism in OSB, by which while mapping the message from WFReq_WS to WFRes_WS (through the proxy service I have), it will pick the JMS message (which will be a string/text) and will make a service callout to the Webservice I mentioned using the message as the input parameter of the WebService.
    2>Now when the response of the WebService will come, OSB should send this response as the message in the response queue (WFRes_WS) I mentioned above.
    To simplify the requirement using an example:
    A> I will send a text/String message (say Jack) to the request queue (WFReq_WS)
    B> OSB should pick the message (Jack) and make a service callout to the webservice
    C> webservice will return 'Hi Jack'
    D> OSB should send this to the response queue (WFRes_WS)
    I know the above might look very basic question to the PROs, but please elaborate (step by step) what need to be done, since I do not know OSB.
    Thanks a lot for your help !

    Your example points A and D are easily done by having a "Proxy Service" which has the following details:
    Service Type = Messaging Service
    Request and Response type = Text
    Protocol = jms
    Endpoint URI = your request queue (format like 'jms://localhost:7013/weblogic.jms.XAConnectionFactory/QueueJNDIName')
    Checkmark "response" so that the proxy service automatically delivers the response to another queue - your response queue
    Response URI = jms://localhost:7013/weblogic.jms.XAConnectionFactory/QueueResponse
    Now since your "Hello" webservice is (probably) a SOAP xml service you need to "convert" your text based JMS message to xml before sending it on to the "Hello" service.
    Your JMS proxy can do that by just doing a "Assign <whom>{$body/text()}</whom>" to a variable (lets call it 'reqHello')
    Now your JMS proxy should actually call the Hello service and since your JMS proxy is text and the Hello service is SOAP you cannot just "pass" on to the Hello service in a "Route to". Instead you can do a Service Callout where you can specify your "reqHello" variable as payload and a "respHello" as response variable.
    Now you have the "<whom>Hi jack</whom>" in the response variable and since the JMS response needs to be text format you can "extract" the text value into the body variable of the JMS proxy (use "replace /* in body with $respHello/text()" - replace node contents)
    The actual Hello service is a simple "SOAP" based Proxy Service. Add a pipeline and add a stage in the reponse pipeline. Do a ...
    Assign fn:concat("Hi ",$body/whom/text()) to $whomVar
    Replace whom in body with $whomVar (replace node contents)

  • Service Callout to HTTP Post Business Service?

    Hi,
    I have created a "Business Service" with following config,
    1) Any XML Service
    2) Prtocol- HTTP
    3) HTTP Request Method- Post.
    I have created a Proxy Service , which is "Any XML Service" based on HTTP ptotocol.
    inside the message flow of proxy service i am routing to the Above Business Service passing query parameter. The business service returns an XML.
    How do i make a service callout to the business service assing a query string?
    I need this functionality to work because i have to call multiple business service (endpoint is a jsp which accepts query string) inside a proxy service and retreive xml from response , merge them and send it back to the client(invoking proxy service).
    Thanks,
    Anup

    Hi Gregory,
    In fact when i used route node to invoke a business service i modified "URL dynamically by setting the value in the pipeline variable $outbound", it worked here.
    Same i tried on Service Callout, it did not work. Also when we create a service callout action it expects us to select either "confugure soap body" or "configure payload document" followed by
    1) Request Document variable
    2) Response Document variable.
    What parameter should i set for above fields?
    Thanks,
    Anup

  • OSB Service callout losing fault info xml structure

    Hi there
    I have a proxy service (getAccount) that being called via service callout by getBilling.proxy service.
    getAccount throws a fault message that I want to catch in getBilling.
    But the original fault from getAccount somehow get lost the xml structure in the detail node. The "<" sign change into "&lt;"
    Am I missing something here. How the xml structure get lost in the detail node ?
    Here's the output:
    <soapenv:Body>
      <soapenv:Fault>
      <faultcode>soapenv:Server</faultcode>
      <faultstring>BEA-382502: OSB Service Callout action received an error response</faultstring>
      <detail>
         <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
         <con:errorCode>BEA-382502</con:errorCode>
         <con:reason>OSB Service Callout action received an error response</con:reason>
        <con:details>
           <con1:ErrorResponseDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
           <con1:detail>
              &lt;ipms:fault xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ipms="http://www.indosat.com/ipms">
              &lt;ipms:faultcode>IPMS-5000&lt;/ipms:faultcode>
              &lt;ipms:faultstring>Account Not Found&lt;/ipms:faultstring>
              &lt;ipms:faultlocation>
              &lt;ipms:faultsource>/billing-stream/proxy/getAccount&lt;/ipms:faultsource>
             &lt;ipms:faultnode>RouteTo_getAccountByMsisdn_db&lt;/ipms:faultnode>
        &lt;ipms:faultpath>response-pipeline&lt;/ipms:faultpath>
      &lt;/ipms:faultlocation>
      &lt;ipms:detail>
        &lt;con:errorCode xmlns:con="http://www.bea.com/wli/sb/context">IPMS-5000&lt;/con:errorCode>
        &lt;con:reason xmlns:con="http://www.bea.com/wli/sb/context">Account Not Found&lt;/con:reason>
        &lt;con:location xmlns:con="http://www.bea.com/wli/sb/context">
          &lt;con:node>RouteTo_getAccountByMsisdn_db&lt;/con:node>
          &lt;con:path>response-pipeline&lt;/con:path>
        &lt;/con:location>
      &lt;/ipms:detail>
    &lt;/ipms:fault>
      </con1:detail>
      </con1:ErrorResponseDetail>
      </con:details>
      <con:location>
      <con:node>PipelinePairNode1</con:node>
      <con:pipeline>PipelinePairNode1_request</con:pipeline>
      <con:stage>stage1</con:stage>
      <con:path>request-pipeline</con:path>
      </con:location>
      </con:fault>
      </detail>
      </soapenv:Fault>
    </soapenv:Body>

    What's the content-type in the HTTP 500 response from the backend service? (not OSB proxy, but the original source of the fault)
    I suspect it is text/plain or just missing. OSB doesn't know it is XML, and so it escapes it.
    Vlad

  • OSB - Error handling, report via service callout?

    I'd like to use Report Action on any error happened in my services. I'd also like to keep only one Report Action to be able to change its configuration later easily if needed.
    As it seems currently, if I add the Report Action to the Error Handler of the service directly, it logs the error code/reason/etc correctly, but if I move the Report Action to a separate service and add a service callout to the Error Handler instead of calling the Report Action directly, I lose the error information (I get the report message but error code/reason/details will be all NULL in the database).
    Am I doing something wrong here? Is that a limitation of the product? Is there any solution to keep the report actions centralized in this case?
    Thanks..

    hi guys,
    thanks for all the suggestions though it's still not working here. Hopefully clarifying the situation:
    a) service -- error handler -- report error
    b) service -- error handler -- service callout -- report error
    a) works, b) does not.
    The syndromes for not working is that the reported message has error code, reason and detail all empty (NULL if I look directly in the database). I suspect the problem is with my service callout in scenario b).
    The service callout originally was made using the following parameters:
    Request document variable: body
    Response document variable: response
    SOAP request header: header
    SOAP response header: rheader
    Reading your suggestions I tried to set the request document variable from 'body' to 'fault', but it did not help either: I get the report message but still no error information in the message.
    How exactly should this service callout look like to properly transfer the error details to the called pipeline?

  • Service callout guidance for Payload configuration..

    To all,
    Scenario:
    1. My proxy service calls Business service-A.
    2. Business service-A returns response to proxy service.
    3. Using this response + some original request fields the proxy service calls Service-B.
    4. Service-B returns the response to proxy service. Proxy service then returns this response to Client.
    I am using Proxy service--->Service callout to Business service-A and then after receiving the response from A-, the proxy service--->route to Business service-B as way to achieve above.
    The problem:
    While doing service call out to Business service-A, OSB prompts to enter following fields for "*configure SOAP Body*":
    SOAP Request Body:
    SOAP Response Body:
    SOAP Request Header:
    SOAP Response Header:
    What should I enter in this?+
    Also, what is the difference between *"Configure SOAP body"* and *"Configure Payload Parameters"*?*+
    Fields in *"Configure Payload Parameters"*:
    Request Parameters:
    SiebelMessage:
    StatusObject:
    Response Parameters:
    SiebelMessage:
    SOAP Request Header:
    SOAP Response Header:
    The Business service-A is a Siebel service.
    When i get response back, where should i store it? and how can i map the response from back end Siebel service to response desired in my schema format?
    Please help! I am a newbie here.
    Thanks and Regards,
    Swapnil Kharwadkar.
    Edited by: Swapnil Kharwadkar on May 27, 2010 1:44 AM

    Hey all,
    I have solved problem with help of one my friend..Actually its possible through routing the service. I agree its a different approach than service callout but it acts as a quick fix.
    The key issue is to map :
    1. Request in format of Proxy service schema to Request of Business service (Legacy service-In this case Siebel)
    2. Response in format of Proxy service schema to Response of Business service (Legacy service-In this case Siebel)
    This is possible using XQuery transformation.
    Steps to achieve this::
    1. Create a XQuery by mapping proxy service schema and business service schema.
    2. Now Create message flow as following: Proxy service-->Pipeline Pair-->Stage1-->Route to business service.
    3. Now in stage1, choose Add an action-->Message processing-->Replace.
    4. In replace, do this - Replace ./* in variable body by Xquery which you created in 1.
    This will work smoothly.
    If any problems, let me know. If any insights on above, please comment.
    Will update this thread whenever I get info about service callout working. Meanwhile anybody searching for quick fix, can use this.
    Thanks and Regards,
    Swapnil Kharwadkar.

  • How to do a service callout to a service with/without MTOM support

    I have a problem trying to call a business service from a proxy service as a service callout related to MTOM.
    Specifically, the service I have is a Java based web service with the following signature:
    void archive(byte[] bytes, String fileName)
    When the WSDL is generated it maps the byte array to base64Binary as follows:
    <xs:element name="archive">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="bytes" type="xs:base64Binary"/>
    <xs:element name="fileName" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    Now in order to call this I try to build the XML payload withint the proxy message flow and I get this (from the logger):
    <8/06/2009 01:07:12 PM NZST> <Debug> <AlsbStagesTransformRuntime> <BEA-000000> <Service callout request payload:
    <archive xmlns="http://mtm.oracle.com/tools">
    <bytes>
    <con:binary-content ref="cid:518df4b0:121bd6029c5:-7fd9" xmlns:con="http://www.bea.com/wli/sb/context"/>
    </bytes>
    <fileName>RQRETMAINT20090608130711.csv</fileName>
    </archive>
    as you can see the bytes are being passed by reference and then when the service is called I get the following ("*non-MTOM endpoint received a MTOM message*") error:
    <8/06/2009 01:07:13 PM NZST> <Debug> <AlsbPipeline> <BEA-000000> <RegistryOutbound_SB_New/ProxyServices/ftpRqRetMaintToRegistry: +PipelineContextImpl.generateFault - messageID:2169050999921023879-518df4b0.121bd6029c5.-7fdc, errorCode:BEA-382500, errorReason:OSB Service Callout action received SOAP Fault response, errorDetails:<xml-fragment xmlns:con="http://www.bea.com/wli/sb/stages/transform/config">
    <con:faultcode xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">soapenv:Server</con:faultcode>
    <con:faultstring>[Server CodecHandler] Failed to decode
    -> non-MTOM endpoint received a MTOM message</con:faultstring>
    <con:detail>
    <bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">weblogic.wsee.codec.CodecException: non-MTOM endpoint received a MTOM message
         at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:170)
         at etc
    </bea_fault:stacktrace>
    </con:detail>
    <con:http-response-code>500</con:http-response-code>
    </xml-fragment>>
    So it seems the business service expects the "bytes" passed by value whereas the proxy is passing by reference. I tried changing the proxy to not use MTOM by disabling XOP/MTOM support in the Message Content tab (actually I did this in the proxy that calls the one in question since it uses the local transport and so doesn't have such a tab) and leaving it enabled but pass by value and it had no effect for some reason.
    I've read the User Guide section on MTOM support but it was not that helpful so any pointers to better information would be much appreciated.
    regards
    Edited by: mdsrobbins on Jun 8, 2009 1:44 PM

    Can you test back-end MTOM end point through a route node and see if its working? I doubt the issue has nothing to do with SC but with the MTOM end-point implementation.
    non-MTOM endpoint received a MTOM message") error: hints that the service call out is sending a mtom message but the end-point is not accepting the message
    Manoj
    Edited by: mneelapu on Jun 8, 2009 11:25 AM

  • OSB Service Callouts - HTTP Threads

    Hi All,
    We are having issues with OSB service callouts calling the business services from the Proxy Services. Due to excessive usage of Service Callouts, the proxy services are hanging out in the OSB server. From the Proxy services,we could able to successfully invoke the business services ( SOA Composistes , EJB Webservices etc ) and the webservices are taking few milliseconds to process the requests,but the response is not reaching the OSB Proxy Service. Ideally the behaviour is not happening for all requests, but for few messages. We have set up a dedicated Worker manager ( 10 Min Threads ) in the Admin Console and mapped the Worker manager to the business services ( dispatch policy ),but with no luck. We have followed the below link and its not working.
    http://allthingsmdw.blogspot.co.uk/2012/09/osb-service-callouts-and-oql-part-3.html
    Request to help us incase if you happen to see this behavior earlier.
    Thanks,
    Phani

    Hi Phani,
    It is a known issue with ALSB/OSB. There is a documentation in oracle as well regarding that "ALSB/OSB - Proxy Service Callout Causes Stuck Threads Under High Load [ID 861724.1]".
    Symptoms
    Stuck threads when calling a proxy service with a service callout /publish under high load. Proxy services using only ROUTE work without problems.
    Cause
    The service callout instantiates a new thread.
    As the proxy services are running in the default thread pool there will be no thread available for the callout under high load because all threads are blocked by the proxy services waiting for the response.
    This is expected behavior when using a service callout action and can be resolved by correct thread tuning.
    Solution
    A separate Workmanager needs to be configured for the Proxy service. This can be done by using the Dispatch Policy for specific proxy services (JMS, WS ..).
    For detailed information go to the OSB transport specific documentation and look for Dispatch Policy.
    There you will also see the link to the WLS Workmanager documentation.
    Please create a Workmanager using <max-threads-constraint> to limit the number of parallel executing proxies.
    Using this configuration the proxy will not block threads in the default queue.
    The service callout will still use the threads from the default thread pool.
    Hope this helps.
    Regards,
    Karan
    http://learn-oraclesoa.blogspot.com/

  • Service Callout Action in OSB

    Hi ,
    Good morning to all
    I have issue on osb service callout.
    1. i developed a synchronous service using bpel after that i invoke that service in osb as business service. my aim by using service callout action to call that service and get response.
    but the problem is how pass the osb input request to bpel input request and also how to transform the bpel response data to osb response data...
    Thanks and regards
    venky

    Venky,
    the problem is how pass the osb input request to bpel input request and also how to transform the bpel response data to osb response data...You can transform the OSB request structure to bpel service request structure using Xquery/Xslt transformations either by using replace action or assign action ( replacing the $body as per Bpel request format ) before sending the request to Bpel in service call out.
    And in similar manner after getting the response from Bpel service use Xquery/Xslt transformation & using replace action to transform bpel response back to OSB response format.
    Regards,
    Abhinav Gupta
    Edited by: Abhinav on Dec 5, 2012 11:49 AM

Maybe you are looking for

  • Trying to update iphone from ios4.x to 5.x moved iphoto

    Moved Iphoto and Itunes libraries to external drive with 700 GB+ available (Those applications won't open anything without the drive hooked up-I think those moves are legit.) when I click the button in itunes that says " a newer version of the iphone

  • Empty trash stuck in infinite loop....

    I just upgraded to Mtn Lion and I have a hard drive with time machine back up from a leopard machine, I wanted to delete that, and use the drive with Mtn lion, I put the backups folder into trash and tried to empty it, it is stuck in an infinite loop

  • HT1660 I'm getting a message that reads 'The iTunes Library file cannot be saved. You do not have enough access privileges for this operation." Why is this? And how can I fix it?

    I'm getting a message that reads 'The iTunes Library file cannot be saved. You do not have enough access privileges for this operation." Why is this? And how can I fix it? I'm worried that I'm going to lose my entire library because of this.

  • Formatting of workitem text

    Hi, while sending the workitem to SAP inbox,i am sending the approver hierachy list with the position and status like Manager->Name1->approved vice president->name2->waiting for approval I want this text has to be foramtted Manager--name1-- approved

  • Issue in ALV reporting

    Dear All, I have an issue in ALV reporting. Pls look at the follow table. <u>Duty Post</u>      <u>Date</u>          <u>Time</u> jurong                   12/06                3.45 jurong                   13/06                3.50 jurong