| Author |
Message
|
| kriersd |
 Posted: Tue Jan 21, 2003 6:22 am Post subject: Cluster Sender Channel does not reconnect! |
 |
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Does anyone else have the issue where the cluster sender channels on both the Workflow server and the any machine housing a client concentrator queue manager not restart after a disconnect. I can't seem to figure this out? It's funny..
I'll go home at night and everything is working properly. The next morning I'll find the Web Client does not work. After looking at the Websphere server I always find that the cluster sender channel on my client concentrator queue manager is not running. Now here is the funny thing. If I attempt to log in with the webclient I'll get a time out error because the channel did not start, however, if I try to log in with the "FMCAUTIL" utility the cluster sender channel will start right up and then every thing is up and running with no problems.
I have set the disconnect interval on the cluster sender channel to 0 and still this keeps happening.
Any ideas? :x
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
 |
| vennela |
| Posted: Tue Jan 21, 2003 10:00 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Dave:
I think I know the remedy for this. But somebody else should confirm if this works.
On the SYSTEM.CLUSTER.TRANSMIT.QUEUE on the Workflow server there were some expired messages (most likely these are stranded messages resulted by killing fmcautil or the web-client requsets' reply messages that haven't reached their destination). Once I got rid of those messages (amqsbcg) everything was fine. Recycling the QMGR also works.
I have this thoery but with a few things unexplained.
The current depth on the transmit queue is greater than 0 and the cluster sender channel is not initiated because of TRIGTYPE(FIRST).
But, how would fmcautil get it to working???
I will try to test it today but if somebody can explain this then it would be great.
But one thing is fore sure. If there are no messaged on the cluster transmit queue then web-client logon will not fail.
---
Venny |
|
| Back to top |
|
|
| amittalekar |
| Posted: Tue Jan 21, 2003 12:30 pm Post subject: |
|
|
Disciple
Joined: 03 Apr 2002
Posts: 166
Location: VA, USA
|
If u refresh the cluster it will work. But to refresh cluster frequently is also not a good idea.
In my case, sometimes even fmcautil command from the appServer is also not able to connect to WF server. In this case I refresh the cluster. Please post if u find any solution on this. |
|
| Back to top |
|
|
| kriersd |
| Posted: Wed Jan 22, 2003 1:39 pm Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Ok, so it's not just me that has this problem..
I am going to try and set the channel disconnect interval to 0. This should prevent the channel from discinnecting. Still this does not resolve the issue of why it can not reconnect on it's own. I'll post my results.
Dave
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Jan 27, 2003 7:00 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Can somebody try this and let me know the results please:
runmqtrm -m FMCQM -q SYSTEM.DEFAULT.INITIATION.QUEUE (on the workflow server box).
If your QMGR name is other than FMCQM then change it to whatever it is.
I am not sure if you have to start the trigger monitor on the web-client box. I am going to start the trigger monitor today and see what happens tomorrow.
P.S.: Anybody with MQWF server on Windows having this problem?
-------
Venny |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Jan 27, 2003 4:54 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
It didn't work. No more trial and errors.
-------
Venny |
|
| Back to top |
|
|
| vedbhat |
| Posted: Mon Jan 27, 2003 11:14 pm Post subject: |
|
|
Disciple
Joined: 19 Mar 2002
Posts: 186
Location: Singapore
|
Hi,
Look at this question that I answered. I hope this helps and you be able to solve your problem.
http://www.mqseries.net/phpBB2/viewtopic.php?t=7329
Note: If you are setting the trigger ON then clear all the message first from the transmission queue.
Cheers
Ved
_________________
IBM Certified Solutions Expert - MQSeries Workflow
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
|
|
