| Author |
Message
|
| ivanachukapawn |
 Posted: Tue Jan 02, 2007 7:58 am Post subject: Toolkit 6.0.2 with RAC 6.0.1 cannot find brokers/exec grp |
 |
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
I have all the recommended updates for Broker 6.0 runtime and Toolkit and have RAC 6.0.1 installed and running as a service.
When I attempt to create a debug launch profile there are no broker/execution groups listed.
I know the broker is running (mqsilist) and the RAC is running. I have clicked refresh and still nothing shows up. I tried stopping and restarting the RAC. Still no luck. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Jan 02, 2007 8:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You need to
1) Stop RAC
2) Stop Brokers
3) Start RAC
4) Start Brokers
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Tue Jan 02, 2007 12:55 pm Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
Jeff,
Thanks a lot for that information. I stopped the RAC then the Broker, started the RAC, then the Broker, and then the execution groups did show up in the debug configuration dialogue window. I assigned the debug to the execution group and then clicked debug (a breakpoint has been set on the output connector from the MQInput node) and then queued a message. The breakpoint was not reached but the message was consumed (current depth = 0). Do you have ideas about this behavior? |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Tue Jan 02, 2007 2:10 pm Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
Jeff,
I GET inhibited the queue just to prove that the message was in fact being queued. When I undid the GET INHIBIT the message was dequeued but this time it hit the breakpoint. I don't know why it didn't work the first time, but I just wanted you to know so you wouldn't waste any time on this.
Thanks,
ivana |
|
| Back to top |
|
|
| Lillian |
| Posted: Thu Jan 18, 2007 6:39 am Post subject: |
|
|
Centurion
Joined: 15 Apr 2002
Posts: 102
|
i have a similar problem ( ie cannot see the execution group when creating the debug config. I have stopped and started as above, checked listener and security is off and nobody else is debugging. First time setup.
WMB version 6.0.0.3 and toolkit 6.0.0.1 RAC 6.0.0.1 |
|
| Back to top |
|
|
| Lillian |
| Posted: Thu Feb 01, 2007 4:48 am Post subject: |
|
|
Centurion
Joined: 15 Apr 2002
Posts: 102
|
I have just checked the servicelog.log and I can see that the RAC is picking the dataflow engines but as soon I I try to connect with tookit I get the error below in the log. any ideas?
<CommonBaseEvent creationTime="2007-02-01T11:39:12.000000Z" globalInstanceId="k5C1D1600003AB3F4A1932394362E475" msg=" Connection refused on socket 5 from 0xa3ca350b" severity="55" version="1.0.1"> |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Feb 01, 2007 4:53 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
That's either a network problem or a RAC security problem.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Lillian |
| Posted: Thu Feb 01, 2007 4:56 am Post subject: |
|
|
Centurion
Joined: 15 Apr 2002
Posts: 102
|
| I have disabled the RAC security. Exactly what do i check with the network guys? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Feb 01, 2007 4:58 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Ask them why the machine is refusing the socket.
And make sure you're using the right RAC port.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| pcelari |
| Posted: Thu Feb 01, 2007 5:03 am Post subject: |
|
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
You should run the rational updater in your Toolkit to upgrade to version 6.0.2. there is some inconsistency between broker 6.0.0.3 and toolkit 6.0.0.1.
I had a lot of problem before. After the update, they all dissappeared.
good luck!
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| Back to top |
|
|
| Lillian |
| Posted: Mon Feb 05, 2007 4:22 am Post subject: |
|
|
Centurion
Joined: 15 Apr 2002
Posts: 102
|
I needed to update the serviceconfig.xml file to have the
<Allow host="XXXXXX"/> as IP address instead of the machine names.
This resolved the socket connect problem. |
|
| Back to top |
|
|
|
|
