JDK-7076621 : Support logging for messages exchanged between server and client JVM
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 7-client
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-08-09
  • Updated: 2013-09-12
  • Resolved: 2011-08-17
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availabitlity Release.

To download the current JDK release, click here.
7u2 b03Fixed 8Fixed
There are potential to cause deadlock between client JVM and server JVM when messages exchange are implemented as blocking code. Also we would like to have a way to monitor those traffic to make sure things are happening as expected.

Support logging would be very helpful to diagnose problems we encountered. This should be optional and disabled by default.

EVALUATION Would be really nice to have.

SUGGESTED FIX Use an environment variable to switch on/off the logging capability. Messages to be logged with thread, timestamp and messages sent/received. The logging should happen only at the client-end so we don't impact browser performance and avoid double-logging.