Thursday, November 1, 2012

Restart that NodeManager

I had a domain with admin listening on port 7013. NodeManager was running.
I have deleted the $DOMAIN_HOME, and recreated the domain from scratch, with the Admin listening at port 7003.
Much to my despair, restarting the ManagedServers through the NodeManager would still bring up instances referring to the admin running at 7013:

"ps -ef" was showing:

 Desperate greps everywhere brought no evidence of a 7013 still hiding somewhere.

At last, restarting the NodeManager fixed the issue. Evidently, NodeManager caches the information relative to a given domain, and if you change relevant stuff in the domain you better restart also the NodeManager.
Sad, but true.

No comments: