ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » WAS4.0 to MQWF3.3.2.2 Connect Problems

Post new topic  Reply to topic
 WAS4.0 to MQWF3.3.2.2 Connect Problems « View previous topic :: View next topic » 
Author Message
robsdman
PostPosted: Tue Oct 22, 2002 10:39 am    Post subject: WAS4.0 to MQWF3.3.2.2 Connect Problems Reply with quote

Apprentice

Joined: 23 Aug 2002
Posts: 27

We have two AIX servers each one running WAS 4.0 and MQWF Client Conc w/ QMgr. A third AIX server runs the MQWF Server.
All 3 Queue managers are at 5.2 CSD04, All WF configurations are at 3.3.2.2. We are using Local Binding on the two WAS/MQWF-cc servers.

If I stop our Appservers and deploy a new build for our Cust App Servlet, then start the AppServers up, it fails. I get FMC error 13 and MQ Error 2059. But yet at this same time the fmcautil command works. I have to stop/start the Appservers one more time then it will connect.


Also, if I stop and start a Qmgr on one of the two servers with WAS/MQWF-cc, then neither my Custom App Servlet or the out of box Runtime Client Servlet can connect.
It fails with FMC 13 and MQ Error 2059, but at the same time I can issue fmcautil from the cmdline and connect, I can also run java console test scripts and connect. I have to recycle their APPServers.

Anyone seen this sort of behavior? or got any clues?
Back to top
View user's profile Send private message
amittalekar
PostPosted: Tue Oct 22, 2002 11:49 am    Post subject: Reply with quote

Disciple

Joined: 03 Apr 2002
Posts: 166
Location: VA, USA

Try adding owner (userId) of the websphere processes to the mqm group.
Let me know if that fixes ur problem.
Back to top
View user's profile Send private message Yahoo Messenger
robsdman
PostPosted: Tue Oct 22, 2002 2:41 pm    Post subject: Reply with quote

Apprentice

Joined: 23 Aug 2002
Posts: 27

Thanks, but the WAS userid was already in the mqm group.

After some more digging I found this in /var/mqm/errors/A*1.LOG :

AMQ5008: An essential MQSeries process 64432 cannot be found and is assumed to be terminated.

EXPLANATION:
1) A user has inadvertently terminated the process. 2) The system is low on resources. Some operating systems terminate processes to free resources. If your system is low on resources, it is possible it has terminated the process so that a new process can be created.

-----------------------------------------------------------------------------------

AMQ6184: An internal MQSeries error has occurred on queue manager MYQMGR1.
EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been called. The failing process is process 55274.
-----------------------------------------------------------------------------------

It seems like I may need to stop the WAS's local Qmgr every time I stop the AppServer connecting to that local Qmgr. And then start the Qmgr up first and the AppServer second. I will try a variety of ways and see if it makes a difference. Does anyone have to do similar work-arounds for their custom workflow web apps ?
Back to top
View user's profile Send private message
leongor
PostPosted: Wed Oct 23, 2002 2:58 am    Post subject: Reply with quote

Master

Joined: 13 May 2002
Posts: 264
Location: Israel

Consider installing CSD05 for MQ 5.2
Won't do any harm
_________________
Regards.
Leonid.

IBM Certified MQSeries Specialist.
Back to top
View user's profile Send private message
amittalekar
PostPosted: Wed Oct 23, 2002 4:49 am    Post subject: Reply with quote

Disciple

Joined: 03 Apr 2002
Posts: 166
Location: VA, USA

Hi Robsdman,

I have similar set up as u have. The difference is I have it on unix with workflow version 3.3.0. When the appServer is restarted, workflow connectivity fails...i.e. fmcautil fails to connect WF Server.

It is because QManager on appServers looses all cluster information. Then I have to expicitely refresh the cluster then it works.

In ur case, before installing WF and other stuff, it u have considered prerequisites (disk space, memory etc) then problem "OS terminate processes" should never come.
Back to top
View user's profile Send private message Yahoo Messenger
udaybho
PostPosted: Wed Oct 30, 2002 5:40 pm    Post subject: Reply with quote

Voyager

Joined: 09 May 2002
Posts: 94
Location: Chicago

robsman,

Can you try with RMI-IIOP ? I faced the same problem with local binding, but I am not recollecting the solutions I applied. I will post here if I remember it.

I found the solutions through some user group.

Uday Bhosle
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » WAS4.0 to MQWF3.3.2.2 Connect Problems
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.