Often we come across situations in which we have to use non-default ports either for multiple servers; or for multiple instance of the same server.
(Apart from the option to fiddle with the configuration files,) JBoss provides a smart way to run it on non-default ports. Apparently, JBoss comes with predefined port sets that can be used using the property jboss.service.binding.set.
Here’s how you do it:
$ ./run.sh -Djboss.service.binding.set=ports-01
This would add an offset of 100 to the default ports. So this JBoss would be accessible at port 8180. Similary, ports-02 would make it available on 8280 and so on..
There’s also an option of passing ports-default parameter that would make it available on — you guessed it — 8080.
If your ApacheDS is misbehaving — doesn’t start or stop — it most probably has to do with its .pid file that’s lying around because of an unclean shutdown. In which case you just need to delete it manually, and things will get back to normal.
In the CentOS 6 machine that I work on, the file is created in /var/lib/apacheds-2.0.0-M7/default/run by the name of apacheds-default.pid. On Ubuntu machines, this could be in /var/run.
Once the file is removed, simply run the /etc/init.d/apacheds start command to get it going!
While in Chrome, just F12 your way to awesomeness!