|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
2232 on Tandem NSK |
« View previous topic :: View next topic » |
Author |
Message
|
pcrparimi |
Posted: Tue Apr 23, 2002 6:40 am Post subject: |
|
|
Apprentice
Joined: 09 Oct 2001 Posts: 43 Location: NY
|
This problem is on Tandem NSK. MQ 5.1 is installed. We have a java pgm which continuously polls on a local queue for messages. If the pgm finds any message it will process it and if no message available, pgm sleeps for some time(say 2 sec) and again looks into the queue. Getting the message by pgm is done under syncpoint. Probelm is, if there is no message available for a long time (say about 3hrs), pgm is abending with reason code of 2232. if the pgm finds message occassionally it's not failing.
here i'm giving the logic of the pgm.
class A{
static void main(){
classB.openqueu(localQ) //this method opens the queue in get mode
while(true){
tx.begin(); //Begin of Transaction
rcvdmsg = classB.getmessage(localQ); //gets the msg under syncpoint
insert the message in DB;
tx.commit(); //commit Transaction
}
closequeue(localQ) //closes the local queue.
}
}
ClassB{
openqueue(){
}
getmessage(MQQueue q1){
try{
getMessage(q1)
}
catch(MQException emq){
if the reason code is 2033 ignore the exception sleep for 2 seconds.
else throw exception
}
}
}
is this problem because, i have opened the queue for long time and doing nothing. Please advise.
Thanks,
Poorna
[ This Message was edited by: pcrparimi on 2002-04-23 08:04 ] |
|
Back to top |
|
 |
bower5932 |
Posted: Tue Apr 23, 2002 11:22 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
I checked an internal database and found an APAR (IC32363) that seems to describe what you are seeing. Basically, it said to make sure that you specify the syncpoint option on the MQGMO. If you don't specify it, you can encounter the error that you are seeing. Hope this helps. |
|
Back to top |
|
 |
mqonnet |
Posted: Tue Apr 23, 2002 5:39 pm Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
Hi pcrparimi,
There are two issues relating to this problem.
1) On Tandem NSK, default is SYNCPOINT. But on MQ 5.1 GA, there was a problem and hence SYNCPOINTING was not functioning as expected. And hence you have to implement this scenario only by using MQGMO_SYNCPOINT option on Get alongwith starting a Transaction all by yourself. The CSD would resolve this problem which is expeted soon.
2) As for why you got 2232. One of the reasons which i can think of is. On NSK, TMF controlls the transactional activity. By default each transaction is valid only for 2 hours on TMF. And after which this transaction is aborted by TMF. You might want to change this value within TMF, or as well modify your program to start a new transaction every 100 odd minutes. This way you would avoid getting this error.
Hope this helps.
Cheers.
Kumar
_________________ IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|