BIGIP Port Translation with SAF (Doc ID 2217665.1)

Last updated on AUGUST 03, 2023

Applies to:

Symptoms

BIGIP Port Translation with SAF

Will the F5 BIGIP port translation work with SAF ?
Domain1: SAF configured with 2 managed server with different ports.
Domain2: JMS Message queue to receive the messages from SAF via BIGIP
 
Error received:

###  <[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > t3://<BigIP_host.domain>:<BigIP_Port>: Destination <Ip_Address>, <BigIP_Port> unreachable.; nested exception is:
java.net.SocketTimeoutException: Read time out after 60000 millis; No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination. [Root exception is java.net.ConnectException: t3://<BigIP_host.domain>:<BigIP_Port>: Destination <Ip_Address>, <BigIP_Port> unreachable.; nested exception is:
java.net.SocketTimeoutException: Read time out after 60000 millis; No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination.]

The issue can be reproduced at will with the following steps:

1. Configure SAF on one domain (source) with 2 managed servers
2. Configure a JMS message queue on another domain (destination) with a managed server
3. Configure BIGIP(load balancer) before destination.
4. Configure SAF remote context URL with BIGIP address and port.
5. Run test client and see if the messages are being delivered to destination.

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.