TroubleShooting: Plug-in regeneration for Version 5.0 and 5.1
 Technote (troubleshooting)
 
Problem(Abstract)
Troubleshooting for plug-in regeneration problems with WebSphere® Application Server. This should help address common issues with this component before calling IBM support and save you time.
 
Resolving the problem

1. Learning more 2. Troubleshooting 3. Collecting data

Steps to help resolve plug-in regeneration problems
  1. Does running the GenPluginCfg command fail with PluginConfigException?
    • Yes, see this technote to resolve the issue.

    • No, continue to the next question.

  2. Do you have issue to regen the plug-in from administrative console?
    • Yes, see this technote to make sure all deployed application has an entry in the serverindex.xml file.

    • No, continue to the next question.

  3. Is the admin_host virtual host not displayed in the plugin-cfg.xml file after plug-in regen?
    • Yes, see this technote for more information.

    • No, continue to the next question.

  4. How do I enable and disable Auto regeneration of the plug-in?
    • Yes, starting in V5.0 releases, the configurable auto regeneration function is no longer available. This is a function that was deprecated in V3.5 and V4.0.

    • No, continue to the next question.

  5. How do I find out if the plug-in regen is failing on cell, node, or server level?
    • Yes, when using the GenPluginCfg command, the plug-in can be regenerated on the cell level, node level and server level. Regenerate the plug-in on the cell level to make sure the plug-in regeneration is failing on the cell level:

      GenPluginCfg.sh/bat -cell.name NetworkDeploymentCell

      Then, run the following command on each and every node to narrow down the problem to a specific node:

      GenPluginCfg.sh/bat -cell.name NetworkDeploymentCell -node.name myNode

      After finding the problematic node, run the following server level command on the problematic node:

      GenPluginCfg.sh/bat -cell.name NetworkDeploymentCell -node.name myProblematicNode -server.name myServerName

      The preceding command will be very useful to narrow down the problem to a specific server or node.

    • No, continue to the next question.

  6. Why the plug-in configuration file must be edited manually to add BackupServers?
    • Yes, see this technote for more information.

    • No, continue to the next question.

  7. Does the plug-in regen fail with the PLGN0062W message?
    • Yes, see this technote to resolve the problem.

    • No, continue to the next question.

  8. Are you getting a PLGC0041W warning message during plug-in regen?
    • Yes, see this technote to resolve the issue.

    • No, continue to the next question.
What to do next
If the preceding steps did not help solve your problem, see the MustGather for Plug-in Regen problems to continue investigation.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Plug-in
Operating system(s): Windows
Software version: 5.1
Software edition:
Reference #: 1224809
IBM Group: Software Group
Modified date: Jan 15, 2008