>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 without modifying the broker. However, this is not working (the client hangs if sending messages larger than 16K).
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. However, it rather seems to be a problem of the c++ api from my point of view. -- View this message in context: http://qpid.2158936.n2.nabble.com/Max-Frame-Size-for-Java-Broker-tp7641393p7641504.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
