IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Back to discussions
Expand all | Collapse all

.Net API (502) Bad Gateway error

  • 1.  .Net API (502) Bad Gateway error

    Posted Tue June 04, 2013 05:34 AM

    Hello,

    Iam using Tamino .net API edit or xml documents to Tamino or getting information from Tamino.

    The problem: when I’m firing a lot of query to Tamino to get some information (the query uses

    TaminoConnectionMode.GlobalTransaction

    sometimes the remote server returned an error: (502) Bad Gateway.

    Why this error happens and what is the right way to solve it if I have to use transactions and i can not use thread sleeping becouse the performance is important to me.

    Thank in advance ,
    Wouter Splinter

    This issue is also related to .Net API (502) Bad Gateway error - webMethods - Software AG Tech Community & Forums.


    #API-Management
    #webMethods
    #webMethods-Tamino-XML-Server-APIs


  • 2.  RE: .Net API (502) Bad Gateway error

    Posted Mon June 10, 2013 04:36 PM

    Bad gateway indicates that the client IP/name is not reachable
    Do you have firewall between these two systems? check that.
    Or check if the target system is up running all the time.


    #API-Management
    #webMethods
    #webMethods-Tamino-XML-Server-APIs


Related Content