Author |
Message
|
srk31 |
Posted: Wed Sep 01, 2010 3:38 pm Post subject: MQSeries Backend +Reason Code 2033 |
|
|
Apprentice
Joined: 01 Sep 2010 Posts: 39
|
Hi All,
I am having MQSeries as backend and mq as front side handler. I am getting following error
The get call timed out before receiving any messages (Reason Code 2033), MQ Reason Code = 2033, MQ URL = dpmq://LocalQM/?RequestQueue=TEST.REQ;ReplyQueue=TEST.RSP;Transactional=true
The get call timed out before receiving any messages (Reason Code 2033)
The same queues are working fine for different mpg where i am get the response with fraction of milliseconds. I have same backend and mqmanager configurations for this new mpg flow
I have set up 120 sec for timeout. I am not able to figure out what could be the problem. No clue in the datapower logs.
Can any one suggest what could be the problem
Thanks,
SRK
|
|
Back to top |
|
|
mqjeff |
Posted: Wed Sep 01, 2010 6:11 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
|
Back to top |
|
|
srk31 |
Posted: Wed Sep 01, 2010 6:36 pm Post subject: |
|
|
Apprentice
Joined: 01 Sep 2010 Posts: 39
|
when i look into dp error code its showing connection time out for this . The same Qmanger and front side handler configurations are working for other mpg. i was wondering whats wrong here |
|
Back to top |
|
|
Vitor |
Posted: Thu Sep 02, 2010 2:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
srk31 wrote: |
i was wondering whats wrong here |
Same thing as for any 2033:
- Code problem meaning a badly identified reply (sender or receiver)
- Code problem indicating no reply at all
- Configuration problem misrouting reply
A simple search of this forum or the documentation would have told you this _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
|
shashivarungupta |
Posted: Thu Sep 02, 2010 4:37 am Post subject: Re: MQSeries Backend +Reason Code 2033 |
|
|
Grand Master
Joined: 24 Feb 2009 Posts: 1343 Location: Floating in space on a round rock.
|
I believe the URL you gave is for MQBEH !!
MQRC 2033 is MQRC_NO_MSG_AVAILABLE
srk31 wrote: |
The same queues are working fine for different mpg where i am get the response with fraction of milliseconds. I have same backend and mqmanager configurations for this new mpg flow.. |
Are you sure that your MPG is UP ?
Are you sure that your MQFSH is UP ?
Whats in MPG Policy (iff you got) ?
srk31 wrote: |
..No clue in the datapower logs.. |
Are you talking about System Log for MPG ? logs related to mpgw(YourMPGname) !!!
If yes, What do you see it there ?
_________________ *Life will beat you down, you need to decide to fight back or leave it. |
|
Back to top |
|
|
srk31 |
Posted: Thu Sep 02, 2010 8:34 am Post subject: |
|
|
Apprentice
Joined: 01 Sep 2010 Posts: 39
|
Hi,
Shashi,
I have checked both system logs and mpg logs. The msg says 2033.
I have recreated mpg again, its working fine.
Thanks for the inputs guys. I dont know where I have done the wrong.
Thanks,
SRK |
|
Back to top |
|
|
Gaya3 |
Posted: Thu Sep 02, 2010 12:44 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
srk31 wrote: |
Hi,
Shashi,
I have checked both system logs and mpg logs. The msg says 2033.
I have recreated mpg again, its working fine.
Thanks for the inputs guys. I dont know where I have done the wrong.
Thanks,
SRK |
i am having a doubt in the configuration part of DP here, when you saidn after recreating the mpg it started working
I would like to know where it went wrong, what was the mistake. _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
|
srk31 |
Posted: Fri Sep 03, 2010 7:42 am Post subject: |
|
|
Apprentice
Joined: 01 Sep 2010 Posts: 39
|
|
Back to top |
|
|
srk31 |
Posted: Mon Sep 13, 2010 2:23 pm Post subject: |
|
|
Apprentice
Joined: 01 Sep 2010 Posts: 39
|
Hi Guys,
I have same problem again. I dont know whats the wrong configuration i had.
I had created new msg flow test_xyz_mpg,with same queue mgr and same queues and dropping the msgs to the queue.
For different flow (test_abc_mpg)i am getting response successfully from mq.
I have taken the msg that comes from last node in the flow through probe and manually tested using rfh2Util,i am getting proper response.
But when i tested through the mpg, i am getting connetion timeout -- 2033. I could not any clue from logs.
Does any one have idea
Thanks,
SRK
|
|
Back to top |
|
|
srk31 |
Posted: Mon Sep 13, 2010 2:34 pm Post subject: |
|
|
Apprentice
Joined: 01 Sep 2010 Posts: 39
|
one thing i observed is the msg from this mpg is going to dead letter queue. I have checked the content, there is nothing wrong in the msg.
Does it shows any clue? i dont see anything wrong here |
|
Back to top |
|
|
Vitor |
Posted: Mon Sep 13, 2010 4:11 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
srk31 wrote: |
one thing i observed is the msg from this mpg is going to dead letter queue. I have checked the content, there is nothing wrong in the msg.
Does it shows any clue? i dont see anything wrong here |
You should see a dead letter header with a clue _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
|
fjb_saper |
Posted: Mon Sep 13, 2010 5:54 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003 Posts: 20729 Location: LI,NY
|
Quote: |
Transactional=true |
Are you sure you meant to put this on a request reply model? If you only commit after having received the reply you will never send the request!
Have fun _________________ MQ & Broker admin |
|
Back to top |
|
|
srk31 |
Posted: Tue Sep 14, 2010 5:27 am Post subject: |
|
|
Apprentice
Joined: 01 Sep 2010 Posts: 39
|
Vitor,
Thanks for the reply. In dead letter header is see MQFB_APPL_FIRST,819.
So what could be the reason.
fjb, i have removed this attribute from mq url, so its not the case. |
|
Back to top |
|
|
Vitor |
Posted: Tue Sep 14, 2010 5:50 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
srk31 wrote: |
In dead letter header is see MQFB_APPL_FIRST,819.
So what could be the reason. |
Urgh. It's being put by an application (presumably DataPower in this context) because there's nowhere else for a message that caused an unhandled exception to go. WMB does this.
Make sure there's a backout queue on all the WMQ queues in use & go through the application logs with a fine tooth comb looking for exceptions. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
|
srk31 |
Posted: Tue Sep 14, 2010 10:56 am Post subject: |
|
|
Apprentice
Joined: 01 Sep 2010 Posts: 39
|
Datapower is dropping the msg to the queue Test.REQ. I have WMB flow, which will listen the queue(Test.REQ) and send the mocked soap fault response msg to Test.RSP queue.
I have the bar file which is deployed, I dont have the source code for this bar file, so thats the reason,i cant able to debug the flow.
I am using same bar file and same queue mgr and same queues for different mpg flow, there i am getting correct response.
BTW, i have created the backout queue for Test.REQ already . but still have same problem.I am pretty much new to MQ,WMB. |
|
Back to top |
|
|
|