| Author |
Message
|
| Galichet |
 Posted: Wed Jun 25, 2003 4:59 am Post subject: deploy problems on WMQI 2.1 |
 |
|
Acolyte
Joined: 26 Jun 2001
Posts: 69
Location: Paris - France
|
Hi all,
I've a strange problem with WMQI V2.1 on AIX ...
I have a Broker with several message sets and Execution Groups (EG).
When I perform an EG deploy delta/complete, all works fine, the log said all is ok.
when I perform a Broker deploy complete, I have no logs (CLOG empty)  (I know something is done because I'm able after a while to deploy again..)
Someone knows what's happening ?
Another problem : I would like to know why a message set stills in the Operation Group Tab even if I've removed it from Assignment Tab before a Broker deploy delta . ??? (I want to remove the old message set in order to import an updated one).
Thanks for your Help
_________________
Eric Galichet
SMABTP
France |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Jun 25, 2003 5:25 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Quote: |
| why a message set stills in the Operation Group Tab even if I've removed it from Assignment Tab before a Broker deploy delta |
I'd say the deploy didn't complete properly. The Operations tab always shows what IS deployed, whereas the Assignments tab shows what you WANT deployed.
As to why your deploy didn't complete properly, I can't say. It sounds like you're having difficulties getting response messages back from your broker, at least when they get large (like from a complete deploy vs. a delta deploy). |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Wed Jun 25, 2003 6:34 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Hi,
Have you got a mcauser id set on the SYSTEM.BRK.CONFIG channel on your configmgr queue manager?
If so, try unsetting it - the userid you query the log with and the one that the broker sees as sending the deploy messages need to be the same.
Cheers,
Vicky |
|
| Back to top |
|
|
| Galichet |
| Posted: Wed Jun 25, 2003 6:58 am Post subject: |
|
|
Acolyte
Joined: 26 Jun 2001
Posts: 69
Location: Paris - France
|
The mcauser id is not set in the channels .... Anyway, I've checked the CLOG table where the logs are stored and nothing is added here ...
As I said, with a EG deploy delta/complet all is fine
With the same user, the deploy complete/delta at the broker level doesn't work ...
_________________
Eric Galichet
SMABTP
France |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 25, 2003 8:19 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Galichet wrote: |
As I said, with a EG deploy delta/complet all is fine
With the same user, the deploy complete/delta at the broker level doesn't work ... |
So, when you send a large deploy message to your broker, you either aren't getting a response or the deploy message isn't even getting to the broker. Since you say there are messages stuck in the REPLY queue, I would suspect that it's the first case. However, in either case it sounds like an issue with the size of the message.
There are other threads here recently active that talk about issues with deployment messages being too large for various parts of the system. |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Jun 25, 2003 10:26 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Take a look at your max message length on these system queues. Make sure you set it to maximum value. How many execution groups do you have? What is your CSD level?
Try to avoid complete deploy of the broker as it involves lots of processing for the broker and configuration manager. Whenever you submit a complete deploy request, broker will make multiple copies of the runtime dictionary for each assigned message sets. These dictionaries are then assigned to each Execution Groups. You might run of heap memory problem (BIP1528) if deploying large number of message sets at one once. Instead, you could doing a delta deploy of each execution group separately. Once you finish doing a delta-deploy for all EG's your operations panel will show the correct view. There was a problem with incorrect view in operations panel, which has been fixed in CSD4.
I hope this helps.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Craig B |
| Posted: Thu Jun 26, 2003 12:11 am Post subject: |
|
|
Partisan
Joined: 18 Jun 2003
Posts: 316
Location: UK
|
Reading through the your starting update it seems you reported two issues. One of these was relating to a successful delta deploy that removes a messageSet from the assignment but it still remains in the operations tab view. There was a known problem in MQSI V2.01, V2.02 and V2.1 such that a messageSet was not removed from the operations tab after a delta deploy to remove it from the broker. According to the memo.ptf file for WMQI V2.1 CSD04 this was fixed in this CSD under reference number IY33904. If your configMgr/brokers are not running at this CSD then this will still appear on your operations tab. This problem will only occur when you have multiple execution groups in a broker which you say you have.
As for the complete deploy problem then I agree with the previous update in that for big configurations these should be avoided where possible. A complete deploy leads to configMgr constructing all the runtime versions of flows and messageSets deploy to that broker which can results in large deploy messages being sent to the broker. Depending on the size of your configuration this can lead to a large amount of Database and MQ queue manager logging to fulfil this request.
When the complete deploy message arrives at the broker then the broker then has to ask all its execution groups to refresh their entire configuration. For an execution group to do this it has to quiesce all its flows before this can happen. If you have long running flows then this may take some time to happen.
I believe some improvements were made to the deploy process in CSD03 onwards, so it may be helpful to run on at least that level of maintenance. However, these do not change the hefty processing that has to take place for a deploy.
_________________
Regards
Craig |
|
| Back to top |
|
|
| Galichet |
| Posted: Thu Jun 26, 2003 12:18 am Post subject: |
|
|
Acolyte
Joined: 26 Jun 2001
Posts: 69
Location: Paris - France
|
Hi Kira,
Yes my SYSTEM.BROKER.* queues are all set with 100Mo for Max Message length.
We have 6 execution groups (with 3 flows max in each) and 9 messages sets (that's not so big) .
We have just installed CSD4 on the broker and Config Manager, but not yet to my control center (as I have to access to other environment that are still with CSD3). Now I'm just thinking that my problem is here ... I'm going to install the CSD4 on my Control Center and perform a new test, just to verify.
I'll keep you in touch.
Thanks for your help.
_________________
Eric Galichet
SMABTP
France |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Jun 26, 2003 10:44 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Hi Eric,
I don't think installing CSD4 on Control Center machine will solve your problem as the deploy process is done by the config mgr and the broker. I think you should start doing delta-deploys of each execution groups one at a time. To reduce the deploy overhead you could also try reducing the number of Execution Groups within your broker.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Galichet |
| Posted: Fri Jun 27, 2003 12:53 am Post subject: |
|
|
Acolyte
Joined: 26 Jun 2001
Posts: 69
Location: Paris - France
|
Hi all,
I've installed the CSD4 on my Control Center and now all works fine with my message sets 
For my problems with big messages, I will perform deploys on the Execution groups and after that a broker deploy delta .
Thanks for your help.
_________________
Eric Galichet
SMABTP
France |
|
| Back to top |
|
|
| mrlinux |
| Posted: Mon Jun 30, 2003 5:00 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Check the size of the transmit queue from the config manager to the broker, This is usally 4mb and needs to be changed also the channel
definition will need to change.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| nukenrg |
| Posted: Wed Jul 02, 2003 7:20 am Post subject: MSG Set woes |
|
|
Newbie
Joined: 29 Apr 2003
Posts: 5
Location: Chicago, IL
|
I found I had the same problem with the old message sets not disappearing. Due to customer constraints, I'm unable to install CSD05 on the fly w/o a major change management ordeal. If someone else is in the same boat, I'll share what IBM told me to do:
Simply enough - do one delta deploy for each execution group. I had 3 EGs, so after my 3rd delta, the operations tab finally reflected the correct message sets.
Hope this helps someone!  |
|
| Back to top |
|
|
|
|
