[
https://issues.apache.org/jira/browse/DIRMINA-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673845#action_12673845
]
Serge Baranov commented on DIRMINA-663:
---------------------------------------
Here it is (same with 1.6.0_11 and 1.6.0_12). Line numbers may not match
because of code reformat in the IDE, running main() stub instead of JUnit
runner:
time = 13:53:26.167
remaining = 1024
limit = 1024
capacity = 2048
Exception in thread "main" java.lang.AssertionError: No message received
at org.junit.Assert.fail(Assert.java:91)
at mina_test.TestingIoHandler.waitForMessage(TestingIoHandler.java:33)
at mina_test.JUTestBigFrame.bigFrame(JUTestBigFrame.java:25)
at mina_test.JUTestBigFrame.main(JUTestBigFrame.java:33)
time = 13:53:31.465
remaining = 2048
limit = 2048
capacity = 2097156
time = 13:53:36.465
remaining = 3072
limit = 3072
capacity = 2097156
time = 13:53:41.465
remaining = 4096
limit = 4096
capacity = 2097156
time = 13:53:46.465
remaining = 5120
limit = 5120
capacity = 2097156
> CumulativeProtocolDecoder doDecode performance problem
> ------------------------------------------------------
>
> Key: DIRMINA-663
> URL: https://issues.apache.org/jira/browse/DIRMINA-663
> Project: MINA
> Issue Type: Bug
> Components: Filter
> Affects Versions: 2.0.0-RC1
> Environment: JDK 1.6.0_12 32-bit, Windows Vista 64-bit, MINA
> 2.0.0-RC1 (up to current date trunk).
> Reporter: Serge Baranov
> Priority: Critical
>
> To reproduce get the mina_test_2.0.zip from DIRMINA-609.
> It seems to be working even worse with the current trunk version, it takes ~5
> seconds between messages and then times out after the first message, if wait
> is increased to 10 seconds, it times out after the second message:
> time = 03:49:36.320
> remaining = 1024
> limit = 1024
> capacity = 2048
> time = 03:49:41.619
> remaining = 2048
> limit = 2048
> capacity = 2097156
> java.lang.AssertionError: No message received
> The issue differs from DIRMINA-609 as it affects not only large messages, but
> any message that doesn't fit into buffer (when doDecode returns false) and
> also all the subsequent messages (when doDecode returns true).
> It's a serious issue making CumulativeProtocolDecoder completely useless.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
