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 » Interesting issue with 2 WF Systems in the same group.

Post new topic  Reply to topic
 Interesting issue with 2 WF Systems in the same group. « View previous topic :: View next topic » 
Author Message
PisgahMan
PostPosted: Thu Dec 22, 2005 1:24 pm    Post subject: Interesting issue with 2 WF Systems in the same group. Reply with quote

Voyager

Joined: 27 Jul 2004
Posts: 93

We had 1 MQWF system set up with 1 queue manager. We started testing batch submissions over the XML interface(CreateandStartProcessInstance), but when a batch job was running, all of the non-batch submissions were timing out. The non-batch job submission were using the java api's.

So we created a second queue manager and a second MQWF system to submit the batches to. The idea is to use 2 systems on the same server, same database and when connections are made the apps will specify the QM instead of the group so WF will not load balance.
So
(1)'normal' submissions go to QM A over the java API's
(2)Batch submission go over the XML interface to QM B.

The problem is that when submitting a batch to queue manager B, the calls to QM A STILL time out. I watched the queue's and the RTSINPUTQ on queue manager A seemed extremely slow to consume messages. The batch itself runs with no problem.

I don't see any errors in the MQ or MQWF logs.

Is this behaviour expected?
Back to top
View user's profile Send private message
hos
PostPosted: Wed Dec 28, 2005 3:14 am    Post subject: Reply with quote

Chevalier

Joined: 03 Feb 2002
Posts: 470

Hi,
this behaviour is very interesting and NOT as expected.
Are your java applications performing well if no batch job is running?
Are you checking XMLINPUTQ of qmgr B vs. RTSINPUTQ of qmgr A?
Which version/service level of MQWF and MQ do you use?
What is your operating system?
I assume you did your tests on a single box. Can you separate your MQWF systems on two different boxes and re-test?
Maybe a concentrator setup could help in your situation(?)
Back to top
View user's profile Send private message
koko
PostPosted: Thu Jan 12, 2006 6:48 pm    Post subject: Reply with quote

Master

Joined: 26 Sep 2003
Posts: 206

Hos,

I have a similar problem. I would like to use one QM for online messages from WF Webclient. One QM for expiration of messages ( from workflow itself - I run the scheduling server on this system)

Strangely I find that I cannot login when RTSINPUTQ on QMB is full.
_________________
Thanks

Koko
Back to top
View user's profile Send private message
PisgahMan
PostPosted: Thu Jan 12, 2006 7:47 pm    Post subject: Reply with quote

Voyager

Joined: 27 Jul 2004
Posts: 93

My problem was fixed by increasing the DB2 buffer size.
Back to top
View user's profile Send private message
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 » Interesting issue with 2 WF Systems in the same group.
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.