locked
BizTalk triggering RPG program in AS/400 BizTalk using HIS RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
     
    0

    Hello Steve,

    I am getting an error while making a connection to AS 400 system from BizTalk using Host Apps adapter.

    Steps followed are :

    1) Created a Host Integration Application type project

    2) added .Net Client Library  --> consumed the RPG program (in AS 400 ) which created the schema

    3) Created an object in TI manager and Remote environment ( Distributed Program Call )

    4) we used the schema which gets generated in step no:2, in the BizTalk application and triggered the input to the HIS program using Host Apps adapter.

    we are using port no:8475

    Error is :

    1. HISETBG0001 Application Integrator has intercepted an exception in method AMMGIDR01. Following is the exception description: HISMDTT0006 The DPCTransport received a socket error while attempting to receive user data when processing method AMMGIDR01. IP Address: 172.22.11.16, port: 8475, program name: AMMGIDR01, Error description: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

    Thanks in Advance

    Monday, June 10, 2013 8:19 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    If the data is being sent by the BizTalk Adapter for Host Applications to the RPG program, it would seem that this part is working OK. If the RPG program is supposed to send a response back to the Host Apps adapter, it sounds like the response is not making it back to the adapter before the underlying TCP/IP socket is closed.

    It sounds like the 2 minute (120 second) timeout is happening because of the Windows TCP/IP TcpTimedWaitDelay default timeout. The TCP/IP stack in Windows was designed to time out sockets according to the TcpTimedWaitDelay timer, which is 120 seconds in current Windows versions.

    The problem may be similar to the one described in the following KB article:

    823183  BUG: Long running COMTI transactions are unsuccessful and you receive an event 102 (2150) error message

    http://support.microsoft.com/kb/823183/EN-US

    By similar I mean that maybe the RPG program (in this case) is slow in sending back the response or is not sending back the response. The result is that the TCP/IP connection times out after 2 minutes so the error is logged.

    Thanks...

    Stephen Jackson - MSFT

    Tuesday, June 11, 2013 5:00 PM