| Author |
Message
|
| jlalbor |
 Posted: Mon Dec 27, 2004 4:04 pm Post subject: Agent Controller on HP UX does not list execution groups |
 |
|
Apprentice
Joined: 18 Feb 2003
Posts: 38
|
We have the following installation.
On HP UX v 11.0
-Broker 5 with FixPack 4
-Agent Controller 5.0.2 (the one available in the Fix Pack 4 download URL)
On Windows XP Professional
-Configuration Manager with Fix Pack 4
-Broker Toolkit with fix pack 4
-Agent controller 5.0.2 (the one available in the Fix Pack 4 download URL)
The HP machine has installed the JRE version 1.4.2.06
In the installation process we got the following warnings at the end of the Agent Controller installation in the HP UX:
| Quote: |
-Checking required disk space requires file service native support.
-File attributes could not be set because native support for that operation is not available
-File times cloud not be set because native support for that operation is not available |
Because of the warnings above, after installing the agent controller we had to set execution permissions to the Agent controller files (shells and libs). After doing this the Agent controller started with no problems.
Everithings looks to work fine, but when we try to debug a message flow in the HP UX, the agent controller does not list any of the execution groups running in the HP, and does not show any error message either.
It looks like there were no execution groups running on the Broker in the HP machine, but there are 2, each with one message Flow. The message flows work fine, they process the input message and insert data in the database with out any problem, but we can not debug them.
The agent controller was installed specifiying the security Disabled and that Any Computer could connect to the agent controller.
We installed the Broker in the Windows machine were the Configuration Manager and the Broker Toolkit resides and created a new Broker, then we deployed the same message flows running in the HP in the windows Broker and test the debugger. We have any problems, the debugger works fine in the windows environment. In the Windows installation process we have no warnings in the Agent controller Installation process.
Reading other problems regarding to remote debugging we found that the Agent controller log should list every execution group running in the broker. Looking at the HP agent controller's log (servicelog.log) we found that none of the execution groups is logged in the file.
We change loggingLevel in the serviceconfig.xml to DEBUG, and all that appears in the log file is this:
| Quote: |
<?xml version="1.0" standalone="yes" ?>
<!DOCTYPE document (View Source for full doctype...)>
<document>
<SERVER_MSG time="2004:12:27:12:27:57" severity="INFORMATION" text="Service starting" />
<SERVER_MSG time="2004:12:27:12:27:57" severity="INFORMATION" text="Started processing Configuration /depura/IBMRAC/config/serviceconfig.xml" />
<SERVER_MSG time="2004:12:27:12:27:57" severity="INFORMATION" text="Completed processing Configuration /depura/IBMRAC/config/serviceconfig.xml" />
<SERVER_MSG time="2004:12:27:12:27:57" severity="SEVERE" text="Service started successfully" />
<SERVER_MSG time="2004:12:27:13:24:38" severity="WARNING" text="Incoming connection request on socket 6 from 0x8f1e013d" />
<SERVER_MSG time="2004:12:27:13:24:38" severity="WARNING" text="Connection accepted on socket 6" />
<SERVER_MSG time="2004:12:27:13:24:38" severity="DEBUG" text="Entering processing thread for client 6" />
<SERVER_MSG time="2004:12:27:13:24:46" severity="DEBUG" text="Validated message of 36 bytes" />
<SERVER_MSG time="2004:12:27:13:24:46" severity="DEBUG" text="Processing message of length 36 bytes." />
<SERVER_MSG time="2004:12:27:13:24:46" severity="DEBUG" text="Processing command: tag=17" />
<SERVER_MSG time="2004:12:27:17:6:53" severity="DEBUG" text="Validated message of 36 bytes" />
<SERVER_MSG time="2004:12:27:17:6:53" severity="DEBUG" text="Processing message of length 36 bytes." />
<SERVER_MSG time="2004:12:27:17:6:53" severity="DEBUG" text="Processing command: tag=17" />
</document> |
We think that maybe the warnings in the Agent Controller installation process are causing the problem, but we have unistalled and installed the Agent controller several times and all the times we have got the same warnings at the end of the installation.
Is there something we need to enable in the HP so the agent controller installs without any warning?
Any ideas of what we sholud do so the agent controller works in the HP UX? |
|
| Back to top |
|
 |
| leongor |
| Posted: Tue Dec 28, 2004 8:35 am Post subject: |
|
|
Master
Joined: 13 May 2002
Posts: 264
Location: Israel
|
Very basic question: do you start Agent Controller before Broker ?
Because all Execution Groups register with Agent Controller when start.
_________________
Regards.
Leonid.
IBM Certified MQSeries Specialist. |
|
| Back to top |
|
|
| jlalbor |
| Posted: Tue Dec 28, 2004 9:13 am Post subject: Yes |
|
|
Apprentice
Joined: 18 Feb 2003
Posts: 38
|
| leongor wrote: |
Very basic question: do you start Agent Controller before Broker ?
Because all Execution Groups register with Agent Controller when start. |
Yes, i have tried every combination. starting first the agent controller and then the broker, and first the broker and then the agent controller, and the result is the same. the agent controller does not detect the execution groups. |
|
| Back to top |
|
|
| chenulu |
| Posted: Wed Dec 29, 2004 3:49 pm Post subject: |
|
|
Voyager
Joined: 27 Mar 2002
Posts: 87
Location: Research Triangle Park, NC
|
Hi ,
Change the loggingLevel from WARNING to DEBUG and loggingDetail from LOW to HIGH in the serviceconfig.xml file <RAC>\config directory. Then stop the broker, RAServer.sh and restart the RAServer.sh wait 10secs for it to initialize and then start the broker and post the details from servicelog.log file. You may want to clear the servicelog.log first so that the only entries are from the new connection. This would ensure that at least your RAC is connecting to the DFEs. If so, then take an EG startup trace which should show whether the DFEs are registering with RAC
-- Chenulu |
|
| Back to top |
|
|
| jlalbor |
| Posted: Wed Dec 29, 2004 5:56 pm Post subject: |
|
|
Apprentice
Joined: 18 Feb 2003
Posts: 38
|
| chenulu wrote: |
Hi ,
Change the loggingLevel from WARNING to DEBUG and loggingDetail from LOW to HIGH in the serviceconfig.xml file <RAC>\config directory. Then stop the broker, RAServer.sh and restart the RAServer.sh wait 10secs for it to initialize and then start the broker and post the details from servicelog.log file. You may want to clear the servicelog.log first so that the only entries are from the new connection. This would ensure that at least your RAC is connecting to the DFEs. If so, then take an EG startup trace which should show whether the DFEs are registering with RAC
-- Chenulu |
Hi,
I have change de logginglevel and loggingDetail, stoped the broker and the agent controller, cleaned the servicelog.log. Then started the agent controller, waited 1 minute and then started the broker. All Execution groups started correctly and the output on the servicelog.log is this:
| Quote: |
<SERVER_MSG time="2004:12:29:19:5:59" severity="INFORMATION" text="Service starting"/>
<SERVER_MSG time="2004:12:29:19:5:59" severity="INFORMATION" text="Started processing Configuration /depura/IBMRAC/config/serviceconfig.xml"/>
<SERVER_MSG time="2004:12:29:19:5:59" severity="INFORMATION" text="Completed processing Configuration /depura/IBMRAC/config/serviceconfig.xml" file="./comm_layer/RAServerConfig/RAServerConfigBinding.cpp" line="190"/>
<SERVER_MSG time="2004:12:29:19:6:0" severity="SEVERE" text="Service started successfully" file="./comm_layer/RAServerConfig/RAServerConfigBinding.cpp" line="319"/>
<SERVER_MSG time="2004:12:29:19:8:32" severity="WARNING" text=" Incoming connection request on socket 6 from 0x8f1e013d" file="./comm_layer/RAServer/messagePump.c" line="925"/>
<SERVER_MSG time="2004:12:29:19:8:32" severity="WARNING" text=" Connection accepted on socket 6" file="./comm_layer/RAServer/messagePump.c" line="1017"/>
<SERVER_MSG time="2004:12:29:19:8:32" severity="DEBUG" text="Entering processing thread for client 6" file="./comm_layer/RAServer/messagePump.c" line="695"/>
<SERVER_MSG time="2004:12:29:19:8:40" severity="DEBUG" text="Validated message of 36 bytes" file="./comm_layer/RAServer/messagePump.c" line="556"/>
<SERVER_MSG time="2004:12:29:19:8:40" severity="DEBUG" text="Processing message of length 36 bytes." file="./comm_layer/RAServer/messagePump.c" line="623"/>
<SERVER_MSG time="2004:12:29:19:8:40" severity="DEBUG" text="Processing command: tag=17" file="./comm_layer/RAServer/RACommS.c" line="397"/>
<SERVER_MSG time="2004:12:29:19:13:0" severity="DEBUG" text="Validated message of 36 bytes" file="./comm_layer/RAServer/messagePump.c" line="556"/>
<SERVER_MSG time="2004:12:29:19:13:0" severity="DEBUG" text="Processing message of length 36 bytes." file="./comm_layer/RAServer/messagePump.c" line="623"/>
<SERVER_MSG time="2004:12:29:19:13:0" severity="DEBUG" text="Processing command: tag=17" file="./comm_layer/RAServer/RACommS.c" line="397"/>
<SERVER_MSG time="2004:12:29:19:13:10" severity="DEBUG" text="Validated message of 36 bytes" file="./comm_layer/RAServer/messagePump.c" line="556"/>
<SERVER_MSG time="2004:12:29:19:13:10" severity="DEBUG" text="Processing message of length 36 bytes." file="./comm_layer/RAServer/messagePump.c" line="623"/>
<SERVER_MSG time="2004:12:29:19:13:10" severity="DEBUG" text="Processing command: tag=17" file="./comm_layer/RAServer/RACommS.c" line="397"/>
<SERVER_MSG time="2004:12:29:19:14:48" severity="WARNING" text=" Incoming connection request on socket 7 from 0x8f1e082e" file="./comm_layer/RAServer/messagePump.c" line="925"/>
<SERVER_MSG time="2004:12:29:19:14:48" severity="WARNING" text=" Connection accepted on socket 7" file="./comm_layer/RAServer/messagePump.c" line="1017"/>
<SERVER_MSG time="2004:12:29:19:14:48" severity="DEBUG" text="Entering processing thread for client 7" file="./comm_layer/RAServer/messagePump.c" line="695"/>
<SERVER_MSG time="2004:12:29:19:14:56" severity="DEBUG" text="Validated message of 36 bytes" file="./comm_layer/RAServer/messagePump.c" line="556"/>
<SERVER_MSG time="2004:12:29:19:14:56" severity="DEBUG" text="Processing message of length 36 bytes." file="./comm_layer/RAServer/messagePump.c" line="623"/>
<SERVER_MSG time="2004:12:29:19:14:56" severity="DEBUG" text="Processing command: tag=17" file="./comm_layer/RAServer/RACommS.c" line="397"/>
<SERVER_MSG time="2004:12:29:19:15:4" severity="DEBUG" text="Exiting processing thread for client 7" file="./comm_layer/RAServer/messagePump.c" line="786"/> |
As far as I can see, no execution group is registered by the agent controller in the log.
The debugger in the broker toolkit does not show any execution group.
Any suggestions? |
|
| Back to top |
|
|
| chenulu |
| Posted: Tue Jan 04, 2005 6:20 pm Post subject: |
|
|
Voyager
Joined: 27 Mar 2002
Posts: 87
Location: Research Triangle Park, NC
|
Hi,
From the log it appears that the broker never registered with the RAC agent. Normally if it does, you should see a message similar to
<SERVER_MSG time="2005:11:16:10:17:15" severity="WARNING" text="Incoming connection request from agent WEBOBROK:default in process 164 with uuid b5559cbb-d939-4778-8183-dfe52eaec192"/>
with the UUID of the EG.
Make sure you can ping the HP-UX system from the toolkit system and also the default port for RAC is not used by some other process.
-- Chenulu |
|
| Back to top |
|
|
| lillo |
| Posted: Thu Sep 01, 2005 4:30 am Post subject: |
|
|
Master
Joined: 11 Sep 2001
Posts: 224
|
Did you solve the problem? I had the same situation.
TIA,
_________________
Lillo
IBM Certified Specialist - WebSphere MQ |
|
| Back to top |
|
|
| lillo |
| Posted: Thu Sep 01, 2005 4:50 am Post subject: |
|
|
Master
Joined: 11 Sep 2001
Posts: 224
|
Finally, SOLVED. Just running the RAC and broker with the same userid.
_________________
Lillo
IBM Certified Specialist - WebSphere MQ |
|
| Back to top |
|
|
|
|
