Re: WMQI: Message Flows, Message Set or Execution Group problems
You might want to try this instead of cataloging as a remote database. You might see better performance. The AIX environment variable EXTSHM can be used to increase the maximum number of shared memory segments to which a process can attach. To use EXTSHM with DB2, do the following: In client sessions: export EXTSHM=ON When starting the DB2 server: export EXTSHM=ON db2set DB2ENVLIST=EXTSHM Db2start -Greg -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Rajkumar Bagavathiappan Sent: Monday, December 29, 2003 9:37 AM To: [EMAIL PROTECTED] Subject: Re: WMQI: Message Flows, Message Set or Execution Group problems Hi Luis, I faced a similar problem in AIXv5.2 with WMQI v2.1 CSD 04, which was due to DB2 problem on AIX, that a process cann't have more than 10 connections if the database is local, as it uses IPC's for DB2 Connections. For analysing the exact problem, try logging the ExceptionList tree from MQOutput Node to a file using Trace node. If the problem is related to DB2, then try cataloging the broker database as a remote database, in which case the DB2 connections are obtained through TCP/IP Sockets. Please refer to the attached text file for information related to changes required for DB2. Regards, Rajkumar Torry Harris Business Solutions Bangalore, India Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: WMQI: Message Flows, Message Set or Execution Group problems
Hi Luis, I faced a similar problem in AIXv5.2 with WMQI v2.1 CSD 04, which was due to DB2 problem on AIX, that a process cann't have more than 10 connections if the database is local, as it uses IPC's for DB2 Connections. For analysing the exact problem, try logging the ExceptionList tree from MQOutput Node to a file using Trace node. If the problem is related to DB2, then try cataloging the broker database as a remote database, in which case the DB2 connections are obtained through TCP/IP Sockets. Please refer to the attached text file for information related to changes required for DB2. Regards, Rajkumar Torry Harris Business Solutions Bangalore, India DB2 Problem in AIX / Alternate Solution Problem : -- On AIX, DB2 will issue SQL 1224N when the Broker process tries to access the Broker database for fetching details regarding Message Sets. Hence the processing of message flows fail. Observation : -- This is due to the limitation in number of connection available to Broker. Since the database is in local machine as that of production broker, the odbc dsn for broker uses Interprocess communication for getting connection to database, which means Shared memory segment will be used for attaching the client (odbc dsn) to the DB2 Server agent process. This has a limitation that a single process (like broker) cannot have more than 10 concurrent sessions with the server. Hence at times, when the requirement to have more than 10 sessions arises, the broker cannot be serviced by DB2. Resolution : - Catalog the database as remote database by configuring the TCP/IP Loopback. This will make broker to use TCP/IP communication, in which case it communicates to DB2 agent process via sockets. Using sockets the broker requests to the database will be serviced completely. Steps: --- 1. Find the db2 service name for the instance. command : = db2 get dbm cfg | grep i svcename 2. Catalog the loopback node command: db2 catalog tcpip node remote 127.0.0.1 server where replace with the reference node name replace with the ouput from step.1 example: db2 catalog tcpip node WMQINODE remote 127.0.0.1 server db2cdb2inst20 3. Catalog the database as follows commands: == db2 catalog db as db2 uncatalog db db2 catalog db as at node example: db2 catalog db WMQIBKDB as PRDBKDB db2 uncatalog db WMQIBKDB db2 catalog db PRDBKDB as WMQIBKDB at node WMQINODE Note : -- The database alias name can be any name but not same as the database name. SQL1334N will result if the database is not configured properly 4. Restart DB2 to refresh to directory cache. commands: = db2stop db2start
WMQI: Message Flows, Message Set or Execution Group problems (3)
Hi, I forgot to mention that MQ has CSD04 and WMQI has CSD05 for both OS.Also, the deployment is clean, no error messages at all.All that message flows and message set are already running in our development environment (Windows 2000), so, it's for sure that there aren't message flow or message set errors. Thanks and regards, Luis Garro MuñozSoluciones y ServiciosGBM de Costa Ricae-mail: [EMAIL PROTECTED]Tel: 2843999 ext 6216 Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
WMQI: Message Flows, Message Set or Execution Group problems (2)
Hi,thanks for yor help.When I debug the non-working message flow, it looks like an empty message is comming in, because the MRM-TDS parser can't get data. But it's for sure that our message has the length and data that we want to pass thru MQ.We set up DB2 to accept 100 connections and we applied all the steps to configure the broker domain (DB2 heap size and bindings) and MQ tunning (MQ log file size).If we see system logging or db2 logging, there aren't errors or warnings. So, that's all I can say for now.Thanks and regards, Luis Garro MuñozSoluciones y ServiciosGBM de Costa Ricae-mail: [EMAIL PROTECTED]Tel: 2843999 ext 6216 Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: WMQI: Message Flows, Message Set or Execution Group problems
Hello Luis, >>>We've a development environment in which all our message flows works correctly. >>>That's a Windows 2000 broker. We've also a production environment in which we >>>import message set and flows correctly. The ConfigMgr is on Windows 2000 and >>>the broker is on AIX 4.3.3. When we deploy on production, everything looks good, >>>however, if we've two or more message flows in the same execution group, one of >>>them doesn't work. If we redeploy the same assignments, both or the other message >>>flow doesn't work. So, It's inconsistenly. If we create one execution group per message >>>flow, everything works well. Any ideas? Could you provide a bit more information on exactly how it "doesn't work"? How does the failure manifest itself? Do the non-working flows show an error status in the Operations view of the Control Center? Or do the non-working flows simply not pull messages off the input queues? Also, are there specific WMQ or WMQI error messages that you see in the system lot or AMQ error logs? Also, what version and CSD level are you at with WMQI, both in the Win2K environment and the AIX environment? Regards, Christopher Frank Certified I/T Specialist - WebSphere Software IBM Certified Solutions Expert - Websphere MQ & MQ Integrator -- Phone: 612-397-5532 (t/l 653-5532) mobile: 612-669-3008 e-mail: [EMAIL PROTECTED] Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
WMQI: Message Flows, Message Set or Execution Group problems
Hi,this is the scenario: We've a development environment in which all our message flows works correctly. That's a Windows 2000 broker.We've also a production environment in which we import message set and flows correctly. The ConfigMgr is on Windows 2000 and the broker is on AIX 4.3.3.When we deploy on production, everything looks good, however, if we've two or more message flows in the same execution group, one of them doesn't work. If we redeploy the same assignments, both or the other message flow doesn't work. So, It's inconsistenly.If we create one execution group per message flow, everything works well. However, we're affraid if something could bring us problems in the future. Any ideas? Thanks and regards, Luis Garro MuñozSoluciones y ServiciosGBM de Costa Ricae-mail: [EMAIL PROTECTED]Tel: 2843999 ext 6216 Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
