Alex's point is that the Java Broker change shouldn't really be necessary as if the client wants 16K, the fact that the Broker offers up to 64K shouldn't matter - the client should just use 16K, and the broker will use 16K... however maybe there is some issue in the client that makes this necessary.
-- Rob On 6 April 2016 at 11:03, rat...@web.de <rat...@web.de> wrote: > Hi, > thanks for your feedback. This already helps me a lot. Appearantly I was > doing the changes at the wrong positions (ServerDelegate.java instead of > ServerConnectionDelegate.java of the 0-10 protocol). > I'll redo my experminents. If it's not working I'll generate the > corresponding client / broker logs as suggested by you. > Regards > Tobias > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/Max-Frame-Size-for-Java-Broker-tp7641393p7641460.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 > >
