When attempting to start the JBOSS Application Server that is deployed with the SAS^® Web applications, the following error might occur in the log:

DEBUG [org.jboss.naming.NamingService] Starting failed jboss:service=Naming
java.rmi.server.ExportException:

Port already in use: 1098; nested exception is:
java.net.BindException: Address already in use: JVM_Bind

This error occurs because port 1098 is already being used by another process.

JBoss reserves a group of static ports for various J2EE services, almost all of which are configurable. By default, 1098 is reserved for use by JNDI. If this port is not available when JBoss starts, JBoss will not initialize correctly. The same problem will occur for all other ports, including those such as 8080, 1099, and others.

For a list of default ports and the service with which they are associated, you should consult UsingJBossBehindAFirewall.

To correct this problem, reserve the port number (such as 1098) on the Windows system. You should consult the instructions in How to reserve a range of ephemeral ports on a computer that is running Windows Server 2003 or Windows 2000 Server.

For example, set a reserved range to include ports 1098-1150 in order to resolve the issue with any ports within that range.

Note: Although restarting the system might appear to solve the problem, such action is only a temporary fix and should not be used as a long term solution.

To determine which process is using the port that is in conflict, issue the netstat -ab command at a CMD window.

If JBOSS does not start correctly due to port conflicts, the SAS Web applications might not function properly. For example, there is an instance where an indicator could not be created using the SAS^® BI Dashboard Web application. The SAS BI Dashboard log contained the following message:

WARN                        
com.sas.svcs.cluster.httpinvoker.AutoDiscoveredHttpService - Have 
received 20 failures while trying to access an auto-discoverable 
service to satisfy request for 
'com.sas.svcs.alerts.client.AlertsServiceInterface'. Please ensure 
that the application and/or process surfacing this interface is still 
in the process of starting.         

Also, in this instance, the Comment Service Web Application failed to invoke. Many other problems might occur when using the SAS Web applications if the JBOSS Application Server does not initiate properly.

Operating System and Release Information