My Oracle Support Banner

Routing message over 64KB failed with the "encoded string too long: 65579 bytes" error (Doc ID 420502.1)

Last updated on JUNE 18, 2018

Applies to:

Oracle ESB - Version 10.1.3.1 and later
Information in this document applies to any platform.
***Checked for relevance on 24-Jul-2012***

Symptoms

On 10.1.3.1 in Production:
When attempting to route message over 64KB with characters, get the "encoded string too long: 65579 bytes" exception.

ERROR
Caused by: java.io.UTFDataFormatException: encoded string too long: 65579 bytes
at java.io.DataOutputStream.writeUTF(DataOutputStream.java:347)
at java.io.DataOutputStream.writeUTF(DataOutputStream.java:306)
at com.evermind.server.jms.JMSUtils.packWrite(JMSUtils.java:401)
at com.evermind.server.jms.EvermindTextMessage.writeBodyTo(EvermindTextMessage.java:82)
at com.evermind.server.jms.EvermindMessage.writeTo(EvermindMessage.java:433)
at com.evermind.server.jms.EvermindMessage.toBytes(EvermindMessage.java:394)
at com.evermind.server.jms.ServerStore.storeMessage(ServerStore.java:815)

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!


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