[
https://issues.apache.org/activemq/browse/AMQ-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-2737.
-----------------------------
Resolution: Fixed
fixed in r945692
the writeTimeoutFilter can now abort an nio broker connection that is blocked
on a write.
> NPE in WriteTimeoutFilter with nio - add support for soWriteTimeout to nio
> transport
> ------------------------------------------------------------------------------------
>
> Key: AMQ-2737
> URL: https://issues.apache.org/activemq/browse/AMQ-2737
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Transport
> Affects Versions: 5.3.2
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.4.0
>
>
> config that shows the problem:{code}
> <amq:transportConnectors>
> <amq:transportConnector name="openwire"
> uri="nio://0.0.0.0:61616?transport.soWriteTimeout=5000&transport.soTimeout=5000"/>
> <amq:transportConnector name="stomp"
> uri="stomp+nio://0.0.0.0:61618?transport.soWriteTimeout=5000&transport.soTimeout=5000"/>
> </amq:transportConnectors>
> {code}
> In the event that a write times out with nio the npe appears in the log:
> 2010-04-12 18:17:03,159 ERROR
> org.apache.activemq.transport.WriteTimeoutFilter$TimeoutThread.run(WriteTimeoutFilter.java:177)
> [WriteTimeoutFilter-Timeout-1] - WriteTimeout thread unable validate
> existing sockets.
> java.lang.NullPointerException: null
> Issue is nio transport doe not support narrow to a
> TcpBufferedOutputStream.class, a little refactor and implementation is needed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
