| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Invalid configuration message problem with WBI v5 broker. |
« View previous topic :: View next topic » |
| Author |
Message
|
| wbiuid |
 Posted: Mon Oct 31, 2005 1:44 am Post subject: Invalid configuration message problem with WBI v5 broker. |
 |
|
Apprentice
Joined: 14 Jun 2005
Posts: 34
|
Hi all,
We are currently migrating all our MQSI v2 environment to WBI v5. In production, we have two brokers - WBI_RTMQBKP1_BROKER and WBI_RTMQBKP2_BROKER. These two production brokers are running on AIX and are under HACMP control. Currently, the RTMQBKP2 broker is working correctly but we are having problems with the RTMQBKP1 broker.
Last week we successfully deployed all our execution groups to both of the brokers and there were no errors. We tried a failover test and RTMQBKP2 worked fine but RTMQBKP1 failed, giving the following errors in the syslog:
Oct 27 15:10:05 rthuas258 MQSIv500[128498]: (WBI_RTMQBKP1_BROKER)[1]BIP2001I: The WebSphere Business Integration Message Brokers service has started, process ID 127998. : WBI_RTMQBKP1_BROKER.service: /build/S500_P/src/AdminAgent/ControlProcess/rios_aix_4/ImbControlService.cpp: 337: ImbControlService::StartNewAA: :
Oct 27 15:10:05 rthuas258 MQSIv500[127998]: (WBI_RTMQBKP1_BROKER)[1]BIP2048E: An Exception was caught while issuing database SQL command connect. : WBI_RTMQBKP1_BROKER.agent: /build/S500_P/src/AdminAgent/ImbAdminStore.cpp: 266: ImbAdminStore::Connect: :
Oct 27 15:10:05 rthuas258 MQSIv500[127998]: (WBI_RTMQBKP1_BROKER)[1]BIP2321E: Database error: ODBC return code '-1'. ::WBI_RTMQBKP1_BROKER.agent: /build/S500_P/src/DataFlowEngine/ImbOdbc.cpp: 213: ImbOdbcHandle::checkRcInner: :
Oct 27 15:10:05 rthuas258 MQSIv500[127998]: (WBI_RTMQBKP1_BROKER)[1]BIP2322E: Database error: SQL State '57048'; Native Error Code '-293'; Error Text '[IBM][CLI Driver] SQL0293N Error accessing a table space container. SQLSTATE=57048 '. : WBI_RTMQBKP1_BROKER.agent: /build/S500_P/src/DataFlowEngine/ImbOdbc.cpp: 366: ImbOdbcHandle::checkRcInner: :
Oct 27 15:10:05 rthuas258 MQSIv500[127998]: (WBI_RTMQBKP1_BROKER)[1]BIP2053E: The broker made an unsuccessful attempt to access its database WBIBK1P with userid wbiprd. : WBI_RTMQBKP1_BROKER.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 474: ImbAdminAgent::instanceOfAdminAgent: :
Our DB2 administrators gave me this explanation and promptly fixed the problem:
"Basically the Failover has FAILED for the filesystems /wbip/WBIBKP1/system and /wbip/WBIBKP1/user. This means that database WBIBKP1 ( and hence broker p1) is currently broken. The system filesystem holds SYSCATSPACE (SYSTEM CATALOG) and user holds USERSPACE4K (BROKER TABLES). Until these filesystems are mounted from the prddatavg then broker1 is dead."
To make sure everything was okay, we switched back to "normal" mode and re-started the brokers. Again, RTMQBKP2 broker is working correctly, but got new set of error messages in the syslog for RTMQBKP1. These errors are:
Oct 31 09:03:29 rthuas258 MQSIv500[527330]: (WBI_RTMQBKP1_BROKER.)[1]BIP2201I: Execution Group started: process '527330'; thread '1'; additional information: brokerName 'WBI_RTMQBKP1_BROKER'; executionGroupUUID 'dce502e5-0601-0000-0080-875c038b9d78'; executionGroupLabel ''; defaultExecutionGroup 'false'; queueManagerName 'RTMQBKP1'; trusted 'false'; dataSourceName 'WBIBK1P'; userId 'wbiprd'; migrationNeeded 'false'; brokerUUID 'c570ece4-0601-0000-0080-875c038b9d78'; filePath '/usr/opt/mqsi'; workPath '/var/mqsi'. : WBI_RTMQBKP1_BROKER.dce502e5-0601-0000-0080-875c038b9d78: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Oct 31 09:03:29 rthuas258 MQSIv500[527330]: (WBI_RTMQBKP1_BROKER.)[1]BIP2203E: An execution group has encountered a problem whilst starting. : WBI_RTMQBKP1_BROKER.dce502e5-0601-0000-0080-875c038b9d78: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 570: main::
Oct 31 09:03:29 rthuas258 MQSIv500[527330]: (WBI_RTMQBKP1_BROKER.)[1]BIP2211E: Invalid configuration message containing attribute value '' which is not valid for target attribute 'userTraceLevel', object 'ComIbmDatabaseConnectionManager'; valid values are 'none, trace, debugTrace' : WBI_RTMQBKP1_BROKER.dce502e5-0601-00000080875c038b9d78:/build/S500_P/src/DataFlowEngine/ImbResource.cpp: 131: ImbResource::setAttribute: ComIbmDatabaseConnectionManager: ComIbmDatabaseConnectionManager
Oct 31 09:03:29 rthuas258 MQSIv500[527330]: (WBI_RTMQBKP1_BROKER.)[1]BIP2204I: Execution group using process '527330' thread '1' stopped. : WBI_RTMQBKP1_BROKER.dce502e5-0601-0000-0080-875c038b9d78: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 624: main: :
Oct 31 09:03:29 rthuas258 MQSIv500[131912]: (WBI_RTMQBKP1_BROKER)[2571]BIP2060W: The broker has detected that the Execution Group , process ID 527330, has shutdown. : WBI_RTMQBKP1_BROKER.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3869: ImbAdminAgent::startAndMonitorADataFlowEngine: :
It seems that about every 5 minutes WBI is trying to re-start the execution groups but the above error is getting reported every time. The RTMQBKP1 broker has about 8 execution groups and none of them are running.
Because of the contents of the syslog error message, we used our toolkits and went through all the execution to ensure the user trace level pop-up menu option was set to none. This, obviously, hasn't solved the problem.
Any ideas? Do you think the problem may be some form of corruption of the broker?
Thanks. |
|
| Back to top |
|
 |
| sieijish |
| Posted: Wed Nov 02, 2005 1:39 am Post subject: |
|
|
Acolyte
Joined: 29 Nov 2004
Posts: 67
Location: London
|
| Check your broker system queues (admin , executiongroup) for any invalid messages & clear it. You may restart the QM to clear off any non-persistent messages |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Nov 02, 2005 3:26 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Did you try redeploying the flows to WBI_RTMQBKP1_BROKER?
_________________
-wayne |
|
| Back to top |
|
|
| x061294 |
| Posted: Tue Jun 13, 2006 9:59 am Post subject: |
|
|
Acolyte
Joined: 05 Apr 2005
Posts: 62
|
We are encountering a similar issue, and looking for suggestions.
It's on Linux, version 6.0, no fixpack. We have two brokers using one database, both brokers are basically duplicates of each other (other than name) One of the brokers is fine, the other is receiving the following errors
BIP2275E: Database record associated with message flow 'af0771b5-0b01-0000-0080-dfc16b54dbd8' is not valid. : FIINFOBR2.c7c8bfd6-0a01-0000-0080-aabaf0b04d6b: /build/S000_P/src/DataFlowEngine/ImbDataFlowDirector.cpp: 2669: ImbDataFlowDirector::loadAllDataFlowsFromDatabase: ExecutionGroup: c7c8bfd6-0a01-0000-0080-aabaf0b04d6b
BIP2211E: Invalid configuration message containing attribute value '' which is not valid for target attribute 'URLSpecifier', object 'com.adp.infolink.mainflow.ENTP_INFO_TRANSFORM_FF_XML.Make WS Call'; valid values are 'http://host[:port][/path]' : FIINFOBR2.c7c8bfd6-0a01-0000-0080-aabaf0b04d6b: /build/S000_P/src/WebServices/WSLibrary/ImbWSRequestNode.cpp: 267: ImbWSRequestNode::setAttribute: ComIbmWSRequestNode: com/adp/infolink/mainflow/ENTP_INFO_TRANSFORM_FF_XML#FCMComposite_1_7
We receive this error when trying to starting the broker up, and stopping/starting the broker and/or the server has no impact. We want to simply remove the flow but because of the error the broker isn't taking deployments (we've tried removing the flow, adding a new flow, adding an EG, no deployements are going in)
The database was scanned for corruption errors and nothing stood out as an error. And as mentioned, the same database is serving another broker and having no problems. This same flow, from the same bar file, was successfully deployed on the other broker and can be successfully removed as well.
Any ideas on how to fix an invalid database record for a flow? It's not as simple as removing from config mgr as the deployment won't work, so it's looking like a manual effort. I haven't tried deleting the broker, was trying to avoid that, and, don't know if that would work anyway. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jun 13, 2006 11:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you delete the broker and tell mqsideletebroker to remove the data from the database, then yes it will fix it.
Otherwise, open a PMR.
And try applying the runtime FP1 first, see if that lets you solve this.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
