[
https://issues.apache.org/jira/browse/QPID-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228615#comment-15228615
]
Tobias Nöll commented on QPID-2410:
-----------------------------------
Meanwhile I got it working:
Solution was:
1.) No need to modify the client c++ api
2.) Don't set max-frame-size in the client (i.e. in connection options)
3.) Modify the java broker to have a max-frame-size of 0x3FFF instead of 0XFFFF
in org/apache/qpid/server/protocol/v0_10/ServerConnectionDelegate.java
Strangely, if I set a max-frame-size:16384 in the connection parameters of the
client, it hangs if sending larger messages than this. If I remove
max-frame-size parameter from the connection option everything works fine.
I don't understand this behaviour, but at least it is working. From my point of
view for a solution it should have been enough for the clients to connect with
max-frame-size accordingly set to 16K. Strangely, it's not. But I'll work for
now with this workaround until a proper fix is available...
> 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
