| Author |
Message
|
| MaheshPN |
 Posted: Wed Oct 20, 2004 11:28 am Post subject: [SOLVED]Communication error |
 |
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
Hi Guys,
I deployed the WF client on SOLARIS and WF servers on AIX. WF servers are working fine. When I try connecting from client(with QueueManager) to WF server, I see this message
fmc /var/fmc> fmcautil -uadmin -ppassword -yfmc
- FMC16006I Administration Utility started.
System group name : [FMCGRP] FMCGRP
System name : [FMCSYS] FMCSYS
Userid : [ADMIN] ADMIN
Password : [********] ********
- FMC00013E Communication error - Failing Action: open, Reason Code: 2085, Fail
ing Object: FMC.FMCGRP.FMCSYS.ADM.
- FMC16302I Not connected to any system.
FMC15010I Main Menu:
s ... System Commands Menu
x ... Exit Main Menu
I have seen this errors in the past in other environment. I can't remember, how they got resolved.
Any idea?
Thanks,
-Mahesh |
|
| Back to top |
|
 |
| CHF |
| Posted: Wed Oct 20, 2004 11:45 am Post subject: |
|
|
Master
Joined: 16 Dec 2003
Posts: 297
|
Mahesh,
Are you able to see FMC.FMCGRP.FMCSYS.ADM in the QMgr on SOLARIS BOX? This Queue is the Cluster Queue (Alias) hosted by the QMgr on AIX Box.
If you can't see it, I believe the QMgr that you created on SOLARIS Box is not joined in the WF Cluster properly.
_________________
CHF  |
|
| Back to top |
|
|
| MaheshPN |
| Posted: Wed Oct 20, 2004 12:47 pm Post subject: |
|
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
Thanks CHF,
I tried the mq command display q(*), it did not show that. But I tried the same command on UAT(which is working) with the same setup. It also did not show up that queue. I guess, I am using wrong command.
Please let me know, how to test it.
Thanks,
-Mahesh |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Oct 20, 2004 1:33 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
You should use display qc(*)
for clustered queses
On the QMGR where you are getting the error you may want to also issue
display clusqmgr(*)
Issue the same command on the workflow server also. If you see any temp qmgrs then there is a problem with clusters.
See if the listeners are running on both the boxes and if you have given the right port numbers in the clusrcvrs |
|
| Back to top |
|
|
| MaheshPN |
| Posted: Thu Oct 21, 2004 6:42 am Post subject: |
|
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
Thanks vennela.
display qc(*)
1 : display qc(*)
AMQ8147: WebSphere MQ object * not found.
portnumbers and listeners seems to be ok. I would guess, cluster refresh might solve this issue.
Let me know your opinion.
thanks,
-Mahesh |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Oct 21, 2004 12:30 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
what does display clusqmgr(*) give you.
If it was an existing setup and was working before, you could try to issue refresh cluster and it might work. |
|
| Back to top |
|
|
| MaheshPN |
| Posted: Mon Oct 25, 2004 8:10 am Post subject: |
|
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
1 : display clusqmgr(*)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(RQSP006B) CLUSTER(FMCGRP)
CHANNEL(TO.RQSP006B.TCP)
03B and 04B are WF server QMs.
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(O5GPS03B) CLUSTER(FMCGRP)
CHANNEL(TO.O5GPS03B.TCP)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(O5GPS04B) CLUSTER(FMCGRP)
CHANNEL(TO.O5GPS04B.TCP)
This is a new setup. I tried cluster refresh, did not soloved the issue.
Before the configuration I ran,
fmczinsx -o env
fmczinsx -o inf
fmczinsx -o mqserver.
Let me know, your thoughts.
thanks,
-Mahesh |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Oct 25, 2004 12:32 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
On the web client box go the directory
/var/fmc/qmgrs/RQSP006B/mqs
(Assuming RQSP006B is the web client QMGR).
do:
runmqsc RQSP006B < fmczcfst.mqs
runmqsc RQSP006B < fmczcfrt.mqs
in that order.
A refresh cluster might also be a good idea after that. Then under runmqsc issue
dis clusqmgr(*) and the output should be
| Code: |
CLUSQMGR(RQSP006B) CLUSTER(FMCGRP)
CHANNEL(TO.RQSP006B.TCP)
CLUSQMGR(O5GPS03B) CLUSTER(FMCGRP)
CHANNEL(TO.O5GPS03B.TCP)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(O5GPS04B) CLUSTER(FMCGRP)
CHANNEL(TO.O5GPS04B.TCP)
|
Hope it works. If not get back |
|
| Back to top |
|
|
| MaheshPN |
| Posted: Thu Oct 28, 2004 7:19 am Post subject: |
|
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
Thanks for your times guys.
The problem was with typo by SA!!!
On servers he typed queue prefix as fnc.xxx.xxx.
On clinnts he typed as fmc.xxx.xxx.
Got resolved and working great 
Thanks,
-Mahesh |
|
| Back to top |
|
|
|
|
