| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP2066E |
« View previous topic :: View next topic » |
| Author |
Message
|
| KittieKat |
 Posted: Mon Feb 04, 2002 12:27 pm Post subject: |
 |
|
Apprentice
Joined: 17 Dec 2001
Posts: 31
|
Hi,
I'm having alot of problems trying to force deploy a message flow to a Solaris broker. There was an ealier entry on the this topic - "BIP2066E when deploying" by NickB, but I'm getting more errors than just the BIP2066E. Here is the list:
BIP2087I: Broker MQSI_SOLARIS_BROKER was unable to process the internal configuration message.
BIP2066E: Broker MQSI_SOLARIS_BROKER (UUID 359c6cc3-eb00-0000-0080-bd40e1e2c251) unable to retrieve internal configuration response message for execution group default.
BIP1536S: Configuration Manager unable to register for internal subscriptions with broker MQSI_SOLARIS_BROKER.
And sometimes the solaris listener would stop on its own (AMQ9218) saying that it can't bind to server's port.
After clearing the system logs and increasing the dabatase heap sizes I am still getting the same errors. I'm not sure if I should upgrade to FP4 (from DB2 7.1) like mpuez said. Also I tried to look for CPU loops caused by re-deploying the message flow, could "PID TTY TIME CMD" be the loop EddieA was referring to?
Can someone please tell me what's cauing these erros? Thank you.
-Alison
|
|
| Back to top |
|
 |
| Segs |
| Posted: Mon Feb 04, 2002 12:39 pm Post subject: |
|
|
Voyager
Joined: 04 Oct 2001
Posts: 78
Location: Zurich Financial Services
|
| Please let me know what versions of MQSI plus any CSD packs and DB2 you are using. |
|
| Back to top |
|
|
| KittieKat |
| Posted: Mon Feb 04, 2002 1:31 pm Post subject: |
|
|
Apprentice
Joined: 17 Dec 2001
Posts: 31
|
| We are using MQSI 2.0.2 and DB2 7.1. The solaris broker's database is running on WinNT server. One more thing I'm not sure about is that I combined the NEON database and broker database, and I have already imported Neon formats and rules in the integrated database. Thanks. |
|
| Back to top |
|
|
| kirani |
| Posted: Mon Feb 04, 2002 5:27 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Try doing a forced deploy (File->Deploy->Complete Configurations (all types)->Forced).
Regards,
Kiran
|
|
| Back to top |
|
|
| Segs |
| Posted: Tue Feb 05, 2002 1:46 am Post subject: |
|
|
Voyager
Joined: 04 Oct 2001
Posts: 78
Location: Zurich Financial Services
|
Alison
Have you applied any of the CSDs for MQSI v2.0.2 |
|
| Back to top |
|
|
| KittieKat |
| Posted: Fri Feb 08, 2002 9:35 am Post subject: |
|
|
Apprentice
Joined: 17 Dec 2001
Posts: 31
|
Hi Segs,
I just installed MQSI CSD01 (U479743) on the solaris box. Also on the WinNT server I installed MQSI CSD01 & CSD02 as well as MQSeries CSD03. But it's still giving me trouble.
At first the Solaris broker worked fine, but then when I tried to deploy a message flow consisting of NEON nodes, the broker returned an error message saying that "it does not have the capability to create nodes of this type". So then I installed the neonsoft portion of the MQSI CSD01 on Solaris. But ever since then, the Solaris broker just completely stopped responding, and I've been getting the exact same error messages (BIP2087I, BIP2066E, BIP1536S).
I tried to uninstall neonsoft and that didn't work. Then I uninstalled the entire MQSI CSD on Solaris and reinstalled it, still didn't work. Am I missing something here? it seems like control center can't even detect the broker's presence but the channels are running just fine. Please help, thank you!
-Alison |
|
| 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
|
|
|
|
