mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRMINA-845) ProtocolEncoderOutputImpl isn't thread-safe
Date Fri, 29 Jul 2011 11:57:09 GMT

    [ https://issues.apache.org/jira/browse/DIRMINA-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072787#comment-13072787

Emmanuel Lecharny commented on DIRMINA-845:


when you send a message, you do it using the thread that was used to process the incoming
request. This thread has been selected when the session n which this message has arrived was

If you haven't changed anything (like, adding an executor in the chain), then an incoming
message for a specific session will *always* use the same thread, so there is no reason a
message B can be written before message A, as the thread isn't available before message A
is injected into the queue.

That's the theory, and trust me, it works. Now, if I don't have the code you are playing with,
I won't be able to explain why you see some concurrent issues.

> ProtocolEncoderOutputImpl isn't thread-safe
> -------------------------------------------
>                 Key: DIRMINA-845
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-845
>             Project: MINA
>          Issue Type: Bug
>          Components: Filter
>    Affects Versions: 2.0.4
>            Reporter: Ilya Ivanov
> ProtocolEncoderOutputImpl uses ConcurrentLinkedQueue and at first look it seems to be
thread-safe. But really concurrent execution of flush method isn't thread-safe (and write-mergeAll
> E.g. in RTMP several channels multiplexed in single connection. According protocol specification
it's possible to write to different channels concurrently. But it doesn't work with MINA.
> I've synchronized channel writing, but it doesn't prevent concurrent run of flushing
(in 2.0.4 it's done directly in ProtocolCodecFilter.filterWrite, but ProtocolEncoderOutputImpl.flush
has the same problem).
> Here the fragment of flushing code:
> while (!bufferQueue.isEmpty()) {
>   Object encodedMessage = bufferQueue.poll();
>   if (encodedMessage == null) {
>     break;
>   }
>   // Flush only when the buffer has remaining.
>   if (!(encodedMessage instanceof IoBuffer) || ((IoBuffer) encodedMessage).hasRemaining())
>     SocketAddress destination = writeRequest.getDestination();
>     WriteRequest encodedWriteRequest = new EncodedWriteRequest(encodedMessage, null,
>     nextFilter.filterWrite(session, encodedWriteRequest);
>   }
> } 
> Suppose original packets sequence is A, B, ...
> Concurrent run of flushing may proceed as following:
> thread-1: Object encodedMessage = bufferQueue.poll(); // gets A packet
> thread-2: Object encodedMessage = bufferQueue.poll(); // gets B packet
> ...
> thread-2: nextFilter.filterWrite(...); // writes B packet
> thread-1: nextFilter.filterWrite(...); // writes A packet
> so, resulting sequence will B, A
> It's quite confusing result especially when documentation doesn't contain any explanation
about such behavior.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message