• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Strange behaviour during deployment

 
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?

 
Bartender
Posts: 6663
5
MyEclipse IDE Firefox Browser Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The exception complains that one of the changes targeted server 2 and it was unavailable during the operation. The problem may be entirely valid.

So server 2 is random in this case ? It could be any server ?
 
Andreas Barrud
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

just to let you know:

Our problem was caused by a configuration problem.
We hadn't configured the IP listen address (left it blank) for any WLS instance.
If left blank the WLS listens to all IPs the Host-machine listens to.
The help text in the WLS console states:

Do not leave the listen address undefined on a Windows computer that uses multiple IP address (a multihomed computer). On such a computer, the server will bind to all available IP addresses.



Well, this also applys to Solaris.
In our case that were: localhost and three different IPs.

Somehow the internal communication between admin and managed servers gets messed up if you don't do this.
Oracle support took two months to give us the right advice .

Maybe that helps someone else too.
 
I will suppress my every urge. But not this shameless plug:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic