The ServletEngine queueing or port is incorrect in queues.properties

Technote (FAQ)
Problem
The ServletEngine queueing or port is incorrect in queues.properties
Solution
After deploying an application which creates a new AppServer, creating models/clones could make one of the clones' ServletEngine not find a port to connect to. The msg on the browser is the generic "document contains no data". The ose native log indicates the correct error - ibmoselink.cloneX.port is missing.

Debugging/Solution:

Open the queues.properties file and ascertain that there is a port with -1 entry.

From the adminconsole, open the affected application server's ServletEngine and change the -1 entry for the port to a valid port number (for example, 8993). Ensure that the port number entered is not already in use by another clone by checking the entries in queues.properties file.

Restart the adminserver.












    Document Information

    Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Servlet Engine/Web Container
    Operating system(s): Solaris
    Software version: 3.5
    Software edition: Advanced
    Reference #: 1044437
    IBM Group: Software Group
    Modified date: 2001-10-25