By design, while getting the session object in the code for a specific operation we extract the super class of jmsBytesMessageImpl class, which is jmsMessageImpl class through reflection calls.
In this specific use case, jmsBytesMessageImpl object was from jmsMessageImpl class itself
A code fix has been made to call the same class instead of calling the superclass of jmsBytesMessageImpl.
No workaround available.
This defect DE350291 has been fixed in: