My Oracle Support Banner

Import/Export Of JMS Byte-message Via WLS Console Corrupts The Message causing a java.lang.AssertionError (Doc ID 1382132.1)

Last updated on DECEMBER 11, 2017

Applies to:

Oracle Weblogic Server - Version 10.3.4 to 10.3.5
Information in this document applies to any platform.

Symptoms

While exporting messages from a WLS Queue, there are null values being added to the exported message. Because of this, the following AssertionError in ChunkedOutputStream is seen when the BytesMessage.writeFloat is called:

java.lang.AssertionError
  at weblogic.utils.io.ChunkedOutputStream.checkWritable(ChunkedOutputStream.java:86)
  at weblogic.utils.io.ChunkedDataOutputStream.writeInt(ChunkedDataOutputStream.java:68)
  at weblogic.utils.io.ChunkedDataOutputStream.writeFloat(ChunkedDataOutputStream.java:108)
  at weblogic.jms.common.BufferOutputStreamChunked.writeFloat(BufferOutputStreamChunked.java:136)
  at weblogic.jms.common.BytesMessageImpl.writeFloat(BytesMessageImpl.java:450)
  at wlstest.functional.jms.haleakala.durable.Bytes_StreamMessageSendModifyRecv.testMessagesAfterSending (Bytes_StreamMessageSendModifyRecv.java:285)

Also, while importing the messages to the Queue, which were exported from the same queue, there are some null values being added to the messages and the message size grows from 9 bytes to 256 bytes.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.