File Adapter Problem (Doc ID 2331492.1)

Last updated on AUGUST 06, 2023

Applies to:

Symptoms

We have 1 cluster with 4 servers. These servers are running in 2 physical servers.
when i shutdown one of physical server, the file adapter is not work as well.

I have checked the log file and found out the error below.

weblogic.jms.extensions.JMSOrderException: hashed member of jmsResources!dist_wlsb.internal.transport.task.queue.file_auto is jmsResources!wlsb.internal.transport.task.queue.file_auto_2 which is not available
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncTran(DispatcherAdapter.java:53)
at weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1289)
at weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:796)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:541)
Truncated. see log file for complete stacktrace
Caused By: weblogic.jms.extensions.JMSOrderException: hashed member of jmsResources!dist_wlsb.internal.transport.task.queue.file_auto is jmsResources!wlsb.internal.transport.task.queue.file_auto_2 which is not available
at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:87)
at weblogic.jms.dispatcher.Request.getResult(Request.java:52)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:1124)
at weblogic.messaging.dispatcher.DispatcherImpl.syncRequest(DispatcherImpl.java:185)
at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSyncTran(DispatcherImpl.java:238)

Changes

Cause

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