| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem with database in WMB |
« View previous topic :: View next topic » |
| Author |
Message
|
| vsethi007 |
 Posted: Mon Jun 30, 2008 6:48 am Post subject: Problem with database in WMB |
 |
|
Novice
Joined: 17 Apr 2008
Posts: 19
|
Hi
I am facing a problem,
my flow starts with a timer node which polls the database(oracle) after every 10 secs and fetch some data, the flow is deployed on AIX server, whenever database is down for some period and comes up, broker should automatically connects again with database, but in my case my flows are not able to connect to db and I have to manually restart the broker after each and every time whenever database is down.
I checked the usage of memory is something looping infinitely and eating CPU, but didn't find anything, even logs didn't give any help
Please suggest. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Jun 30, 2008 8:43 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
It is my understanding the Broker keeps a set of connections to a DB open after the first use of that DB.
From my experience, having Databases 'go away' is not a good thing and broker does not handle it gracefully and is therefore something I would avoid if at all possible.
If I have to take DB down (for backup etc) then it is AFAIK, good practice to stop any applications from using it first unless they are specifically designed to test for connection lost errors, try to connect again and if that fails, go to sleep for while before trying again.
I think you should raise a PMR so that you get a definitive statement of how this should be handled with respect to your particular system.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jun 30, 2008 11:30 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| smdavies99 wrote: |
It is my understanding the Broker keeps a set of connections to a DB open after the first use of that DB.
From my experience, having Databases 'go away' is not a good thing and broker does not handle it gracefully and is therefore something I would avoid if at all possible.
If I have to take DB down (for backup etc) then it is AFAIK, good practice to stop any applications from using it first unless they are specifically designed to test for connection lost errors, try to connect again and if that fails, go to sleep for while before trying again.
I think you should raise a PMR so that you get a definitive statement of how this should be handled with respect to your particular system. |
This is another reason why we do not have the bus talk to our DBs. We have fronted the DBs with an app talking to the BUS (MQ).
The other advantage is to offer independant scalability from the flow. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jun 30, 2008 1:43 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
|
| Back to top |
|
|
| vsethi007 |
| Posted: Tue Jul 01, 2008 6:22 am Post subject: |
|
|
Novice
Joined: 17 Apr 2008
Posts: 19
|
Thanks so much for your replies...
in adition to this, I am facing one more broker problem which add on to it which doesn't occurs always but frequency of occurence is high
whenever i tries to stop or start the flow, it throws me error and refuses to start
BIP2270W: Request to start message flow '177de3de-1a01-0000-0080-ad946e79c7ae': message flow does not exist.
The message broker received an operational control message containing an instruction to start the message flow '177de3de-1a01-0000-0080-ad946e79c7ae', but this message flow does not exist.
Ensure that the message flow, and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
"BIP4041E: Execution group 'EG' received an invalid configuration message. See the following messages for details of the error.
The message broker received an invalid configuration message and has not updated its configuration. This can arise as a result of errors in the specification of either message flows or message sets which the configuration manager was unable to detect. It can also result from a message flow requiring a type of node that is not supported by the broker installation, from the broker having become out of step with the configuration database or from other applications sending extraneous messages to the broker's configuration queues (SYSTEM.BROKER.ADMIN.QUEUE & SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).
Check the relevant message flow and message set definitions, check that all necessary user-defined extensions are installed, perform a complete redeploy of the broker's configuration and ensure that no applications are writing to the broker's configuration queues." |
|
| Back to top |
|
|
| Lisa |
| Posted: Tue Jul 01, 2008 11:58 am Post subject: Connection issue |
|
|
Master
Joined: 07 Jun 2002
Posts: 287
Location: NJ
|
Hi,
Take a look at DB_CACHE parm. Set it to 'YES' in the mqsiprofile and this may resolve your issue.
Lisa |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
