| Author |
Message
|
| jdouch |
 Posted: Tue Jul 09, 2002 2:14 am Post subject: Multiple Brokers on AIX & DB2 |
 |
|
Apprentice
Joined: 31 May 2002
Posts: 32
Location: London, UK
|
Hi,
we're currently moving toward integration testing using UNIX AIX box and DB2. The plan is to have multiple brokers running on the box (for 2 different projects) , but presently there would appear to be a problem with having multiple connections to the DB2 database. The consequence of this is that WMQI fails and a stream of error messages follows.
Has anyone encoutered this problem, or can anyone provide any advice. As far as i know there should not be a problem with running multiple brokers on one machine. I have previously used this configuration on AIX with Oracle and this worked fine. The support team here have raised the problem with IBM but with no reply as yet, and our go live date is nearing quickly
thanks
J
_________________
Julian Douch
E-business Solutions Consultant
WMQ/WMQI Specialist |
|
| Back to top |
|
 |
| TorpedoSTu |
| Posted: Tue Jul 09, 2002 3:52 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2001
Posts: 73
|
Try upping the DB2 max_appls and max_agents parameters.
The is (effectively) the number of concurrent connectoins allowed by Db2.
regs
Stuart |
|
| Back to top |
|
|
| jdouch |
| Posted: Tue Jul 09, 2002 4:16 am Post subject: |
|
|
Apprentice
Joined: 31 May 2002
Posts: 32
Location: London, UK
|
Stuart,
thanks for your response - i actually have some more information, in that our guys have replicated the error using a single broker too. the current theory is that the problem may lie with us using a remote db2 database.
do you have any experience regarding this issue ?
thanks
J
_________________
Julian Douch
E-business Solutions Consultant
WMQ/WMQI Specialist |
|
| Back to top |
|
|
| TorpedoSTu |
| Posted: Tue Jul 09, 2002 5:09 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2001
Posts: 73
|
Hiya,
Yes, we've got remote DB2 Broker and Application databases. and it works fine.
There are no differences in setup between local or remote databases
Can you let me know the exact symptoms you're getting i.e. MQSI/DB2 Errors
Regs
Stuart |
|
| Back to top |
|
|
| jdouch |
| Posted: Tue Jul 09, 2002 5:28 am Post subject: |
|
|
Apprentice
Joined: 31 May 2002
Posts: 32
Location: London, UK
|
i am just trying to get the relevant information.
at the moment i know that the problem experienced is that the broker will be available for around 1/2hr for example, but then the connection will fall off, the broker becomes unusable in the fact you can not deploy to it or start or stop it.
rgds
J
_________________
Julian Douch
E-business Solutions Consultant
WMQ/WMQI Specialist |
|
| Back to top |
|
|
| mpuetz |
| Posted: Tue Jul 09, 2002 8:47 am Post subject: |
|
|
Centurion
Joined: 05 Jul 2001
Posts: 149
Location: IBM/Central WebSphere Services
|
Hi,
the default connection mode after setting up a DB2 instance
is not use TCP/IP mode on AIX ! Change your instance
settings to use TCPIP (using DB2 SET command) which
allows you to have more than 8 concurrent connections
to your databases.
Also modify MAX_APPL to reflect this. As rule of thumb use
5 connections per Broker plus any other connections
used by your flows (1 per message flow with database
connection couting multiple instances).
_________________
Mathias Puetz
IBM/Central WebSphere Services
WebSphere Business Integration Specialist |
|
| Back to top |
|
|
| amigupta1978 |
| Posted: Tue Jul 09, 2002 7:51 pm Post subject: |
|
|
Centurion
Joined: 22 Jan 2002
Posts: 132
Location: India
|
Hi,
Actually we too faced the problem while running the broker database on DB2 v6.1 fxpac 4 on AIX. It had some problem if we define it as local database. Even after increasing the number of concurrent connections it was giving the problem. So we changed that database instance to the remote datbase and everything works fine. (I think this is a known problem with DB2, since IBM team only had said us to make the DB2 instance as remote). and after that evrything worked fine.
Thanks and Regards,
Amit |
|
| Back to top |
|
|
| jdouch |
| Posted: Wed Jul 10, 2002 8:21 am Post subject: |
|
|
Apprentice
Joined: 31 May 2002
Posts: 32
Location: London, UK
|
Hi all,
i finally have the information !
We are running WMQI 2.1 CSD 1 on AIX, connecting to a remote DB2 v7.1 Fix Pack 3 on AIX. The database is administered by DBA's so playing around with that is not so easy.
Apparently when they thought it was a connections problem they implemented what apparently was a known solution where they have used DB aliases to provide some loopback situation ?? not too sure on what this is supposed to do - i haven't asked them whether they tried setting the DB2 variables listed above. Are they still relevant to this ?
it would now appear that the problem is repeatable using 1 broker and 1 message flow. when trying to deploy, after a while it will timeout, not returning any information. this is turn apparently kills the dataflow engine processes . the only way to stop the broker is by doing a forced stop.
any more ideas ??!!
thanks
J
_________________
Julian Douch
E-business Solutions Consultant
WMQ/WMQI Specialist |
|
| Back to top |
|
|
|
|
