[ 
https://issues.apache.org/jira/browse/APLO-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603204#comment-13603204
 ] 

Lionel Cons commented on APLO-304:
----------------------------------

In fact, there seems to be a problem with the auto_tune parameters. After 
upgrading to the latest snapshot, Apollo refuses to start and logs:

2013-03-15 08:10:07,663 | WARN  |   fatal error at (62:68): cvc-complex-type.4: 
Attribute 'receive_buffer_auto_tune' must appear on element 'connector'.  | 
[...]
2013-03-15 08:10:07,667 | ERROR | Strict validation was configured, shutting 
down | 

Indeed the XSD file contains:

        <xs:attribute name="receive_buffer_auto_tune" type="xs:boolean" 
use="required"/>

Could these be made optional?

Could a test be added to catch these (i.e. with validation="strict" and a few 
good XML files)?
                
> Inconsistent documentation wrt connector buffer size options
> ------------------------------------------------------------
>
>                 Key: APLO-304
>                 URL: https://issues.apache.org/jira/browse/APLO-304
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>         Environment: 99-trunk-SNAPSHOT
>            Reporter: Lionel Cons
>
> The user manual has a "connectors" section describing the receive_buffer_size 
> and send_buffer_size options:
> http://activemq.apache.org/apollo/versions/99-trunk-SNAPSHOT/website/documentation/user-manual.html#Connectors
> They are described via "A connector element can be configured with the 
> following attributes" so one would expect to use:
> <connector id="tcp" bind="tcp://0.0.0.0:61613" receive_buffer_size="1024">
> but later in the manual we see:
> <connector id="tcp" 
> bind="tcp://0.0.0.0:61613?receive_buffer_size=1024&amp;max_read_rate=65536"/>
> So, what is the correct way to specify these options: as eponymous 
> attributes? as part of the bind attribute URL? both?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to