My Oracle Support Banner

Item Messages Not Processed from ITEM_MFQUEUE Table; Item Publisher RIB-RMS Adapter Times Out and Goes Offline (Doc ID 1449580.1)

Last updated on MARCH 19, 2018

Applies to:

Oracle Retail Merchandising System - Version 13.2.3.3 and later
Oracle Retail Integration Bus - Version 13.2.3 and later
Information in this document applies to any platform.
Checked for relevance on March 10th, 2017

Symptoms

 
Item messages are not being processed out from ITEM_MFQUEUE successfully.  Even after restarting the Item Publisher adapter, it still goes down without successfully processing any messages.  The problem seems to occur when there is high volume within ITEM_MFQUEUE table.

Steps to Reproduce:

Generate an event in Retail Merchandising System (RMS) that creates a record on the ITEM_MFQUEUE table and have the RIB-RMS adapter for Item Publisher online.

 

Some errors shown are:

2012-03-12 13:02:22,334 [Timer-24] DEBUG com.retek.rib.collab.OracleObjectDescriptor - OracleObjectDescriptor.setOracleFieldMap: structName is RMS13PROD.RIB_ItemHdrDesc_REC
2012-03-12 13:02:22,335 [Timer-24] ERROR com.retek.rib.collab.general.OracleObjectPublisherComponentImpl - Error dumping STRUCT
java.sql.SQLRecoverableException: Closed Connection

2012-03-12 13:02:22,335 [Timer-24] ERROR com.retek.rib.domain.oo.translate.OracleObjectDynamicXMLBuilder - Error processing message type of ItemHdrMod returned

2012-03-12 13:02:22,338 [Timer-24] DEBUG com.retek.rib.log.timings.TimingsLoggerFactory$WrapperTimingsLogger - Reusing old logger(org.apache.log4j.Logger@42c178dc) with name(rib.pub.timings.Items_pub_1) in thread(Timer-24).
2012-03-12 13:02:22,338 [Timer-24] ERROR com.retek.rib.app.getnext.impl.GetNextPublisherEjb - Rolling back the transaction.
com.retek.rib.binding.exception.PublishException: Unable to publish message to JMS.

Caused by: javax.ejb.EJBException: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 602 seconds
BEA1-007F955E43369A03D246
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1733)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1578)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1900)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1488)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 602 seconds
BEA1-007F955E43369A03D246

 

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.