JDK-4897898 : lwp_set_priority cleanup
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.4.2
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_8,solaris_9
  • CPU: sparc
  • Submitted: 2003-07-29
  • Updated: 2012-10-08
  • Resolved: 2003-11-11
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.
5.0 b18Fixed
Related Reports
Duplicate :  
Relates :  
See attached lwpset.txt for details on cleanups needed.

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger-beta INTEGRATED IN: tiger-b18 tiger-beta

EVALUATION (Copied from evaluation of 4810500) The majority of these cleanups are needed. We need a better model for providing informational printouts to customers than yet another flag here. For the initial bug reported, it is worth returning EAGAIN, OR putting a small retry logic in right here. It might make more sense to turn this into an assertion for debug time. While this is hard to duplicate it would be valuable to understand why it failed and if it is ever the case that retrying could succeed. Definately worth a small email proposal for fixes prior to implementing. The suggested cleanups The cleanups suggested by Dave Dice have been implemented. The assertion checking has been moved to the debug VM and the UseThreadPriorities flag has been used to guard all priority changes. ###@###.### 2003-08-19