Offhand, your options at this point are: - Fix the bug (most long-term benefit) - Write an alternative SSL handling mechanism (more difficult) - Split them and reassemble at the other end. I don't know anything about your system so don't know how hard this would be. I've seen a system that does something similar. It's more complexity, probably more than fixing the problem.
I recommend fixing it... it's the most direct, and beneficial option. In the long run it's going to help you much more. -Steve > -----Original Message----- > From: rat...@web.de [mailto:rat...@web.de] > Sent: Thursday, March 31, 2016 4:49 PM > To: users@qpid.apache.org > Subject: RE: SSL maximum message size? > > Hm, this is really getting me into trouble because I need to send encrypted > messages of larger sizes than 16k. Is there really no other option, e.g. to > link > qpid with alternative SSL implementations like OpenSSL or NSS? Could I split > up messages into smaller parts and send somehow guarantee that they are > received by the same server and put them together manually? > Any hint would help me. > Thx! > > > > -- > View this message in context: http://qpid.2158936.n2.nabble.com/SSL- > maximum-message-size-tp7641114p7641154.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 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
