You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Chow (JIRA)" <qp...@incubator.apache.org> on 2009/07/10 13:29:14 UTC
[jira] Updated: (QPID-1980) Java broker does not parse protection
I/O configuration with expected XML structure
[ https://issues.apache.org/jira/browse/QPID-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Chow updated QPID-1980:
-----------------------------
Attachment: ServerConfiguration.java.diff
I have created a patch against trunk to load the three protection I/O parameters with these keys:
connector.protectio.enabled
connector.protectio.readBufferLimitSize
connector.protectio.writeBufferLimitSize
> Java broker does not parse protection I/O configuration with expected XML structure
> -----------------------------------------------------------------------------------
>
> Key: QPID-1980
> URL: https://issues.apache.org/jira/browse/QPID-1980
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.5
> Reporter: Keith Chow
> Attachments: ServerConfiguration.java.diff
>
>
> The following is the default 0.5 java broker config.xml structure for protection I/O related configuration.
> <broker>
> <connector>
> <qpidnio>false</qpidnio>
> <protectio>
> <enabled>false</enabled>
> </protectio>
> </connector>
> </broker>
> But ServerConfiguration expects a config value with key "broker.connector.protectio.enabled", which makes the "broker." prefix appears to be extraneous if the default config's XML structure is correct.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org