OSB 10.3 MTOM problems.

Guys,
I am trying to get MTOM working in the osb. Elas, with a lot of problems.
To make things easier, I started a small test project but also that I cannot get to work.
I have an incoming message with a MTOM attachment. I need to get the binary from the request and save it to file.
But I cannot get it to file. Changing my Business Service to http instead of file , I can get the message to TCPMON. There I see the request contains the right data.
In my proxy I have MTOM, by reference turned on.
Can u guys , give me a clue of how to do it? What other info can I give u?
I have the following WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="XrayStorage" targetNamespace="http://mediStor.org/x-rays"
     xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://mediStor.org/x-rays"
     xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:xsd1="http://mediStor.org/types/"
     xmlns:xmime="http://www.w3.org/2005/05/xmlmime"
     xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <types>
          <schema targetNamespace="http://mediStor.org/types/" xmlns="http://www.w3.org/2001/XMLSchema">
               <complexType name="xRayType">
                    <sequence>
                         <element name="patientName" type="xsd:string" />
                         <element name="patientNumber" type="xsd:int" />
                         <element name="imageData" type="xsd:base64Binary"
                              xmime:expectedContentTypes="application/octet-stream" />
                    </sequence>
               </complexType>
               <element name="xRay" type="xsd1:xRayType" />
          </schema>
     </types>
     <message name="storRequest">
          <part name="record" element="xsd1:xRay" />
     </message>
     <message name="storResponse">
          <part name="success" type="xsd:boolean" />
     </message>
     <portType name="xRayStorage">
          <operation name="store">
               <input message="tns:storRequest" name="storRequest" />
               <output message="tns:storResponse" name="storResponse" />
          </operation>
     </portType>
     <binding name="xRayStorageSOAPBinding" type="tns:xRayStorage">
          <soap12:binding style="document"
               transport="http://schemas.xmlsoap.org/soap/http" />
          <operation name="store">
               <soap12:operation soapAction="" style="document" />
               <input name="storRequest">
                    <soap12:body use="literal" />
               </input>
               <output name="storResponse">
                    <soap12:body use="literal" />
               </output>
          </operation>
     </binding>
     <service name="xRayStorageService">
          <port binding="tns:xRayStorageSOAPBinding" name="xRayStoragePort">
               <soap12:address location="http://localhost:8080/xRay-1/xRayStorage" />
          </port>
     </service>
</definitions>

Do a backup, using either Time Machine or a cloning program, to ensure files/data can be recovered. Two backups are better than one. 
Try setting up another admin user account to see if the same problem continues. If Back-to-My Mac is selected in System Preferences, the Guest account will not work. The intent is to see if it is specific to one account or a system wide problem. This account can be deleted later.
Isolating an issue by using another user account
Try booting into the Safe Mode using your normal account.  Disconnect all peripherals except those needed for the test. Shut down the computer and then power it back up after waiting 10 seconds. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear and again when you log in. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. When you reboot normally, the initial reboot may be slower than normal. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart by using the application un-installer. For each disable/delete, you will need to restart if you don’t do them all at once.
Safe Mode - About
Safe Mode - Yosemite

Similar Messages

  • OSB - Business Service Import Problem

    Hi,
    When I import my OSB project (from an Oracle Service Bus Configuration .jar) for the first time, it imports my business service perfectly. However, in the second half when the project already exists on the workspace, new tags are added to the xml even though I have not made any changes in the business service.
    Thats my problem:
    First Import:
    <ser:coreEntry isProxy="false" isEnabled="true">
    After Second Import:
    <ser:coreEntry isProxy="false" isEnabled="true" isTracingEnabled="false">
    and a few other tags are added to the file:
    <ser:throttling enabled="false">
    <ser:capacity>0</ser:capacity>
    <ser:maxQueueLength>0</ser:maxQueueLength>
    <ser:timeToLive>0</ser:timeToLive>
    </ser:throttling>
    <tran:delay-interval-configuration isEnabled="false">
    <tran:delay-interval>0</tran:delay-interval>
    </tran:delay-interval-configuration>
    Any help on how to import the project without these new tags in my business service will be very welcome.
    Regards,
    Ricardo Azevedo

    you can influence the amount of info actually imported choosing to override operational settings, environment setting etc (I can't remember by heart and I am too lazy to start my server now and verify)
    Anyway unless this impacts your operations I would not be too worried that some defaults are explicitly stated in the xml. Surely if you import in Production a BS with "message tracing" on, this can affect seriously your performance.

  • OSB 11g - Conditional Branch Problem using attribute selection

    Folks,
    Came across a problem using OSB Conditional Branch using attribute selection, it fails & is most likely a bug. It was bug in ALSB2.5 but read in forums was fixed in ALSB 2.6
    things I am doing -
    1. In the Msg Flow, Conditional branch is @ the start of the flow
    Xpath :- ./cm:processLineItem/cm:lineItem/@actionCode
    In-Variable: - body
    Label: - MODIFY
    Operator:- =
    Value:- 'Modify'
    It fails with BEA-382000 error Code
    <con:errorCode>BEA-382000</con:errorCode>
         <con:reason>
         com.bea.wli.sb.stages.StageException: {bea-err}TYPE003: Runtime Type Mismatch
         </con:reason>
    What could be wrong with Xpath or is it a Bug ?
    Thanks,
    Abhijeet

    Hi Abhijeet,
    Your case is re-producible. It may be a bug.
    BTW, I have noticed a strange behaviour -
    1. If there is only one attribute then it works fine (<cus:lineItem actionCode="Modify")
    2. If the attribute which you want to refer in selection, is in the last then also it works fine (<cus:lineItem priorityRanking="201" quantity="1"> actionCode="Modify")
    So I will suggest you to raise a case with support and meanwhile as a workaround I would suggest you to use actionCode attribute in the last of lineItem node. So your XML should be like -
    <soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <cus:processLineItem xmlns:com="http://vodafone.com.au/ebo/vha/CommonComponents" xmlns:cus="http://vodafone.com.au/cm/ocv/ebm/CustomerOrder" xmlns:cus1="http://vodafone.com.au/ebo/vha/CustomerManagement">
    <com:header>
    <com:createDateTime>2008-09-29T11:49:45</com:createDateTime>
    <!--Optional:-->
    <com:webUser>test</com:webUser>
    <com:channel>string</com:channel>
    <com:applicationName>string</com:applicationName>
    <com:businessIdentifier>string</com:businessIdentifier>
    <!--Optional:-->
    <com:entityIdentifier>string</com:entityIdentifier>
    <!--Optional:-->
    <com:sourceIdentifier>string</com:sourceIdentifier>
    <!--Optional:-->
    <com:statusCode>Success</com:statusCode>
    <!--Optional:-->
    <com:messageIdentifier>string</com:messageIdentifier>
    </com:header>
    <cus:lineItem priorityRanking="201" quantity="1" actionCode="Modify">
    <!--You have a CHOICE of the next 3 items at this level-->
    <!--Optional:-->
    <cus1:product ID="string">
    <!--Zero or more repetitions:-->
    <cus1:attribute>
    <com:name>test</com:name>
    <com:value>test1</com:value>
    </cus1:attribute>
    </cus1:product>
    </cus:lineItem>
    </cus:processLineItem>
    </soapenv:Body>
    Regards,
    Anuj

  • OSB proxy mail read problem from inbox

    Hi,
    I have made one osb process.It is reading data from one particular mailbox.For that I have configured one proxy,and mentioned one service account in that proxy configuration.It is working fine in my local server and printing logs(I have put some log activity in message flow).
    But when I deployed it to one cluster env,It is not printing anything in logs.But I think it is reading data from mailbox.I have set post read action to archive and the mails are archived properly in cluster env,so I am assuming that osb proxy is reading mails.
    Anybody has any idea of the above problem?

    Did you check in weblogic console, if you click in your proxy service (the one which consumes from email server) -> Operational settings, is logging enabled?
    In your pipeline, are you logging at the end of the message flow? Do you mind adding a global exception handing and log there as well?
    This is what I can think of. Otherwise, try to use a report action from your proxy, just to see if the issue is the logging or the consumption.
    If none of this work, I would stop of the managed servers, leave only one running. Then you have a couple of options: Enable tracing or run a tcpdump. These 2 will be the source of truth of what is going on.
    Regards,
    Fabio Douek

  • [OSB] Calling a secured proxy from another secured proxy

    Hi,
    I would like to call a secured proxy from another secured proxy. However, the call fails.
    I'm making a call from a Java stand alone Web Service client. The client uses policy "oracle/wss11_message_protection_client_policy".
    The call is made to a proxy secured with a "oracle/wss11_x509_token_with_message_protection_service_policy". The secured proxy routes to a non secured proxy, which does not process WSS Security Header. The non-secured proxy then routes to a non-secured business service. The call is a success.
    Then I add a policy to the second proxy, say "oracle/log_policy". Also I set the value of "Process WS-Security Header" to yes. The call fails.
    I'm getting
    java.lang.NullPointerException
         at oracle.wsm.agent.handler.WSMEngineInvoker.createWsmMessageContextFromInvokerContext(WSMEngineInvoker.java:733)
    in the osb logs.
    I have tried adding an empty WSS Security Header in the Soa headers before calling the second proxy. It didn't change anything.
    Do you have any ideas?
    I have also came up with a super simplified sitution when this error comes up. This happens when I'm calling a pass through proxy (no policy, process WSS security header set to no). Then when this proxy calls a secured proxy with "oracle/log_policy", the call results in this error. Why??
    Here is the OSB output when the problem occurs:
    ####<2011-11-21 13:00:46 CET> <Info> <OSB Kernel> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846831> <BEA-398077> <
    [OSB Tracing] Entering proxy MyProject/ProxyServices/MyFirstProxyService with message context:
    [MessageContextImpl  body="<soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"/>"
    operation="null"
    attachments="<con:attachments xmlns:con="http://www.bea.com/wli/sb/context"/>"
    outbound="null"
    fault="null"
    inbound="<con:endpoint name="ProxyService$MyProject$ProxyServices$MyFirstProxyService" xmlns:con="http://www.bea.com/wli/sb/context">
      <con:service/>
      <con:transport/>
      <con:security/>
    </con:endpoint>"
    header="<soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"/>"
    ]>
    ####<2011-11-21 13:00:46 CET> <Info> <OSB Kernel> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846832> <BEA-398200> <
    [OSB Tracing] Inbound request was received.
    Service Ref = MyProject/ProxyServices/MyFirstProxyService
    URI = /MyProject/ProxyServices/MyFirstProxyService
    Message ID = 3657493765399211266-5215cc49.133c5a81e20.-7f81
    Request metadata =
    <xml-fragment>
    <tran:headers xsi:type="http:HttpRequestHeaders" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <http:Accept>text/xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2</http:Accept>
    <http:Connection>keep-alive</http:Connection>
    <http:Content-Length>7614</http:Content-Length>
    <http:Content-Type>text/xml;charset="utf-8"</http:Content-Type>
    <http:Host>myLaptop:8011</http:Host>
    <http:SOAPAction>"execute"</http:SOAPAction>
    <http:User-Agent>Oracle JAX-WS 2.1.5</http:User-Agent>
    </tran:headers>
    <tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">utf-8</tran:encoding>
    <http:client-host xmlns:http="http://www.bea.com/wli/sb/transports/http">myLaptop</http:client-host>
    <http:client-address xmlns:http="http://www.bea.com/wli/sb/transports/http">192.168.148.155</http:client-address>
    <http:http-method xmlns:http="http://www.bea.com/wli/sb/transports/http">POST</http:http-method>
    </xml-fragment>
    Payload =
    <?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Header><wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" S:mustUnderstand="1"><wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Timestamp-Tt0jQKXTNFAd6lUGgmYuPA22"><wsu:Created>2011-11-21T12:00:46Z</wsu:Created><wsu:Expires>2011-11-21T20:00:46Z</wsu:Expires></wsu:Timestamp><wsse:BinarySecurityToken xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v1" wsu:Id="BST-q10SkWxeoYTKKaeyCSmomA22">MIICpDCCAYwCAQcwDQYJKoZIhvcNAQEEBQAwdDELMAkGA1UEBhMCUEwxFDASBgNVBAgTC01hem93aWVja2llMQ8wDQYDVQQHEwZXYXJzYXcxETAPBgNVBAoTCGluNG1hdGVzMQswCQYDVQQDEwJDQTEeMBwGCSqGSIb3DQEJARYPY2FAaW40bWF0ZXMuY29tMB4XDTExMTExODEyMzgyN1oXDTEyMTExNzEyMzgyN1owQDELMAkGA1UEBhMCUEwxDzANBgNVBAcTBldhcnNhdzERMA8GA1UEChMISW40bWF0ZXMxDTALBgNVBAMTBGFwcGEwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAJdFSnlREuzVIQKvmzcD6YCgzvvshHXGG6MQJtM8HvkYUcwEP7xIn1TYfD/A6J6+lIpxa7SBqQ2PO/Y4OCSeOJDbhm2bkwLWPWlcy1CCxfQcup/ylrkWVO5EYT+5dg+LxBcHAzh4trzICvy8Qxw81AsEVsy0O6un6qanx8/gcNWXAgMBAAEwDQYJKoZIhvcNAQEEBQADggEBADqMZWnIeOPhycUE4S5zaFp50cYMR/0wb89k0iOTD/k3Fmy4SHqpvmx3AJQ1vBrlP6z7TyycOTA7yVUXDfy6xdLWg26W+5SdQNCv/vf1OIS2cwIXrxcUgrOs4TNmdubzSqO6WCQCngUz+oGQbAqRr/gmiYukT7oW7DmsXKMdsd9vI9gHSqpy3kGrqvTOO3MYkS50xdS59aKoMA9OYKbBp3sjCGJT7h5pytTARH6BfPuKNR+r6bUZ6sq3BScY7umjVO3egkDGqAD/PFI5UCSi3qic2cfHQn1+nnME7AJ2zqEGTKD5ASevZE95ndkFVqZt6YFNQ9SHf6Jx4jNC5FSFCaI=</wsse:BinarySecurityToken><xenc:EncryptedKey xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Id="EK-N74ve0QpUQxEpFgJc9YR0A22"><xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"><dsig:DigestMethod xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/></xenc:EncryptionMethod><dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><wsse:SecurityTokenReference xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><wsse:KeyIdentifier xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1">rbWc2O0Y7yBBsPYkcHOgqxuF3t4=</wsse:KeyIdentifier></wsse:SecurityTokenReference></dsig:KeyInfo><xenc:CipherData><xenc:CipherValue>RGltJV8OQehqBg9EDaae0SO1lH1zBrlrn3/JwSljOPzwwFum9zCzFsu8Gpz05Q9R+Yaz2QXMDpghYuDvcomqDmkANYBrmIQHKKyWCCu8xvGF78jcwEp+RS+e3oy9suejGwUViYGlU4zkIRpGba6xjdkAQsRkX1mWRYMQvrfs/cM=</xenc:CipherValue></xenc:CipherData><xenc:ReferenceList><xenc:DataReference URI="#_igoSptS7UdOzwe4gYy18qg22"/></xenc:ReferenceList></xenc:EncryptedKey><dsig:Signature xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:SignedInfo><dsig:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/><dsig:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/><dsig:Reference URI="#BST-q10SkWxeoYTKKaeyCSmomA22"><dsig:Transforms><dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><dsig:DigestValue>GBpMSv85l75tSIZDG9WiKp3rHvM=</dsig:DigestValue></dsig:Reference><dsig:Reference URI="#XSIG-eKzAOdtEBafB7pzBx01wMw22"><dsig:Transforms><dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><dsig:DigestValue>mEMP/yHb3k474vnbgn3IBvhJqZM=</dsig:DigestValue></dsig:Reference></dsig:SignedInfo><dsig:SignatureValue>ELM50yvmDvJzIH/jpId3LSae1cCtboFau5I4Z8Cws+vZU6JD994hRnaWIFqxxK5vVVIUVu9mKg9+p/QJp8g7SMvhOYBIqRsHKY/2vKGZ36BrcUSXOofDNwV7l9QUzWw0dyV51N/pHX7+PTF9whPgZh48SXdpmU6MV0UkPCXAixA=</dsig:SignatureValue><dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" Id="KeyInfo-SLUCjT2uaAlI9n0spmTgnw22"><wsse:SecurityTokenReference xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><wsse:Reference xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" URI="#BST-q10SkWxeoYTKKaeyCSmomA22" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v1"/></wsse:SecurityTokenReference></dsig:KeyInfo></dsig:Signature><dsig:Signature xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" Id="XSIG-eKzAOdtEBafB7pzBx01wMw22"><dsig:SignedInfo><dsig:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/><dsig:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1"/><dsig:Reference URI="#Timestamp-Tt0jQKXTNFAd6lUGgmYuPA22"><dsig:Transforms><dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><dsig:DigestValue>AliE9el9Dmmw3U5W69/zn6QVZEo=</dsig:DigestValue></dsig:Reference><dsig:Reference URI="#Body-ogLysWiLTgk5UjAaaIhIvg22"><dsig:Transforms><dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><dsig:DigestValue>wJaIENiwWQg/B2MW6Q0xdLAzCRM=</dsig:DigestValue></dsig:Reference></dsig:SignedInfo><dsig:SignatureValue>4k1bNpdK7AaAk296wzFi63dRgwA=</dsig:SignatureValue><dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><wsse:SecurityTokenReference xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><wsse:Reference xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" URI="#EK-N74ve0QpUQxEpFgJc9YR0A22" ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#EncryptedKey"/></wsse:SecurityTokenReference></dsig:KeyInfo></dsig:Signature></wsse:Security></S:Header><S:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Body-ogLysWiLTgk5UjAaaIhIvg22"><xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Id="_igoSptS7UdOzwe4gYy18qg22" Type="http://www.w3.org/2001/04/xmlenc#Content"><xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc"/><dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><wsse:SecurityTokenReference xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><wsse:Reference xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" URI="#EK-N74ve0QpUQxEpFgJc9YR0A22" ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#EncryptedKey"/></wsse:SecurityTokenReference></dsig:KeyInfo><xenc:CipherData><xenc:CipherValue>vcPRlrky4U7GunHF3pYWFCGrEofmAecajIXIT1+YgBdIJTb8gt7g0GMZyBXGqu29WY+rQajArCajet+pTUeKkUHA3qi9oRmL8wEJkFM858fAyejzxeBWDPBI9C1sjcf+OKGAP4jr3nQzSfzl58d8IhH2uT0uUHD3h/i1pcQuSI/sXAgBb+YblR4+SwQJ6LLBHMTyuymEngoY4KVyI3UYMqePQQQjmD0dXt87Ld1xAOXgWhWRTrnoc48Nq85HQf0qWLyrdXIq9MvXeKc0CDmbLMdKUFWaGdTdNaTNH2iBM5ZEtk4qO4hbJFVU3zczKUhyYa+JzBFi0NCMHKnKCpF2TQ==</xenc:CipherValue></xenc:CipherData></xenc:EncryptedData></S:Body></S:Envelope>
    >
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846832> <BEA-000000> <WssHandlerImpl.doInboundRequest>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846833> <BEA-000000> <WsmInboundHandler.processRequest>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846833> <BEA-000000> <Got SOAP Message Factory from the Provider: oracle.j2ee.ws.saaj.soap.MessageFactoryImpl@1a99544>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846834> <BEA-000000> <WsmInboundHandler.processRequest()->WSMMessageContext[oracle.integration.platform.request.processed.headers]=[]>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846834> <BEA-000000> <WsmInboundHandler.processRequest()->WSMMessageContext[com.bea.contextelement.alsb.router.inbound.request.metadata.http.client-host]=myLaptop>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846834> <BEA-000000> <WsmInboundHandler.processRequest()->WSMMessageContext[com.bea.contextelement.alsb.router.inbound.request.MessageId]=3657493765399211266-5215cc49.133c5a81e20.-7f81>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846834> <BEA-000000> <WsmInboundHandler.processRequest()->WSMMessageContext[com.bea.contextelement.alsb.router.inbound.request.CharacterEncoding]=utf-8>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846834> <BEA-000000> <WsmInboundHandler.processRequest()->WSMMessageContext[com.bea.contextelement.alsb.router.inbound.TransportProvider]=http>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846834> <BEA-000000> <WsmInboundHandler.processRequest()->WSMMessageContext[com.bea.contextelement.alsb.router.ServiceVersion]=-8022206267159469084>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846835> <BEA-000000> <WsmInboundHandler.processRequest()->WSMMessageContext[com.bea.contextelement.alsb.router.inbound.request.headers.http.Content-Type]=text/xml;charset="utf-8">
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846835> <BEA-000000> <WsmInboundHandler.processRequest()->WSMMessageContext[com.bea.contextelement.alsb.router.ServiceUri]=/MyProject/ProxyServices/MyFirstProxyService>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846835> <BEA-000000> <WsmInboundHandler.processRequest()->WSMMessageContext[com.bea.contextelement.alsb.router.inbound.request.metadata.http.client-address]=192.168.148.155>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846835> <BEA-000000> <WsmInboundHandler.processRequest()->WSMMessageContext[com.bea.contextelement.alsb.router.ProxyService]=MyProject/ProxyServices/MyFirstProxyService>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846835> <BEA-000000> <WsmInboundHandler.processRequest()->WSMMessageContext[com.bea.contextelement.alsb.router.inbound.request.headers.http.SOAPAction]="execute">
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846835> <BEA-000000> <WsmInboundHandler.processRequest()->WSMMessageContext[com.bea.contextelement.alsb.router.inbound.MessagePattern]=SYNCHRONOUS>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846835> <BEA-000000> <WsmInboundHandler.processRequest()->WSMMessageContext[com.bea.contextelement.wli.Message]=org.apache.xmlbeans.impl.store.Saver$InputStreamSaver@211082>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846835> <BEA-000000> <WsmInboundHandler.processRequest()->WSMMessageContext[com.bea.contextelement.alsb.router.inbound.IsTransactional]=false>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846835> <BEA-000000> <invoking WSM Engine's handleRequest()...>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846856> <BEA-000000> <storing the new message in the router message context>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846856> <BEA-000000> <getting subject out of WSSecurityContext>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846856> <BEA-000000> <doing message-level access control (wss-active-intermediary: true; has-custom-message-level-authentication: false)>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846857> <BEA-000000> <calling isAccessAllowed; resource: 'type=<alsb-proxy-service>, path=MyProject/ProxyServices, proxy=MyFirstProxyService, action=wss-invoke, operation=execute', Subject: 1
         Principal = class weblogic.security.principal.WLSUserImpl("myPrincipal")
    >
    ####<2011-11-21 13:00:46 CET> <Info> <OSB Security> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846857> <BEA-387027> <Message-level access control policy grants access to proxy "MyProject/ProxyServices/MyFirstProxyService", operation "execute", message-id: 3657493765399211266-5215cc49.133c5a81e20.-7f81, subject: Subject: 1
         Principal = class weblogic.security.principal.WLSUserImpl("myPrincipal")
    .>
    ####<2011-11-21 13:00:46 CET> <Info> <OSB Kernel> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846858> <BEA-398078> <
    [OSB Tracing] Entering route node RouteToMySecondProxyService with message context:
    [MessageContextImpl  body="<S:Body wsu:Id="Body-ogLysWiLTgk5UjAaaIhIvg22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
      <processRequest xmlns="http://www.in4mates.com/targetNamespace"/>
    </S:Body>"
    operation="execute"
    messageID="3657493765399211266-5215cc49.133c5a81e20.-7f81"
    attachments="<con:attachments xmlns:con="http://www.bea.com/wli/sb/context"/>"
    outbound="null"
    fault="null"
    inbound="<con:endpoint name="ProxyService$MyProject$ProxyServices$MyFirstProxyService" xmlns:con="http://www.bea.com/wli/sb/context">
      <con:service>
        <con:operation>execute</con:operation>
      </con:service>
      <con:transport>
        <con:uri>/MyProject/ProxyServices/MyFirstProxyService</con:uri>
        <con:mode>request-response</con:mode>
        <con:qualityOfService>best-effort</con:qualityOfService>
        <con:request xsi:type="http:HttpRequestMetaData" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
          <tran:headers xsi:type="http:HttpRequestHeaders" xmlns:tran="http://www.bea.com/wli/sb/transports">
            <http:Accept>text/xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2</http:Accept>
            <http:Connection>keep-alive</http:Connection>
            <http:Content-Length>7614</http:Content-Length>
            <http:Content-Type>text/xml;charset="utf-8"</http:Content-Type>
            <http:Host>myLaptop:8011</http:Host>
            <http:SOAPAction>"execute"</http:SOAPAction>
            <http:User-Agent>Oracle JAX-WS 2.1.5</http:User-Agent>
          </tran:headers>
          <tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">utf-8</tran:encoding>
          <http:client-host>myLaptop</http:client-host>
          <http:client-address>192.168.148.155</http:client-address>
          <http:http-method>POST</http:http-method>
        </con:request>
        <con:response xsi:type="http:HttpResponseMetaData" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
          <tran:headers xsi:type="http:HttpResponseHeaders" xmlns:tran="http://www.bea.com/wli/sb/transports">
            <http:Content-Type>text/xml</http:Content-Type>
          </tran:headers>
          <tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">0</tran:response-code>
        </con:response>
      </con:transport>
      <con:security>
        <con:transportClient>
          <con:username>&lt;anonymous></con:username>
        </con:transportClient>
        <con:messageLevelClient>
          <con:username>myPrincipal</con:username>
        </con:messageLevelClient>
      </con:security>
    </con:endpoint>"
    header="<S:Header xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"/>"
    ]>
    Edited by: user13604541 on Nov 21, 2011 4:27 AM

    This is the rest of log:
    ####<2011-11-21 13:00:46 CET> <Info> <OSB Kernel> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846860> <BEA-398072> <
    [OSB Tracing] Routing to MyProject/ProxyServices/MySecondProxyService with message context:
    $body = <S:Body wsu:Id="Body-ogLysWiLTgk5UjAaaIhIvg22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
    <processRequest xmlns="http://www.in4mates.com/targetNamespace"/>
    </S:Body>
    $header = <S:Header xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"/>
    $attachments = <con:attachments xmlns:con="http://www.bea.com/wli/sb/context"/>
    >
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846860> <BEA-000000> <WssHandlerImpl.doOutboundRequest>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846860> <BEA-000000> <WsmOutboundHandler.processRequest>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846860> <BEA-000000> <target operation: execute>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846860> <BEA-000000> <Got SOAP Message Factory from the Provider: oracle.j2ee.ws.saaj.soap.MessageFactoryImpl@1a99544>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846860> <BEA-000000> <invoking WSM Engine's Client Agent.>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846861> <BEA-000000> <invoking WSM Engine's handleRequest()>
    ####<2011-11-21 13:00:46 CET> <Debug> <AlsbSecurityWss> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846861> <BEA-000000> <unexpected exception
    java.lang.NullPointerException
         at oracle.wsm.agent.handler.WSMEngineInvoker.createWsmMessageContextFromInvokerContext(WSMEngineInvoker.java:733)
         at oracle.wsm.agent.handler.WSMEngineInvoker.handleRequest(WSMEngineInvoker.java:359)
         at com.bea.wli.sb.security.wss.wsm.WsmOutboundHandler$1.run(WsmOutboundHandler.java:141)
         at com.bea.wli.sb.security.wss.wsm.WsmOutboundHandler$1.run(WsmOutboundHandler.java:139)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.security.wss.wsm.WsmOutboundHandler.processRequest(WsmOutboundHandler.java:138)
         at com.bea.wli.sb.security.wss.WssHandlerImpl.doOutboundRequest(WssHandlerImpl.java:992)
         at com.bea.wli.sb.context.BindingLayerImpl.createTransportSender(BindingLayerImpl.java:532)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.doDispatch(PipelineContextImpl.java:521)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:501)
         at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:128)
         at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
         at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
         at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
         at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
         at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
         at com.bea.wli.sb.transports.http.generic.RequestHelperBase$1.run(RequestHelperBase.java:154)
         at com.bea.wli.sb.transports.http.generic.RequestHelperBase$1.run(RequestHelperBase.java:152)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.transports.http.generic.RequestHelperBase.securedInvoke(RequestHelperBase.java:151)
         at com.bea.wli.sb.transports.http.generic.RequestHelperBase.service(RequestHelperBase.java:107)
         at com.bea.wli.sb.transports.http.wls.HttpTransportServlet.service(HttpTransportServlet.java:127)
         at weblogic.servlet.FutureResponseServlet.service(FutureResponseServlet.java:24)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3686)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
         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:2268)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<2011-11-21 13:00:46 CET> <Error> <OSB Security> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846861> <BEA-387024> <An error ocurred during web service security outbound request processing [error-code: InternalError, message-id: 3657493765399211266-5215cc49.133c5a81e20.-7f81, proxy: MyProject/ProxyServices/MyFirstProxyService, target: MyProject/ProxyServices/MySecondProxyService, operation: execute]
    --- Error message:
    java.lang.NullPointerException
         at oracle.wsm.agent.handler.WSMEngineInvoker.createWsmMessageContextFromInvokerContext(WSMEngineInvoker.java:733)
         at oracle.wsm.agent.handler.WSMEngineInvoker.handleRequest(WSMEngineInvoker.java:359)
         at com.bea.wli.sb.security.wss.wsm.WsmOutboundHandler$1.run(WsmOutboundHandler.java:141)
         at com.bea.wli.sb.security.wss.wsm.WsmOutboundHandler$1.run(WsmOutboundHandler.java:139)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.security.wss.wsm.WsmOutboundHandler.processRequest(WsmOutboundHandler.java:138)
         at com.bea.wli.sb.security.wss.WssHandlerImpl.doOutboundRequest(WssHandlerImpl.java:992)
         at com.bea.wli.sb.context.BindingLayerImpl.createTransportSender(BindingLayerImpl.java:532)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.doDispatch(PipelineContextImpl.java:521)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:501)
         at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:128)
         at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
         at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
         at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
         at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
         at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
         at com.bea.wli.sb.transports.http.generic.RequestHelperBase$1.run(RequestHelperBase.java:154)
         at com.bea.wli.sb.transports.http.generic.RequestHelperBase$1.run(RequestHelperBase.java:152)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.transports.http.generic.RequestHelperBase.securedInvoke(RequestHelperBase.java:151)
         at com.bea.wli.sb.transports.http.generic.RequestHelperBase.service(RequestHelperBase.java:107)
         at com.bea.wli.sb.transports.http.wls.HttpTransportServlet.service(HttpTransportServlet.java:127)
         at weblogic.servlet.FutureResponseServlet.service(FutureResponseServlet.java:24)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3686)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
         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:2268)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<2011-11-21 13:00:46 CET> <Info> <OSB Kernel> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846871> <BEA-398102> <
    [OSB Tracing] Exiting route node with fault:
    <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
    <con:errorCode>BEA-386400</con:errorCode>
    <con:reason>General outbound web service security error</con:reason>
    <con:location>
    <con:node>RouteToMySecondProxyService</con:node>
    <con:path>request-pipeline</con:path>
    </con:location>
    </con:fault>>
    ####<2011-11-21 13:00:46 CET> <Info> <OSB Kernel> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846873> <BEA-398074> <
    [OSB Tracing] The following variables are added:
    $outbound = <con:endpoint name="ProxyService$MyProject$ProxyServices$MySecondProxyService" xmlns:con="http://www.bea.com/wli/sb/context">
    <con:service>
    <con:operation>execute</con:operation>
    </con:service>
    <con:transport>
    <con:mode>request-response</con:mode>
    <con:qualityOfService>best-effort</con:qualityOfService>
    <con:request xsi:type="http:HttpRequestMetaData" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <tran:headers xsi:type="http:HttpRequestHeaders" xmlns:tran="http://www.bea.com/wli/sb/transports">
    <http:Content-Type>text/xml</http:Content-Type>
    <http:SOAPAction>"execute"</http:SOAPAction>
    </tran:headers>
    </con:request>
    </con:transport>
    <con:security>
    <con:doOutboundWss>true</con:doOutboundWss>
    </con:security>
    </con:endpoint>
    >
    ####<2011-11-21 13:00:46 CET> <Info> <OSB Kernel> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846874> <BEA-398076> <
    [OSB Tracing] The following variables are changed:
    $inbound = <con:endpoint name="ProxyService$MyProject$ProxyServices$MyFirstProxyService" xmlns:con="http://www.bea.com/wli/sb/context">
    <con:service>
    <con:operation>execute</con:operation>
    </con:service>
    <con:transport>
    <con:uri>/MyProject/ProxyServices/MyFirstProxyService</con:uri>
    <con:mode>request-response</con:mode>
    <con:qualityOfService>best-effort</con:qualityOfService>
    <con:request xsi:type="http:HttpRequestMetaData" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <tran:headers xsi:type="http:HttpRequestHeaders" xmlns:tran="http://www.bea.com/wli/sb/transports">
    <http:Accept>text/xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2</http:Accept>
    <http:Connection>keep-alive</http:Connection>
    <http:Content-Length>7614</http:Content-Length>
    <http:Content-Type>text/xml;charset="utf-8"</http:Content-Type>
    <http:Host>myLaptop:8011</http:Host>
    <http:SOAPAction>"execute"</http:SOAPAction>
    <http:User-Agent>Oracle JAX-WS 2.1.5</http:User-Agent>
    </tran:headers>
    <tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">utf-8</tran:encoding>
    <http:client-host>myLaptop</http:client-host>
    <http:client-address>192.168.148.155</http:client-address>
    <http:http-method>POST</http:http-method>
    </con:request>
    <con:response xsi:type="http:HttpResponseMetaData" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <tran:headers xsi:type="http:HttpResponseHeaders" xmlns:tran="http://www.bea.com/wli/sb/transports">
    <http:Content-Type>text/xml</http:Content-Type>
    </tran:headers>
    <tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">0</tran:response-code>
    </con:response>
    </con:transport>
    <con:security>
    <con:transportClient>
    <con:username>&lt;anonymous></con:username>
    </con:transportClient>
    <con:messageLevelClient>
    <con:username>myPrincipal</con:username>
    </con:messageLevelClient>
    </con:security>
    </con:endpoint>
    >
    ####<2011-11-21 13:00:46 CET> <Info> <OSB Kernel> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb7> <1321876846874> <BEA-398104> <
    [OSB Tracing] Exiting pipeline pair>
    ####<2011-11-21 13:00:46 CET> <Info> <OSB Kernel> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb8> <1321876846879> <BEA-398096> <
    [OSB Tracing] Exiting MyProject/ProxyServices/MyFirstProxyService>
    ####<2011-11-21 13:00:46 CET> <Info> <OSB Kernel> <myLaptop> <osb_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0add29b7d176a5e4:5215cc49:133c5a81e20:-7ff4-0000000000000cb8> <1321876846881> <BEA-398201> <
    [OSB Tracing] Inbound response was sent.
    Service Ref = MyProject/ProxyServices/MyFirstProxyService
    URI = /MyProject/ProxyServices/MyFirstProxyService
    Message ID = 3657493765399211266-5215cc49.133c5a81e20.-7f81
    Response metadata =
    <xml-fragment>
    <tran:headers xsi:type="http:HttpResponseHeaders" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <http:Content-Type>text/xml; charset=utf-8</http:Content-Type>
    </tran:headers>
    <tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">1</tran:response-code>
    <tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">utf-8</tran:encoding>
    </xml-fragment>
    Payload =
    <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>BEA-386400: General outbound web service security error</faultstring><detail><con:fault xmlns:con="http://www.bea.com/wli/sb/context"><con:errorCode>BEA-386400</con:errorCode><con:reason>General outbound web service security error</con:reason><con:location><con:node>RouteToMySecondProxyService</con:node><con:path>request-pipeline</con:path></con:location></con:fault></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>
    >

  • TransportException - OSB 10gR3 Failed to invoke Service

    Hi there,
    We are getting several errors on my OSB environment, OSB is running into problems, ramdomly is shutting down!
    Follow errors below :
    ####<Apr 29, 2011 1:15:25 AM GMT-03:00> <Error> <ALSB Alert Rule Engine> <rjux0087> <AdminServer> <pool-1-thread-1> <<anonymous>> <> <> <13040
    50525306> <BEA-394004> <Failed to invoke action email that is part of alert destination AlertDestination ClaroEnterpriseMonitoring/ClaroAlertD
    estination. Resource: ProxyService ClaroEnterpriseServices/Claro/ListarPacotesDisponiveisAssinante/v1/ListarPacotesDisponiveisAssinantePSv1. A
    lert Rule Name: SLA Response.
    com.bea.wli.sb.transports.TransportException: 501 Syntax error in return path - please go to http://www.xmailserver.test/smtp_errors.html to get more information about this error.
    I didn´t find anything relevant on :
    http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/javadoc/com/bea/wli/sb/transports/TransportException.html
    I was wondering if a specific service may cause the outage !
    The service "ClaroEnterpriseServices/Claro/ListarPacotesDisponiveisAssinante/v1/ListarPacotesDisponiveisAssinantePSv1" is a flow. The service is highlighted in dashboard with alerts, but there is no clue.
    Have you seen this before ?
    I appeciate any help !
    Thanks Edson

    Hi Edson,
    Looks like there is some alert actions+ in the proxy - ClaroEnterpriseServices/Claro/ListarPacotesDisponiveisAssinante/v1/ListarPacotesDisponiveisAssinantePSv1
    And this error is due to the same, looks like the alert destination configurations is having some issues.
    Failed to invoke action email that is part of alert destination AlertDestination ClaroEnterpriseMonitoring/ClaroAlertD
    estination. Resource: ProxyService ClaroEnterpriseServices/Claro/ListarPacotesDisponiveisAssinante/v1/ListarPacotesDisponiveisAssinantePSv1. A
    lert Rule Name: SLA Response.
    To confirm this out, I would suggest you can disable the alerting on the proxy service @ Operational Settings > Monitoring > SLA Alerts & Pipeline Alerts and see if the errors disappear.
    Thanks,
    Patrick

  • Unable to configure SocketTransport in eclipse(oepe11.1.1.8.0)(OSB11.1.1.6)

    Hi,
    i am trying to create socket transport in OSB 11.1.1.6 and i ahve followed http://docs.oracle.com/cd/E13171_01/alsb/docs25/transportsdk/example.html documentation i was able to deploy successfully, because i am able to see the socket option in the dropdown but on OSB console...
    problem is : when i am trying to configure the same for Eclipse Indigo ( oepe_11.1.1.8.0 ) i am unble to see the socket transport option in the dropdown.
    But when i followed the same documentation with OSB 11.1.1.4 and Eclipse Helios i was able to do it successfully.
    Reageds,
    Sampath.
    Edited by: 944553 on Jul 5, 2012 1:09 AM
    Edited by: 944553 on Jul 5, 2012 1:11 AM

    Hi,
    You should be able to follow the document for the new version, check this link, may there is some difference...
    http://docs.oracle.com/cd/E23943_01/dev.1111/e15866/developingeclipse.htm#OSBDV1385
    Cheers,
    Vlad
    It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts)
    https://forums.oracle.com/forums/ann.jspa?annID=893

  • Oracle Service Bus Question

    Hi,
    I have 6 systems that I want to connect using OSB. The first three are DEV, TEST and PROD versions of system A, and the second are DEV, TEST and PROD versions of system B.
    DEV_A needs to connect to DEV_B,
    TEST_A connects to TEST_B
    And PROD_A connects to PROD_B
    I realise that in the standard AIA header of the message there is a Target system element but the security people in my company insist that it must be impossible for a message from DEV_A to be passed to PROD_B by mistake. We would like to enforce this with policies.
    Ideally we would do the following:
    Install a unique security certificate on each system.
    Setup a proxy endpoint in OSB for every service.
    Configure the OSB endpoints to recognise the source system based on the security certificate and forward the messages on to the correct target system.
    Could anyone give me advice saying if this is possible, and if this is the best practice way of doing this?
    Robert

    Hi,
    This is one of the options that we have for setup however this leaves us with a remaining problem.
    In our SOA server the composites have the endpoints of other systems coded into them.
    Currently as we move from SOADEV -> SOATST -> SOAPROD we have a manual step which is to go into enterprise manager -> HTTP Adapter and manually change the addresses. This needs to be done for more than 10 services.
    Sometimes our DBA’s need to shuffle systems around. e.g. Our server prj09 may one day be our ICISDEV environment and another day be ICISTST. At the moment this requires our DBA’s to manually adjust the addresses in all services that call the service.
    Neither AIA’s endpoint Configurator or Configuration plans can address this issue as they are only activated on deployment.
    The problem isn’t just making sure SOA sends messages to the correct system. We have 3 SOA servers (DEV/TST/PROD) and other systems also need to know the correct one to call. We have resolved this with custom tables and custom PLSQL. This gives the DBA's another maintainance job.
    To avoid hardcoding addresses weblogic I realise it would be possible to create Java programs to read from simular tables to call the correct system and getting the composites to call the Java code but this is all very complex.
    I had thought OSB would solve this problem by providing a single endpoint which every system would call. It would then route the message to the correct system, but if you have 3 different OSB’s (DEV, TST, PROD) then it wouldn’t help resolve this problem at all.
    In fact the high level sales talk stuff led me to believe that this was exactly the sort of problem OSB is designed to address. Maybe I mis-understood.
    How do you address this issue?
    Robert

  • OSB MTOM HTTP Streaming

    Hello everybody,
    I have just started using Service Bus 11gR1 and I run into a problem. I need to define a proxy service (web service) which accepts large files (hundreds of MB).
    I opted for using MTOM/XOP combined with HTTP streaming. To do this, I enabled in the "Message Handling Configuration" screen, the "XOP/MTOM Support" option and I set "Page Attachments to Disk" to true.
    Actually, when I try to send large messages, the memory usage does not increase because the binary sent is buffered into the disk. Now I noticed that, before the proxy server is called, the binary sent is saved in a temporary file. I was wondering whether or not we can define a limit on the Message Size to be checked*before* the file is buffered on the disk. I want OSB to start reading the HTTP streaming and, when the max size is reached, to reset the http connection with the client. If this is not possible, I think that this is an issue from a security point of view.
    Thank you in advance.
    Edited by: 837199 on Feb 16, 2011 6:23 AM

    I don't know the answer to your question. Sorry! But It sounds like you have more succes with mtom on OSB than me. So I have a question that I hope you can help me with. Is you service based on a WSDL? if it is, can I see how it looks because I have some problems, making a wsdlbased proxyservice with mtom and invoking it from soapui
    BR,
    Mads

  • OSB: Calling MTOM business service from non-MTOM proxy

    Hi,
    it is very easy to call non-MTOM business service from MTOM enabled proxy service, but I don't know how to do it in an opposite way. I have web service proxy (http) with binary data in Base64 in a soap body element and I'd like to call a business service (web service over http again) using MTOM format to send binary data in binary format (and not in Base64 as it is in proxy). Is it possible to somehow decode binary data from Base64 in a proxy service and send them from this proxy to a business service using MTOM?

    I understand the flow you propose, but I don't know how to pass decoded data from Java callout back to message flow. As far as I know I can only return primitives, String and XmlObject, because anything else can't be processed in message flow.Yes you are correct.But you can also return DataSource in java callout. Please http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/pojo.html
    Now the working solution/POC --Tested on my local linux box
    package manoj.javacallout.binary;
    import java.io.BufferedReader;
    import java.io.ByteArrayOutputStream;
    import java.io.InputStream;
    import java.io.InputStreamReader;
    import java.io.OutputStream;
    import javax.activation.DataSource;
    import javax.mail.util.ByteArrayDataSource;
    import com.sun.org.apache.xml.internal.security.utils.Base64;
    * TODO: I have use sun internal API for decoding for simplicity. You should modify this code with any base64 decoding library
    * Ideally should be using using http://commons.apache.org/downloads/download_codec.cgi
    * @author mneelapu
    public class Util {
         public static DataSource decodeBase64(DataSource ds) throws Exception {
         InputStream in=ds.getInputStream();
         BufferedReader bin = new BufferedReader(new InputStreamReader(in));
         byte[] decodedB64=Base64.decode(bin);
         ByteArrayDataSource decodedDS= new ByteArrayDataSource(decodedB64,"binary/octet-stream");
         return(decodedDS);
    Java Callout to decodeBase64
    Parameters
    javax.activation.DataSource=[ $body/* ]
    Result
    javax.activation.DataSource=response
    Now replace the $body with the decoded base64 response from java callout
    Replace [ node contents ] of [  undefined XPath  ]
    in [ body ] with [ $response ]
    Use $BEA_HOME/modules/javax.mail_1.4.jar for compiling.
    Let me know if this solves your problem.
    Thanks
    Manoj
    Edited by: mneelapu on Apr 20, 2009 3:23 PM

  • OSB: MTOM and OWSM policies together

    Hi,
    I've set up a proxy chain, that invokes business service, that invokes soapUI mock.
    The mock return a file. All services are set up with MTOM pass by reference.
    It works like a charm. I receive my file as ctx:binary-content element.
    I have to add an OWSM policy to a business service. I've picked the simplest one, oracle/log_policy.
    Now the problem occurs. The business service returns:
    [OSB Security:387009]Failed to convert message context to SOAPMessage
    com.bea.wli.sb.context.BindingLayerException: Decoding of MIME attachments from MIME Content-Transfer-Encoding='7bit' not supportedDo you have any idea what's going on?
    Additonal question: is there a living soul which has been able to set up OWSM policies ant MTOM together?
    Edited by: Veronica on 2013-04-12 07:44

    I got this to work by switching "WSDL definition" from binding to port. Why would that help?

  • OSB 10.3.1 : Calling externall MTOM webservice through HTTPS

    Hi,
    We have OSB process that calls MTOM webservice via Business Service. It's works fine over HTTP connection.
    We secure the connection one-way ssl client, we imported public certificate to trusted keystore in wls.
    The business service calls the webservice over https, the Webservice receive the streaming and generates file.
    The problem is when the webservice returns result, the connection is froze and the wls where is the webservice generates this exception
    Couldn't create SOAP message due to exception: org.jvnet.mimepull.MIMEParsingException: Missing start boundary
    com.sun.xml.ws.protocol.soap.MessageCreationException: Couldn't create SOAP message due to exception: org.jvnet.mimepull.MIMEParsingException: Missing start boundary
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:292)
    at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276)
    at com.sun.xml.ws.transport.http.HttpAdapter.access$500(HttpAdapter.java:93)
    at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:432)
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
    at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
    at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
    at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: org.jvnet.mimepull.MIMEParsingException: Missing start boundary
    at org.jvnet.mimepull.MIMEParser.skipPreamble(MIMEParser.java:290)
    at org.jvnet.mimepull.MIMEParser.access$200(MIMEParser.java:62)
    at org.jvnet.mimepull.MIMEParser$MIMEEventIterator.next(MIMEParser.java:130)
    at org.jvnet.mimepull.MIMEParser$MIMEEventIterator.next(MIMEParser.java:117)
    at org.jvnet.mimepull.MIMEMessage.makeProgress(MIMEMessage.java:186)
    at org.jvnet.mimepull.MIMEMessage.parseAll(MIMEMessage.java:168)
    at org.jvnet.mimepull.MIMEMessage.<init>(MIMEMessage.java:85)
    at com.sun.xml.ws.encoding.MimeMultipartParser.<init>(MimeMultipartParser.java:88)
    at com.sun.xml.ws.encoding.MimeCodec.decode(MimeCodec.java:180)
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:279)
    I tested over https the same webservice using java client WS (generated by jdeveloper) and that works fine.
    Any idea
    Thanks,
    Maroun

    Resolved
    The problem is coming from OSB it happens when Business Service invoke WS in HTTPS, BS sends twice the request the first one contains the right envelop and the second one contains in empty request.
    The Oracle Support helped me to resolve the problem; we changed the QoS (Quality Of Service) to Exactly once
    Maroun

  • OSB: xs:base64 and MTOM - validation

    Hi,
    I have a xs:base64 that I would like to transfer on OSB using MTOM with include binary data by reference.
    I'm required to walidate the response before sending.
    Now the problem is, I get the schema validation error on this element. It says "did not expect the ctx:binary-content" in my xs:base64 element.
    Help please?

    It is very simple and the thread you are referring to describes that in full detail - just use Java Callout with javax.activation.DataSource as a return value. In Java Callout, you assign return value (your binary data) to a new OSB variable. Then use Replace action to put your variable into any other variable.

  • OSB MTOM...

    Hello everybody,
    I am using Oracle Service Bus 10gR3. I need to define a proxy service (wsdl based web service) which accepts large files (attachments).
    I am supposed to use MTOM/XOP combined with HTTP and I need to pass this request attachment to the backend using a Business Service. After googling I came to know that for this I need to enable the "XOP/MTOM Support" in the configuration settings for the proxy service. Still I am not sure about how to go for it.
    Can anyone help me with a sample code for the same.
    Thanks in advance.

    I don't know the answer to your question. Sorry! But It sounds like you have more succes with mtom on OSB than me. So I have a question that I hope you can help me with. Is you service based on a WSDL? if it is, can I see how it looks because I have some problems, making a wsdlbased proxyservice with mtom and invoking it from soapui
    BR,
    Mads

  • OSB: Retrieving file from disk and sending it via MTOM

    Hi,
    I'm trying to retrieve binary file from OSB local disk and than send it via MTOM.
    I've created a JCA synchronized reading file adapter. I've unchecked the "native message" option to disable schema translation. The files content seems getting picked up into <wsdl:part name="opaque" element="opaque:opaqueElement" />. I don't like the fact that it is encoded in base64. How to disable base64 decoding?
    I've tried to set the "native message" to some binary element, like <xs:element name="Attachment" type="xs:base64Binary" />. Then I get the "Schema translation failed" exception every time. What my native message should be to pick up a straight forward binary file?
    Can you guide me please how to create a file OSB transport service that would be able to read files?
    Also, if I obtain the file's content, how do I send it from proxy to proxy as a mtom? All of my proxy chains have enabled MTOM and pass binary as reference, but when I look up the messages transmitted, the opaque element seems to contain straigth forward base64 content, not binary reference.
    I would appreciate any help regarding any of this topics.

    Hi Veronica,
    there is absolutely nothing in my $body variableI did a quick test, the reference for the binary content goes to the $body variable...
    Service type = Messaging Service ... Transport = file
    Content of body after picking up a bmp image...
    <soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <con:binary-content ref="cid:-63889258:138079cb851:-7d8e" xmlns:con="http://www.bea.com/wli/sb/context"/>
    </soapenv:Body>
    Cheers,
    Vlad
    It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts)
    https://forums.oracle.com/forums/ann.jspa?annID=893

Maybe you are looking for