On starting JBoss, errors like javax.naming.NameNotFoundException: comp not bound are thrown

Explanation: In general, this is a result of an earlier error, where JBoss was unable to start the Naming Service on the configured port.

Fix: There are several potential causes of this issue.

• The port in question is being used by some other application. If the server had previously started successfully, it may be that a newly installed application or service is using that port and is causing a conflict. If this is the case, a new port-settings value will have to be set up for JBoss, including the manual modification of the 8080 port setting due to the known JBoss configuration error. See the SourceIQ Installation and Deployment Guide for details on changing these settings.
• JBoss is currently running on the active session or some other session that's running on the same server. The simplest means to diagnose this is to try to bring up the SourceIQ login page. If it comes up correctly, another instance of JBoss is running on that server. If that's the case, the version of JBoss that encountered the issue should be stopped. A restart the other JBoss instance is probably also in order, just in case the start of the second instance messed up the first instance.
• Sometimes, if the JBoss instance was shut down in some inappropriate fashion which didn't restart the entire server, it doesn't correctly release the ports to which it was bound. If this is the case, a restart the OS is required, followed by a restart of JBoss.

If none of those are the problem or the amelioration steps don't work, a more detailed diagnostics of the situation is required. Please contact SourceIQ Technical Support for assistance.