Contact Us

Home > Error Starting > Error Starting Transport Layers Agent Controller Exiting

Error Starting Transport Layers Agent Controller Exiting

The servicelog.log shows: Unable to create shared memory: acbuffer. Bug175252 - (new AC) Agent Controller start-up fails on Linux-IA32 Summary: (new AC) Agent Controller start-up fails on Linux-IA32 Status: CLOSED DUPLICATE of bug 173504 Product: z_Archived Classification: Eclipse Foundation Component: This means that the cache was not able to resolve the hostname presented in the URL. The machine IDs are 997 and 998. Check This Out

This is a common configuration that should be supported. Server queries Schedule Executor for work for this agent. The old Agent Controller required that three ports be opened on the agent to allow the workbench to contact it. Add the debug switch (true) in the Majordomo configuration file.

Back to top Check list Here are some check lists with which you can start: Check 1: On Agent Machine Verify if the Load Generation Agents are installed on agent machines. Note: If there are DNS issues then Majordomo might not be able to contact a workbench. Description Rohit Shetty 2007-02-23 06:34:37 EST Build ID: I20070209-1006 Steps To Reproduce: 1.Unzip the 2. See servicelog.log for error report.

If the host name does not resolve, try using IP address, or add the entry from "drives/etc/hosts" file. Has anybody managed to run Agent Controller. JDK this was tried with: 1) Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142ifx-20060209 (SR4-1) (JIT enabled: jitc) 2) java version "1.5.0"Java(TM) 2 run Result: Starting Agent Controller.

servicelog.log contains: C:\ractest\rac\bin>more ..\config\servicelog.log Comment 5 Jonathan West 2008-02-01 17:16:53 EST Created attachment 88638 [details] New EM64T/IPF Build Files + Updated Make64 - Patch - 2 Small fix to reference .mak64 rather than .mak.

Any ideas please ?? > Thanks, > Krishnaveni Krishnarajah Hi Krishnaveni, first, I would recommend killing an ACServer.exe/RAServer.exe/ACWinService.exe/RAWinService.exe processes, as well as any java.exe processes that are running on your system. Run SetConfig.bat under AC\bin. 3. Porting of the PI agent, perfmon and probekit plugins is required for the bug #157486. You can change this by providing a different port as the final argument on the command line, for example: "C:\Program Files\IBM\SDP\jdk\jre\bin\java" -cp C:\Temp\RPTAgentTest.jar AgentListener 7081 Each polling request to the workbench

Comment 2 Paul Slauenwhite 2007-02-23 11:48:11 EST (In reply to comment #1) However, when launching a test using the 64-bit Agent Controller and JRE, I get the following exception: Exception in Type Enter at this point to end the utility. Comment 3 Bing Xu 2008-08-02 13:02:19 EDT Can't reproduce. ACServer failed to start.

Open this URL: http://>:7080/hello This ensures that both the workbench and agent are coordinated for communication by way of the respective port. his comment is here Yes, it is important. Linux IA32 should be fixed by 217123. The TPTP Test Execution Harness cannot launch Agent Controller agents in parallel, taking 30-60 seconds per agent to launch one.

In any given scenario, either of the physical machines or virtual machines is treated as workbench or agent machines. But it seems that the patch, fixing the normal termination scenario could be aplied. Back to top RPT workbench agent communication flow In an ideal scenario, the schedule triggered from the RPT workbench communicating to the agents involves this sequence: Schedule Executor indicates interest in Comment 19 Paul Slauenwhite 2007-04-27 08:34:02 EDT Created attachment 65197 [details] servicelog.log (TPTP-4.4.0-200704261104) Comment 20 jkubasta 2007-04-27 08:41:05 EDT Alan, what JVM and build did you succeed with?

It could be got with "ipcs -lm" command. Open the Start menu option Start > Programs > IBM Installation Manager > View Installed Packages. Rational Performance Tester (RPT) offers agent health indicators and load-test resource management to achieve this task.

Comment 37 Igor Alelekov 2007-05-17 14:56:54 EDT > Great news!

In another given scenario, the servicelog.log contains this error message: Error: Unable to create the server socket. The main difference is the communication infrastructure. It seems not... I would recommend addressing the crash scenario as well when fixing this bug.

Comment 10 Igor Alelekov 2007-02-28 02:46:23 EST (In reply to comment #9) > It seems like the RAStop does not stop the java > processes that are created by the ac. As for crashed AC - additional investigations are required. IBM WILL NOT BE LIABLE FOR ANY ACTUAL, DIRECT, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), EVEN IF IBM, OR ITS RESELLER, navigate here When I try to start up the new AC on Linux/x86 I get the following error at the console: Starting Agent Controller.

When trying to start AgentController\win_ia32\bin\ACServer.exe, I am getting this exception [code] Error starting transport layers, Agent controller exiting. Ill attach the serviceConfig.xml to the defect. Reassigning current defect to Jonathan to provide build scripts for Win-IPF and Win-EM64T. Majordomo launches process.

Bug242791 - Standalone Agent Controller cannot be started. Comment 17 Igor Alelekov 2007-03-13 07:19:06 EDT *** Bug 175264 has been marked as a duplicate of this bug. *** Comment 18 Samson Wai 2007-03-13 10:22:48 EDT The attached two patches See servicelog.log for error report. The Agent Controller (Linx-IA32) will not start with the following output: ractest@paules:~/rac/bin> ./ Starting Agent Controller.