AIP-52251: Error identifying remote trading partner at MLLP Exchange with

Question

used HL7 over MLLP, one trading partner is EAI(B2B Localhost), another is EchoServer(a java application, the hostname is is4-nb4.corp.ha.org.hk). used a script to enqueue message. like below:
DECLARE
enqueue_options dbms_aq.enqueue_options_t;
message_properties dbms_aq.message_properties_t;
msg_handle RAW(16);
ipmsg b2b.IP_MESSAGE_TYPE;
xml_clob clob;
msg_id number(10);
subscribers dbms_aq.aq$_recipient_list_t;
BEGIN
select message_seq.nextval into msg_id from dual;
xml_clob := '<?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>EDI</HD.1></MSH.3><MSH.4><HD.1>PWH</HD.1></MSH.4><MSH.5><HD.1>EchoPac</HD.1></MSH.5><MSH.6><HD.1>PWH</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>TEST007</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>TEST, Patient 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>
subscribers(1) := SYS.AQ$_AGENT('b2buser', null, null);
message_properties.RECIPIENT_LIST := subscribers;
ipmsg := b2b.IP_MESSAGE_TYPE (msg_id, null,'EAI','EchoServer','Echo_ADTA01_Process', 'ADT_A01', '2.3.1', 1, xml_clob, null);
dbms_aq.enqueue(queue_name => 'b2b.IP_OUT_QUEUE',
enqueue_options => enqueue_options,
message_properties => message_properties,
payload => ipmsg,
msgid => msg_handle);
commit;
END;
show errors;
then go to the B2B Report tab, can see two message like below
EAI EchoServer MLLP - 1.0 HL7 - 2.3.1 Echo_ADTA01_Process WaitFA 2007年11月12日 星期一 下午05:51:37
Acknowledgement Invalid 2007年11月12日 星期一 下午
and in the log file, like this:
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.mllp.MLLPExchangePlugin:decodeIncomingMessage Could not find a Trading Partner with MLLP ID = is4-nb4. Please check the Trading Partner Identification section of your Trading Partner
2007.11.12 at 17:51:43:064: Thread-10: B2B - (ERROR) Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
     at oracle.tip.adapter.b2b.exchange.mllp.MLLPExchangePlugin.decodeIncomingMessage(MLLPExchangePlugin.java:247)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1177)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2030)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1962)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1920)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:463)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:335)
     at java.lang.Thread.run(Thread.java:534)
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.mllp.MLLPExchangePlugin:decodeIncomingMessage identify trading partner by MLLP Id failed for is4-nb4 with ExceptionError -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
2007.11.12 at 17:51:43:064: Thread-10: B2B - (ERROR) Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
     at oracle.tip.adapter.b2b.exchange.mllp.MLLPExchangePlugin.decodeIncomingMessage(MLLPExchangePlugin.java:257)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1177)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2030)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1962)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1920)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:463)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:335)
     at java.lang.Thread.run(Thread.java:534)
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {From=is4-nb4, FromIP=160.19.23.102, FARequired=true, protocolVersion=1.0, ToIP=160.19.55.114, Port=4911, Message-Id=1194861102002-1207274363, protocol=TCP, To=is4wingw02}
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning true
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error Set
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: createAndSendFA Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: createAndSendFA processed by HL7
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7DocumentPlugin:createFA Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7DocumentPlugin:createFA Not creating an ACK for an incoming ACK Message
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: createAndSendFA B2BMessage is null
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: createAndSendFA Exit
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA Sent
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Leave
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum not null
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message protocol message id
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Native Event Tbl Row
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = 1194861102002-1207274363
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException notifying App
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) Engine:notifyApp Enter
2007.11.12 at 17:51:43:096: Thread-10: 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>A0133772116334587C90000068CD8000</b2bMessageId>
<errorCode>AIP-52251</errorCode>
<errorText>Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4</errorText>
<errorDescription>
<![CDATA[Machine Info: (is4wingw02)
Error -:  AIP-52251:  Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4  ]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) Engine:notifyApp Exit
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updated the Error Message Successfully: Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Exit
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Exit
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Exit
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Exit
2007.11.12 at 17:51:43:111: Thread-10: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Exit
2007.11.12 at 17:51:43:111: Thread-10: B2B - (DEBUG) DBContext commit: Enter
2007.11.12 at 17:51:43:111: Thread-10: B2B - (DEBUG) DBContext commit: Transaction.commit()
2007.11.12 at 17:51:43:111: Thread-10: B2B - (DEBUG) DBContext commit: Leave
2007.11.12 at 17:51:43:111: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
here said not find the remote partner, but in B2B server, can ping Echoserver.
what is wrong?

Answer 1

Hello again,
I have tried all different combinations with the IP addresses and host names, but to no avail. Then I changed the Trading Partner Identification Type from MLLP Id to Sending Application (one of the customer requirements is to be able to identify the Trading Partner by the combination of Sending App/Sending Facility, since they are running multiple HL7 applications on one host). However, I still see the same error in the log file - for some reason, B2B is still trying to identify the Trading Partner by the MLLP Id. Redeploying the configuration didn't help, the requested identification type is ignored.
Please help! If needed, I can send the B2B log file, but maybe I'm missing something obvious.
BTW, the customer has installed the patch for bug 6439217 on October 10th. The B2B version is 10.1.2.2.0.
Thanks in advance!