Author |
Message
|
lckwj |
Posted: Tue May 08, 2007 7:13 am Post subject: Error starting second broker on Windows |
|
|
Novice
Joined: 24 May 2006 Posts: 12
|
Hi all
I have created two separate config managers and brokers on a windows box (ie CFG1 , BKR1 and CFG2,BKR2) - they are separate configurations ie separate queue managers / databases etc.
They have been created with 2 different user profiles ie user1 and user2
The problem is ...
I can start CFG1 and BKR1 successfully, or CFG2 and BKR2 but never both at the same time. Whichever broker I start second, abends (no BIP message ID just an abend file which does not highlight the cause)
I have managed to start multiple config managers and brokers running under the same user id's but never when the user id is different.
Any suggestions would be greatly appreciated.
Environment details
Windows XP (will be going onto a Win 2003 server eventually)
Broker v6.0.3
MQ v6 |
|
Back to top |
|
 |
lckwj |
Posted: Tue May 08, 2007 7:37 am Post subject: |
|
|
Novice
Joined: 24 May 2006 Posts: 12
|
If I need 2 isolated config managers and brokers on the same box, should I have 2 broker installations??
ie so each broker can have its own unique classpath to reference different shared jars? |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue May 08, 2007 8:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You can't have two separate broker installations, at the same product level at least. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Mensch |
Posted: Tue May 08, 2007 5:46 pm Post subject: |
|
|
Disciple
Joined: 17 Jul 2005 Posts: 166
|
Hi,
Why do you want two Configuration managers ( CFG1 and CFG2) on the same machine? Is it really required??
You can have only one config manager (say CFG1 ) and you can connect two brokers BRK1 and BRK2 to one config manager.
In short make your brokers part of a broker domain managed by one Config Manager. _________________ Thanks and Regards ,
Mensch |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue May 08, 2007 6:17 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
In v6, you can have as many configmgrs on one machine as you can queue managers.
It just doesn't make much sense. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
lckwj |
Posted: Tue May 08, 2007 11:49 pm Post subject: |
|
|
Novice
Joined: 24 May 2006 Posts: 12
|
Thanks for your replies.
I want the system to be totally spearate, ie should I need to restart the one config manager, i dont need to bring the other one down.
Also, the CFG1 and BKR1 and all associated application queues can be on 1 queuemanager (QMGR1), and all CFG2, BKR2 and application queues can be on a second queue manager (QMGR2). this was to keep the configuration 'simple' but I take you point about adding the second broker to an existing domain.
Would this account for the abend problem that have running the second broker as a different user id? |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed May 09, 2007 1:47 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
If you want the systems to be totally separate, they should be on separate machines.
Nothing you have said gives any information about why you are getting an abend starting the second environment. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
lckwj |
Posted: Wed May 09, 2007 2:37 am Post subject: |
|
|
Novice
Joined: 24 May 2006 Posts: 12
|
Apologies.
I start CFG1 and BKR1 (user1) fine.
I the start CFG2 (user2) fine.
However, when I start BKR2 (user2), I get the following 4 messages repeating in the application event viewer :
1.
( BKR2 ) The WebSphere Message Brokers service has started at version '6003'; process ID 2824.
The WebSphere Message Brokers service executable has been started.
No user action required.
2.
( BKR2.agent ) Message broker internal error: diagnostic information '
Severe Abend Error detected.
For full details see Abend File: C:\Documents and Settings\All Users\Application Data\IBM\MQSI/common/errors/BKR2.agent.1560.3164.Abend '.
An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions. The diagnostic information associated with this message is: '
Severe Abend Error detected.
For full details see Abend File: C:\Documents and Settings\All Users\Application Data\IBM\MQSI/common/errors/BKR2.agent.1560.3164.Abend '.
Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
3.
( BKR2 ) An unexpected exception ''ImbException'' was caught.
The broker caught an unexpected exception.
Use the information in this message and previous messages to determine the cause of the problem, correct the error. A redeploy will be required if this error occurred as a result of a deploy operation.
4.
( BKR2 ) Broker failed to create semaphore
An internal semaphore could not be created.
Use the system log messages to determine why the semaphore failed to be created. Contact your IBM support center if you are unable to resolve the problem.
Again, it does not matter which broker I start first, the first one always starts fine, it is when the second broker starts that the error occurrs
The top section of the abend file is as follows:
+-----------------------------------------------------------------------------+
| |
| |
| First Failure Symptom Report |
| ======================== |
| |
| |
| Proc start time :- Wed May 09 11:24:41 2007 |
| |
| Product Details |
| +++++++++++++++ |
| |
| Vendor :- IBM |
| Product Name :- WebSphere Message Brokers |
| Program ID :- 5724-J04 |
| Version :- 6003 |
| |
| OS Information |
| ++++++++++++++ |
| |
| Operating System :- Microsoft Windows XP |
| Product Type :- Professional |
| Maintenance :- Service Pack 2 (Build 2600) |
| Node Name :- HARTHIG-CATVM |
| No of Processors :- 2 |
| Processor Type :- x86 Family 6 Model 14 Stepping 8 |
| Current Type :- Multiprocessor Free |
| Dbghelp version :- 4.0.5.0 |
| |
| Environment |
| +++++++++++ |
| |
| Service User ID :- user2 |
| Executable Name :- bipbroker.exe BKR2 |
| Process ID :- 3428 |
| |
| Deployment |
| ++++++++++ |
| |
| |
| Build Information |
| +++++++++++++++++ |
| |
| Backing build :- |
| Sandbox :- F:\build\S600_P |
| CMVC Level :- S600-CSD03 |
| Build type :- Production |
| 64 Bit Build :- no |
| |
+------------------------- Thread Context unavailable ------------------------+
Abend Record for PID: 3428 TID: 0x1A4 on: Wed May 09 11:24:41 2007
---> Location <---
File: F:\build\S600_P\src\CommonServices\Win32\ImbNamedMutex.cpp
Line: 81
Function: CreateMutexW
AbendAction: 3
---> Inserts <---
5
ImbNamedMutex::ImbNamedMutex
@(#) 1.7 CommonServices/Win32/ImbNamedMutex.cpp, CommonServices, S000, S000-L50818.2 05/06/10 15:05:11 [8/23/05 11:14:43]
---> Last Errors <---
Note these error codes are not necessarily reliable
GetLastError() returned: 5
errno returned: 17
Do you need the rest of the details in the abend file?
Many Thanks for your help - it is much appreciated |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed May 09, 2007 3:32 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I'd say you're running out of kernel resources to create new semaphores.
Abend files should always result in opening a PMR - you'll really have to talk to Support to get more assistance with this.
Maybe your machine is simply underpowered for what you're trying to do, maybe there is some tuning that can be done to help, or maybe your configuration is mangled.
But you should be talking to Support on anything that creates an Abend. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
|