Last updated on AUGUST 03, 2016
Applies to:Oracle SOA Platform - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Accessing SOA Composer from one node of a two node cluster is very slow compared to accessing from the other.
The rules in SOA Composer load fine and respond soon to save after edits etc when accessed from Node 1 in the 2 node cluster.
But when the same thing is attempted on SOA Composer hosted by Node 2, the load times are at least 3 times longer and the landing page is sometimes unusable where the rules cannot be expanded etc. The following replication errors are seen in the logs of Node 1.
####<May 3, 2012 9:33:36 PM GMT+00:00> <Warning> <RMI> <machine1> <soa_server1> <[ACTIVE] ExecuteThread: '2' for
queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336080816247> <BEA-080003> <RuntimeException thrown by rmi server:
weblogic.cluster.replication.ApplicationUnavailableException: WebApp with contextPath: /soa/composer is not replicatable in the secondary server.
weblogic.cluster.replication.ApplicationUnavailableException: WebApp with contextPath: /soa/composer is not replicatable in the secondary server
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms