Conquering LDAP Redeploy Errors By Using Them Up and Wearing 'Em Out
By docteger on Apr 07, 2008
The lab machines reserved for us writers are none-too-current: hard drive size and RAM are not the correct specifications for deploying Glassfish, OpenSSO, and other agents/web services. Because of this I always have issues re-deploying a new OpenSSO WAR file successfully...until today (actually Friday but I'm writing this today). When I undeploy the OpenSSO WAR, it leaves some processes running on Glassfish which don't allow for a new WAR to be deployed. (I've seen mainly LDAP and OpenDS errors.) I figured out that I can redeploy a new OpenSSO WAR if I have a new install of Glassfish - which puts the step where I have to jumpstart and wait for a new OS to be installed (and therefore wait for the lab guy to restart the DNS) in the trash. So follow this procedure to find the processes, kill them, uninstall Glassfish, and get it back up.
jpsat the command line.
This is the command for discovering running Java processes.
- Kill any
PELaunchprocesses you see using the
kill -9 process-numbercommand on the command line.
- Remove the
- Start all over again using this blog entry.