Getting Started with WebSphere Application Server
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
198 <strong>Getting</strong> <strong>Started</strong> <strong>with</strong> <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> Community Edition<br />
Community Edition supported environments are documented at:<br />
http://www.ibm.com/support/docview.wss?rs=2359&uid=swg27006834<br />
11.3.2 Port already in use<br />
This problem is often accompanied <strong>with</strong> a java.net.BindException, when a user<br />
starts the Community Edition server. It means the port number Community Edition wants to<br />
use is already used by another application.<br />
First, make sure that the server is not already running. If the server is already running, the<br />
second attempt to start the server will fail because the server's ports are already being<br />
used.<br />
Next, examine the message text associated <strong>with</strong> the exception to determine the port<br />
number that was already in use. To find details about these messages you can review the<br />
server log located at /var/log/server.log<br />
Then determine which application has caused the conflict and determine how to resolve<br />
the conflict. Consider simply stopping the application that caused the conflict or<br />
reconfiguring the Community Edition server to use a different port.<br />
To change the port number for the Community Edition server instance, open the configsubstitutions.properties<br />
file under /var/config/ and change<br />
the value of portOffset. This was discussed in more detail in Chapter 9.<br />
11.3.3 Could not communicate <strong>with</strong> the server<br />
If you get an error message indicating your application cannot communicate <strong>with</strong> the<br />
Community Edition server, most likely, the Community Edition server is not running. If this<br />
is the case, start the server and try again.<br />
Another cause for this problem may be that the Community Edition server is not listening<br />
on the port number used by the application. Normally remote method invocation (RMI) is<br />
used, but maybe the RMI port configured at the application does not match the one<br />
configured at the Community Edition server. By default, the server is configured to listen on<br />
port number 1099 on all network interfaces for RMI requests.<br />
To resolve this problem set up RMI to use the local loopback interface (127.0.0.1) for<br />
development or test machines by adding the following to your JAVA_OPTS environment<br />
variable as shown below:<br />
-Djava.rmi.server.hostname=127.0.0.1<br />
Also, make sure the server and the utility are using matching port numbers. To find the port<br />
number used by the server, examine /var/config/config.xml and<br />
find the value of the port attribute in the gbean tag where name="RMIRegistry". Make<br />
sure the same value is passed to the application.
Change language