[
https://issues.apache.org/jira/browse/DERBY-3578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John H. Embretsen updated DERBY-3578:
-------------------------------------
Attachment: d3578_v01.diff
Attached a patch (d3578_v01.diff) implementing this improvement and modifying a
test accordingly. Changed files are:
M java/drda/org/apache/derby/impl/drda/NetworkServerMBeanImpl.java
M java/drda/org/apache/derby/mbeans/drda/NetworkServerMBean.java
M
java/testing/org/apache/derbyTesting/functionTests/tests/management/NetworkServerMBeanTest.java
I have run suites.All with this patch (jdk1.5) and saw no failures apart from
DERBY-3561. Requesting review.
Since this involves a change of a public interface that is new in 10.4, it
would be great if this could be committed to the 10.4 branch (and trunk) as
soon as possible (before creating the release candidate), to avoid potential
compatibility issues.
> DrdaStreamOutBufferSize attribute of NetworkServerMBean should be of type int
> instead of String
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-3578
> URL: https://issues.apache.org/jira/browse/DERBY-3578
> Project: Derby
> Issue Type: Improvement
> Components: JMX
> Affects Versions: 10.4.0.0, 10.5.0.0
> Environment: N/A
> Reporter: John H. Embretsen
> Assignee: John H. Embretsen
> Priority: Minor
> Fix For: 10.4.1.0, 10.5.0.0
>
> Attachments: d3578_v01.diff
>
>
> The DrdaStreamOutBufferSize attribute of
> org.apache.derby.mbeans.drda.NetworkServerMBean is currently of type String.
> The value of this attribute describes the size of the buffer for streaming
> blob/clob from server to client (derby.drda.streamOutBufferSize property),
> and is handled as an integer (int) in the DDMWriter class of the Network
> Server.
> The type was changed to int in the functional specification of DERBY-1387
> [1], since no reason was found for this to be a String. Similar attributes,
> such as DrdaMaxThreads, have return type int. It may useful for a JMX client
> to know that the value should be an int instead of just any arbitrary string;
> hence this change.
> [1]:
> https://issues.apache.org/jira/browse/DERBY-1387?focusedCommentId=12571899#action_12571899
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.