PLGN0021E : WebGroup / virtual host not defined–A list of things to check


When you have a “WebGroup / virtual host not defined” error what to do?

PLGN0021E: Servlet Request Processor Exception: Virtual Host/WebGroup Not Found : The host xxxxxxx has not been defined.

Access application from app server:
By pass the web server and access the application directly from the application server using app_server_name:port/context_root

Check any recent application install/update:
If you have recently updated or installed the application, ensure that the Web server plug-in was regenerated and propagated to the Web server. Also, ensure
that the Web server is using the new plug-in configuration file.

Verify Plug-in is working:
Attempt to access other applications running on the same application server through the Web server. If you can access another application, this will verify that the plug-in and Web server are working with the application server, but not necessarily that the plug-in configuration is correct.

Verify Virtual Host/ Host Alias etc..

  • Verify that the virtual host associated with the Web module has a host alias defined containing the host name and port matching the host name and port in the URL causing the failure.
  • Find the URL pattern for the servlet.
  • Find the context root of the Web module containing the servlet.
  • Find the virtual host where the Web module is installed.
  • Find the aliases by which the virtual host is known.

  •  

After finding above four, check the following:

  • Combine the virtual host alias, context root and URL pattern to form the correct URL request for the servlet.
  • Compare the correct URL for the servlet with the URL reported in the problem.
  • If they are the same, verify the resource file exists in the deployed application.
  • If not, correct the application calling the resource.

If you don’t know how to check url pattern/context root/virtual host/host alias….follow these instructions

Finding URL pattern

1. In the administrative console, select Applications -> Enterprise Applications.
2. Click on the application name.
3. Select Manage Modules.
4. Click the WebModule_name Web application
5. Click View Deployment Descriptor.
Look for the servlet in a <servlet-mapping> entry and note the url-pattern value.
Note: If the Web module has security configured, check the <security-constraint> and <security-role> deployment descriptor tags for the role that is needed for access to the selected Web resource.

Finding the context root of the web module

1. Select Applications ?Enterprise Applications.
2. Click on the application name.
3. Click on Context Root for Web Modules.
4. Note the context root for the appropriate Web module.

Finding the virtual host used for application

Find the virtual host where the Web module is installed:
1. Select Applications ?Enterprise Applications.
2. Click on the application name.
3. Click on Virtual hosts under Web Module Properties.
4. Note the virtual host for the Web module.

Finding the host aliases for the virtual host

1. From the console navigation tree, select Environment ?Virtual Hosts.
2. Click on the virtual host.
3. Select Host Aliases under Additional Properties.

An alias is composed of a host name and port number. Each alias represents a valid host:port combination for the Web module to be accessed from web server.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s