|
Problem(Abstract) |
The PluginConfigException is thrown when executing the
GenPluginCfg command. |
|
Symptom |
The address tag in the server.xml file should have a
host="" variable. If it does not have a host="" variable,
the GenPluginCfg command throws the exception shown below.
PLGC0032E: Exception caught while generating plugin configuration:
PLGC0006E: An exception occurred while outputting the document.
com.ibm.websphere.plugincfg.exception.PluginConfigException: PLGC0006E:
An exception occurred while outputting the document.
at
com.ibm.websphere.plugincfg.generator.PluginConfigGenerator.outputPluginConfigFile(PluginConfig
Generator.java:193)
at
com.ibm.websphere.plugincfg.generator.PluginConfigGenerator.generate(PluginConfigGenerator.
java:138)
at
com.ibm.websphere.plugincfg.generator.PluginConfigGenerator.main(PluginConfigGenerator.java:634)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:189)
|
|
Cause |
There are several possible causes for the missing host=""
variable, including the following:
- Editing the xml files manually. It is not recommended to edit any IBM®
WebSphere® Application Server configuration files manually.
- You could see this behavior after migrating from V5.0 to V5.1
|
|
Resolving the
problem |
Edit the server.xml file under Install_Root
/config/cells/cellname/nodes/nodename/servers/servername.
- Find the address tag. It will look similar to the
following line.
<address xmi:id="EndPoint_1111424123476" port="9085"/>
- Add the host="" variable in the address tag similar
to the following line.
<address xmi:id="EndPoint_1111424123476" host =""
port="9085"/>
- Save the changes.
- Repeat the same thing for other servers.
- Run the GenPluginCfg command again.
If you have the host="" variable in the server.xml file and get a
similar exception, contact IBM support for further assistance. |
|