Skip to Content

TCP Gateway Issues

Hi all ,

For RFC to SOAP Scenario, we are using TCP gateway to monitor the payload's response.

The Issue ocurs when large amount of data is triggered, TCP gateway goes down and ends up with connection being lost and data being not sent to Webservices. This issue always requires manual trigger or a dedicated resource monitoring the same ( twice daily).

Can someone help me how to overcome this issue or whether any special tool is there as a substitute for TCP gateway?

P.S : Few ppl suggested SOAP UI comment on this tool too.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Sep 30, 2015 at 08:25 AM

    Hi Sai,

    The TCP gateway is a tool useful for testing connections and possible issue but in determined moments, it is not a tool to have set all the time.

    What is you really want?, if you want to know the errors you can have the alert configuration enabled.

    What is your issue?, if you share the exceptions, may be we can help you better.

    For you main question, there are some programs that help to know what happen in the communication, you can try with a sniffer like WireShark.


    Add comment
    10|10000 characters needed characters exceeded

  • Sep 30, 2015 at 08:33 AM

    Hi Sai,

    Please check the tool given in below blog by Stefan

    Troubleshooting SOAP, HTTP and Mail Adapter Scenarios with TCPGateway



    Add comment
    10|10000 characters needed characters exceeded

  • Sep 30, 2015 at 09:28 AM

    Hi Sai,

    TCP Gateway is a Java SE application, which means it is executed in context of JVM and you can size and tune that JVM by calling TCP Gateway with additional JVM specific parameters. For example, I assume you may have run out of available threads or exhaust memory (it would be a good starting point to check if TCP Gateway didn't end up with out of memory in heap or non-heap area), which will affect TCP Gateway stability.

    Is Iñaki already replied, TCP Gateway is good for troubleshooting, but it is not intended to be used for day to day usage, especially in high volume environment. You can for sure size it accordingly so that it will be capable of handling even high load, but this is just not the tool for regular monitoring.

    If you use PI/PO or other middleware solution in between RFC caller and SOAP service, you may want to log messages and their payloads in the middleware and get more advanced and well-equipped monitoring toolset for your requirements.

    If you want to persist application data coming in RFC response, then you may consider enhancing the application which issues outbound RFC calls and add logging functionality to it.



    Add comment
    10|10000 characters needed characters exceeded