This error has several possible causes and workarounds for
these symptoms:
Virtual Host or Web Application Not Found: The host
alias has not been defined:
This problem occurs because you have an alias defined in a virtual host
(like default_host) and this virtual host is not associated with a Web
module, or a change was made to the virtual host and the Application
Server was not restarted. If a request is made using this alias, the above
error occurs. To resolve the problem, do one of the following things:
- Remove the virtual host because it is not associated with any Web
modules.
- Associate the virtual host with an installed Web module.
- Restart the Application Server.
Virtual Host or Web Application Not Found: The web group
virtual_host/context root has not
been defined:
This problem is known to occur for the following reasons:
- The Web module associated with the context root in the error
message is not started.
- You have the same Host Alias listed in more than one virtual host.
Example:
<VirtualHostGroup Name="default_host">
<VirtualHost Name="*:80"/>
<VirtualHost Name="*:9080"/>
</VirtualHostGroup>
<VirtualHostGroup Name="my_host">
<VirtualHost Name="spartan:80"/>
<VirtualHost Name="*:9081"/>
</VirtualHostGroup>
spartan:80 is duplicated in both virtual hosts because a request
over spartan:80 would match aliases in both virtual hosts
(*:80 and spartan:80). To resolve, remove the
*:80 alias in default_host and add more specific
aliases, such as:
wolverine:80
buckeye:80
www.wolverine.com:80
www.buckeye.com:80
NOTE:
- The existence of localhost as an alias can cause
duplicate entries.
If localhost is used as an alias entry, check the etc/hosts file
to ensure all host names (aliases) associated with the loopback address
(127.0.0.1) are part of the same virtual host grouping (for example,
default_host).
For example, if I have an entry in my hosts file that looks like this:
127.0.0.1 localhost kolinski
- Aliases need to be in the same virtual host grouping. So,
you cannot put the aliases of localhost and kolinski in
different virtual host groupings.
- The request was made directly to the internal HTTP transport of the
Application Server and the URI entered is not valid.
This message is seen only because the URI entered is not valid. If
you do not want to see these messages, do one of the following:
- Ensure that the URI entered into your browser is
valid.
- Send the requests through a Web server that has the
WebSphere plug-in installed. The plug-in routes only the proper
URI''s to the Application Server
To resolve this problem, ensure that your Web module is started, or that
you do not have the same alias listed in more than one virtual host.
Otherwise, make sure that the requesting URI is valid for your
application.
The browser shows "Page cannot be displayed".
Servlet Engine trace shows:
Virtual Host/WebGroup Not Found : The host 123.45.67.89 on port
4567 has not been defined.
This problem is known to occur because the port number in the
plugin-cfg.xml does not match the port number in the virtualhosts.xml
(V5.0 or V5.1), XML export (V4.0).
To resolve this problem, ensure that the port number is correctly added
through the administrative console,
If problem not resolved
If the information in this document does not resolve your problem,
please follow the instructions for the link that corresponds to your
WebSphere version and open a PMR with IBM support:
|