-
Bug
-
Resolution: Fixed
-
P4
-
6
-
b15
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2129280 | 5.0u6 | Luis-Miguel Alventosa | P4 | Resolved | Fixed | b03 |
JDK-2146892 | jdmk5.1_03 | Laurence Caullet | P4 | Closed | Fixed | 03 |
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
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
- backported by
-
JDK-2129280 Environment parameter should be notification.buffer.size instead of buffer.size
- Resolved
-
JDK-2146892 Environment parameter should be notification.buffer.size instead of buffer.size
- Closed
- relates to
-
JDK-8345045 Remove the jmx.remote.x.buffer.size JMX notification property
- Resolved