Ok - that's curious.  That would suggest a defect either in the
'legacy' AMQP 0-x Qpid JMS client or CPP Broker.   Would you be able
to produce a minimal JMS test case that demonstrates the problem and
raise a JIRA?  When you say corrupted - how exactly?

https://issues.apache.org/jira/browse/QPID

Thanks, Keith



On 20 September 2016 at 11:39, Jean-Marc Pedersen <j...@euman.com> wrote:
> Hi,
>
> I am the one doing the client end using qpid java library. I can confirm
> that this problem doesn't seem to exists when using the AMQP 1.0 version
> 0.11.0 library.
>
>
>
> --
> View this message in context: 
> http://qpid.2158936.n2.nabble.com/QPID-C-Java-JMS-client-Data-gets-corrupted-when-sent-to-the-server-over-SSL-tp7650810p7650932.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

Reply via email to