| Author |
Message
|
| WBI_user |
 Posted: Fri Oct 06, 2006 12:21 pm Post subject: Cannot deploy to new broker |
 |
|
Partisan
Joined: 07 Aug 2001
Posts: 386
|
I have a new broker running on AIX WMB V6002.
ps -ef shows Broker, configmgr and UserNameserver are all running.
Using the tookit (V6001) on Windows, I can talk to the config manager and can see the broker on the topology screen. However, I have the warning saying broker not running and execution group not running. If I remember correctly, for a brand new broker, before any flow is deploy, I should see broker is running and execution group is not running.
Anyway, I created a simple flow and deploy to the broker. I got the response back from the config mgr. But never get anything on the event log. Any subsequent deploy will fail saying that the previous deply was still outstanding. There is no error in the windows event viewer or AIX user.log. The broker and the configmgr is sharing the same QMgr. So they should be talking. I hope. BTW there is no error in the MQ log.
Any idea ? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Oct 06, 2006 2:54 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
check that the channels from the configmgr to the broker and from the broker to the configmgr are working well. Make sure they are triggered.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| WBI_user |
| Posted: Mon Oct 09, 2006 8:13 pm Post subject: |
|
|
Partisan
Joined: 07 Aug 2001
Posts: 386
|
| The broker and the config mgr share the same Qmgr. So there is no channel between them. |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Mon Oct 09, 2006 8:27 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi WBI_user,
What does the Windows Event Viewer say ?
Regards. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 10, 2006 2:17 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You don't remember correctly.
For a brand-new broker, neither the broker nor the default EG will be in a running state until you deploy a flow to the EG.
If the Broker registered to the configmgr correctly, and it shows up in the domain, then it is active and ready for deploys.
Also, you did run mqsistart <broker> after you ran mqsicreatebroker, right?
Did you get back a good response when you added the broker to the domain?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| nathanw |
| Posted: Tue Oct 10, 2006 2:59 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
OK as a followup to this i have a very similar problem
Windows 2000
installed all fine
created a default config so everything running under
WBRK6_DEFAULT_QUEUE_MANAGER
Deafult broker starts up and appears in the domain window etc
problem encountered when I try to deploy either delta or msgflows
| Code: |
( WBRK6_DEFAULT_BROKER ) Execution Group '$SYS_mqsi' failed to return an internal configuration 'Start' message response within a 60 second time period.
|
Basically it is sending teh deploys to the broker but it is not receiving a reply
yes i know RTFM but at this point I am pulling my hair out as everything is as per manual
Any help appreciated
As an update i get teh good old
BIP2066E and BIP2087E errors in the event log window when a deploy is attempted
_________________
Who is General Failure and why is he reading my hard drive?
Artificial Intelligence stands no chance against Natural Stupidity.
Only the User Trace Speaks The Truth  |
|
| Back to top |
|
|
| pdrabik |
| Posted: Tue Oct 10, 2006 6:18 am Post subject: |
|
|
Apprentice
Joined: 29 Sep 2006
Posts: 31
Location: poland
|
i can say im having similar problem though...
im still using default configuration ... but once upon the time, during deployment, nothing happens... just simple reply that conf. manager got mine notification about deployment ... normally after a while under execution group some flow appears as running.. but these day was another.. nothing has happened, now flow under exec. group.. no event log error, warning, info..
while deploy via command line, i get 'time expired' note... (as someone above)
when im trying to redeploy there is notification, that deployment cannot be mantained due to previos process still operating...
only after 'cancel deploy' option i can try again.
moreover, i ve tried to recreate the default broker. since i deleted it from toolkit, i cant create new one, why.. because deletion is still in progress since 7 days now :/
should i maintain new default configiruration... i smell already bunch of problems with 'the broker already exist' or something like that :/
_________________
---
cc: poltreak@o2.pl |
|
| Back to top |
|
|
| WBI_user |
| Posted: Tue Oct 10, 2006 6:48 am Post subject: |
|
|
Partisan
Joined: 07 Aug 2001
Posts: 386
|
As I mentioned ps -ef shows that the broker is running
$ ps -ef | grep MY_BRK
mqsiuid 512018 1 0 Oct 06 - 0:00 bipservice MY_BRK
mqsiuid 532630 512018 0 Oct 06 - 0:00 bipbroker MY_BRK
There is no error on Windows event viewer because it has successfullt send the message to the config mgr and received a reply from the CM.
I just noticed that There is no open count on SYSTEM.BROKER.ADMIN.QUEUE. I think the broker should be opening the queue for Input. Am I right ? This may explain why deploymnet request were perfomed. Am I right ? But I see no error in AMQERR01.LOG.
I'll investigate this further. Please let me know if I am going down the wrong path. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 10, 2006 6:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You were able to successfully add the Broker to the configmgr? Or not?
If nobody is listening to SYSTEM.BROKER.ADMIN.QUEUE, then something is not right at all.
At a minimum, try mqsistop and mqsistart and check the aix system log to ensure it started successfully.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| WBI_user |
| Posted: Tue Oct 10, 2006 7:12 am Post subject: |
|
|
Partisan
Joined: 07 Aug 2001
Posts: 386
|
The user.log says that the broker service has started and so is the ps -ef. However I was never able to stop the broker properly. The mqsistop will hang and I have to kill the process.
Then I can start it again and get the same message saying that broker service is running in the log. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 10, 2006 7:17 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Did you try mqsistop -i ?
Does that function?
It sounds like your broker is not working right.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| nathanw |
| Posted: Tue Oct 10, 2006 7:24 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
jeff i know i am probably going to get a sharp reply but
if am the prereqs are installed and products are at teh right level (which on my system they are) then taking a default config should mean no problems
i am pulling even more hair out now
not a happy bunny
_________________
Who is General Failure and why is he reading my hard drive?
Artificial Intelligence stands no chance against Natural Stupidity.
Only the User Trace Speaks The Truth |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 10, 2006 7:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I personally never use the default configuration - in part because I hate the naming standard. In part because it can be hard to debug when it fails - because too many things are being created all at once and if you miss the first error, then you've missed the likely actual cause.
That said, given a default configuration that has failed to work... you can either start entirely from scratch, or try and recreate bad components from scratch. Or you can really bear down and troubleshoot everything - including running trace and opening PMRs and etc.
Also, you haven't really shown that you're having a "similar" problem. You're having some problem with a default configuration. It may be entirely unlike the problem that WBI_user has, and entirely unlike pdrabik's problem.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| WBI_user |
| Posted: Thu Oct 12, 2006 10:22 am Post subject: |
|
|
Partisan
Joined: 07 Aug 2001
Posts: 386
|
I decided to start all over again.
I created a new QMgr (WMB_QM)
I created a new config mgr (WMB_CM)
$ mqsicreateconfigmgr WMB_CM -i 12345 -a 12345 -q WMB_QM
AMQ8110: WebSphere MQ queue manager already exists.
WebSphere MQ queue manager running.
The setmqaut command completed successfully.
:
The setmqaut command completed successfully.
BIP8071I: Successful command completion.
I start the config mgr
mqsistart WMB_CM
I can see
"BIP1003I: The Configuration Manager is available for use. in the log"
At this time, I check the MQ Qmgr and found out that I only have SYSTEM.BROKER.ADMIN.REPLY but not SYSTEM.BROKER.ADMIN.QUEUE
I think something is already wrong here. But not sure !!
So I created the queue
SYSTEM.BROKER.ADMIN.QUEUE
I then create the broker
$ mqsicreatebroker WMB_BRK -i 12345 -a 12345 -q WMB_QM -n MQSIDB
AMQ8110: WebSphere MQ queue manager already exists.
WebSphere MQ queue manager running.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
:
The setmqaut command completed successfully.
But I never get any message saying "Successful command completion."
After 25 minutes of wait, I try to start the borker
mqsistart WMB_BRK
I can see
"BIP2001I: The WebSphere Message Brokers service has started at version 6002; process ID 725238. " in user.log
I checked the SYSTEM.BROKER.ADMIN.QUEUE, there is still no open count.
I started the toolkit and added the broker to the topology. I got the message saying that my request was accepted and I should check the event log for successful completion. But there is nothing in the event log.
If I refresh the topology screen, I can see the broker added to the toolkit.
I check MQ again, I can see a message in SYSTEM.BROKER.ADMIN.QUEUE
Since there is no open count, I know that I am back to the same problem again.
Was the broker creation completely successful ? Should I get a successful command completion message ?
Why is the SYSTEM.BROKER.ADMIN.QUEUE not created ?
Why the Broker not openning the queue for input ? |
|
| Back to top |
|
|
| WBI_user |
| Posted: Thu Oct 12, 2006 10:43 am Post subject: |
|
|
Partisan
Joined: 07 Aug 2001
Posts: 386
|
Found out that SYSTEM.BROKER.ADMIN.QUEUE is created when the broker is created.
But I still do'nt understand why the broker does not open the queue ?
I was wondering if the broker was created with complete sucess because I never receive any message saying command sucessfully completed |
|
| Back to top |
|
|
|
|
