WebSphere Plugin Issue

[a***@ymail.com]

Hi All,
I have a Dmgr which has cluster with 2 members( 2 members are on other box which is federated to the dmgr). I'm running a IIS on the same box as the Dmgr. Now the problem is when ever I do an update or any changes(like updating a file in an application) on websphere side, the Plugin file is automatically being changed and it bring down the whole website. the changed plugin doesn't have any entries besides the default entries. every time I have to change this newly generated plugin with my old backup plugin and then every thing works fine. Is there something I can do about this, I am about to deploy a new application on the Production Server and it pretty much replicates the server which I had this plugin issue.
PS:I h've also manually generated the Plugin from the websphere console but it still generates the default plugin but not the plugin with all entries.
Please gimme your thoughts on this. Thanks to everyone in advance

[HenkW]

most common mistake: did you map your application(s) to the appserver AND
the webserver during deployment?
Check "Manage Modules" under your application.

WAS versions and fixpacks?

Henk

[Doug Breaux]

Post by HenkW
most common mistake: did you map your application(s) to the appserver AND
the webserver during deployment?
Check "Manage Modules" under your application.
WAS versions and fixpacks?
Henk

I agree that this sounds like the most likely cause to me at this point.

[Brian S Paskin]

Hi, it does not sound like a plugin issue. When you update an application is forces the application to reload, so it will be unavailable until it is stopped and started. Depending on your version of WebSphere you are using, which you did not specify nor the platform, you can do a rolling update that installs the appplication on one App Server at a time.

Regards,
Brian

[a***@ymail.com]

Brian,
Thanks for your prompt reply. Apologies for not providing the precise info.
WebSphere 6.1.0.19 running on Windows 2003, Sp2. Well I totally agree with what you said in regards to the rolling update but even If I do a rolling update it still generates the plugin automatically. For example: If I install a new ear file called "lala" I would be expecting the plugin to add "/lala" to the plugin, inspite of doing that the websphere generates a plugin deleting all the previous entries. I am pasting the working Plugin.xml and new generated plugin.xml(which deletes all entries).

Working Plugin.xml
















Newly generated Plugin after the new ear installation or updating a file











Thanks in advance

[Brian S Paskin]

Is your application part of the Web Server application?

Regards,
Brian

[a***@ymail.com]

Thanks Brett & Brian,
I will disable the automatic generation of plugin, I am guessing doin that should work.
Brian yes its mapped to web server application (If that is what you meant by "Is your application part of the Web Server application?" ). I ran into another problem now, I Have a similar environment but with IHS WebServer.In the process of solving this plugin issue I actually changed httpd.conf file and now the Http logs says

[Wed May 13 11:44:53 2009] [error] ws_common: websphereUpdateConfig: Failed to stat plugin config file: C:\\Program Files\\IBM\\HTTPServer\\Plugins\\config\\atkswebserver\\plugin-cfg.xml
[Wed May 13 11:44:53 2009] [error] ws_common: websphereInit: Failed to load the config file
[Wed May 13 11:44:53 2009] [error] mod_was_ap20_http: as_init: unable to initialize .

I actually reverted it to the original httpd.conf file (I had the backup) but still it shows the error. I restarted the WebServer,DMgr,Cluster.. but no luck. can you guys throw some light on this. Thank you for your prompt replies guys, you doing a gr8 work. Much appreciated!!

[Ken Hygh]

Post by a***@ymail.com
Brian,
Thanks for your prompt reply. Apologies for not providing the precise info.
WebSphere 6.1.0.19 running on Windows 2003, Sp2. Well I totally agree with what you said in regards to the rolling update but even If I do a rolling update it still generates the plugin automatically. For example: If I install a new ear file called "lala" I would be expecting the plugin to add "/lala" to the plugin, inspite of doing that the websphere generates a plugin deleting all the previous entries. I am pasting the working Plugin.xml and new generated plugin.xml(which deletes all entries).
Working Plugin.xml
Newly generated Plugin after the new ear installation or updating a file
Thanks in advance

Are you certain the new/updated application is successfully installed?
It almost looks like the application with a WAR with a context root of
/application is not successfully installed.

Having 3 identical uri's in there is awfully suspicious!

Ken

[S***@PRINCIPAL.COM]

You can change this behavior by turning off automatic generation and propogation of the plug-in file in the Admin console. To do this you go to Servers / Web servers / SERVERNAME / Plug-in properties. You just uncheck the 2 boxes for these values.

When the plug-in configuration service is enabled, a plug-in configuration file is automatically generated for a Web server whenever:
- The WebSphere Application Server administrator defines new Web server.
- An application is deployed to an Application Server.
- An application is uninstalled.
- A virtual host definition is updated and saved.