Hi!
we are using WLS 10.3 as our application server.
We have set up a domain consisting of 1 admin server and about 18 managed servers.
On our new Solaris M5000 machine (2,5GHz CPUs, 24 Cores inside local zone) we are facing the following strange behaviour:
We have an application that is targeted to a managed server named: (just for example, can be any name) server17 (and ONLY to that server!).
Using WLST to deploy this application to
server17 there
sometimes(!) is the following exception:
Traceback (innermost last): File "<
string>", line 9, in ? File "<iostream>", line 364, in activate WLSTException: Error occured while performing activate : Error while Activating changes.[Deployer:149145]Unable to contact '[Deployer:149145]Unable to contact '
server2'. Deployment is deferred until '
server2' becomes available.; nested exception is: java.rmi.UnknownHostException: Could not discover administration URL for server 'server2''. Deployment is deferred until '[Deployer:149145]Unable to contact '
server2'. Deployment is deferred until 'server2' becomes available.; nested exception is: java.rmi.UnknownHostException: Could not discover administration URL for server '
server2'' becomes available. Use dumpStack() to view the full stacktrace
The managed server
server2 wasn't assigned as a target anywhere. This (existing but in this case wrong!) servername is (randomly?) changing to one of the configured server names in the domain.
Did anyone ever observed such a situation?