My Oracle Support Banner

Batch Usage Transaction Errors and Threads Fail when Communicating with JMS Queues Over T3s Connection (Doc ID 2760738.1)

Last updated on MARCH 18, 2021

Applies to:

Oracle Utilities Customer Care and Billing Integration to Oracle Utilities Meter Data Management - Version 12.1.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Batch Usage Transactions get errors and threads fail when communicating with JMS queues over t3s connection

When executing MDM Batch Job D2-UTCD and similar Usage Transaction Calculations, each time a thread encounters the following error, it aborts. Eventually, every thread encounters the error.

 

ERROR
-----------------------
Complete com.splwg.base.messaging.impl.jms.RealtimeJMSSenderHelper committing <MSG_SNDR>
weblogic.jms.common.JMSException: weblogic.messaging.dispatcher.DispatcherException: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException

Changes

This occurs when the Message Sender uses a JMS Connection with a JNDI Server that maps to a t3s URL.

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.