ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere DataPower » MQSeries Backend +Reason Code 2033

Post new topic  Reply to topic Goto page 1, 2  Next
 MQSeries Backend +Reason Code 2033 « View previous topic :: View next topic » 
Author Message
srk31
PostPosted: Wed Sep 01, 2010 3:38 pm    Post subject: MQSeries Backend +Reason Code 2033 Reply with quote

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
View user's profile Send private message
mqjeff
PostPosted: Wed Sep 01, 2010 6:11 pm    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

mqrc 2033
Back to top
View user's profile Send private message
srk31
PostPosted: Wed Sep 01, 2010 6:36 pm    Post subject: Reply with quote

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
View user's profile Send private message
Vitor
PostPosted: Thu Sep 02, 2010 2:37 am    Post subject: Reply with quote

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
View user's profile Send private message
shashivarungupta
PostPosted: Thu Sep 02, 2010 4:37 am    Post subject: Re: MQSeries Backend +Reason Code 2033 Reply with quote

Grand Master

Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.

srk31 wrote:


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)


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
View user's profile Send private message Send e-mail
srk31
PostPosted: Thu Sep 02, 2010 8:34 am    Post subject: Reply with quote

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
View user's profile Send private message
Gaya3
PostPosted: Thu Sep 02, 2010 12:44 pm    Post subject: Reply with quote

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
View user's profile Send private message
srk31
PostPosted: Fri Sep 03, 2010 7:42 am    Post subject: Reply with quote

Apprentice

Joined: 01 Sep 2010
Posts: 39

Gayatri,

exactly dont know whats the wrong configuration i have done. As i recollect, i have turned off processbackenderrors. By default its on.
This might be culprit i suppose.

I have gone through one of the tutorial
http://www-01.ibm.com/support/docview.wss?uid=swg27018746&aid=1




Thanks,
SRK
Back to top
View user's profile Send private message
srk31
PostPosted: Mon Sep 13, 2010 2:23 pm    Post subject: Reply with quote

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
View user's profile Send private message
srk31
PostPosted: Mon Sep 13, 2010 2:34 pm    Post subject: Reply with quote

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
View user's profile Send private message
Vitor
PostPosted: Mon Sep 13, 2010 4:11 pm    Post subject: Reply with quote

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
View user's profile Send private message
fjb_saper
PostPosted: Mon Sep 13, 2010 5:54 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
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
View user's profile Send private message Send e-mail
srk31
PostPosted: Tue Sep 14, 2010 5:27 am    Post subject: Reply with quote

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
View user's profile Send private message
Vitor
PostPosted: Tue Sep 14, 2010 5:50 am    Post subject: Reply with quote

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
View user's profile Send private message
srk31
PostPosted: Tue Sep 14, 2010 10:56 am    Post subject: Reply with quote

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
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » WebSphere DataPower » MQSeries Backend +Reason Code 2033
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.