[
https://issues.apache.org/jira/browse/DIRMINA-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835878#action_12835878
]
Emmanuel Lecharny commented on DIRMINA-764:
-------------------------------------------
I have used the latest stable version, as the user did the comparison with a
stable version, I guess. Anyway, I may have been wrong about NETTY crashing,
but I was able to reproduce it 3 or 4 times yesterday with Julien as a witness.
And as I said, it may perfectly be a problem with the OS and JVM i'm using on
my mac.
If the test can be used to demonstrate the problem with NETTY, then fine, but
I'm not really interested in the fact that NETTY works or not with this test,
I'm just using NETTY because the user has created a test for it.
What is important to me is to get MINA working, and as I already said, the
performances I get are totally irrelevant but for this very test, as I'm
running the clients and the server on one single machine. The initial test I
run gave me a baseline and I'm using this baseline (ie, 13200 msg/s with MINA)
to see if the fixes I'm introducing in MINA have a real impact on the code.
> DDOS possible in only a few seconds...
> --------------------------------------
>
> Key: DIRMINA-764
> URL: https://issues.apache.org/jira/browse/DIRMINA-764
> Project: MINA
> Issue Type: Bug
> Affects Versions: 2.0.0-RC1
> Reporter: Emmanuel Lecharny
> Assignee: Emmanuel Lecharny
> Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: screenshot-1.jpg, screenshot-2.jpg
>
>
> We can kill a server in just a few seconds using the stress test found in
> DIRMINA-762.
> If we inject messages with no delay, using 50 threads to do that, the
> ProtocolCodecFilter$MessageWriteRequest is stuffed with hundred of thousands
> messages waiting to be written back to the client, with no success.
> On the client side, we receive almost no messages :
> 0 messages/sec (total messages received 1)
> 2 messages/sec (total messages received 11)
> 8 messages/sec (total messages received 55)
> 8 messages/sec (total messages received 95)
> 9 messages/sec (total messages received 144)
> 3 messages/sec (total messages received 162)
> 1 messages/sec (total messages received 169)
> ...
> On the server side, the memory is totally swamped in 20 seconds, with no way
> to recover :
> Exception in thread "pool-1-thread-1" java.lang.OutOfMemoryError: Java heap
> space
> (see graph attached)
> On the server, ConcurrentLinkedQueue contain the messages to be written (in
> my case, 724 499 Node are present). There are also 361629
> DefaultWriteRequests, 361628 DefaultWriteFutures, 361625 SimpleBuffer, 361
> 618 ProtocolCodecFilter$MessageWriteRequest and 361 614
> ProtocolCodecFilter$EncodedWriteRequests.
> That mean we don't flush them to the client at all.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
