1 2 3 Previous Next 37 Replies Latest reply: Oct 12, 2009 12:23 AM by Anuj Dwivedi RSS

    error in inbound processing: EDI message -> XML Gateway

    Wanda
      Hello!

      I've setup a DELFOR transaction in B2B and modified XML Gateway settings for internal delivery channel in order to send the message to EBS, but I'm getting weird errors in b2b.log. (XML Gateway in EBS is not setup yet, but it should't be an issue since incoming errors are handled in EBS, and I would just see an inbound transaction with processing errors in Transaction Monitor.)

      In the beginning of b2b.log I see this:
      2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Push Stack: queryInternalDeliveryChannel
      2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Pop Stack: queryInternalDeliveryChannel
      2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound initialize
      2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 Obtaining inbound connection...
      2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound connect string: jdbc:oracle:thin:@server64.xa.si:1521:test2
      2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound username: apps
      2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:32 CEST 2009 inbound initialize exit
      2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Enter
      2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Exit
      2009.07.07 at 15:26:32:538: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run Thread start
      2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Exit
      2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) B2BStarter - B2B initialized


      After I copy the edi file to the incoming directory B2B starts processing the file:
      2009.07.07 at 15:30:01:878: Thread-10: B2B - (DEBUG)
      Protocol = File
      Version = 1.0
      Transport Header
      filename:00003442_23.CMS
      filesize:12345
      file_ext:CMS
      fullpath:C:\xa_endpoint\00003442_23.CMS
      timestamp:2009-07-06T16:14:29.393+01:00


      As I see in the log: B2B finds the trading partner and agreement and all looks fine. But later comes this:
      2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Enter
      2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to destination. protocol is XMLGateway Queues
      2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to XMLGW
      2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Converting B2B message to ECX message..
      2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Inbound - B2BtoECX - Enter
      2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 B2B Message -
      2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : COLLABORATION_NAME : null
      2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : ACTION_NAME : DELFOR
      2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE : DELFOR
      2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE_REVISION : D97A
      2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : SOURCE_NAME : tpartner
      2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DESTINATION_NAME : Xa d.d.
      2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : PAYLOAD : UNB+UNOA.............. edi message continues here
      2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : PAYLOAD : <?xml version="1.0" ?><Transaction-DELFOR............... xml continues here
      2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 ECX Message -
      2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry Could not deliver the message; exception message is null
      2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry No application side retry
      2009.07.07 at 15:30:06:081: Thread-9: B2B - (ERROR) Error -: AIP-50903: Message "0A14011912255682A58000003257C600-1" retry count is zero
           at oracle.tip.adapter.b2b.msgproc.MessageHandler.handleAppMessageRetry(MessageHandler.java:394)
           at oracle.tip.adapter.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:344)
           at oracle.tip.adapter.b2b.msgproc.Request.putMsg(Request.java:657)
           at oracle.tip.adapter.b2b.msgproc.Request.continueRequest(Request.java:481)
           at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:410)
           at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
           at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
           at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
           at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
           at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
           at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
           at java.lang.Thread.run(Thread.java:534)

      Last message repeats once more and then:
      2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
      2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
      2009.07.07 at 15:30:06:096: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
      2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateMsgError(3 params) Exit
      2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Enter
      2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Transaction.commit()
      2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Leave
      2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Exit
      2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Exit
      2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: processIncomingMessage setting seq numbers
      2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Call Incoming Request Processor
      2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Enter
      2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest TransportBindings created
      2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Create a Message Table Row for Request message with message state Continue Processing
      2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
      2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
      2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryExchangeProtocolRevision
      2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryExchangeProtocolRevision
      2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
      2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryDocumentProtocolRevision
      2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryDocumentProtocolRevision
      2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (ERROR) Error -: AIP-13115: Not in an active transaction
           at oracle.tip.repos.core.persistency.BaseObject.prologue(BaseObject.java:1408)
           at oracle.tip.repos.core.persistency.BaseObject.createObject(BaseObject.java:913)
           at oracle.tip.model.instance.DataStorage.create(DataStorage.java:794)
           at oracle.tip.adapter.b2b.message.MessageStorage.create(MessageStorage.java:145)
           at oracle.tip.adapter.b2b.msgproc.DbAccess.insertMsgTblRow(DbAccess.java:953)
           at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:397)
           at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
           at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
           at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
           at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
           at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
           at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
           at java.lang.Thread.run(Thread.java:534)

      2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
      2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage General Exception ERROR

      Error repeats a few times.
      Wire message stays in Processing status, Business message is errored and an exception message is created in ip_in_queue.
      Both remote and host delivery channels have retry set to 1. Agreement was re-deployed + all B2B restared, but the problem remained.


      Could anyone help with this? What could be wrong?

      Thanks in advance.

      Kind regards,
      Wanda


      PS. I've checked all threads that might have anything to do with this, but found nothing useful.
        • 1. Re: error in inbound processing: EDI message -> XML Gateway
          Anuj Dwivedi
          Hi Wanda,

          Your configuration is fine and B2B is behaving as expected. It's retrying once(retry count) before erroring out the message (that's why you are seeing same error two times). Since your XMLGateways are not setup yet so B2B is not able to connect to them and deliver the message.

          Configure XMLGateways and test. Everything will work fine. For XMLGateway integration, please refer-
          http://www.b2bgurus.com/2007/08/xmlgateway-integration.html

          Regards,
          Anuj
          • 2. Re: error in inbound processing: EDI message -> XML Gateway
            Wanda
            Hi Anuj,

            thanks for your answer.

            I've seen this article already, but XML Gateway setup in E-Business Suite has nothing to do with this. Those 2 ECX queues are standard components of E-Business Suite, so it's absolutely not advisable to drop and/or re-create them. What I need is to connect the B2B server to E-Business Suite. As you could see in the beginning of the log, the connection was established and B2B started to listen to messages. Any inappropriate changes in B2B's XML Gateway setup (servername, ip, port, sid and the name of the 2 ECX queues) cause B2B not to initialize properly and also errors appear in the log.

            XML Gateway setup in E-Business Suite is about adding rows to tables in standard way through gui (forms). In order to enqueue a message in a queue you don't have to setup trading partner, transaction and message map. These are just "accessories" for processing it. Enqueue can be done using dbms_aq.enqueue and incoming message will be seen in Transaction monitor. (This scenario can be tested also using EBS's Transport agent page without even touching XML Gateway setup.)

            Another thing is that when I had zero for retry count, the error messages were still more than once, so I don't see any connection between these parameters.

            Interesting are the following errors in b2b.log:
            -> oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry Could not deliver the message; exception message is null
            -> Error -: AIP-13115: Not in an active transaction
            and that Wire message stays in Processing status.

            Do you maybe know what these errors above mean and what is causing them to appear? Retry count is definitely not a solution, even though the message sounds alike.


            Thanks again.

            Regards,
            Wanda
            • 3. Re: error in inbound processing: EDI message -> XML Gateway
              Anuj Dwivedi
              Hi Wanda,

              Can you please mail me the B2B log and IDC log (b2b_idc_transport.log) in debug mode (id in my profile)?

              Regards,
              Anuj
              • 4. Re: error in inbound processing: EDI message -> XML Gateway
                Wanda
                Hi Anuj,

                thanks for your quick reply.

                IDC log is empty (which I find very weird), but B2B I'm sending to you.

                Regards,
                Wanda
                • 5. Re: error in inbound processing: EDI message -> XML Gateway
                  Anuj Dwivedi
                  Hi Wanda,

                  I checked B2B log and it shows that B2B is not able to deliver the message to XML Gateway but reason is not clear. Even after that exception when B2B tries to update the wire and business message state to "Error" then also an exception occurs.

                  Can you plaese let me know -

                  1. Is this the first time you are testing this system?
                  2. On which patch are you and was this patch applied successfully (run Opatch lsinventory command to check)
                  3. Did you run the post installation scripts?

                  IDC log will actually tell that what problem occured while passing message to xml gateway. For IDC log ,make sure that you have below entry in your tip.properties file and it is uncommented -

                  oracle.tip.adapter.b2b.transportTrace = /<Ora_Midtier_Directory>/ip/log/transport.trc

                  HTH.

                  Regards,
                  Anuj
                  • 6. Re: error in inbound processing: EDI message -> XML Gateway
                    Prasanna Chandrashekhara
                    Hi Wanda,

                    Can you please check permission on the ECX QUEUES

                    Thanks and Regards,
                    Prasanna
                    • 7. Re: error in inbound processing: EDI message -> XML Gateway
                      Wanda
                      Hi Anuj,

                      thanks for taking the time to examine the file.

                      Answers to your questions:
                      1. Yes, this is the 1st time for B2B, but the EBS I'm trying to connect to is up and running for approx. 2 years (it's a test instance).

                      2. Patching was done by the customer's sysadmin, so I don't really have an overview on what and how he did. Result of opatch:
                      Installed Patch List:
                      =====================
                      1) Patch 8298731 applied on Sat Jun 13 09:23:42 CEST 2009
                      2) Patch 5907304 applied on Thu Jul 17 14:26:55 CEST 2008


                      3. In theory the sysadmin should have run it, but how could I double-check this?
                      I know he had problems while applying patch 8298731, but he said it was solved later. (Customer is using windows os, which is making a lot of troubles otherwise.)


                      Regarding IDC log there is no success. I've restared B2B at least 5 times plus once the database, but still nothing. In tip.properties:
                      oracle.tip.adapter.b2b.transportTrace = C:\APPS\OAS\ip\log/transport.trc

                      also I tried the following values:
                      C:\\APPS\\OAS\\ip\\log/transport.trc (since there is a similar entry: oracle.tip.LogDirectory = C:\\APPS\\OAS\\ip\\log)
                      C:\\\\\\\\\\\\\\\\APPS\\\\\\\\\\\\\\\\OAS\\\\\\\\\\\\\\\\ip\\\\\\\\\\\\\\\\log/transport.trc (this was commented before; maybe it comes from some default)
                      true (I had no other idea)

                      Result is the same for all the cases: b2b_idc_transport.log file is 0 bytes, but b2b_dc_transport.log has initial data+writes log when processing.
                      If I remove or comment the above line from tip.properties, then no transport log files are created.


                      I've updated the agreement to have B2B inbound for the internal delivery channel, re-deployed it and it worked fine -> transaction(s) appeared in IP_IN_QUEUE.
                      Changing it back to XML Gateway (and re-deploying) causes all original problems.

                      Regards,
                      Wanda
                      • 8. Re: error in inbound processing: EDI message -> XML Gateway
                        Wanda
                        Hi Prasanna,

                        Thanks for writing me. I don't really understand what you mean by permissions. ECX_INBOUND is a standard queue in E-Business Suite. In our version (11.5.10) it's owned by APPS user, which is the same user that is setup in B2B's XML Gateway Inbound parameters. So, if connecting with apps user to EBS database, it's possible to enqueue an xml using dbms_aq.enqueue procedure.

                        I've tried to enqueu a message (using the xml from the errored business message in B2B) and I was able to find it in Oracle Workflow Manager's Agent Activity page (included in EBS, accessible with Workflow Administrator responsibility). Also it was possible to see results of processing in ecx_inbound_logs and ecx_error_msgs tables.

                        Regards,
                        Wanda
                        • 9. Re: error in inbound processing: EDI message -> XML Gateway
                          Anuj Dwivedi
                          Hi Wanda,

                          Did IDC log generate when you changed IDC's to B2B Inbound? If yes, then really problem is strange because then I cannot say that patch is the culprit.

                          I am not very sure whether it is possible for you or not, but can you test the same configuration from any other system or in any other environment?

                          Regards,
                          Anuj
                          • 10. Re: error in inbound processing: EDI message -> XML Gateway
                            Wanda
                            Hi Anuj,

                            No, I don't remember ever seeing anything in that file. It was always 0 size even when having B2B Inbound.

                            Unfortunately I don't know any other client of ours that would be even interested in this. Plus there is no chance to get a place on our servers. (Even more, I don't know any other company that would use windows os in order to have exactly the same test case...)

                            Thanks for your efforts. I hope you still have some ideas about what could be wrong...

                            Regards,
                            Wanda


                            PS. In the meanwhile I've opened a SR on metalink, but I don't really have good experience with their help.
                            • 11. Re: error in inbound processing: EDI message -> XML Gateway
                              Anuj Dwivedi
                              Hi Wanda,

                              You can setup same system in local machines also, if feasible and possible. Check whether you can reproduce the issue in local. OS can never be a problem and I am saying this on the basis of my personal experience with Oracle B2B on three different OS (Windows, Solaris and Unix)

                              If patch could not apply successfully then it may cause the problem but still in your case I am not sure that problem is same. The only reason behind my doubt on Patch is because of IDC logs not getting generated. Is it possible to reapply the patch and test? If yes, then make sure that patch is applying successfully.

                              Follow up on SR and post the SR number here so that Oracle B2B IDC team can also look into that.

                              Regards,
                              Anuj
                              • 12. Re: error in inbound processing: EDI message -> XML Gateway
                                Wanda
                                Hi Anuj,

                                I'll try to ask that sysadmin to re-apply the patch and maybe even go there to see what is done. To install this OAS to another place, I'm afraid it won't go.

                                Worst case I can make db link to EBS and a job that'll be checking if there were any new edi-s processed and if so, enqueue the xml myself (I mean with my procedure). Anyway I'll keep trying with standard way maybe once it'll go.

                                SR number and name is:
                                7600994.993: error in B2B intergration inbound processing: EDI message -> XML Gateway

                                First response was the same as yours 'cause they thought EBS is not setup at all - but this is not the case. I'll let you know if they come up with some news.

                                Regards,
                                Wanda
                                • 13. Re: error in inbound processing: EDI message -> XML Gateway
                                  Anuj Dwivedi
                                  Hi Wanda,

                                  I was going through other threads and found that similar problems have been identified earlier also when transport parameters could not be seeded properly while applying the patch.

                                  Please refer -

                                  error in inbound processing: EDI message -> XML Gateway

                                  Re: AIP-50077:  Cannot Initialize Transport

                                  B2B Seed Errors

                                  So would be better if you go for reapplication of both the patches and make sure that no error occurs.

                                  Regards,
                                  Anuj
                                  • 14. Re: error in inbound processing: EDI message -> XML Gateway
                                    Wanda
                                    Hi Anuj,

                                    thank you very much for the links, I'll go through them and contact the customer's sysadmin in order to re-apply the patches. (I'm not allowed to do it on their servers.)

                                    There is nothing new on SR yet.

                                    Have a nice weekend & Regards,
                                    Wanda
                                    1 2 3 Previous Next