[
https://issues.apache.org/jira/browse/QPID-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222921#comment-15222921
]
Rob Godfrey commented on QPID-2410:
-----------------------------------
Hi Tobias - changing the FRAME_MAX in ServerDelegate will certainly ensure that
no frame over 16K, or whatever limit you need, will be allowed by the Java
Broker. If you are only using the broker with the (broken) C++ client and SSL
then that should be fine for you. Obviously other clients are capable of
coping with properly sized frames and this may cause a bit of a performance
issue for them. If the client provides enough information in its connection
properties to identify it as the C++ client running on Windows, then it would
theoretically be possible to conditionally return either 16K (for the broken
client) or 64K for everything else.
> perftest hang in SSL on Windows with large buffers
> --------------------------------------------------
>
> Key: QPID-2410
> URL: https://issues.apache.org/jira/browse/QPID-2410
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Affects Versions: 0.7
> Environment: Windows client, Linux broker
> Reporter: Cliff Jansen
> Assignee: Steve Huston
> Attachments: ssl_windows_patch.patch
>
>
> The following command:
> perftest --count 1 --size 102400 -P ssl --port 5671 --broker linuxhost
> --username testuser --password secret --mechanism PLAIN
> hangs on a Windows client. Reducing the message body size to 1024 bytes
> makes the hang go away, as does turning off SSL.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
