Topic
  • 18 replies
  • Latest Post - ‏2014-04-22T20:39:33Z by tomiLee
haranath
haranath
37 Posts

Pinned topic WSP with MQ backend

‏2013-06-11T14:33:36Z |

Hi,

I have webservice proxy with MQ back end,when I invoked this service through soap-UI I am getting the proper response.

But at the same time I am getting the following error in logs.

Network Error (Connection timed out) on Back interface (URL: dpmq://MQGroup/?RequestQueue=RQ.C8537.XMLM.INQUIRE;ReplyQueue=LQ.C8537.XMLM.INQUIRE;SetReplyTo=true;Sync=true) when processing the server response

currently back side time out is set to 300 sec ,I have verified the configurations across the regions and it looks fine .TCP test also working fine with MQ host.Anyone  please help me to  find out the root cause of this issue ?.

 

Thanks,

Haranath.

 

 

Updated on 2013-06-11T14:35:21Z at 2013-06-11T14:35:21Z by haranath
  • kenhygh
    kenhygh
    1789 Posts

    Re: WSP with MQ backend

    ‏2013-06-11T14:54:58Z  

    Are the messages getting to the backend?

    Is the backend system responding? are there response messages on the queue?

  • haranath
    haranath
    37 Posts

    Re: WSP with MQ backend

    ‏2013-06-11T16:26:23Z  

    Yes, messages are reaching back end and it is responding too.I found one interesting thing in logs all these error messages in logs  are associated with single transaction ID (like 12345) .This error message is coming in logs for every 10 secs gap so some process is keep on trying to read the message not sure what it is?.

  • kenhygh
    kenhygh
    1789 Posts

    Re: WSP with MQ backend

    ‏2013-06-11T16:39:46Z  
    • haranath
    • ‏2013-06-11T16:26:23Z

    Yes, messages are reaching back end and it is responding too.I found one interesting thing in logs all these error messages in logs  are associated with single transaction ID (like 12345) .This error message is coming in logs for every 10 secs gap so some process is keep on trying to read the message not sure what it is?.

    What else is going on in those transactions? is there some special processing somewhere?

  • haranath
    haranath
    37 Posts

    Re: WSP with MQ backend

    ‏2013-06-11T16:56:56Z  

    No special processing on those transactions , once after receiving the request datapower sends it to  MQ.

    Is it due to retry configurations in MQ manager?

  • kenhygh
    kenhygh
    1789 Posts

    Re: WSP with MQ backend

    ‏2013-06-11T17:30:20Z  
    • haranath
    • ‏2013-06-11T16:56:56Z

    No special processing on those transactions , once after receiving the request datapower sends it to  MQ.

    Is it due to retry configurations in MQ manager?

    It's not going to retry if the response was returned. Are you sure all requests are getting responses?

    In the default log, you can click on the transaction ID and see every log entry for that transaction. Can you do that, and see if anything jumps out at you?

  • haranath
    haranath
    37 Posts

    Re: WSP with MQ backend

    ‏2013-06-11T19:26:46Z  

    If the service doesn't returns any response  within the time limit and timedout does MQ maanger retry it for getting response?.Currently log level is set at error  

    level so it is not possible  check all messages.

     

  • kenhygh
    kenhygh
    1789 Posts

    Re: WSP with MQ backend

    ‏2013-06-11T20:13:53Z  
    • haranath
    • ‏2013-06-11T19:26:46Z

    If the service doesn't returns any response  within the time limit and timedout does MQ maanger retry it for getting response?.Currently log level is set at error  

    level so it is not possible  check all messages.

     

    MQ can retry, but you only get this message when a response has not been received within the timeout. 

    Can you reproduce this anywhere but Prod? 

  • haranath
    haranath
    37 Posts

    Re: WSP with MQ backend

    ‏2013-06-11T20:43:21Z  

    This is not happening in any environments except TEST region. I have verified configurations of all objects but didn't find any difference.

    Currently in DEV region front & back end time out parameters are set to 1 sec, how we will re-produce this scenario?.

     

  • haranath
    haranath
    37 Posts

    Re: WSP with MQ backend

    ‏2013-06-17T15:54:22Z  

    Can you guys please help on this issue?.

  • kenhygh
    kenhygh
    1789 Posts

    Re: WSP with MQ backend

    ‏2013-06-17T16:07:24Z  

    The description you've given so far isn't clear.

    What else is happening in the failing transactions? What backend cannot be reached? You probably need to turn log level to 'debug' to be able to figure this out.

  • swlinn
    swlinn
    1391 Posts

    Re: WSP with MQ backend

    ‏2013-06-17T22:40:09Z  
    • haranath
    • ‏2013-06-17T15:54:22Z

    Can you guys please help on this issue?.

    I'm assuming you are getting a 2033 MQ return code where your Get of your reply queue with correlation id = request message id not finding a message.  You can verify the status code by placing

    <xsl:variable name="respcode" select="dp:response-header('x-dp-response-code')" />

    and writing it to your logs.  Are you seeing the message processed by your provider and are you seeing a response on your reply queue?  If so, is your provider copying the request message id to the response correlation id?  That has been a scenario I've seen recently with one customer.  If the provider isn't doing this your reply will never be found and you'll get a 2033.  If the message isn't showing up on the reply queue, can you verify the request MQMD headers on the provider side, particularly the ReplyToQ and ReplyToQMgr and determine if/where the provider is sending the reply.

    Regards,

    Steve

  • haranath
    haranath
    37 Posts

    Re: WSP with MQ backend

    ‏2013-06-18T16:25:22Z  

    Hi Guys,

    Thanks for your responses.

    We are getting the following error message in logs repeatedly for every 10 seconds.

    Network Error (Connection timed out) on Back interface (URL: dpmq://MQGroup/?RequestQueue=RQ.C8537.XMLM.INQUIRE;ReplyQueue=LQ.C8537.XMLM.INQUIRE;SetReplyTo=true;Sync=true) when processing the server response

    All the error messages have same transaction-ID and same source IP address,when we invoke the service through soapUI we are getting the proper response.We are not sure whether datapower is doing retry of the failed transaction or front end client ?.We are seeing this error message from the last 10 days Could you please suggest the way to stop this retry?.

     

    Thanks

     

     

     

  • Dream-S
    Dream-S
    32 Posts

    Re: WSP with MQ backend

    ‏2014-04-16T11:45:48Z  

    same issue here!! Anyone has the answer? please? :)

  • NILAY97
    NILAY97
    241 Posts

    Re: WSP with MQ backend

    ‏2014-04-17T17:55:08Z  
    • Dream-S
    • ‏2014-04-16T11:45:48Z

    same issue here!! Anyone has the answer? please? :)

    Hi,

    What is the cache timeout set on the Queue Manager DataPower? If it is blank, set it to 60 and do a re-test please.

    Thanks,

    Nilay

  • NILAY97
    NILAY97
    241 Posts

    Re: WSP with MQ backend

    ‏2014-04-17T17:56:00Z  
    • Dream-S
    • ‏2014-04-16T11:45:48Z

    same issue here!! Anyone has the answer? please? :)

    Hi,

    What is the cache timeout set on the Queue Manager DataPower? If it is blank, set it to 60 and do a re-test please.

    Thanks,

    Nilay

  • NILAY97
    NILAY97
    241 Posts

    Re: WSP with MQ backend

    ‏2014-04-17T17:56:30Z  
    • Dream-S
    • ‏2014-04-16T11:45:48Z

    same issue here!! Anyone has the answer? please? :)

    Hi,

    What is the cache timeout set on the Queue Manager DataPower? If it is blank, set it to 60 and do a re-test please.

    Thanks,

    Nilay

  • NILAY97
    NILAY97
    241 Posts

    Re: WSP with MQ backend

    ‏2014-04-17T17:58:38Z  
    • Dream-S
    • ‏2014-04-16T11:45:48Z

    same issue here!! Anyone has the answer? please? :)

    Hi,

    What is the cache timeout set on the Queue Manager DataPower? If it is blank, set it to 60 and do a re-test please.

    Thanks,

    Nilay

  • tomiLee
    tomiLee
    44 Posts

    Re: WSP with MQ backend

    ‏2014-04-22T20:39:33Z  
    • haranath
    • ‏2013-06-18T16:25:22Z

    Hi Guys,

    Thanks for your responses.

    We are getting the following error message in logs repeatedly for every 10 seconds.

    Network Error (Connection timed out) on Back interface (URL: dpmq://MQGroup/?RequestQueue=RQ.C8537.XMLM.INQUIRE;ReplyQueue=LQ.C8537.XMLM.INQUIRE;SetReplyTo=true;Sync=true) when processing the server response

    All the error messages have same transaction-ID and same source IP address,when we invoke the service through soapUI we are getting the proper response.We are not sure whether datapower is doing retry of the failed transaction or front end client ?.We are seeing this error message from the last 10 days Could you please suggest the way to stop this retry?.

     

    Thanks

     

     

     

    You can also try setting a timeout value in the dpmq url

     


    "Note that the Timeout must be set in the Destination URL used to contact the WebSphere MQ
    back-end queue or the Gateway will continuously poll for a response message,
    causing the front side HTTP connection to time out."