| Author |
Message
|
| akm.mohan |
 Posted: Tue Feb 23, 2010 9:45 am Post subject: QL Complition Code 2 : reson code 2219 |
 |
|
Apprentice
Joined: 07 Oct 2008
Posts: 41
|
Hi Friends,
Greetings..!! Hope you all doing great.I one issue here,could you please help in this.
Issue: we have a process which built in .Net application.Usually this process picks msgs from the local queue.during some time this process get hung and msgs are filling up in the queue. THere are no logs in about this in MQ part.but in the application logs it says error "Complition Code 2 : reson code 2219".i checked the channels they are fine..what could be the issue.
my doubt is,recently we ugraded our MQ 6 to MQ 7.is that Application should need to update the new dll provided by MQ 7?
Please give me some solution to resolve this isse.
THanks in Advance for your support..!!
Kris |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Feb 23, 2010 10:04 am Post subject: Re: QL Complition Code 2 : reson code 2219 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| akm.mohan wrote: |
my doubt is,recently we ugraded our MQ 6 to MQ 7.is that Application should need to update the new dll provided by MQ 7?
|
It won't hurt.
It sounds more like there's an application bug where 2 concurrent calls are being made, but (due to the exact nature of the situation) the v6 queue manager let you get away with it while the v7 queue manager has tightened up the checking (or fixed the bug in the checking).
This is especially likely if the application is multi-threaded and you've not been explicitly careful in your thread & connection handling.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| akm.mohan |
| Posted: Wed Feb 24, 2010 12:57 pm Post subject: |
|
|
Apprentice
Joined: 07 Oct 2008
Posts: 41
|
HI Thanks for your reply.yeah it seems multiple process running and it was multi threaded. can we decrease the Threads. if so how can we do that?
Thanks
Kris |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 24, 2010 1:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| akm.mohan wrote: |
| HI Thanks for your reply.yeah it seems multiple process running and it was multi threaded. can we decrease the Threads. if so how can we do that? |
Ask the guy who wrote it.
But you can't eliminate the quoted problem unless you reduce the number of threads to 1. While this is possible, I wonder about the effect on your throughput.... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Wed Feb 24, 2010 1:20 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
It sounds like the threads are sharing the same MQ connection handle. The simple solution is to have each thread make its own connection to the queue manager.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
|
|
