RIHA for LGF Messages Published from LogFire Stuck in RIB-LGF with Service Unavailable (Doc ID 2953235.1)

Last updated on JUNE 07, 2023

Applies to:

Goal

Frequently issue is seen with messages published from LogFire are stuck in RIB-LGF with Service Unavailable. Below error message was seen:

javax.ejb.EJBException: Error while calling Injector Service.: The server sent HTTP status code 503: Service Unavailable
at com.retek.rib.j2ee.RIBMessageSubscriberEjb$MessageHandler.handleMessage(RIBMessageSubscriberEjb.java:461)
at com.retek.rib.collab.HospitalController.performHandlerCall(HospitalController.java:389)
at com.retek.rib.collab.HospitalController.doMessage(HospitalController.java:292)
at com.retek.rib.collab.HospitalController.doMessage(HospitalController.java:194)
at com.retek.rib.j2ee.RIBMessageSubscriberEjb.onMessage(RIBMessageSubscriberEjb.java:268)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:438)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:361)
at weblogic.ejb.container.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:276)
at weblogic.ejb.container.internal.JMSMessagePoller.pollContinuously(JMSMessagePoller.java:343)
at weblogic.ejb.container.internal.JMSMessagePoller.pollForParent(JMSMessagePoller.java:526)
at weblogic.ejb.container.internal.JMSMessagePoller.run(JMSMessagePoller.java:541)
at java.lang.Thread.run(Thread.java:750)
Caused by: com.retek.rib.binding.exception.RIBIntegrationException: Error while calling Injector Service.: The server sent HTTP status code 503: Service Unavailable - Nested exception: - com.sun.xml.ws.client.ClientTransportException: The server sent HTTP status code 503: Service Unavailable
at com.retek.rib.binding.subscriber.impl.WebServiceSubscriberCoreServiceImpl.subscribe(WebServiceSubscriberCoreServiceImpl.java:75)
at com.retek.rib.j2ee.RIBMessageSubscriberEjb$MessageHandler.handleMessage(RIBMessageSubscriberEjb.java:443)
... 11 more

Also another error was seen with stuck messages as below:

javax.ejb.EJBException: Error while calling Injector Service.: The server sent HTTP status code 502: Bad Gateway
at com.retek.rib.j2ee.RIBMessageSubscriberEjb$MessageHandler.handleMessage(RIBMessageSubscriberEjb.java:461)
at com.retek.rib.collab.HospitalController.performHandlerCall(HospitalController.java:389)
at com.retek.rib.collab.HospitalController.doMessage(HospitalController.java:292)
at com.retek.rib.collab.HospitalController.doMessage(HospitalController.java:194)
at com.retek.rib.j2ee.RIBMessageSubscriberEjb.onMessage(RIBMessageSubscriberEjb.java:268)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:438)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:361)
at weblogic.ejb.container.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:276)
at weblogic.ejb.container.internal.JMSMessagePoller.pollContinuously(JMSMessagePoller.java:343)
at weblogic.ejb.container.internal.JMSMessagePoller.pollForParent(JMSMessagePoller.java:526)
at weblogic.ejb.container.internal.JMSMessagePoller.run(JMSMessagePoller.java:541)
at java.lang.Thread.run(Thread.java:750)
Caused by: com.retek.rib.binding.exception.RIBIntegrationException: Error while calling Injector Service.: The server sent HTTP status code 502: Bad Gateway - Nested exception: - com.sun.xml.ws.client.ClientTransportException: The server sent HTTP status code 502: Bad Gateway
at com.retek.rib.binding.subscriber.impl.WebServiceSubscriberCoreServiceImpl.subscribe(WebServiceSubscriberCoreServiceImpl.java:75)
at com.retek.rib.j2ee.RIBMessageSubscriberEjb$MessageHandler.handleMessage(RIBMessageSubscriberEjb.java:443)
... 11 more
 

Solution

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