SAF AGENT MESSAGES ARE LOST AFTER SERVER RESTART (Doc ID 3003919.1)

Last updated on FEBRUARY 12, 2024

Applies to:

Symptoms

Encountered a connectivity error with the OSB servers, from this they generated errors with the SAF agents, no longer being able to communicate with the SOA servers, they stopped forwarding messages and only stored them.
When the connection was restored, the SAF agents did not automatically resume the forwarding of the messages continuing to store them, until the server was restarted which then allowed the SAF to resume the correct routing of the messages.

For clarity, the test case with which the issue was systematically reproduced is the following:

Domain A
OSB Mediation-> write on a SAF Queue (imported destination) -> SAF Agent -> write on remote queue (on Domain B)

Domain B
Remote Queue

No consumer (e.g. MDB) is connected to the remote queue of domain B

The persistence stores involved in the test are of the JDBC type

The tests performed are the following:

1) TEST OK
Pause the SAF forward, then load 200 messages onto the SAF queue
After loading the messages the SAF forward was enabled

Messages are placed correctly by the SAF Agent on the remote queue

Before running another test, all messages were manually deleted on the Remote queue.

1) TEST KO
Pause the SAF forward, then load 200 messages onto the SAF queue

After loading the messages, restart the managed WLS where the SAF Agent runs

After the managed has started correctly, no messages are observed on the remote queue
and on the SAF Queue the message counter becomes zero, so the messages saved on the SAF (imported destination) queue have disappeared.

Cause

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