JDK-6431704 : Deadlock in RMIConnector.close
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 1.4.2_07
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_9
  • CPU: sparc
  • Submitted: 2006-05-30
  • Updated: 2013-04-30
  • Resolved: 2012-12-06
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 Availability Release.

To download the current JDK release, click here.
JDK 8
8Fixed
Related Reports
Relates :  
JDK-6296324 - Deadlock in RMIConnector.close
Description
IncidentID:	714878
Category:	jmx-remote
Subcategory:	classes
Language:	en
Release:	1.0
Priority:	4
Severity:	2
State:	Waiting
Disposition:	
Bug/RFE:	bug
Synopsis:	Deadlock in RMIConnector implementation
Submit Date:	2006-05-25 13:50:07.3
Description:	

FULL PRODUCT VERSION :
java version "1.4.2_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_07-b05)
Java HotSpot(TM) Client VM (build 1.4.2_07-b05, mixed mode)

ADDITIONAL OS VERSION INFORMATION :
SunOS admin 5.10 Generic_118833-03 sun4u sparc SUNW,Sun-Fire-V210

EXTRA RELEVANT SYSTEM CONFIGURATION :
jmxremote-1_0_1_04-b58 2005.11.23_16:04:12_MET

A DESCRIPTION OF THE PROBLEM :
Deadlock detected in jmxremote.  Here are the call stacks copied out from JConsole.

Name: Thread-17413
State: BLOCKED on [I@b6a850 owned by: ClientNotifForwarder-104
  Total blocked: 3  Total waited: 0

Stack trace:
javax.management.remote.rmi.RMIConnector.close(RMIConnector.java:408)
javax.management.remote.rmi.RMIConnector$RMIClientCommunicatorAdmin.doStop(RMIConnector.java:1583)
com.sun.jmx.remote.internal.ClientCommunicatorAdmin.restart(ClientCommunicatorAdmin.java:133)
com.sun.jmx.remote.internal.ClientCommunicatorAdmin.access$500(ClientCommunicatorAdmin.java:16)
com.sun.jmx.remote.internal.ClientCommunicatorAdmin$Checker.run(ClientCommunicatorAdmin.java:178)
java.lang.Thread.run(Thread.java:595)


Name: ClientNotifForwarder-104
State: BLOCKED on javax.management.remote.rmi.RMIConnector@ec6a11 owned by: Thread-17413
  Total blocked: 65  Total waited: 0

Stack trace:
javax.management.remote.rmi.RMIConnector.close(RMIConnector.java:403)
javax.management.remote.rmi.RMIConnector$RMIClientCommunicatorAdmin.gotIOException(RMIConnector.java:1435)
javax.management.remote.rmi.RMIConnector$RMINotifClient.fetchNotifs(RMIConnector.java:1290)
com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.fetchNotifs(ClientNotifForwarder.java:508)
com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.run(ClientNotifForwarder.java:399)
com.sun.jmx.remote.internal.ClientNotifForwarder$LinearExecutor$1.run(ClientNotifForwarder.java:83)



REPRODUCIBILITY :
This bug can be reproduced rarely.


Work Around:	


Comments:	

(company - Intervoice, Inc. , email - ###@###.###)


Suggested Fix:	

 


History:	

Insert from Submit.Backend.processBug

************************************************
Dear Java Developer,

Thank you for your interest in improving the quality of Java Technology.

Your report has been assigned an internal review ID of 714878, which is NOT visible on the Sun Developer Network (SDN).

Please be aware that the large volume of reports we receive sometimes prevents us from responding individually to each message.

We currently have a three week average response time.  If the information is determined to be a new Bug or RFE, or a duplicate of a known Bug or RFE, you will receive a followup email containing a seven digit bug number.  You may search for, view, or vote for this bug in the Bug Database at http://bugs.sun.com/.

If you just reported an issue that could have a major impact on your project and require a timely response, please consider purchasing one of the support offerings described at http://developers.sun.com/services/.

The Sun Developer Network (http://developers.sun.com) is a free service that Sun offers. To join, visit http://developers.sun.com/global/join_sdn.html.

For a limited time, SDN members can obtain fully licensed Java IDEs for web and enterprise development.  More information is at http://developers.sun.com/prodtech/javatools/free/.

Thank you for using our bug submit page.

Regards,
Java Developer Bug Report Review Team



---------------------------------------------------------------


Date Created: Thu May 25 13:50:07 MDT 2006
Type:        bug
Customer Name:   Miklos Lengyel
Customer Email:  ###@###.###
SDN ID:       mlengyel
status:      Waiting
Category:    jmx-remote
Subcategory: classes
Company:     Intervoice, Inc.
release:     1.0
hardware:    sun4
OSversion:   solaris_10
priority:    4
Synopsis:    Deadlock in RMIConnector implementation
Description:
 FULL PRODUCT VERSION :
java version "1.4.2_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_07-b05)
Java HotSpot(TM) Client VM (build 1.4.2_07-b05, mixed mode)

ADDITIONAL OS VERSION INFORMATION :
SunOS admin 5.10 Generic_118833-03 sun4u sparc SUNW,Sun-Fire-V210

EXTRA RELEVANT SYSTEM CONFIGURATION :
jmxremote-1_0_1_04-b58 2005.11.23_16:04:12_MET

A DESCRIPTION OF THE PROBLEM :
Deadlock detected in jmxremote.  Here are the call stacks copied out from JConsole.

Name: Thread-17413
State: BLOCKED on [I@b6a850 owned by: ClientNotifForwarder-104
  Total blocked: 3  Total waited: 0

Stack trace:
javax.management.remote.rmi.RMIConnector.close(RMIConnector.java:408)
javax.management.remote.rmi.RMIConnector$RMIClientCommunicatorAdmin.doStop(RMIConnector.java:1583)
com.sun.jmx.remote.internal.ClientCommunicatorAdmin.restart(ClientCommunicatorAdmin.java:133)
com.sun.jmx.remote.internal.ClientCommunicatorAdmin.access$500(ClientCommunicatorAdmin.java:16)
com.sun.jmx.remote.internal.ClientCommunicatorAdmin$Checker.run(ClientCommunicatorAdmin.java:178)
java.lang.Thread.run(Thread.java:595)


Name: ClientNotifForwarder-104
State: BLOCKED on javax.management.remote.rmi.RMIConnector@ec6a11 owned by: Thread-17413
  Total blocked: 65  Total waited: 0

Stack trace:
javax.management.remote.rmi.RMIConnector.close(RMIConnector.java:403)
javax.management.remote.rmi.RMIConnector$RMIClientCommunicatorAdmin.gotIOException(RMIConnector.java:1435)
javax.management.remote.rmi.RMIConnector$RMINotifClient.fetchNotifs(RMIConnector.java:1290)
com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.fetchNotifs(ClientNotifForwarder.java:508)
com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.run(ClientNotifForwarder.java:399)
com.sun.jmx.remote.internal.ClientNotifForwarder$LinearExecutor$1.run(ClientNotifForwarder.java:83)



REPRODUCIBILITY :
This bug can be reproduced rarely.
workaround:  
comments:    (company - Intervoice, Inc. , email - ###@###.###) 


Processor:	
Submitter:	###@###.###
Comments
Already fixed in non-eol:ed versions.
06-12-2012
WORK AROUND Using Tiger or Mustang, the bug has been fixed in the both versions.
23-08-2006
EVALUATION When an IOException is detected by a RMI client, and the client decides to close the connection, it is not necessary to call the method "close" under the synchronization of the veariable "terminationLock", because the method "close" is under synchronization protection. This bug has been fixed in Tiger and Mustang
22-08-2006