OGG Capture From JMS Queue Fails When Data is in Multibyte Characterset (e.g.Hebrew)

(Doc ID 1343295.1)

Last updated on JANUARY 31, 2017

Applies to:

Oracle GoldenGate - Version and later
Information in this document applies to any platform.


When using JMS adapter with double-byte or multi-byte data (e.g. Hebrew, Chinese, ...) character sets,
the JMS capture will exit with errors like following:

JMSPROVIDER(jmsprovider.c:546) [DEBUG]: Get Message
JMSPROVIDER(jmsprovider.c:548) [DEBUG]: Push Frame
JMSPROVIDER(jmsprovider.c:552) [DEBUG]: Call get Message method
JMSPROVIDER(jmsprovider.c:559) [DEBUG]: Store message in global
JMSPROVIDER(jmsprovider.c:405) [DEBUG]: Get jstring from Text Msg
JMSPROVIDER(jmsprovider.c:409) [DEBUG]: Get text from jstring
JMSPROVIDER(jmsprovider.c:153) [DEBUG]: Got length of jstring (len=65, to_alloc=66, status=0)
JMSPROVIDER(jmsprovider.c:170) [ERROR]: JNI StringIndexOutOfBoundsException while creating native string from Java (length=65, error=0)
JMSPROVIDER(jmsprovider.c:178) [ERROR]: JNI Error creating native string from Java (error=-1)


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 hundreds of Community platforms