[
https://issues.apache.org/jira/browse/AMQ-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795128#comment-13795128
]
Claire Chan commented on AMQ-4802:
----------------------------------
I have the same problem. using the out-of-the-box activemq 5.8.0 configuration,
the activeInputStream hangs after reading some number of bytes at
FifoMessageDispatchChannel.dequeue(long timeout) at the mutex.wait() line.
Looks like it's waiting for some other thread to fill the
LinkedList<MessageDispatch> list. I'm trying to understand whose responsible
for that, and if I'm missing something in the usage. My code looks just like
the above, and is actually straight out of the Activemq in Action book. I'm
using large content too.
> ActiveMQInputStream does not work for big content
> -------------------------------------------------
>
> Key: AMQ-4802
> URL: https://issues.apache.org/jira/browse/AMQ-4802
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.8.0
> Environment: Mac OS 10.6.8
> Reporter: Marc Leineweber
>
> Sending a file with size 4.6 MB with ActiveMQOutputStream works and results
> in 71 messages on the ActiveMQ broker.
> Trying to receive this file / these messages using an ActiveMQInputStream
> fails - after a while (720896 bytes received so far) inputStream.read(buffer)
> never answers (it waits in ...). If inputStream is created with a timeout, I
> get a ActiveMQInputStream$ReadTimeoutEcxeption.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
