Community
Participate
Working Groups
The org.eclipse.hyades.logging.core.LoggingAgent class does not throw any exceptions or provide a way for the user to determine if the Agent Controller is available or accessible. For example, if a user of LoggingAgent does not have the AgentController native DLL libraries in their PATH, the logging agent cannot register with the Agent Controller but the user gets no notification of this problem. An example of this is the live log file monitoring scenario using standalone GLA configured with a logging agent outputter. See defect https://bugs.eclipse.org/bugs/show_bug.cgi?id=113171.
One solution is to throw an AgentControllerUnavailableException from the LoggingAgent constructors. However that is a breaking API change. Another solution is to provide an isAgentControllerAvailable() method.
P2 Highly desirable and planned for this release, but not stop ship normal A problem making a function difficult to use but no special work around is required
I also suggest calling RemoteComponentSkeleton.initialize() instead of initializeFast() in the LoggingAgent constructor to have a better chance of the Agent Controller active response being received before LoggingAgent constructor returns. Current behaviour in the 113171 scenario is that initializeFast() throws an AgentControllerUnavailableException() even though the agent registers successfully with Agent Controller.
Dave, would LoggingAgent#isLogging() solve your problem (checks if the Logging Agent is logging (e.g. Agent Controller is available and the Logging Agent is being monitored))?
No, isLogging() will not work. I want to check if Agent Controller is available before the client starts monitoring. isLogging() will always return false at that time.
Created attachment 28498 [details] Patch Here is a patch with my suggested fix.
Cannot contain in TPTP V4.2.0 (i2).
Cannot contain in TPTP V4.2.0 (i3).
Re-targeting to 4.3 since no opposition to the request for deferral (http://dev.eclipse.org/mhonarc/lists/tptp-platform-dev/msg00975.html).
Applied the patch, and submitted to the head of the CVS.
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 originator of this enhancement/defect has an inactive Bugzilla account 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.
