activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filip Hanik (JIRA)" <>
Subject [jira] Updated: (AMQ-1860) soTimeout transport property- Incorrect documentation (or code, you pick)
Date Tue, 05 Aug 2008 04:07:54 GMT


Filip Hanik updated AMQ-1860:

    Attachment: transport-options.patch

Example of how to make the soTimeout work for the server, one must of course verify that the
client is picking up the option too

> soTimeout transport property- Incorrect documentation (or code, you pick)
> -------------------------------------------------------------------------
>                 Key: AMQ-1860
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, Documentation
>    Affects Versions: 5.0.0, 5.1.0
>         Environment: All
>            Reporter: Filip Hanik
>            Assignee: Rob Davies
>         Attachments: transport-options.patch
> The documentation for TCP transport, shows soTimeout, connectionTimeout and socketBufferSize
as properties without a prefix.
> The code in doesn't have the support for these properties.
> hence setting a URL to tcp:// does nothing, and defaults
to soTimeout=0 (which is a bad value due to how sockets get closed, and can cause the system
to hang on  a socketWrite call, causing the rest of the server to hang, but I can explain
that on the dev lists for those interested)
> Bug description: Transport properties are incorrectly document or implemented
> There are two solutions to this bug:
> 1. The preferred, would be to fix the documentation
> the mentioned options will work if they are prefixed with "transport."
> so the URL would be 
> tcp://
> 2. Add the properties with their getters/setters into and then
during the handleSocket method add them to the options map
> Please note, this bug refers to the soTimeout setting on the socket that gets created
on the server when a producer/consumer connects in using TCP
> best
> Filip

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message