United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-7076621 Support logging for messages exchanged between server and client JVM
JDK-7076621 : Support logging for messages exchanged between server and client JVM

Details
Type:
Enhancement
Submit Date:
2011-08-09
Status:
Resolved
Updated Date:
2011-09-22
Project Name:
JDK
Resolved Date:
2011-08-17
Component:
deploy
OS:
generic
Sub-Component:
plugin
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
7-client
Fixed Versions:
7u2 (b03)

Related Reports
Backport:

Sub Tasks

Description
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.

                                    

Comments
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.
                                     
2011-08-09
EVALUATION

Would be really nice to have.
                                     
2011-08-09
SUGGESTED FIX

Use "JPI2_PIPE_LOGDIR" to switch logging support, the environment variable should point to a directory where log file to be stored.

Log file will be names as pipe_<timestamp>.log

Heartbeat rate is reduced when logging is enabled.

http://sa.us.oracle.com/projects/deployment_data/7-client/7076621.0
                                     
2011-08-09



Hardware and Software, Engineered to Work Together