| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message Broker 6.0.0.1 Runtime Issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| jcarr |
 Posted: Tue Apr 25, 2006 5:27 pm Post subject: Message Broker 6.0.0.1 Runtime Issue |
 |
|
Novice
Joined: 25 Apr 2006
Posts: 20
Location: Minneapolis, MN
|
After installing Message Broker 6.0.0.1 on a Windows 2003 Server, I receive the following errors when bringing up the broker service:
The description for Event ID ( 2322 ) in Source ( WebSphere Broker v6001 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: MBRS.CEM, 'HY000', 0, '[Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt'.
The description for Event ID ( 2371 ) in Source ( WebSphere Broker v6001 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: MBRS.CEM, 'SELECT ResourceData FROM MQIBDBS.BROKERRESOURCES WHERE BrokerUUID = ? AND ExecGroupUUID = ? AND ResourceType = ? AND ResourceName = ?'.
The description for Event ID ( 2275 ) in Source ( WebSphere Broker v6001 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: MBRS.CEM, '918686d2-0a01-0000-0080-bfb5a4825ee6', CEM.
I believe I get these groups of messages for each flow the message broker cannot start. Everything works fine on 6.0, with and without MSCS.
For reference, these are the steps I followed to install MB 6.0.0.1 runtime:
Stop Message Broker and Config Mgr services
Stopped Queue Managers
Even stopped the RAC
executed U200255.exe (MB 6.0.0.1 installer)
installed product into MB base directory (ex. F:\WMB)
started Queue Managers
started started Config Mgr and Message Broker services
Other than the errors listed, it appears the Config Mgr cannot get a status of most, but not all, of the message flows. Each execution group has more than one flow, but only one flow is started in each group. You can perform actions on the started flows, but no actions on the other ones; they don't exist in the Config Mgr's eyes.
Working with this most of the day, I am able to uninstall the Message Broker Runtime and reinstall 6.0 and all flows work fine again, even in MSCS.
Any thoughts?
_________________
If you can read this, you're too close. |
|
| Back to top |
|
 |
| jcarr |
| Posted: Fri Apr 28, 2006 4:33 am Post subject: |
|
|
Novice
Joined: 25 Apr 2006
Posts: 20
Location: Minneapolis, MN
|
As an update, I contacted IBM support two days ago and
provided trace info.
After an initial review, it has been passed along to level 3 support. Perhaps a hotfix may be the answer. I'll keep everyone posted so you don't have to go through the same challanges.
_________________
If you can read this, you're too close. |
|
| Back to top |
|
|
| venusboy |
| Posted: Fri May 26, 2006 8:25 am Post subject: |
|
|
Acolyte
Joined: 11 Jun 2002
Posts: 51
|
jcarr,
Have IBM replied to you yet? I see the APAR is still in a open state. I have the same problem with 6.0.0.1 when using ms-sql, but not with ibm-db2.
Thanks in advance,
Tom. |
|
| Back to top |
|
|
| jcarr |
| Posted: Fri May 26, 2006 8:35 am Post subject: |
|
|
Novice
Joined: 25 Apr 2006
Posts: 20
Location: Minneapolis, MN
|
Yes.
IBM delivered a temporary workaround binary. Working with it since that day, the workaround provided has resolved this SQLServer 2000 issue. I also tried it with SQLServer 2005 and everything appears to be fine.
The 'Connection is busy with results for another hstmt'
error appears that SQLServer 2000 and 2005 has a limitation
whereby it is unable to handle 2 "current" resultsets on the same
connection.
IBM has not posted an official fix on their site, so you will have to contact Level 2 support for the a workaround dll. They may ask you a few questions like do you have any additional patches placed on top of MB runtime 6.0.0.1. Based off your answers, they may make a custom dll until they get a true resolution.
Thanks.
_________________
If you can read this, you're too close. |
|
| Back to top |
|
|
| venusboy |
| Posted: Mon May 29, 2006 11:32 pm Post subject: |
|
|
Acolyte
Joined: 11 Jun 2002
Posts: 51
|
Thanks for this. I will give IBM a buzz.
Regards,
Tom. |
|
| Back to top |
|
|
| jfluitsm |
| Posted: Thu Jul 27, 2006 12:28 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands
|
I got similar problems with the Berkely database.
I reverted to 6.0.0.0
_________________
Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
| Back to top |
|
|
| jfluitsm |
| Posted: Fri Jul 28, 2006 12:10 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands
|
Berkely DB with 6.0.0.1 on Windows now works fine.
The first time I installed fp1 the installation failed because the InstanceMgr was still running. Although a subsequent installation of fp1 succeeded something was probably corrupted.
Re-installation of the base version and fp 6 solved the problem.
_________________
Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
| 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
|
|
|
|
