Have a classic webtier setup, only enabled with “Selfservice-portal” webtiers are operational and working. The issue is that the initial login on the portal takes 20 seconds.
This is the case on both web-tiers – in the logs I think we can see why :
--------LOGS SNIP START-------
@@@2023-09-28 09:18:19,676, [[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'], (EJBRemoteTarget.java:302), trace.com.rsa.command.EJBRemoteTargetBase, ERROR, Webtier-Server.domain.net,,,,Attempting downgraded connection protocol to EJB/2.1.
@@@2023-09-28 09:18:25,448, [[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'], (EJBRemoteTarget.java:316), trace.com.rsa.command.EJBRemoteTargetBase, ERROR, Webtier-Server.domain.net,,,,Unable to connect to downgraded EJB/2.1 command server.Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
t3s://Webtier-Server.domain.net:7002: Destination 1.2.3.4, 7002 unreachable.; nested exception is:
java.net.ConnectException: Connection refused: no further information; No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination.
@@@2023-09-28 09:18:31,158, [[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'], (EJBRemoteTarget.java:302), trace.com.rsa.command.EJBRemoteTargetBase, ERROR, Webtier-Server.domain.net,,,,Attempting downgraded connection protocol to EJB/2.1.
@@@2023-09-28 09:18:36,248, [[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'], (EJBRemoteTarget.java:316), trace.com.rsa.command.EJBRemoteTargetBase, ERROR, Webtier-Server.domain.net,,,,Unable to connect to downgraded EJB/2.1 command server.Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
t3s://Webtier-Server.domain.net:7002: Destination 1.2.3.4, 7002 unreachable.; nested exception is:
java.net.ConnectException: Connection refused: no further information; No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination.
@@@2023-09-28 09:18:36,248, [[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'], (EJBRemoteTarget.java:327), trace.com.rsa.command.EJBRemoteTargetBase, ERROR, Webtier-Server.domain.net,,,,Unable to connect to command server for command execution.Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
t3s://Webtier-Server.domain.net:7002: Destination 1.2.3.4, 7002 unreachable.; nested exception is:
java.net.ConnectException: Connection refused: no further information; No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination.
--------LOGS SNIP END-------
But why would the webtier server attempt to connect on port 7002 (to itself), a port its not listning on?
