OSB 11g - "Aggregation Server Not Available. Failed to get remote aggregator" Over Load-Balanced T3s Protocol
Last updated on NOVEMBER 03, 2016
Applies to:Oracle Service Bus - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 11g]
Information in this document applies to any platform.
***Checked for relevance on 03-March-2014***
In a load balanced OSB cluster, the 2nd node fails to connect to the Aggregator.
The servers in the cluster are using certificates which match the load balancer names, but the "ALSB Statistics manager" is attempting to connect over t3s directly to the first node.
The OSB cluster has the "Http Frontend Host" value set to the load balancer's name.
You may see an error similar to this one in the log files:
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://aggregator-hostname:8110: Destination unreachable; nested exception is:
javax.net.ssl.SSLKeyException: [Security:090504]Certificate chain received from "aggregator-hostname" - 192.168.0.2 failed hostname verification check. Certificate contained "loadbalancer-hostname" but check expected "aggregator-hostname"; No available router to destination]
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms