ORAMED-01304:[Payload schematron validation error]

Hi
I'm trying to do a simple Schematron validation with Oracle Mediator and am receiving the following error: ORAMED-01304:[Payload schematron validation error]
Any tips on how to debug?$
UPDATE: I should add that if I test my composite with xml data that doesn't validate against the xml schema, I get an xsd validation error. only when I pass valid data (valid for the xml schema) does it actually return the schematron validation error.
Edited by: SwC on Apr 10, 2012 9:23 AM

I found the reason.
I was missing the namespace declaration
<sch:ns uri="{your namespace}" prefix="{your prefix}" />
and the prefix for the context and test attribute elements.

Similar Messages

  • ORAMED-01301:[Payload custom validation]Schematron validation fails

    Receiving "oracle.tip.mediator.infra.exception.MediatorException: ORAMED-01301:[Payload custom validation]Schematron validation fails with error "{0}".Possible Fix:Fix the payload" error however the payload being sent matches with what is expected. Are there any other causes that may be causing this issue?
    Update:This happens every other request..i.e first request would work second fail third work fourth fail
    Edited by: 960635 on May 7, 2013 12:57 PM with addition of symptom occurrences

    I found the reason.
    I was missing the namespace declaration
    <sch:ns uri="{your namespace}" prefix="{your prefix}" />
    and the prefix for the context and test attribute elements.

  • Schematron validation error in BPEL, Oracle Soa Suite 11g

    Hi Friends,
    As per the requirement, I have to validate all the mandatory element values from an XML payload and need to send the consolidated report to the source application with all the validation failure elements.
    I am trying to implement Schematron validation in BPEL, but its giving me the following error:
    +<remoteFault>+
    +<part name="summary">+
    +<summary>oracle.fabric.common.FabricException: Cannot get Object part 'result'. No parts are set on the message</summary>+
    +</part>+
    +<part name="detail">+
    +<detail>Cannot get Object part 'result'. No parts are set on the message</detail>+
    +</part>+
    +</remoteFault>+
    I have followed the below process and created very basic sample composite.
    1) Extracted the validate.wsdl from bpm-services.jar.
    2) Imported the validate.wsdl into my Jdev Project.
    3) Created partenr link based on the validation.wsdl and used Invoke activty to invoke the partner link.
    4) Created .sch file and passed to input variable of the invoke activity.
    If any one knows about this issue, plz help me. Or if any one has developed an example on how to use schematron in BPEL plz share it with me.
    Thanks
    Ramesh

    1) How often did u see SOA suite being used in Non-Oracle Apps projects i.e projects that do not use Oracle Applications as the source data provider.Frankly speaking, not very often but still there are many customers who are using/willing to migrate on Oracle SOA Suite because of the many advantages provided by 11g stack.
    2) How much Oracle Apps knowledge is required for choosing the career of Oracle SOA Suite Integration Architect? I would say that both the technologies have very less in common so it never depends on your level of Apps knowledge to architect a SOA solution. You have to learn SOA from scratch but if you have prior experience in Oracle Apps then it may not be very difficult for you to go ahead with SOA.
    Regards,
    Anuj

  • B2B-51507 - Payload Validation Error - while creating  VDA -4913V3

    I created a document definition under Positional Flat file for VDA-> 4913V4. I created ecs file using the Document editor and created the xsd. I used both these files in creating the Document definition. In the document definition, under identification tab, I have these values.
    Identification Value -> empty
    Identification Start Position -> 0
    Identification End Position -> 128
    And I created a Partner Agreement using this Document Definition. I created a channel to send the document to GXS Mailbox.
    In the agreement if I have both Validate and Translate checked on, I am getting an error which is show in the reports->Business Message.
    Error Code B2B-51507
    Error Description Machine Info: (RRDV2SOA) Description: Payload validation error.
    Error Level ERROR_LEVEL_COLLABORATION
    Error Severity ERROR
    Error Text Payload validation error.
    If I have only Translate checked on, I am not getting any error, but the message that is sent to GXS is zero bytes.
    If I leave both Validate and translate unchecked, the xml is sent to GXS but not the native Format.
    I took the payload from the business message and validated and it looks correct.
    I am using the sample data that is already validated in the B2B Document Editor using Data Analyzer.
    Can you help me on this. I am not sure what I am doing wrong. If needed I can send you the ecs, xsd, and B2B partner definition export zip file to your email address.
    Here is the logfile for this error.
    [2011-04-06T21:00:41.652-07:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@1a33f088] [userId: <anonymous>] [ecid: 0000Iwi7c0MCcpiF_7I7S61DVcAD0051W4,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [dcid: 4e45f5dff566a29f:-335a9823:12eb62ea520:-7ffd-000000000000008c] [SRC_METHOD: synchedLog_J] oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Exit
    [2011-04-06T21:00:41.653-07:00] [soa_server1] [ERROR] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@1a33f088] [userId: <anonymous>] [ecid: 0000Iwi7c0MCcpiF_7I7S61DVcAD0051W4,0] [APP: soa-infra] [dcid: 4e45f5dff566a29f:-335a9823:12eb62ea520:-7ffd-000000000000008c] Error -: B2B-51507: Payload validation error.: Error -: B2B-51507: Payload validation error.[[
    at oracle.tip.b2b.document.pff.PFFDocumentPlugin.processOutgoingDocument(PFFDocumentPlugin.java:835)
    at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1326)
    at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:837)
    at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1411)
    at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:781)
    at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3319)
    at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2948)
    at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:575)
    at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused by: Error -: B2B-51507: Payload validation error.
    at oracle.tip.b2b.document.pff.PFFDocumentPlugin.processOutgoingDocument(PFFDocumentPlugin.java:798)
    ... 11 more
    Error -: B2B-51507: Payload validation error.
    at oracle.tip.b2b.document.pff.PFFDocumentPlugin.processOutgoingDocument(PFFDocumentPlugin.java:798)
    at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1326)
    at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:837)
    at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1411)
    at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:781)
    at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3319)
    at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2948)
    at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:575)
    at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Error -: B2B-51507: Payload validation error.: Error -: B2B-51507: Payload validation error.
    at oracle.tip.b2b.document.pff.PFFDocumentPlugin.processOutgoingDocument(PFFDocumentPlugin.java:835)
    at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1326)
    at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:837)
    at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1411)
    at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:781)
    at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3319)
    at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2948)
    at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:575)
    at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused by: Error -: B2B-51507: Payload validation error.
    at oracle.tip.b2b.document.pff.PFFDocumentPlugin.processOutgoingDocument(PFFDocumentPlugin.java:798)
    ... 11 more
    Thank you
    Krishna.

    I selected the option "Save guideline before exporting". I am guessing it is failing on the main element of the xml message because of some namespace issue. I am generating the XML using xsl transformationin BPEL and sending the XML payload to B2B Service.
    Is there a way to know what part of the XML is erroring duing the validation on the server. The error message is not helpful even I turned on Trace 32 level.
    Any ideas?
    Thank you
    Krishna

  • B2B-51507- Payload validation error - 11.1.1.7 Latest Version

    Anuj/Nitesh (B2B Gurus)
    I am facing a problem when Posting the message from SOA to B2b (XML->EDI) using the B2b Adapter.
    Flow is : Ebusiness->PLSQL->AQ->BPEL->B2B.  Once the message is posted to B2b It is throwing the following Error.
    But I am passing all the mandatory and Optional Parameters.
    Tried the Following Threads, But No luck. I am passing all the Mandatory Parameters.
    How to map Internal-Properties in XSLT.
    Oracle B2B Payload Validation exception
    Scenario - 1 (Success No Errors , Output Does not Contain PO Details)
    Disabled the Validate flag in the Partner Agreement for the B2B Document.
    Verified the B2b Wired Message, Output got generated but without the PO information I am passing from BPEL.
    Scenario - 2 (Error )
    Enabled the Validate flag in the Partner Agreement for the B2B Document. The system is generating an error and throwing list of errors.
    Error
    Id
    C064016C14103689486000005559CD14
    Message Id
    C064016C14103688C7F000005559CD0F
    Refer To Message
    Refer To Message
    Sender Type
    Name
    Sender Value
    ABC
    Receiver Type
    Name
    Receiver Value
    TEST123
    Sender
    ABC
    Receiver
    TEST123
    Agreement Id
    EDI_850_tpa_Lt7763342564515893374
    Agreement
    XXX_EDI_X12_4010_850_Outbound
    Document Type
    850
    Document Protocol
    EDI_X12
    Document Version
    4010
    Message Type
    REQ
    Direction
    OUTBOUND
    State
    MSG_ERROR
    Acknowledgement Mode
    NONE
    Response Mode
    NONE
    Send Time Stamp
    9/9/2013 10:48
    Receive Time Stamp
    9/9/2013 10:48
    Document Retry Interval(Channel)
    0
    Document Remaining Retry(Channel)
    0
    Document Retry Interval(Agreement)
    0
    Document Remaining Retry(Agreement)
    0
    Native Message Size
    Translated Message Size
    5471
    Business Action Name
    Business Transaction Name
    Xpath Name1
    XPathName1
    Xpath Value1
    Xpath Expression1
    Xpath Name2
    XPathName2
    Xpath Value2
    Xpath Expression2
    Xpath Name3
    XPathName3
    Xpath Value3
    Xpath Expression3
    Correlation From XPath Name
    CorrelationFromXPathName
    Correlation From XPath Value
    Correlation From XPath Expression
    Correlation To XPath Name
    CorrelationToXPathName
    Correlation To XPath Value
    Correlation To XPath Expression
    Wire Message
    Wire Message
    Application Message
    Application Message
    Payload Storage
    Payload Storage
    Attachment
    Attachment
    Label
    soa_b2b_ - Thu Sep 05 11:51:44 CDT 2013 - 4
    Collaboration Id
    C064016C14103688E1A000005559CD13
    Collaboration Name
    Collaboration Version
    Business Action Name
    Exchange Protocol Name
    Generic File
    Exchange Protocol Version
    1
    Interchange Control Number
    Group Control Number
    Transaction Set Control Number
    Error Code
    B2B-51507
    Error Description
    Description: Payload validation error.
    Error Level
    ERROR_LEVEL_COLLABORATION
    Error Severity
    ERROR
    Error Text
    Error Brief : Error reporting limit exceeded. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A functional group code mismatch was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A transaction ID mismatch was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered.
    Error Brief :^M
    Error reporting limit exceeded.^M
    Validator error - Extra data was encountered.^M
    Validator error - Extra data was encountered.^M
    Validator error - Extra data was encountered.^M
      Validator error - Extra data was encountered.^M
    Validator error - Extra data was encountered.^M
    Validator error - Extra data was encountered.^M
    Validator error - Extra data was encountered.^M
    Validator error - Extra data was encountered.^M
      Validator error - Extra data was encountered.^M
    Validator error - Extra data was encountered.^M
    Validator error - Extra data was encountered.^M
    Validator error - Extra data was encountered.^M
    Validator error - Extra data was encountered.^M
      Validator error - Extra data was encountered.^M
    Validator error - Extra data was encountered.^M
    A data element with 'Mandatory' status is missing.^M
    A data element with 'Mandatory' status is missing.^M
      A data element with 'Mandatory' status is missing.^M
    A data element with 'Mandatory' status is missing.^M
    A data element with 'Mandatory' status is missing.^M
    A data element with 'Mandatory' status is missing.^M
      A data element with 'Mandatory' status is missing.^M
    A data element with 'Mandatory' status is missing.^M
    A data element with 'Mandatory' status is missing.^M
    A data element with 'Mandatory' status is missing.^M
      A data element with 'Mandatory' status is missing.^M
    A data element with 'Mandatory' status is missing.^M
    A data element with 'Mandatory' status is missing.^M
    A data element with 'Mandatory' status is missing.^M
      A data element with 'Mandatory' status is missing.^M
    A data element with 'Mandatory' status is missing.^M
    Validator error - Extra data was encountered.^M
    Validator error - Extra data was encountered.^M
      Validator error - Extra data was encountered.^M
    Description: Payload validation error., null, null, null, null, C064016C140EF31BFCA000005559CC
    A4, null, null, 1258, B2B-51507, null, null, null, null, null, 2013-09-05 12:35:49.092, null, ^M
      Error :^M
    Analysis halted after 101 error(s) (Limit for Transaction is 100). Large numbers of errors usually indicate that the same error is repeatedly encountered in multiple segments or transactions. Fix the repeating error and resubmit the test to obtain further results.^M
      Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 1{br}{tab}Characters: 210 through 212^M
      Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 2{br}{tab}Characters: 247 through 257^M
      Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 3{br}{tab}Characters: 292 through 294^M
      Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 4{br}{tab}Characters: 329 through 339^M
      Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 5{br}{tab}Characters: 374 through 376^M
      Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 6{br}{tab}Characters: 411 through 426^M
      Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 7{br}{tab}Characters: 463 through 465^M
      Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 8{br}{tab}Characters: 502 through 517^M
      Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 9{br}{tab}Characters: 552 through 558^M
      Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 10{br}{tab}Characters: 593 through 597^M
      Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 11{br}{tab}Characters: 632 through 633^M
      Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 12{br}{tab}Characters: 668 through 673^M
      Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 13{br}{tab}Characters: 708 through 717^M
      Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 14{br}{tab}Characters: 752 through 753^M
    Thanks
    Rao.

    Issue is resolved by doing the Following Steps.
    1. Open the ECS file in the Document Editor, Exclude the ISA, GS segments in the ECS file. Save the File and Upload the Document and Redeploy the Agreement.
    2. Export the XSD and refer it in the BPEL process and do the transformation.
    Thanks
    Nethi.

  • Payload validation Error - Outbound flow

    Hi,
    I am trying to create an outbound flow to send a X12,4010,810 document to a trading partner.
    Got the error - Payload Validation error.
    Payload is as below
    <?xml version = '1.0' encoding = 'UTF-8'?><Transaction-810 xmlns="http://www.edifecs.com/xdata/200" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="X12" Version="V4010" CreatedDate="2007-04-10T17:16:24" CreatedBy="ECXEngine_837" GUID="{12345678-1234-1234-1234-123456789012}"><Internal-Properties><Data-Structure Name="Interchange"><Lookup Name="InterchangeControlVersion">00401</Lookup><Lookup Name="InterchangeReceiverID">MarketInc</Lookup><Lookup Name="InterchangeReceiverQual">ZZ</Lookup><Lookup Name="InterchangeSenderID">OracleServices</Lookup><Lookup Name="InterchangeSenderQual">ZZ</Lookup><Lookup Name="InterchangeUsageIndicator">I</Lookup><Lookup Name="Standard">X12</Lookup><Property Name="ElementDelimiter">0x7e</Property><Property Name="InterchangeAckRequested">0</Property><Property Name="InterchangeAuthorizationInfo">Authorizat</Property><Property Name="InterchangeAuthorizationInfoQual">00</Property><Property Name="InterchangeChildCount">1</Property><Property Name="InterchangeComponentElementSep">0x5c</Property><Property Name="InterchangeControlNumber">000000001</Property><Property Name="InterchangeControlStandard_RepeatingSeparator">U</Property><Property Name="InterchangeControlVersion">00401</Property><Property Name="InterchangeDate">140313</Property><Property Name="InterchangeReceiverID">MarketInc</Property><Property Name="InterchangeReceiverQual">ZZ</Property><Property Name="InterchangeSecurityInfo">Security I</Property><Property Name="InterchangeSecurityInfoQual">00</Property><Property Name="InterchangeSenderID">OracleServices</Property><Property Name="InterchangeSenderQual">ZZ</Property><Property Name="InterchangeTime">1727</Property><Property Name="InterchangeTrailerControlNumber">000000001</Property><Property Name="InterchangeUsageIndicator">I</Property><Property Name="SegmentDelimiter">0x0d0x0a</Property><Property Name="Standard">X12</Property><Property Name="SubelementDelimiter">0x5c</Property></Data-Structure></Internal-Properties><Segment-ST><Element-143>IN</Element-143><Element-329>0001</Element-329></Segment-ST><Segment-BIG><Element-373>20140313</Element-373><Element-76>I</Element-76></Segment-BIG><Segment-TDS><Element-610>2</Element-610></Segment-TDS><Segment-SE><Element-96>4</Element-96><Element-329>0001</Element-329></Segment-SE></Transaction-810>
    Can someone suggest what is the problem with this payload.

    More detail --
    Below is the message that is displayed in Oracle B2B Reports -> Business Message
    Id
    7F000001144BE0AB3A100000231A6860
    Message Id
    11d1def534ea1be0:-7e1384fb:144bd539c55:-8000-0000000000007dfc
    Refer To Message
    Refer To Message
    Sender Type
    Name
    Sender Value
    OracleServices
    Receiver Type
    Name
    Receiver Value
    MarketInc
    Sender
    OracleServices
    Receiver
    MarketInc
    Agreement Id
    OS_MI_X12_4010_810_OutboundInvoiceAgr
    Agreement
    OS_MI_X12_4010_810_OutboundInvoiceAgr
    Document Type
    IN
    Document Protocol
    EDI_X12
    Document Version
    4010
    Message Type
    REQ
    Direction
    OUTBOUND
    State
    MSG_ERROR
    Acknowledgement Mode
    NONE
    Response Mode
    NONE
    Send Time Stamp
    Mar 13, 2014 7:42 PM
    Receive Time Stamp
    Mar 13, 2014 7:42 PM
    Document Retry Interval(Channel)
    0
    Document Remaining Retry(Channel)
    0
    Document Retry Interval(Agreement)
    0
    Document Remaining Retry(Agreement)
    0
    Native Message Size
    Translated Message Size
    2344
    Business Action Name
    Business Transaction Name
    Xpath Name1
    XPathName1
    Xpath Value1
    Xpath Expression1
    Xpath Name2
    XPathName2
    Xpath Value2
    Xpath Expression2
    Xpath Name3
    XPathName3
    Xpath Value3
    Xpath Expression3
    Correlation From XPath Name
    CorrelationFromXPathName
    Correlation From XPath Value
    Correlation From XPath Expression
    Correlation To XPath Name
    CorrelationToXPathName
    Correlation To XPath Value
    Correlation To XPath Expression
    Wire Message
    Wire Message
    Application Message
    Application Message
    Payload Storage
    Payload Storage
    Attachment
    Attachment
    Label
    soa_b2b_ - Thu Mar 17 08:30:33 CDT 2014 - 8
    Collaboration Id
    7F000001144BE0AB37E00000231A6850
    Collaboration Name
    Collaboration Version
    Business Action Name
    Exchange Protocol Name
    Generic File
    Exchange Protocol Version
    1.0
    Interchange Control Number
    Group Control Number
    Transaction Set Control Number
    Error Code
    B2B-51507
    Error Description
    Machine Info: (XXXX) Description: Payload validation error.
    Error Level
    ERROR_LEVEL_COLLABORATION
    Error Severity
    ERROR
    Error Text
    Error Brief : XEngine error.
    Application Message :
    Id7F000001144BE0AB22400000231A6820Sender Id TypeSender ValueOracleServicesReceiver Id TypeReceiver ValueMarketIncDocument TypeINDocument Definition810_DefDocument Protocol NameEDI_X12Document Protocol Version4010Refer To Application Message IdRefer To Application Message IdApp Conversation IdApp Message property{fabric.enterpriseId=-1, b2b.documentProtocolVersion=4010, b2b.documentDefinitionName=810_Def, b2b.messageId=11d1def534ea1be0:-7e1384fb:144bd539c55:-8000-0000000000007dfc, MESH_METRICS=null, b2b.messageType=1, tracking.parentReferenceId=mediator:954F1AF0AB1111E3BF8A5F99BC4D6B4E:954F6910AB1111E3BF8A5F99BC4D6B4E:oneway, tracking.compositeInstanceId=20012, tracking.ecid=11d1def534ea1be0:-7e1384fb:144bd539c55:-8000-0000000000007dfc, b2b.toTradingPartnerId=MarketInc, b2b.fromTradingPartnerId=OracleServices, tracking.compositeInstanceCreatedTime=Thu Mar 13 19:42:55 CDT 2014, tracking.conversationId=snbwNIP3idSWrxOB_9mfQZizjgj_IKJyb-EozcpIyP4., tracking.parentComponentInstanceId=mediator:954F1AF0AB1111E3BF8A5F99BC4D6B4E, b2b.documentTypeName=IN}DirectionOUTBOUNDStateMSG_COMPLETEError CodeError TextError DescriptionCreatedMar 13, 2014 7:42 PMModifiedMar 13, 2014 7:42 PMMessage Size2344PayloadPayloadBusiness MessageBusiness MessageRetry Interval0Reattempt CountRemaining Retry0ECID11d1def534ea1be0:-7e1384fb:144bd539c55:-8000-0000000000007dfcComposite Instance Id20012Parent Composite Instance Idmediator:954F1AF0AB1111E3BF8A5F99BC4D6B4EConversation IdsnbwNIP3idSWrxOB_9mfQZizjgj_IKJyb-EozcpIyP4.Domain NamedefaultComposite NameOSToMIOutboundInvoiceProjectComposite Version1.0Reference NameB2BOSToMarketIncOutboundUrl
    Payload Storage :
    <?xml version = '1.0' encoding = 'UTF-8'?><Transaction-810 xmlns="http://www.edifecs.com/xdata/200" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="X12" Version="V4010" CreatedDate="2007-04-10T17:16:24" CreatedBy="ECXEngine_837" GUID="{12345678-1234-1234-1234-123456789012}"><Internal-Properties><Data-Structure Name="Interchange"><Lookup Name="InterchangeControlVersion">00401</Lookup><Lookup Name="InterchangeReceiverID">MarketInc</Lookup><Lookup Name="InterchangeReceiverQual">ZZ</Lookup><Lookup Name="InterchangeSenderID">OracleServices</Lookup><Lookup Name="InterchangeSenderQual">ZZ</Lookup><Lookup Name="InterchangeUsageIndicator">I</Lookup><Lookup Name="Standard">X12</Lookup><Property Name="ElementDelimiter">0x7e</Property><Property Name="InterchangeAckRequested">0</Property><Property Name="InterchangeAuthorizationInfo">Authorizat</Property><Property Name="InterchangeAuthorizationInfoQual">00</Property><Property Name="InterchangeChildCount">1</Property><Property Name="InterchangeComponentElementSep">0x5c</Property><Property Name="InterchangeControlNumber">000000001</Property><Property Name="InterchangeControlStandard_RepeatingSeparator">U</Property><Property Name="InterchangeControlVersion">00401</Property><Property Name="InterchangeDate">140313</Property><Property Name="InterchangeReceiverID">MarketInc</Property><Property Name="InterchangeReceiverQual">ZZ</Property><Property Name="InterchangeSecurityInfo">Security I</Property><Property Name="InterchangeSecurityInfoQual">00</Property><Property Name="InterchangeSenderID">OracleServices</Property><Property Name="InterchangeSenderQual">ZZ</Property><Property Name="InterchangeTime">1727</Property><Property Name="InterchangeTrailerControlNumber">000000001</Property><Property Name="InterchangeUsageIndicator">I</Property><Property Name="SegmentDelimiter">0x0d0x0a</Property><Property Name="Standard">X12</Property><Property Name="SubelementDelimiter">0x5c</Property></Data-Structure></Internal-Properties><Segment-ST><Element-143>IN</Element-143><Element-329>0001</Element-329></Segment-ST><Segment-BIG><Element-373>20140313</Element-373><Element-76>I</Element-76></Segment-BIG><Segment-TDS><Element-610>2</Element-610></Segment-TDS><Segment-SE><Element-96>4</Element-96><Element-329>0001</Element-329></Segment-SE></Transaction-810>
    I have set the following b2b headers in SOA before sending it to B2B outbound
    Constant: 4010_810_Def Property: b2b.documentDefinitionName 
    Constant: 4010 Property: b2b.documentProtocolVersion
    Constant: OracleServices Property: b2b.fromTradingPartnerId
    Constant: MarketInc Property: b2b.toTradingPartnerId
    Constant: 1 Property: b2b.messageType
    Constant: IN Property: b2b.documentTypeName ( I defined my docuemnt with name 'IN')
    Property: tracking.ecid Property: b2b.messageId

  • - 0 fatal error(s), 3 error(s)     ----------- Payload: Adobe Photoshop Lightroom 5 5.6.0.0 Adobe_Lightroom_x64.msi_5.6 -----------  ERROR: Key not valid for use in specified state.    ERROR: Install MSI payload failed with error: 1603 - Fatal error durin

    I keep getting this error code when trying to download         
    - 0 fatal error(s), 3 error(s) ----------- Payload: Adobe Photoshop Lightroom 5 5.6.0.0 Adobe_Lightroom_x64.msi_5.6 ----------- ERROR: Key not valid for use in specified state. ERROR: Install MSI payload failed with error: 1603 - Fatal error during installation. MSI Error message: Key not valid for use in specified state. ERROR: Third party payload installer Adobe_Lightroom_x64.msi failed with exit code: 1603

    Generally this error happens because of an encrypted folder or insufficient permissions on that folder: http://support.microsoft.com/kb/834484 (MS Explanation)
    Adobe has a page here: Error 1603: A fatal error occurred during installation

  • Can SOA 11g fault policy handle XSD Validation errors from the Mediator?

    I would like all errors in my SOA process to go through the fault-policies.xml. But I don't seem to be able to catch any mediator error caused by an XSD validation failure. A sample of the sort of error I am trying to 'catch' is:
    Nonrecoverable System Fault          oracle.tip.mediator.infra.exception.MediatorException: ORAMED-01303:[Payload default schema validation error]XSD schema validation fails with error Invalid text 'A' in element: 'TermCode'Possible Fix:Fix payload and resubmit.
    My fault-policies.xml file is as follows:
    <?xml version="1.0" encoding="UTF-8" ?>
    <faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy">
    <faultPolicy version="2.0.1"
         id="NewStudentRegistrationFaults"
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns="http://schemas.oracle.com/bpel/faultpolicy"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <Conditions>
    <faultName xmlns:medns="http://schemas.oracle.com/mediator/faults" name="medns:1303">
    <condition>
    <action ref="java-fault-handler"/>
    </condition>
    </faultName>
    <faultName xmlns:rjm="http://schemas.oracle.com/sca/rejectedmessages" name="rjm:GetNewStudentRegistrationFile">
    <condition>
    <action ref="java-fault-handler"/>
    </condition>
    </faultName>
    <faultName xmlns:medns="http://schemas.oracle.com/mediator/faults" name="medns:TYPE_ALL">
    <condition>
    <action ref="java-fault-handler"/>
    </condition>
    </faultName>
    <faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:mediatorException">
    <condition>
    <action ref="java-fault-handler"/>
    </condition>
    </faultName>
    <faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:bindingFault">
    <condition>
    <action ref="java-fault-handler"/>
    </condition>
    </faultName>
    <faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:remoteFault">
    <condition>
    <action ref="java-fault-handler"/>
    </condition>
    </faultName>
    </Conditions>
    <Actions>
    <Action id="java-fault-handler">
    <javaAction className="edu.villanova.soa.handlers.FaultNotificationHandler"
    defaultAction="ora-human-intervention" propertySet="faultNotificationProps">
    <returnValue value="OK" ref="ora-human-intervention"/>
    </javaAction>
    </Action>
    <!-- Human Intervention -->
    <Action id="ora-human-intervention">
    <humanIntervention/>
    </Action>
    <!-- Terminate -->
    <Action id="ora-terminate">
    <abort/>
    </Action>
    </Actions>
    <!-- Property sets used by custom Java actions -->
    <Properties>
    <!-- Property set for FaultNotificationHandler customer java action -->
    <propertySet name="faultNotificationProps">
    <property name="from">[email protected]</property>
    <property name="to">[email protected]</property>
    <property name="subject">Reporting a SOA fault</property>
    </propertySet>
    </Properties>
    </faultPolicy>
    <faultPolicy version="2.0.1"
         id="MediatorFaults"
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns="http://schemas.oracle.com/bpel/faultpolicy"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <Conditions>
    <faultName xmlns:medns="http://schemas.oracle.com/mediator/faults" name="medns:1303">
    <condition>
    <action ref="java-fault-handler"/>
    </condition>
    </faultName>
    </Conditions>
    <Actions>
    <Action id="java-fault-handler">
    <javaAction className="edu.villanova.soa.handlers.FaultNotificationHandler"
    defaultAction="ora-human-intervention" propertySet="faultNotificationProps">
    <returnValue value="OK" ref="ora-human-intervention"/>
    </javaAction>
    </Action>
    <!-- Human Intervention -->
    <Action id="ora-human-intervention">
    <humanIntervention/>
    </Action>
    <!-- Terminate -->
    <Action id="ora-terminate">
    <abort/>
    </Action>
    </Actions>
    <!-- Property sets used by custom Java actions -->
    <Properties>
    <!-- Property set for FaultNotificationHandler customer java action -->
    <propertySet name="faultNotificationProps">
    <property name="from">[email protected]</property>
    <property name="to">[email protected]</property>
    <property name="subject">Reporting a SOA rejected msg. fault</property>
    </propertySet>
    </Properties>
    </faultPolicy>
    </faultPolicies>
    My fault-bindings.xml file is as follows:
    <?xml version="1.0" encoding="UTF-8" ?>
    <faultPolicyBindings version="2.0.1"
    xmlns="http://schemas.oracle.com/bpel/faultpolicy"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <composite faultPolicy="NewStudentRegistrationFaults"/>
    <component faultPolicy="MediatorFaults">
    <name>NewStudentRegistrationMediator</name>
    </component>
    <service faultPolicy="NewStudentRegistrationFaults">
    <name>GetNewStudentRegistrationFile</name>
    </service>
    </faultPolicyBindings>
    You'll notice that I've tried a number of ways (and various other combinations) to try to steer the error above into my Java fault handler but nothing has meet with success. The mplan is as follows:
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <!--Generated by Oracle SOA Modeler version 1.0 at [2/3/10 1:21 PM].-->
    <Mediator name="NewStudentRegistationMediator" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.oracle.com/sca/1.0/mediator"
    wsdlTargetNamespace="http://xmlns.oracle.com/pcbpel/adapter/ftp/Experiments/NewStudentRegistration/GetNewStudentRegistrationFile%2F">
    <operation name="Get" deliveryPolicy="AllOrNothing" priority="4"
    validateSchema="true">
    <switch>
    <case executionType="queued" name="RegToBanner.insert_2">
    <action>
    <transform>
    <part name="$out.NewstudentregistrationCollection"
    function="xslt(xsl/NewStudentRegistration_To_NewstudentregistrationCollection.xsl, $in.body)"/>
    </transform>
    <invoke reference="RegToBanner" operation="insert"/>
    </action>
    </case>
    </switch>
    </operation>
    </Mediator>
    I'm a newbie to Oracle SOA. So perhaps I am missing the obvious. But I haven't read much in the documentation specifically about using the XSD validation option on the mediator and have seen nothing specifically about catching this sort of exception in the fault policy (apart from the faults I already have in my policy). Can anyone suggest what I am doing incorrectly here or perhaps whether what I am attempting to do is not possible? Thanks.
    - Cris

    Has anyone got it working yet?
    In my case, I have the following sequence:
    FileAdapter -> Mediator1 -> Mediator2->DB Adapter
    I am deliberately introducing validation error in File. Isn't it correct to assume Fault framework would get triggered at Mediator1 level since we are invoking FileAdapter service?
    I am getting a strange behaviour. If I enable XSD validation at Mediator1 level, process is Faulted with no re-try option. However, if I enable XSD validation ONLY at Mediator2 level, I get Recoverable fault. There seems to be some disconnect between documentation and reality. I am using JDeveloper 11.1.1.3.0 version and SOA Suite 11g.
    Thanks,
    Amjad.

  • FA/997 for Validation Error

    Hi All,
    I need some clarification on receiving the 997/FA for the Validation error that happens at the remote trading partner.
    Will the 997 payload contain the details of the error in it??
    How will B2B interpret the FA as positive FA or negative FA?
    In my case the payload which I am sending is getting validation error at receiving side, they are sending me the FA. But in my side, both the initial transaction and the ack transaction goes to MSG_Completed state. Is it a normal behavior?
    Thanks in advance.
    Regards,
    Monica

    Hi,
    1. The 997 has fields which will tell if the EDI transactions has SNIP errors. In your case, the outbound EDI should goto MSG_ERROR.
    2. In a 999 transaction, the fields such as AK9, IK4, IK5 will tell the problem in the EDI, I am sure 997 should also have something like that.

  • Adapter Engine XML Schema Validation Error Surpression

    We recently developed a number of web services that are called by 3rd parties outside our network. The web service request once made is picked up by a Web Dispatcher which then forwards the request to the de-central adapter. Both of these components reside within within a DMZ.
    We have, as an additional security measure made use of the new Adapter Engine XML Schema validation available with PI 7.1, to ensure that the payload of incomming messages is checked to ensure that it is a known structure.
    Now here is my problem, we recently had these services penetration tested by a 3rd party to ensure that they were secure and whilst the report was very good showing no major weaknesses they did pickup on a couple of items including that the fact that if the XSD to be used during payload message validation cannot be found an 'ADAPTER.JAVA_EXCEPTION' is returned to the web service consumer that highlights the path details of where the XSD should be (but could not be found).
    This was viewed as useful to an attacker for a number of reasons:
    1. Feedback in SQL injection attempts via verbatim DB error messages greatly improves attacker efficiency
    2. Path information is useful to the attacker for OS fingerprinting, directory traversal attempts
    3. Other miscellaneous stack trace information is useful to an attacker to understand how the application works
    Is there anyway this can be surpressed so that the adapter does not show this information in the returned error message - see example message below ?
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: Schema MaintenanceOrderByIDQuery_sync.xsd not found in E:\usr\sap\DPI\DVEBMGS40\j2ee\cluster\server0\validation\schema\f7cd3b50a87411e08830ed9d0af006a5\urnstw.contractor.wfm.workorderretrieval\MaintenanceOrderByIDQueryRequest_Out\httpsap.comxiSAPGlobal20~Global\MaintenanceOrderByIDQuery_sync.xsd  (validation\schema)
         at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)
         at sun.reflect.GeneratedMethodAccessor497.invoke(Unknown Source)
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: Schema Schema1.xsd not found in E:\usr\sap\DPI\DVEBMGS40\j2ee\cluster\server0\validation\schema\f7cd3b50a87411e08830ed9d0af006a5\urnstw.contractor.wfm.workorderretrieval\MaintenanceOrderByIDQueryRequest_Out\httpsap.comxiEA-APPLSEGlobal\Schema1.xsd  (validation\schema)
         at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)

    Hi,
    We are having the same problem, so you are not alone.
    I had an extensive call with Azure premium support and we where able to determine that:
    - Nothing is missing or in the wrong place in my exported .xml file.
    - Any changes to the VNET's using the web gui interface of https://manage.windowsazure.com is not possible when you have dns servers and use an gateway
    - You can download the .xml configuration file of the network and make manual changes to it, then import it again , to add/remove dns servers and or subnet's. 
    I am currently waiting for an solution,  i have let them lower the urgency from A to B (because i can make changes trough xml) and responded to the next support contact (saying he will continue with the issue) that the problems seems to be with azure and
    he should speak with the previous person helping me.  I have not heard from Azure support since.
    SR Number:115021812414226
    Open on:02/18/2015 09:28
    > There are networks with and without gateways created and the issue is happening on all the networks.
    > We are unable to add or remove the DNS servers. (by web gui)
    > Also not able to add or remove any subnets. (by web gui)
    > Every time the error message is same but the DNS server name is different. (from another subnet then the one we are changing)
    > Created CRI- 3405931, but they said it will need WATS team.
    > Confirmed with WATS engineer as well and moving case to WATS.
    > Cx agreed to lower the severity of the case as they are able to make changes through the network configuration file.
    > But they still want to get this resolved soon.
    > Agreed and dropped off, reducing severity to B 24/7.
    I hope microsoft is going to resolve this soon, as i do not want to edit my xml for little things like adding a subnet all the time. I have requested an status update in the issue.
    Should anyone have more information on this, please share it here.

  • Validator error - Extra data was encountered.

    Hi All,
    I am working on Outbound EDI870, getting below Error:
    2010.06.03 at 04:33:34:988: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (ERROR) Error -: B2B-51505: General validation error.
         at oracle.tip.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2539)
         at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1279)
         at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:790)
         at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1201)
         at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:713)
         at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:2754)
         at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2444)
         at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:464)
         at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:180)
         at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:77)
         at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:171)
         at java.lang.Thread.run(Thread.java:619)
    2010.06.03 at 04:33:34:988: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) Engine: processOutgoingMessageImpl: B2BDomainException
    2010.06.03 at 04:33:34:988: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.engine.Engine:handleOutboundException Updating Error Message: Error -: B2B-51505: General validation error.
    2010.06.03 at 04:33:34:988: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) DbAccess:updateWireBusinessToErrorState
    2010.06.03 at 04:33:34:988: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
    2010.06.03 at 04:33:34:989: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: queryById: Enter
    2010.06.03 at 04:33:34:989: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: queryById: Got RTP Context
    2010.06.03 at 04:33:35:006: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: queryById: Got 1messages for field messageId with value 1410017
    2010.06.03 at 04:33:35:007: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: queryById: Exit
    2010.06.03 at 04:33:35:007: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: findWireMessageByB2BMessageId: querying for id = 1410017
    2010.06.03 at 04:33:35:007: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: findWireMessageByB2BMessageId: Returning null
    2010.06.03 at 04:33:35:007: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message not found.
    2010.06.03 at 04:33:35:008: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
    2010.06.03 at 04:33:35:008: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Enter:
    2010.06.03 at 04:33:35:008: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Got RTP Context
    2010.06.03 at 04:33:35:008: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Exit
    2010.06.03 at 04:33:35:009: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:updateAppMessageState Enter
    2010.06.03 at 04:33:35:009: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: getAppMessageById: Enter appMsg id = 7F000001128FCF1A4C600000EA6A8D00
    2010.06.03 at 04:33:35:009: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: getAppMessageById: Got RTP Context
    2010.06.03 at 04:33:35:012: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: getAppMessageById: Got [1] messages for AppMessage ID 7F000001128FCF1A4C600000EA6A8D00
    2010.06.03 at 04:33:35:012: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: getAppMessageById: Exit
    2010.06.03 at 04:33:35:013: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:setAppMsgErrorInfo Enter
    2010.06.03 at 04:33:35:013: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:setAppMsgErrorInfo Setting AppMessage to ERROR
    2010.06.03 at 04:33:35:013: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:setAppMsgErrorInfo Exitr
    2010.06.03 at 04:33:35:013: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Enter:
    2010.06.03 at 04:33:35:013: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Got RTP Context
    2010.06.03 at 04:33:35:014: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Exit
    2010.06.03 at 04:33:35:014: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:updateAppMessageState Exit
    2010.06.03 at 04:33:35:014: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:DbAccess:updateMsgError(3 params) Enter
    2010.06.03 at 04:33:35:015: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Enter:
    2010.06.03 at 04:33:35:015: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Got RTP Context
    2010.06.03 at 04:33:35:016: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Exit
    2010.06.03 at 04:33:35:016: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:DbAccess:updateMsgError(3 params) Exit
    2010.06.03 at 04:33:35:016: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.engine.Engine:handleOutboundException Updating Native Event Tbl Row
    2010.06.03 at 04:33:35:016: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:updateNativeEvtTblRow Enter
    2010.06.03 at 04:33:35:017: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: queryById: Enter
    2010.06.03 at 04:33:35:017: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: queryById: Got RTP Context
    2010.06.03 at 04:33:35:019: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: queryById: Got 1messages for field messageId with value 1410017
    2010.06.03 at 04:33:35:019: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: queryById: Exit
    2010.06.03 at 04:33:35:019: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: findWireMessageByB2BMessageId: querying for id = 1410017
    2010.06.03 at 04:33:35:019: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: findWireMessageByB2BMessageId: Returning null
    2010.06.03 at 04:33:35:019: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) DbAccess:updateNativeEvtTblRowGot WireMessage with B2BMessage ID 1410017
    2010.06.03 at 04:33:35:020: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:
    ** DbAccess:updateNativeEvtTblRow:tip_wireMsg wiremsg not found
    2010.06.03 at 04:33:35:020: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.engine.Engine:handleOutboundException notifying App
    2010.06.03 at 04:33:35:020: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) Notification: notifyApp: Enter
    2010.06.03 at 04:33:35:020: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) Notification: notifyApp: payload = <Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <correlationId>7F000001128FCF1A4C600000EA6A8D00</correlationId>
    <b2bMessageId>1410017</b2bMessageId>
    <errorCode>B2B-51505</errorCode>
    <errorText>
    Error Brief :
    Validator error - Extra data was encountered.
    An X12 syntax error occurred.
    An X12 syntax error occurred.
    Validator error - Extra data was encountered.
    Validator error - Extra data was encountered.
    A data element with 'Mandatory' status is missing.
    </errorText>
    <errorDescription>
    <![CDATA[
    Error :
    Extra Element was found in the data file as part of Segment REF. Segment REF is defined in the guideline at position 046.{br}{br}This error was detected at:{br}{tab}Segment Count: 3{br}{tab}Element Count: 2{br}{tab}Characters: 567 through 575
    At least one of REF02, REF03 must be present. The syntax rule R0203 of Segment REF is violated. Segment REF is defined in the guideline at position 046.{br}{br}This error was detected at:{br}{tab}Segment Count: 3{br}{tab}Element Count: 2{br}{tab}Characters: 593 through 593
    At least one of REF02, REF03 must be present. The syntax rule R0203 of Segment REF is violated. Segment REF is defined in the guideline at position 046.{br}{br}This error was detected at:{br}{tab}Segment Count: 3{br}{tab}Element Count: 3{br}{tab}Characters: 593 through 593
    Extra Element was found in the data file as part of Segment ISR. Segment ISR is defined in the guideline at position 030.{br}{br}This error was detected at:{br}{tab}Segment Count: 6{br}{tab}Element Count: 1{br}{tab}Characters: 870 through 872
    Extra Element was found in the data file as part of Segment ISR. Segment ISR is defined in the guideline at position 030.{br}{br}This error was detected at:{br}{tab}Segment Count: 6{br}{tab}Element Count: 2{br}{tab}Characters: 907 through 915
    Element ISR01 (Shipment/Order Status Code) is missing. This Element's standard option is 'Mandatory'. Segment ISR is defined in the guideline at position 030.{br}{br}This Element was expected in:{br}{tab}Segment Count: 6{br}{tab}Element Count: 1{br}{tab}Character: 933
    ]]>
    </errorDescription>
    <errorSeverity>2</errorSeverity>
    </Exception>
    Even though I am providing REF01 and ISR01 values, I am getting this Error.
    Below is my XML payload.
    <?xml version="1.0" encoding="UTF-8" ?>
    - <Transaction-870 xmlns:ns0="http://www.edifecs.com/xdata/200" Standard="X12" xmlns="http://www.edifecs.com/xdata/200">
    - <ns0:Segment-ST>
    <ns0:Element-143>870</ns0:Element-143>
    <ns0:Element-329>000000043</ns0:Element-329>
    </ns0:Segment-ST>
    - <ns0:Segment-BSR>
    <ns0:Element-850>3</ns0:Element-850>
    <ns0:Element-847>PA</ns0:Element-847>
    <ns0:Element-127>3110000031OTM_TestPR</ns0:Element-127>
    <ns0:Element-373>20100603</ns0:Element-373>
    </ns0:Segment-BSR>
    - <ns0:Loop-REF>
    - <ns0:Segment-REF>
    <ns0:Element-128>VR</ns0:Element-128>
    <ns0:Element-127>RHEEM002</ns0:Element-127>
    </ns0:Segment-REF>
    </ns0:Loop-REF>
    - <ns0:Loop-HL>
    - <ns0:Segment-HL>
    <ns0:Element-628>1</ns0:Element-628>
    <ns0:Element-735>O</ns0:Element-735>
    </ns0:Segment-HL>
    - <ns0:Segment-PRF>
    <ns0:Element-324>OTM_Test</ns0:Element-324>
    </ns0:Segment-PRF>
    - <ns0:Loop-ISR>
    - <ns0:Segment-ISR>
    <ns0:Element-368>PR</ns0:Element-368>
    <ns0:Element-373>20100531</ns0:Element-373>
    </ns0:Segment-ISR>
    </ns0:Loop-ISR>
    </ns0:Loop-HL>
    - <ns0:Loop-HL>
    - <ns0:Segment-HL>
    <ns0:Element-628>2</ns0:Element-628>
    <ns0:Element-735>I</ns0:Element-735>
    </ns0:Segment-HL>
    - <ns0:Loop-PO1>
    - <ns0:Segment-PO1>
    <ns0:Element-350>1</ns0:Element-350>
    <ns0:Element-330>2</ns0:Element-330>
    <ns0:Element-355>EA</ns0:Element-355>
    <ns0:Element-235>SK</ns0:Element-235>
    <ns0:Element-234>6836003</ns0:Element-234>
    <ns0:Element-235_1>VP</ns0:Element-235_1>
    <ns0:Element-234_1>TAHM ITEM</ns0:Element-234_1>
    </ns0:Segment-PO1>
    - <ns0:Segment-PID>
    <ns0:Element-349>F</ns0:Element-349>
    <ns0:Element-352>TAHM ITEM</ns0:Element-352>
    </ns0:Segment-PID>
    </ns0:Loop-PO1>
    </ns0:Loop-HL>
    - <ns0:Segment-CTT>
    <ns0:Element-354>2</ns0:Element-354>
    </ns0:Segment-CTT>
    - <ns0:Segment-SE>
    <ns0:Element-96>11</ns0:Element-96>
    <ns0:Element-329>000000043</ns0:Element-329>
    </ns0:Segment-SE>
    </Transaction-870>
    Thanks in Advance
    Ravdeep

    Hi Ravdeep,
    Have you validated the payload against the ecs using document editor? If no, please do so.
    Also refer -
    5084: XEngine error - Invalid data (outbound with validation disabled)
    Please paste the complete B2B log here/mail it to my id (in my profile)
    Regards,
    Anuj

  • Getting Validation Error at B2B Console for 856 Outbound B2B-51507

    Hi,
    We are getting this error while sending the EDI 856 in an outgoing Process. We are getting the data from Oracle Apps and sending it to B2B via B2b adapter using mediator.
    we are using X856 ecx file and X856 xsd.
    Can Anyone help in this. If Anyone is having any idea please help us on this.
    Do we need to set the Deployment Validation Property to False? If yes then is it in EM we need to Set?
    Appreciate quick response.
    Below is the error details:
    Id 0AF6038D12BE3AE21CF0000011881680
    Message Id 0AF6038D12BE3AE1C5E0000011881630
    Refer To Message Refer To Message
    Sender Type Specialties
    Receiver Type Name
    Receiver Value XXXX_4010
    Sender Sybron Dental Specialties
    Receiver :XXXX_4010
    Agreement Id:XXXXXXX
    Agreement HEN_KRR_AGR
    Document Type 856
    Document Protocol EDI_X12
    Document Version 4010
    Message Type REQ
    Direction OUTBOUND
    State MSG_ERROR
    Acknowledgement Mode NONE
    Response Mode NONE
    Send Time Stamp Monday, October 25, 2010 6:57:41 AM GMT-07:00
    Receive Time Stamp Monday, October 25, 2010 6:57:41 AM GMT-07:00
    Document Retry Interval 0
    Document Remaining Retry 0
    Native Message Size
    Translated Message Size 3811
    Business Action Name
    Business Transaction Name
    Xpath Name1 XPathName1
    Xpath Value1
    Xpath Expression1
    Xpath Name2 XPathName2
    Xpath Value2
    Xpath Expression2
    Xpath Name3 XPathName3
    Xpath Value3
    Xpath Expression3
    Correlation From XPath Name CorrelationFromXPathName
    Correlation From XPath Value
    Correlation From XPath Expression
    Correlation To XPath Name CorrelationToXPathName
    Correlation To XPath Value
    Correlation To XPath Expression
    Wire Message Wire Message
    Application Message Application Message
    Payload Storage Payload Storage
    Attachment Attachment
    Label soa_b2b_ - Fri Oct 22 04:32:37 PDT 2010
    Collaboration Id 0AF6038D12BE3AE205B0000011881670
    Collabration Name
    Collabration Version
    Business Action Name
    Exchange Protocol Name Generic File
    Exchange Protocol Version 1.0
    Interchange Control Number
    Group Control Number
    Transaction Set Control Number
    Error Code B2B-51507
    Error Description Machine Info: (org-vmsosoa.sds.sybrondental.com) Description: Payload validation error.
    Error Level ERROR_LEVEL_COLLABORATION
    Error Severity ERROR
    Error Text Error Brief : XEngine error.
    This is the Application Message we are getting in Error Details:
    Document Type 856
    Document Definition 856_DocDefHENK
    Document Protocol Name EDI_X12
    Document Protocol Version 4010
    Refer To Application Message Id Refer To Application Message Id
    App Conversation Id
    App Message property {tracking.compositeInstanceId=11, b2b.documentProtocolVersion=4010, b2b.toTradingPartnerId=HEN_KRR_4010, tracking.ecid=0000IjZLVsfDCgS5IFc9yf1ChDOY0034Rz, b2b.fromTradingPartnerId=Sybron Dental Specialties, tracking.conversationId=BPEL, tracking.compositeInstanceCreatedTime=Mon Oct 25 06:57:39 PDT 2010, tracking.parentComponentInstanceId=mediator:D4A7EA60E03F11DFBFC66D8172AE9492, MESH_METRICS=null, b2b.documentTypeName=856, tracking.parentReferenceId=mediator:D4A7EA60E03F11DFBFC66D8172AE9492:D4AC5730E03F11DFBFC66D8172AE9492:oneway}
    Direction OUTBOUND
    State MSG_ERROR
    Error Code B2B-51507
    Error Text Error Brief : XEngine error.
    Error Description Error : Mandatory attribute missing: Standard.
    Created Date Monday, October 25, 2010 6:57:40 AM GMT-07:00
    Modified Date Monday, October 25, 2010 6:57:41 AM GMT-07:00
    Message Size 3811
    Payload Payload
    Business Message Business Message
    Retry Interval 0
    Reattempt Count 0
    Remaining Retry 0
    ECID 0000IjZLVsfDCgS5IFc9yf1ChDOY0034Rz
    Composite Instance Id 11
    Parent Composite Instance Id mediator:D4A7EA60E03F11DFBFC66D8172AE9492
    Conversation Id BPEL
    Domain Name default
    Composite Name Generate856ASNOutbound
    Composite Version 2.0
    Reference Name B2B_GetData

    Hi,
    It looks like , Payload is not valid as per the ecs/xsd so B2B is giving Payload validation Error.
    If Validation is must then validate the payload against ecs/xsd offline and correct.
    or you can turn off validation in Agreement (Validation = false) and redeploy the agreement.
    Rgds,
    Nitesh Jain

  • Internal Delievery channel AIP-51505:  General Validation Error

    hi ,
    I am trying HL7 sample provided with B2b installation. It works fine . Have modified internal delievery channel as file protocol & provided the folder uri , so as to b2b engine picks it up as xml message is dropped in folder. It is resulting in B2B - (ERROR) Error -: AIP-51505: General Validation Error .
    Just wondering why the B2B process is not validating xml file by just modifing internal delievery channel. Do i have to take additional care to configure Internal Delievery channel. ??
    2008.12.04 at 12:05:49:734: Thread-14: B2B - (ERROR) Error -: AIP-51505: General Validation Error
         at oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin.decodeIncomingMessage(GenericExchangePlugin.java:195)
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1364)
         at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2404)
         at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2303)
         at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2258)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)
         at java.lang.Thread.run(Thread.java:534)
    2008.12.04 at 12:05:49:734: Thread-14: B2B - (ERROR) Error -: AIP-51505:  General Validation Error
         at oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin.decodeIncomingMessage(GenericExchangePlugin.java:195)
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1364)
         at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2404)
         at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2303)
         at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2258)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)
         at java.lang.Thread.run(Thread.java:534)
    2008.12.04 at 12:05:49:734: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
    2008.12.04 at 12:05:49:734: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
    2008.12.04 at 12:05:49:734: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-51505: General Validation Error
    2008.12.04 at 12:05:49:734: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
    2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {filename=a01.xml, filesize=1901, file_ext=xml, *fullpath=C:\files\a01.xml, timestamp=2008-12-04T11:43:31.640-05:00}*
    2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning false
    2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA not required
    2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-51505: General Validation Error
    2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
    2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
    2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
    2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum not null
    2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
    2008.12.04 at 12:05:49:781: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
    2008.12.04 at 12:05:49:812: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
    2008.12.04 at 12:05:49:812: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
    2008.12.04 at 12:05:49:812: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exception null
    2008.12.04 at 12:05:49:812: Thread-14: B2B - (ERROR) java.lang.NullPointerException
         at oracle.tip.adapter.b2b.msgproc.DbAccess.insertMsgTblRow(DbAccess.java:839)
         at oracle.tip.adapter.b2b.msgproc.DbAccess.updateWireBusinessToErrorState(DbAccess.java:5150)
         at oracle.tip.adapter.b2b.engine.Engine.handleInboundException(Engine.java:3831)
         at oracle.tip.adapter.b2b.engine.Engine.handleExceptionBeforeIncomingTPA(Engine.java:3702)
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1383)
         at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2404)
         at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2303)
         at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2258)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)
         at java.lang.Thread.run(Thread.java:534)
    Thanks

    Hi Ramesh,
    Thank you for your reply. Basically i need to convert HL7 xml to HL7 binary with delivery channel as file. Changed the
    oracle.tip.adapter.b2b.allTPInOneDirectory= True from false.
    Created Internal Delievery channel with folder as c:\USLabs (USLabs is a host trading partner) on localhost.
    i am placing xml file with name as USLabs_123.xml in this particular folder.
    This xml file is same as a01.xml provided with HL7 sample. but i get this exception.
    Protocol = File
    Version = 1.0
    Transport Header
    filename:USLabs_123.xml
    filesize:1888
    file_ext:xml
    fullpath:C:\USLabs\USLabs_123.xml
    timestamp:2008-12-04T12:27:58.546-05:00
    <?xml version="1.0" ?><ADT_A01 xmlns="http://www.edifecs.com/xdata/200 " xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="HL7" Version="2.3.1" CreatedDate="2005-08-16T16:52:26" CreatedBy="ECXEngine_826" GUID="{1A2726C6-B00E-DA11-8F7A-080020C8D296}"><MSH><MSH.1>|</MSH.1><MSH.2>^~\&amp;</MSH.2><MSH.3><HD.1>#Property(MessageSendingApp)#</HD.1></MSH.3><MSH.4><HD.1>#Property(MessageSendingFacility)#</HD.1></MSH.4><MSH.5><HD.1>#Property(MessageReceivingApp)#</HD.1></MSH.5><MSH.6><HD.1>#Property(MessageReceivingFacility)#</HD.1></MSH.6><MSH.7><TS.1>20050804162010</TS.1></MSH.7><MSH.8 xsi:nil="true"></MSH.8><MSH.9><MSG.1>ADT</MSG.1><MSG.2>A01</MSG.2></MSH.9><MSH.10>#ControlNumber#</MSH.10><MSH.11><PT.1>#Property(ProcessingID)#</PT.1></MSH.11><MSH.12><VID.1>2.3.1</VID.1></MSH.12><MSH.13 xsi:nil="true"></MSH.13><MSH.14 xsi:nil="true"></MSH.14><MSH.15>AL</MSH.15><MSH.16>ER</MSH.16><MSH.17>#Property(CountryCode)#</MSH.17><MSH.18>ASCII</MSH.18><MSH.19><CE.1>ENG</CE.1></MSH.19></MSH><PID><PID.1>1</PID.1><PID.2 xsi:nil="true"></PID.2><PID.3><CX.1>A0000010</CX.1></PID.3><PID.4 xsi:nil="true"></PID.4><PID.5><XPN.1><FN.1>Miranda Charles 01_10</FN.1></XPN.1></PID.5><PID.6 xsi:nil="true"></PID.6><PID.7><TS.1>20001001</TS.1></PID.7><PID.8>F</PID.8></PID><PV1><PV1.1>1</PV1.1><PV1.2 xsi:nil="true"></PV1.2><PV1.3 xsi:nil="true"></PV1.3><PV1.4 xsi:nil="true"></PV1.4><PV1.5 xsi:nil="true"></PV1.5><PV1.6 xsi:nil="true"></PV1.6><PV1.7 xsi:nil="true"></PV1.7><PV1.8 xsi:nil="true"></PV1.8><PV1.9 xsi:nil="true"></PV1.9><PV1.10 xsi:nil="true"></PV1.10><PV1.11 xsi:nil="true"></PV1.11><PV1.12 xsi:nil="true"></PV1.12><PV1.13 xsi:nil="true"></PV1.13><PV1.14 xsi:nil="true"></PV1.14><PV1.15 xsi:nil="true"></PV1.15><PV1.16 xsi:nil="true"></PV1.16><PV1.17 xsi:nil="true"></PV1.17><PV1.18 xsi:nil="true"></PV1.18><PV1.19><CX.1>10010</CX.1></PV1.19></PV1></ADT_A01>
    2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) DBContext beginTransaction: Enter
    2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
    2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) DBContext beginTransaction: Leave
    2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS enter
    2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS checking header names
    2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS name =filename
    2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS name =filesize
    2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS name =file_ext
    2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS name =fullpath
    2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS name =timestamp
    2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS exit
    2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Enter
    2008.12.05 at 06:03:28:109: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Exit
    2008.12.05 at 06:03:28:109: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:onMessage sendEventtrue
    2008.12.05 at 06:03:28:125: Thread-17: B2B - (DEBUG) DBContext commit: Enter
    2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Enter
    2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) DBContext beginTransaction: Enter
    2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
    2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) DBContext beginTransaction: Leave
    2008.12.05 at 06:03:28:125: Thread-16: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Enter
    2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processEvents begin transaction
    2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) DBContext beginTransaction: Enter
    2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) DBContext beginTransaction: Leave
    2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Enter
    2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Enter
    2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:getWireMessage Enter
    2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:getWireMessage Exit
    2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:formTransportMessage Enter
    2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:formTransportMessage Exit
    2008.12.05 at 06:03:28:125: Thread-16: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Enter
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Identify Business Protocol
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Do Unpack using the BP specific package class
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) MimePackaging:unpack:Enter
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) MimePackaging:doUnpack:Enter
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:Enter
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:encoding = null
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:oracle.tip.adapter.b2b.packaging.Component@7f8922
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:Exit
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) MimePackaging:unpack:Exit
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Decode the Incoming Message into B2B Message
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Enter
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Number of Components = 1
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage Transport Protocol = {File}
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage filename = USLabs_123.xml
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage File TP Host name = USLabs
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: USLabs Type: null Value: null
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage fromParty = USLabs
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: USLabs Type: null Value: null
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: null Type: null Value: null
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage security info NULL
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Exit
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Enter
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage toTP null
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage hubUrl null
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Exit
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage ProtocolCollabId = null
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage CollaborationName null
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Enter
    2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate check non-RosettaNet Message
    2008.12.05 at 06:03:28:187: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Exit
    2008.12.05 at 06:03:28:187: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Protocol Collaboration Id : null
    2008.12.05 at 06:03:28:187: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7DocumentPlugin:identifyIncomingDocument Enter
    2008.12.05 at 06:03:28:187: Thread-16: B2B - (WARNING) checkForEB:Does not end with EB. Appending EB to payload
    2008.12.05 at 06:03:28:234: Thread-17: B2B - (DEBUG) DBContext commit: Transaction.commit()
    2008.12.05 at 06:03:28:234: Thread-17: B2B - (DEBUG) DBContext commit: Leave
    2008.12.05 at 06:03:28:406: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7SelectorImpl:HL7SelectorImpl Enter
    2008.12.05 at 06:03:28:406: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7SelectorImpl:HL7SelectorImpl document params = null
    2008.12.05 at 06:03:28:406: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7SelectorImpl:isValidateEnvelope oracle.tip.adapter.b2b.hl7.ignoreValidation set to ALL
    2008.12.05 at 06:03:28:406: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7SelectorImpl:HL7SelectorImpl validateEnvelope = false
    2008.12.05 at 06:03:28:406: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7SelectorImpl:HL7SelectorImpl Leave
    2008.12.05 at 06:03:28:406: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7SelectorImpl:cloneSelector Enter
    2008.12.05 at 06:03:28:421: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7SelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.hl7.HL7SelectorImpl@1e1ec86
    2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7DocumentPlugin:identifyIncomingDocument errcode = Execute failed - CECToolsException thrown - HRESULT[650007], description[The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons:  A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect.]
    2008.12.05 at 06:03:31:046: Thread-16: B2B - (ERROR) com.edifecs.shared.jni.JNIException: Execute failed - CECToolsException thrown - HRESULT[650007], description[The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons:  A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect.]
         at com.edifecs.shared.jni.xdata.INativeToXData.ExecuteNative(Native Method)
         at com.edifecs.shared.jni.xdata.INativeToXData.Execute(Unknown Source)
         at oracle.tip.adapter.b2b.document.hl7.HL7DocumentPlugin.identifyIncomingDocument(HL7DocumentPlugin.java:328)
         at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3024)
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1552)
         at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2404)
         at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2303)
         at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2258)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)
         at java.lang.Thread.run(Thread.java:534)
    *2008.12.05 at 06:03:31:046: Thread-16: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error*
         at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3043)
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1552)
         at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2404)
         at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2303)
         at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2258)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)
         at java.lang.Thread.run(Thread.java:534)
    2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
    2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
    2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-50083: Document protocol identification error
    2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
    2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {filename=USLabs_123.xml, filesize=1888, file_ext=xml, fullpath=C:\USLabs\USLabs_123.xml, timestamp=2008-12-04T12:27:58.546-05:00}
    2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning false
    2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA not required
    2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-50083: Document protocol identification error
    2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
    2008.12.05 at 06:03:31:062: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
    2008.12.05 at 06:03:31:062: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
    2008.12.05 at 06:03:31:062: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum not null
    2008.12.05 at 06:03:31:062: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
    2008.12.05 at 06:03:31:062: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message protocol message id
    2008.12.05 at 06:03:31:062: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
    2008.12.05 at 06:03:31:078: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
    2008.12.05 at 06:03:31:078: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
    2008.12.05 at 06:03:31:078: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name null
    2008.12.05 at 06:03:31:078: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value nullnull
    2008.12.05 at 06:03:31:078: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
    2008.12.05 at 06:03:31:093: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
    2008.12.05 at 06:03:31:093: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
    2008.12.05 at 06:03:31:093: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Native Event Tbl Row
    2008.12.05 at 06:03:31:093: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
    2008.12.05 at 06:03:31:093: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = USLabs_123.xml@C0A8006411E06D104AB0000013426420
    2008.12.05 at 06:03:31:109: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
    ** DbAccess:updateNativeEvtTblRow:tip_wireMsg protocolCollabID = null
    2008.12.05 at 06:03:31:109: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException notifying App
    2008.12.05 at 06:03:31:109: Thread-16: B2B - (DEBUG) Engine:notifyApp Enter
    2008.12.05 at 06:03:31:109: Thread-16: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
    <Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <correlationId>null</correlationId>
    <b2bMessageId>C0A8006411E06D1048C0000013426410</b2bMessageId>
    <errorCode>AIP-50083</errorCode>
    <errorText>Document protocol identification error</errorText>
    <errorDescription>
    <![CDATA[Machine Info: (xpone)
    Description: Unable to identify the document protocol of the message
    StackTrace:
    Error -:  AIP-50083:  Document protocol identification error
         at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3043)
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1552)
         at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2404)
         at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2303)
         at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2258)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)
         at java.lang.Thread.run(Thread.java:534)
      ]]>
    </errorDescription>
    <errorSeverity>2</errorSeverity>
    </Exception>
    Please help.
    Thanks

  • Read-only radio group losing value on validation error

    It took quite a while to track this down, but I think I've got it narrowed down properly. I have an APEX form for updating a record in a databse table with a radio group which is conditionally read-only. If that radio group has a value AND is read-only, when the form is submitted and hits a validation error, the value of the radio group is lost.
    For example, the radio group SUBMITTED_FOR_APPROVAL is set to Y and is read-only for a given user. That user then changes something else on the form and submits it. However, the form now hits a validation error for some field. When the form reloads with the validation error displayed, all the fields are restored except the read-only radio group which is now blank. If a select list is used with the identical read-only condition, it works fine. Likewise, if a radio group is used, but the read-only condition is removed, it works fine. It is only when it is a radio group and it is read-only, that the value does not appear to be submitted to the session with all the form values whent he form is submitted.
    Is this a bug or am I simply missing something?
    Apex 3.1.2
    Rgds/Mark M.

    It's using a shared component LOV cleverly called LOV_YN which consists of a static LOV with
    1 Display=Yes, Return=Y
    2 Display=No, Return=N
    The settings in the LOV section on the item iteself:
    Named LOV: LOV_YN
    Display Extra values: No Dynamic translation: Not translated
    Number of columns: 2 Display null: No
    Null display value is blank as is null return value
    Item was setup as a radio group and was only converted over to a select list to work around this issue. Let me know what else you need and thanks again.
    Rgds/Mark M.

  • Weblogic app server wsdl web service call with SSL Validation error = 16

    Weblogic app server wsdl web service call with SSL Validation error = 16
    I need to make wsdl web service call in my weblogic app server. The web service is provided by a 3rd party vendor. I keep getting error
    Cannot complete the certificate chain: No trusted cert found
    Certificate chain received from ws-eq.demo.xxx.com - xx.xxx.xxx.156 was not trusted causing SSL handshake failure
    Validation error = 16
    From the SSL debug log, I can see 3 verisign hierarchy certs are correctly loaded (see 3 lines in the log message starting with “adding as trusted cert”). But somehow after first handshake, I got error “Cannot complete the certificate chain: No trusted cert found”.
    Here is how I load trustStore and keyStore in my java program:
         System.setProperty("javax.net.ssl.trustStore",”cacerts”);
         System.setProperty("javax.net.ssl.trustStorePassword", trustKeyPasswd);
         System.setProperty("javax.net.ssl.trustStoreType","JKS");
    System.setProperty("javax.net.ssl.keyStoreType","JKS");
    System.setProperty("javax.net.ssl.keyStore", keyStoreName);
         System.setProperty("javax.net.ssl.keyStorePassword",clientCertPwd);      System.setProperty("com.sun.xml.ws.transport.http.client.HttpTransportPipe.dump","true");
    Here is how I create cacerts using verisign hierarchy certs (in this order)
    1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignClass3G5PCA3Root.txt -alias "Verisign Class3 G5P CA3 Root"
    1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignC3G5IntermediatePrimary.txt -alias "Verisign C3 G5 Intermediate Primary"
    1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignC3G5IntermediateSecondary.txt -alias "Verisign C3 G5 Intermediate Secondary"
    Because my program is a weblogic app server, when I start the program, I have java command line options set as:
    -Dweblogic.security.SSL.trustedCAKeyStore=SSLTrust.jks
    -Dweblogic.security.SSL.ignoreHostnameVerification=true
    -Dweblogic.security.SSL.enforceConstraints=strong
    That SSLTrust.jks is the trust certificate from our web server which sits on a different box. In our config.xml file, we also refer to the SSLTrust.jks file when we bring up the weblogic app server.
    In addition, we have working logic to use some other wsdl web services from the same vendor on the same SOAP server. In the working web service call flows, we use clientgen to create client stub, and use SSLContext and WLSSLAdapter to load trustStore and keyStore, and then bind the SSLContext and WLSSLAdapter objects to the webSerive client object and make the webservie call. For the new wsdl file, I am told to use wsimport to create client stub. In the client code created, I don’t see any way that I can bind SSLContext and WLSSLAdapter objects to the client object, so I have to load certs by settting system pramaters. Here I attached the the wsdl file.
    I have read many articles. It seems as long as I can install the verisign certs correctly to web logic server, I should have fixed the problem. Now the questions are:
    1.     Do I create “cacerts” the correct order with right keeltool options?
    2.     Since command line option “-Dweblogic.security.SSL.trustedCAKeyStore” is used for web server jks certificate, will that cause any problem for me?
    3.     Is it possible to use wsimport to generate client stub that I can bind SSLContext and WLSSLAdapter objects to it?
    4.     Do I need to put the “cacerts” to some specific weblogic directory?
    ---------------------------------wsdl file
    <wsdl:definitions name="TokenServices" targetNamespace="http://tempuri.org/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata">
         <wsp:Policy wsu:Id="TokenServices_policy">
              <wsp:ExactlyOne>
                   <wsp:All>
                        <sp:TransportBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
                             <wsp:Policy>
                                  <sp:TransportToken>
                                       <wsp:Policy>
                                            <sp:HttpsToken RequireClientCertificate="true"/>
                                       </wsp:Policy>
                                  </sp:TransportToken>
                                  <sp:AlgorithmSuite>
                                       <wsp:Policy>
                                            <sp:Basic256/>
                                       </wsp:Policy>
                                  </sp:AlgorithmSuite>
                                  <sp:Layout>
                                       <wsp:Policy>
                                            <sp:Strict/>
                                       </wsp:Policy>
                                  </sp:Layout>
                             </wsp:Policy>
                        </sp:TransportBinding>
                        <wsaw:UsingAddressing/>
                   </wsp:All>
              </wsp:ExactlyOne>
         </wsp:Policy>
         <wsdl:types>
              <xsd:schema targetNamespace="http://tempuri.org/Imports">
                   <xsd:import schemaLocation="xsd0.xsd" namespace="http://tempuri.org/"/>
                   <xsd:import schemaLocation="xsd1.xsd" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>
              </xsd:schema>
         </wsdl:types>
         <wsdl:message name="ITokenServices_GetUserToken_InputMessage">
              <wsdl:part name="parameters" element="tns:GetUserToken"/>
         </wsdl:message>
         <wsdl:message name="ITokenServices_GetUserToken_OutputMessage">
              <wsdl:part name="parameters" element="tns:GetUserTokenResponse"/>
         </wsdl:message>
         <wsdl:message name="ITokenServices_GetSSOUserToken_InputMessage">
              <wsdl:part name="parameters" element="tns:GetSSOUserToken"/>
         </wsdl:message>
         <wsdl:message name="ITokenServices_GetSSOUserToken_OutputMessage">
              <wsdl:part name="parameters" element="tns:GetSSOUserTokenResponse"/>
         </wsdl:message>
         <wsdl:portType name="ITokenServices">
              <wsdl:operation name="GetUserToken">
                   <wsdl:input wsaw:Action="http://tempuri.org/ITokenServices/GetUserToken" message="tns:ITokenServices_GetUserToken_InputMessage"/>
                   <wsdl:output wsaw:Action="http://tempuri.org/ITokenServices/GetUserTokenResponse" message="tns:ITokenServices_GetUserToken_OutputMessage"/>
              </wsdl:operation>
              <wsdl:operation name="GetSSOUserToken">
                   <wsdl:input wsaw:Action="http://tempuri.org/ITokenServices/GetSSOUserToken" message="tns:ITokenServices_GetSSOUserToken_InputMessage"/>
                   <wsdl:output wsaw:Action="http://tempuri.org/ITokenServices/GetSSOUserTokenResponse" message="tns:ITokenServices_GetSSOUserToken_OutputMessage"/>
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:binding name="TokenServices" type="tns:ITokenServices">
              <wsp:PolicyReference URI="#TokenServices_policy"/>
              <soap12:binding transport="http://schemas.xmlsoap.org/soap/http"/>
              <wsdl:operation name="GetUserToken">
                   <soap12:operation soapAction="http://tempuri.org/ITokenServices/GetUserToken" style="document"/>
                   <wsdl:input>
                        <soap12:body use="literal"/>
                   </wsdl:input>
                   <wsdl:output>
                        <soap12:body use="literal"/>
                   </wsdl:output>
              </wsdl:operation>
              <wsdl:operation name="GetSSOUserToken">
                   <soap12:operation soapAction="http://tempuri.org/ITokenServices/GetSSOUserToken" style="document"/>
                   <wsdl:input>
                        <soap12:body use="literal"/>
                   </wsdl:input>
                   <wsdl:output>
                        <soap12:body use="literal"/>
                   </wsdl:output>
              </wsdl:operation>
         </wsdl:binding>
         <wsdl:service name="TokenServices">
              <wsdl:port name="TokenServices" binding="tns:TokenServices">
                   <soap12:address location="https://ws-eq.demo.i-deal.com/PhxEquity/TokenServices.svc"/>
                   <wsa10:EndpointReference>
                        <wsa10:Address>https://ws-eq.demo.xxx.com/PhxEquity/TokenServices.svc</wsa10:Address>
                   </wsa10:EndpointReference>
              </wsdl:port>
         </wsdl:service>
    </wsdl:definitions>
    ----------------------------------application log
    adding as trusted cert:
    Subject: CN=VeriSign Class 3 International Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
    Issuer: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
    Algorithm: RSA; Serial number: 0x641be820ce020813f32d4d2d95d67e67
    Valid from Sun Feb 07 19:00:00 EST 2010 until Fri Feb 07 18:59:59 EST 2020
    adding as trusted cert:
    Subject: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
    Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
    Algorithm: RSA; Serial number: 0x3c9131cb1ff6d01b0e9ab8d044bf12be
    Valid from Sun Jan 28 19:00:00 EST 1996 until Wed Aug 02 19:59:59 EDT 2028
    adding as trusted cert:
    Subject: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
    Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
    Algorithm: RSA; Serial number: 0x250ce8e030612e9f2b89f7054d7cf8fd
    Valid from Tue Nov 07 19:00:00 EST 2006 until Sun Nov 07 18:59:59 EST 2021
    <Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Cipher: SunPKCS11-Solaris version 1.6 for algorithm DESede/CBC/NoPadding>
    <Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Cipher for algorithm DESede>
    <Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.6 for algorithm RSA/ECB/NoPadding>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSetup: loading trusted CA certificates>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 28395435>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 115>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <25779276 SSL3/TLS MAC>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <25779276 received HANDSHAKE>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 2400410601231772600606506698552332774
    Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
    Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
    Not Valid Before:Tue Dec 18 19:00:00 EST 2012
    Not Valid After:Wed Jan 07 18:59:59 EST 2015
    Signature Algorithm:SHA1withRSA
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number: 133067699711757643302127248541276864103
    Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
    Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
    Not Valid Before:Sun Feb 07 19:00:00 EST 2010
    Not Valid After:Fri Feb 07 18:59:59 EST 2020
    Signature Algorithm:SHA1withRSA
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 2400410601231772600606506698552332774
    Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
    Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
    Not Valid Before:Tue Dec 18 19:00:00 EST 2012
    Not Valid After:Wed Jan 07 18:59:59 EST 2015
    Signature Algorithm:SHA1withRSA
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number: 133067699711757643302127248541276864103
    Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
    Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
    Not Valid Before:Sun Feb 07 19:00:00 EST 2010
    Not Valid After:Fri Feb 07 18:59:59 EST 2020
    Signature Algorithm:SHA1withRSA
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 16>
    <Mar 7, 2013 6:59:22 PM EST> <Warning> <Security> <BEA-090477> <Certificate chain received from ws-eq.demo.xxx.com - xx.xxx.xxx.156 was not trusted causing SSL handshake failure.>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 16>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is untrusted>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 16>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (16): CERT_CHAIN_UNTRUSTED>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
    java.lang.Exception: New alert stack
         at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
         at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
         at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
         at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
         at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
         at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
         at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
         at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
         at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
         at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
         at com.certicom.tls.record.WriteHandler.write(Unknown Source)
         at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
         at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
         at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
         at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
         at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
         at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
         at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
         at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)
         at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
         at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
         at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
         at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
         at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:296)
         at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
         at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
         at javax.xml.ws.Service.<init>(Service.java:56)
         at ideal.ws2j.eqtoken.TokenServices.<init>(TokenServices.java:64)
         at com.citi.ilrouter.util.IpreoEQSSOClient.invokeRpcPortalToken(IpreoEQSSOClient.java:165)
         at com.citi.ilrouter.servlets.T3LinkServlet.doPost(T3LinkServlet.java:168)
         at com.citi.ilrouter.servlets.T3LinkServlet.doGet(T3LinkServlet.java:206)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
         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(Unknown Source)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
         at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 6457753>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 6457753>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.removeContext(ctx): 22803607>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 14640403>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 115>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <23376797 SSL3/TLS MAC>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <23376797 received HANDSHAKE>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 2400410601231772600606506698552332774
    Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
    Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
    Not Valid Before:Tue Dec 18 19:00:00 EST 2012
    Not Valid After:Wed Jan 07 18:59:59 EST 2015
    Signature Algorithm:SHA1withRSA
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number: 133067699711757643302127248541276864103
    Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
    Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
    Not Valid Before:Sun Feb 07 19:00:00 EST 2010
    Not Valid After:Fri Feb 07 18:59:59 EST 2020
    Signature Algorithm:SHA1withRSA
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 2400410601231772600606506698552332774
    Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
    Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
    Not Valid Before:Tue Dec 18 19:00:00 EST 2012
    Not Valid After:Wed Jan 07 18:59:59 EST 2015
    Signature Algorithm:SHA1withRSA
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number: 133067699711757643302127248541276864103
    Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
    Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
    Not Valid Before:Sun Feb 07 19:00:00 EST 2010
    Not Valid After:Fri Feb 07 18:59:59 EST 2020
    Signature Algorithm:SHA1withRSA
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 16>
    <Mar 7, 2013 6:59:22 PM EST> <Warning> <Security> <BEA-090477> <Certificate chain received from ws-eq.demo.xxx.com - 12.29.210.156 was not trusted causing SSL handshake failure.>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 16>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is untrusted>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 16>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (16): CERT_CHAIN_UNTRUSTED>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
    java.lang.Exception: New alert stack
         at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
         at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
         at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
         at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
         at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
         at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
         at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
         at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
         at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
         at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
         at com.certicom.tls.record.WriteHandler.write(Unknown Source)
         at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
         at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
         at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
         at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
         at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
         at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
         at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
         at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)
         at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
         at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
         at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
         at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
         at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:296)
         at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
         at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
         at javax.xml.ws.Service.<init>(Service.java:56)
         at ideal.ws2j.eqtoken.TokenServices.<init>(TokenServices.java:64)
         at com.citi.ilrouter.util.IpreoEQSSOClient.invokeRpcPortalToken(IpreoEQSSOClient.java:165)
         at com.citi.ilrouter.servlets.T3LinkServlet.doPost(T3LinkServlet.java:168)
         at com.citi.ilrouter.servlets.T3LinkServlet.doGet(T3LinkServlet.java:206)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
         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(Unknown Source)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
         at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 16189141>

    I received a workaround by an internal message.
    The how to guide is :
    -Download the wsdl file (with bindings, not the one from ESR)
    -Correct it in order that the schema corresponds to the answer (remove minOccurs or other things like this)
    -Deploy the wsdl file on you a server (java web project for exemple). you can deploy on your local
    -Create a new logicial destination that point to the wsdl file modified
    -Change the metadata destination in your web dynpro project for the corresponding model and keep the execution desitnation as before.
    Then the received data is check by the metadata logical destination but the data is retrieved from the correct server.

Maybe you are looking for

  • Batch Printing with File Names in Photoshop CS5

    How can I batch print hundreds of images with the file name on each of the print? I also need them to be printed at their original dimensions, which mean they should not be scaled when printed to papers.  Any help would be greatly appreciated. Thanks

  • Need info on how Palm OS Works

    Question is about PalmOS, not webOS. Moved to Software. WyreNut I am a Volunteer here, not employed by HP. You too can become an HP Expert! Details HERE! If my post has helped you, click the Kudos Thumbs up! If it solved your issue, Click the "Accept

  • Dreamweaver CS5-6 What is the difference

    HI I currently use CS4 and am wondering what the difference is between 5 and or 6. Do I need to upgrade? Is it worth the price? I currently most likely use about 40% of the features. Dougas SImons

  • Hello World page error

    I'm getting following error while testing my connections.We have Oracle apps versiopn 11.5.9, Database version 8i. Any help to fix this problem ? oracle.apps.fnd.framework.OAException: Application: FND, Message Name: SECURITY_APPL_USERID_INVALID. (Co

  • Naming Song Problems in Library

    i downloaded the new itunes 7.0.1.8 and i want to change the song info of some of the songs in my library and its not letting me change anything. its not letting me add an album name to it, but when i right click -> change info, it says the album nam