Community
Participate
Working Groups
Build: TPTP 4.2.0 To Reproduce: 1) Install 4.2.0 on OS/400 V5R4 2) Install 4.2.0 workbench on either Linux or Windows 3) Import the servicelog.log file from <rac_install>/config/servicelog.log Note: I did not notice this problem on Windows, or Linux_PPC64
This is a serious problem. The import is failing consistently.
I have debugged this down to the native communication layer code between the RAC and agent. The agent thread that listens on the agent pipe for messages from the RAC is hung trying to attach to the Java VM in order to call some java methods on the RemoteComponentSkeleton object for the agent. The AttachCurrentThread call is made in _java_notifyMessage in hcjbind.c when handling the RA_AGENT_CONTROLER_AVAILABLE command. Note, this is the first time that it is called. The native stack at this point looks like: _java_notifyMessage (hcjbind.c) messageLoop (RABindings.c) PipeServer (RABindings.c) This problem does not occur when profiling on this system and log import works on other iSeries systems running at older OS levels (eg. V5R3).
This is a Platform problem either in the underlying agent code or in the RAC native communication layer.
PMC approved deferring this to iteration 2 because it is a new O/S level of iSeries for this release and the problem does not occur on older versions of O/S so it won't block existing testcases.
Created attachment 35180 [details] Debug output from RAC native code This file contains debug messages from collection/framework/RABindings/RABindings.c and collection/collectors/java/hcjbnd.c
Created attachment 35182 [details] Debug messages from java agent code Debug output from org.eclipse.hyades.internal.execution.remote.reRemoteComponentSkeleton agent class.
Created attachment 35184 [details] Agent Controller log file without debug Agent Controller log file without debug for log import scenario that corresponds to the logAgent and rsc debug files.
Created attachment 35185 [details] Agent Controller log file with debug Agent Controller log file with debug - this shows example of output for profiling which works and log import which does not work.
The debug file from the Agent Controller communication layer code shows where the hang occurs. For example: hcjbnd: Java Log Agent: notifyMessage: Received message RA_AGENT_CONTROLER_AVAILABLE - about to attach to VM in current thread using VM pointer SPP:0000 :0000 :0:0:2
Deferring this to i3 with approval of Platform project lead. Also reducing severity to major because testing can proceed on older versions of OS/400.
Will test this on another V5R4 system to see if the problem is consistently failing.
Thay has confirmed this problem does not exist on on another iSeries V4R5 system and the system where the original problem was reported has been reconfigured so the problem cannot be reproduced. However, a potential problem we discovered is that the pluginconfig.xml for org.eclipse.hyades.logging.parsers includes an application definition for RemoteLogParserLoader and hardcode's the "-Djava.version=1.4" JVM argument that forces the 1.4 JVM to be used on iSeries. On the sytem where the problem was encountered the default JVM was 1.5 and perhaps the 1.4 JMV was corrupted which caused the problem. I have opened bugzilla 145412 to add a readme item for this log import timeout problem on V5R4 systems and the workaround is to change the JVM argument in pluginconfig.xml to "-Djava.version=1.5". We'll close this defect as unreproducible. If the problem is found again it can be reopened.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
