activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5518) Producer hangs on socketWrite0 on Solaris
Date Wed, 14 Jan 2015 16:24:34 GMT

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

Timothy Bish commented on AMQ-5518:
-----------------------------------

You should have a look at the broker log to see what's happening there, and also check if
there any known issues in your Java runtime for things like this.  

> 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)

Mime
View raw message