Why Are TAFR JMS Hospital Retry And TAFR Sub Hospital Retry Shutting Down? (Doc ID 1339893.1)

Last updated on OCTOBER 06, 2016

Applies to:

Oracle Retail Integration Bus - Version 13.0.2 and later
Information in this document applies to any platform.
Checked for relevance 06-Feb-2013
checked for relevance on Dec 2, 2014
Checked for relevance on 06-October-2016

Goal

Why TAFR JMS Hospital Retry and TAFR SUB Hospital Retry shutdown with the below exceptions?

2011-07-19 15:40:49,380 [Timer-11] ERROR com.retek.rib.j2ee.ErrorHospitalRetryEjb - Exception thrown during retry.
com.retek.platform.persistence.PersistenceException: Unable to execute delete query(select he from HospitalEntryImpl he where he.jmsQueueId = ?1 and he.deletePendingWorkAround = ?2 and he.inQueueWorkAround = ?3)
exception id: 1311061249358
..
..
Caused by:
javax.ejb.EJBException:
Exception Description: Error while obtaining information about the database. Please look at the nested exception for more details.; nested exception is: Exception [TOPLINK-4019] (Oracle TopLink Essentials - 2.0 (Build b41-beta2 (03/30/2007))): oracle.toplink.essentials.exceptions.DatabaseException
Exception Description: Error while obtaining information about the database. Please look at the nested exception for more details.
..
.
Caused by:
javax.resource.ResourceException: RollbackException: Resource was in use during abnormal shutdown of server and during subsequent recovery processing was either unobtainable or failed to have recovery permissions. Consult logs if this issue continues to occur after the next recovery processing interval completes




Solution

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