JDK-6174229 : Environment parameter should be notification.buffer.size instead of buffer.size
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2004-10-05
  • Updated: 2010-07-29
  • Resolved: 2004-12-04
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.
Other JDK 6 Other
5.0u6,jdmk5.1_03Fixed 6 b15Fixed jdmk5.1_03Fixed
Description
First the code is not in sync with the spec. (see non-standard environment parameters).
Then, it is not coherent too with other "notifications" env. parameters, such as :
- notification.fetch.max
- notification.fetch.timeout
###@###.### 10/5/04 12:44 GMT
Comments
EVALUATION Indeed, this is inconsistent, and a spec violation (although it is in a non-normative part of the spec). For compatibility, we will need to continue to recognize the jmx.remote.x.buffer.size parameter, but we must also recognize jmx.remote.x.notification.buffer.size if present. The standard parameter should take precedence. ###@###.### 10/5/04 14:22 GMT
05-10-2004