My Oracle Support Banner

Mgw Exception Handler For INcompatible Payload Type - JMS-108 (Doc ID 2140427.1)

Last updated on MARCH 20, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Using Oracle Messaging Gateway (OMG) configured to interact with an upstream IBM MQ Series.

The Advanced Queue into which the MQ messages are forwarded has a defined payload type of JMS Message.

The MQSeries side queue does not validate whether a message is properly enqueued with the same payload type as defined at the Oracle side. So if a message is enqueued as a "Text" instead of JMS format for example, once the message hits the Oracle incoming queue, the MGW will abort with expected error:
 

oracle.jms.AQjmsException: JMS-108: Messages of type TextMessage not allowed with Destinations containing payload of type SYS.AQ$_JMS_MAP_MESSAGE

 

MGW will not be able to restart until the offended message is deleted from the remote MQ Series queue. 

 

Changes

 

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
Changes
Cause
Solution
References


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