| Author |
Message
|
| ucbus1 |
 Posted: Mon Jul 19, 2004 7:51 am Post subject: [SOLVED]No connection to MQSeries Workflow server error |
 |
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
All,
I am getting this error while configuring a client concentrator using web clinet on NT and workflow server on AIX. Usually this means some thing wrong with cluster channles. I find nothing wrong iwht any of the set up. I have refreshed the cluster( usually this should fix).. Still no luck. What am I missing?
Also, please let me know if mca id has any role to play in this. Because, I have an existing clinet concenrator with FMC/workflow server and it works fine. The cluster queue managers have mca id as "spaces"
But when I am building a new configuration FMC1 and new web client I am getting the above error and the mca id for the cluster queue manager is shown as "fmc1". i am not sure if it causes any error. I am not sure how can change the mca id to spaces. please let me know |
|
| Back to top |
|
 |
| kriersd |
| Posted: Mon Jul 19, 2004 10:27 am Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
ucbus,
So, there is no error messages durring the setup? If so please post..
I would check the TAB file from the AIX server, which you must use durring the client concentrator setup on the NT server. Make sure you ftp the tab file in binary mode. I have had problems with corrupted tab files when I don't FTP in binary mode.
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Jul 19, 2004 10:37 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| I would check the TAB file from the AIX server, which you must use durring the client concentrator setup on the NT server. |
I am not sure if we have to worry about channel tab at all. Because a client concentraotr is a QMGR to QMGR communication and through CLUSSDR and CLUSRCVR channels.
On the other hand if you think there is any problem with the clusters then these are the following cluster MQSC commands that you should run to make sure your workflow cluster setup is OK
On both the AIX machine and NT machine run the following MQSC commands and see the output
| Code: |
dis clusqmgr(*)
dis chs(*)
dis qc(*)
|
The first one should return both the AIX QMGR and NT QMGR on both the machines. If there is any temp queue manager then that's when you know there is a cluster problem. |
|
| Back to top |
|
|
| jack_the_ripper |
| Posted: Mon Jul 19, 2004 12:15 pm Post subject: |
|
|
Apprentice
Joined: 12 Feb 2003
Posts: 46
Location: NJ
|
ucbus,
the first thing to do is to isolate the problem if it is MQ cluster related or Workflow related.
So, create a cluster Q and put a mesg on that, if it comes across the otherside, atleast ur cluster is working.
Otherwise, post things here then ppl can help.
Thanks,
_________________
Jack,
IBM Certified in Websphere MQSeries
IBM Certified in Websphere MQSI
IBM Certified in Websphere MQWorkflow |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Tue Jul 20, 2004 8:22 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Thanks.
One thing I have observed. The message I was getting was 2085 "mq series object not found" for "FMC1.FMCGRP1.EXE".
This is a cluster queue and should have been defined automatically when we configured the cluster.
Today I found the same error on our test environment and when I refreshed the cluster, it brought back all the cluster queues.
When I am trying with the new configuration, this is not happenning.
Any suggestions? |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Tue Jul 20, 2004 4:16 pm Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Still waiting....
Any clues why the cluster queues are not getting created.
Just eloborate what I am trying to do. I have the MQServer configuration created and available on AIX node. I do see all the queues FMC1.FMCGRP1.exe etc vaiable on FMCQM1. On NT box I am creating a clinet concentrator with a quue manager FMCLNTCON yo be in cluster with FMCQM1.
Now if I am correct, the cluster queues from FMCQM1 should be available to FMCLINTCON and users who logon using web client should be able to access it. For some reason my web application is failing with 2085 error and unable to fimd FMC.FMCGRP1.EXE.
Even refreshing of the clusters did not help...
Please let me know |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Jul 21, 2004 6:15 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
We too are still waiting....
You haven't answered these
| Code: |
dis clusqmgr(*)
dis chs(*)
dis qc(*)
|
There is nothing new in your posts so how do you expect us to solve your problem....
For me the output of dis clusqmgr(*) is very helpful in resolving cluster issues |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Wed Jul 21, 2004 8:53 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
my bad..
| Code: |
on windows2k
****************
dis clusqmgr(*)
1 : dis clusqmgr(*)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(FMCONQM1) CLUSTER(FMCGRPPROD )
CHANNEL(TO.FMCONQM1.TCP)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(SYSTEM.TEMPQMGR.aixnode(14010))
CLUSTER(FMCGRPPROD ) CHANNEL(TO.FMCQM1.TCP)
dis qc(*)
2 : dis qc(*)
AMQ8147: MQSeries object * not found.
dis chs(*)
3 : dis chs(*)
AMQ8417: Display Channel Status details.
CHANNEL(TO.FMCQM1.TCP) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
CONNAME(aixnode(14010)) CURRENT
CHLTYPE(CLUSSDR) STATUS(RUNNING)
****************
on AIX
*****************
dis clusqmgr(*)
15 : dis clusqmgr(*)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(FMCONQM1) CLUSTER(FMCGRPPROD )
CHANNEL(TO.FMCONQM1.TCP)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(FMCQM1) CLUSTER(FMCGRPPROD )
CHANNEL(TO.FMCQM1.TCP)
dis qc(*)
16 : dis qc(*)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.ADM)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.CLE)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.EXE)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.EXE.XML)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.ADM)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.CLE)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.DIS)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.EXE)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.EXE.XML)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.GWY)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.MOD)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.PES.PESERVER)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.SCH)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.TRC)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.PES.PESERVER)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.SCH)
dis chs(*)
17 : dis chs(*)
AMQ8417: Display Channel Status details.
CHANNEL(SYSTEM.ADMIN.SVRCONN) XMITQ( )
CONNAME(mydesktop) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
AMQ8417: Display Channel Status details.
CHANNEL(SYSTEM.ADMIN.SVRCONN) XMITQ( )
CONNAME(somebody else's desktop) CURRENT
CHLTYPE(SVRCONN) STATUS(RUNNING)
AMQ8417: Display Channel Status details.
CHANNEL(TO.FMCQM1.TCP) XMITQ( )
CONNAME(win2k) CURRENT
CHLTYPE(CLUSRCVR) STATUS(RUNNING)
AMQ8417: Display Channel Status details.
CHANNEL(TO.FMCONQM1.TCP) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
CONNAME(win2k(14010)) CURRENT
CHLTYPE(CLUSSDR) STATUS(STOPPED)
|
I think I could figure out problem with the FMC1.FMCGRP1.EXE the cluster queue was pointing to FMCGRP1 instead of cluster FMCGRPPROD. Unfortunately the workflow config on server side was set up with FMCGRP1 as cluster then it has been changed to FMCGRPPROD. I have corrected all the cluster queues to point to new cluster
Now that I could recognize it, I am trying to recreate the client, the fmczutil is just hanging and is unable to finsih. Is something still wrong???? |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Wed Jul 21, 2004 7:24 pm Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
While waiting for the response, I have continued my reasearch.....
I could figure out the reasons for hanging up of Config utility. Somehow my mqwfchnl.tab file got messed up with our frequent changing of configuration over the last few days. Luckily we have the old chltab file saved.Once I changed it, it fixed the problem
We have changed all the queues FMC1.FMCGRP1.EXE etc.. alias cluster queues to point to the right cluster name FMCGRPPROD and now I can see all the queues on the WIndows 2000 machine
Also, as suggested by JACK_THR_RIPPER, I have created a cluster TESTQ on aix node and the queue appeared on the Windows machine. We put a test message on windows box and it appeared on the aix node.This confirmed that the cluster is working fine.
Now we are facing another problem.
Now we are getting the following error
| Quote: |
error:
FMC00013E Communication error - Failing Action: open, Reason Code: 2189, Failing Object: FMC1.FMCGRP1.EXE.": com.ibm.workflow.api.FmcException:
FMC38009E MQSeries Workflow API Error :
API Return Code : 13
Error Origin : e:\v330\src\fmcjcesv.cxx, line 2120
Error Message : FMC00013E Communication error - Failing Action: open, Reason Code: 2189, Failing Object: FMC1.FMCGRP1.EXE.
Nested Exception : None |
I know it is something to do with the clusters.
I have tried all the attements including refreshing the cluster, but to of no avail
I have observed a weird thing on win2k machine. The documentation says that both win2k and Aix need to be having full repository. I have tried all commands "ALTER" repos to make win2k mgr a full repository for FMGRPPROD. But I find that the under MQ explorer> Q mgr properties for windows qmgr> repository " says FMCGRPPROD-- NO.
is this casusing the dreaded 2189 error??????????
please let me know....
Following is the results from the commands that Vennela suggested to run
| Code: |
Windows 2000
***************
dis clusqmgr(*)
1 : dis clusqmgr(*)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(FMCONQM1) CLUSTER(FMCGRPPROD)
CHANNEL(TO.FMCONQM1.TCP)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(FMCQM1) CLUSTER(FMCGRPPROD)
CHANNEL(TO.FMCQM1.TCP)
dis chs(*)
2 : dis chs(*)
AMQ8417: Display Channel Status details.
CHANNEL(TO.FMCONQM1.TCP) XMITQ( )
CONNAME(aix node) CURRENT
CHLTYPE(CLUSRCVR) STATUS(RUNNING)
AMQ8417: Display Channel Status details.
CHANNEL(TO.FMCQM1.TCP) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
CONNAME(aix node(14010)) CURRENT
CHLTYPE(CLUSSDR) STATUS(RUNNING)
dis qc(*)
3 : dis qc(*)
AMQ8147: MQSeries object * not found.
error:
FMC00013E Communication error - Failing Action: open, Reason Code: 2189, Failing Object: FMC1.FMCGRP1.EXE.": com.ibm.workflow.api.FmcException:
FMC38009E MQSeries Workflow API Error :
API Return Code : 13
Error Origin : e:\v330\src\fmcjcesv.cxx, line 2120
Error Message : FMC00013E Communication error - Failing Action: open, Reason Code: 2189, Failing Object: FMC1.FMCGRP1.EXE.
Nested Exception : None
**************
UNIX node
**************
dis clusqmgr(*)
1 : dis clusqmgr(*)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(FMCONQM1) CLUSTER(FMCGRPPROD)
CHANNEL(TO.FMCONQM1.TCP)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(FMCQM1) CLUSTER(FMCGRPPROD)
CHANNEL(TO.FMCQM1.TCP)
dis chs(*)
3 : dis chs(*)
AMQ8417: Display Channel Status details.
CHANNEL(TO.FMCONQM1.TCP) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
CONNAME(wind2k(14010)) CURRENT
CHLTYPE(CLUSSDR) STATUS(RUNNING)
AMQ8417: Display Channel Status details.
CHANNEL(TO.FMCQM1.TCP) XMITQ( )
CONNAME(win2k) CURRENT
CHLTYPE(CLUSRCVR) STATUS(RUNNING)
dis qc(*)
4 : dis qc(*)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.ADM)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.CLE)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.EXE)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.EXE.XML)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.ADM)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.CLE)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.DIS)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.EXE)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.EXE.XML)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.GWY)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.MOD)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.PES.PESERVER)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.SCH)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.FMCSYS1.TRC)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.PES.PESERVER)
AMQ8409: Display Queue details.
QUEUE(FMC1.FMCGRP1.SCH)
AMQ8409: Display Queue details.
QUEUE(TESTQ)
****************** |
|
|
| Back to top |
|
|
| vennela |
| Posted: Thu Jul 22, 2004 11:11 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
Now we are getting the following error
Quote:
error:
FMC00013E Communication error - Failing Action: open, Reason Code: 2189, Failing Object: FMC1.FMCGRP1.EXE.": com.ibm.workflow.api.FmcException:
FMC38009E MQSeries Workflow API Error :
API Return Code : 13
Error Origin : e:\v330\src\fmcjcesv.cxx, line 2120
Error Message : FMC00013E Communication error - Failing Action: open, Reason Code: 2189, Failing Object: FMC1.FMCGRP1.EXE.
Nested Exception : None
I know it is something to do with the clusters.
|
When are you getting this error
While using admin utility?
On the windows machine did you try
refresh cluster |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Thu Jul 22, 2004 1:16 pm Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
I am getting this error while using "out of box" web client that comes with Workflow.I did refresh the Windows cluster and it did not help.
Thanks |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Sat Jul 24, 2004 4:27 am Post subject: Solved: No connection to MQ Series Workflow |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
The issue got resolved.
We had to stop the queue manager clean. We could not stop it clean while the out-of -box client was running. So we tried immeiate option. This had messed up the repositories. When we stopped ou-of-box client, shudown FMCONQM on win2k, the queue manager started working fine and so is the clusters.....
Do not know why????? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jul 24, 2004 4:27 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Probably still held a reference to the obsolete bad stuff in memory... |
|
| Back to top |
|
|
|
|
