You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2015/12/23 17:22:46 UTC
[jira] [Closed] (AMQ-5518) Producer hangs on socketWrite0 on
Solaris
[ https://issues.apache.org/jira/browse/AMQ-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-5518.
-----------------------------
Resolution: Cannot Reproduce
This doesn't appear to be a broker side issue.
> Producer hangs on socketWrite0 on Solaris
> -----------------------------------------
>
> Key: AMQ-5518
> URL: https://issues.apache.org/jira/browse/AMQ-5518
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.10.0
> Environment: cat /etc/release
> Oracle Solaris 10 9/10 s10x_u9wos_14a X86
> uname -a
> SunOS kenvng 5.10 Generic_142910-17 i86pc i386 i86pc
> Reporter: Pawel Remiszewski
> Attachments: SampleProgram.java, activemqtest.hang.stack.txt
>
>
> When multiple producers are writing in request-response model (using topics), application hang (deadlock) is visible on Solaris platform (see Environment for details). Tests on Linux (Ubuntu) show no issues.
> Adding soWriteTimeout in broker settings can be used as workaround, because the whole connection is broken when timeout exceeds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)