|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Broker doesn't start up: SOLVED |
« View previous topic :: View next topic » |
Author |
Message
|
dexter |
Posted: Mon Jan 10, 2011 11:04 am Post subject: Broker doesn't start up: SOLVED |
|
|
 Apprentice
Joined: 07 Jan 2011 Posts: 32 Location: Michigan, USA
|
zLinux 11, WMB v7, MQ v7
I tried to start the newly created broker, but it doesn't start.
dummy_id@dummy_host:~/scripts> mqsistart BRK_T
BIP8875W: The component verification for 'BRK_T' has finished, but one or more checks failed.
One or more of the component verification checks failed.
Check the error log for preceding error messages.
dummy_id@dummy_host:~/scripts> ps -ef|grep bip
dummy_id 51594 50274 0 13:51 pts/2 00:00:00 grep bip
dummy_id@dummy_host:~/scripts> dspmq
QMNAME(BRK_QMT) STATUS(Running)
The queue manager is running and so is the listener.
The error that I get is as follows.
BIP8907E: Verification failed. Unable to verify Java level. : BRK_T.mqsistart: /build/S700_P/src/CommandLine/ImbCmdLib/ImbEnvironmentVerification.cpp: 419: ImbEnvironmentVerification::verify: :
Last edited by dexter on Mon Jan 10, 2011 11:26 am; edited 1 time in total |
|
Back to top |
|
 |
dexter |
Posted: Mon Jan 10, 2011 11:24 am Post subject: Issue Resolved |
|
|
 Apprentice
Joined: 07 Jan 2011 Posts: 32 Location: Michigan, USA
|
Issue got resolved when I logged out and logged back in.
I had added the WMB path to my .profile file.
I guess I had to log out and log back in for this to take effect.
Maybe, maybe not. But issue is resolved now. |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Jan 10, 2011 11:39 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
No, probably it's not resolved.
You really should have sourced the mqsiprofile rather than added anything to your path. |
|
Back to top |
|
 |
dexter |
Posted: Mon Jan 10, 2011 11:43 am Post subject: |
|
|
 Apprentice
Joined: 07 Jan 2011 Posts: 32 Location: Michigan, USA
|
I did source it. That was part of my environment setup process, when I created the broker.
Then I put the start/stop scripts in place.
The stop script brought the broker, QM and listener down, but it was when I ran the start script that I started having this issue.
I didn't really get an error up front. The error showed up in the log file. |
|
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
|
|
|
|