Hi All,
Is anyone doing this? We ran into a VERY strange deployment issue when
deploying our Click application WAR on a Weblogic clustered environment.
The symptoms where this:
1.) Deployed to Server (from the Weblogic Console)
2.) Weblogic showed successful deployment and the WAR was active. No error
messages or warnings.
3.) Tried to run the app and were getting http 403 errors.
4.) Deployed same WAR file on a non-clustered Weblogic server and everything
was good. We could run the application with no problem.
5.) Looking at the weblogic log files, found this log entry:
<Error> <Deployer> <BEA-149265> <Failure occurred in the execution of
deployment request...
weblogic.management.DeploymentException: [Deployer:149003]Unable to access
application source information in...
after much toil and head scratching, we found this in our web xml:
<security-constraint>
<web-resource-collection>
<web-resource-name>WASN
Settlements</web-resource-name>
<url-pattern>*.htm</url-pattern>
</web-resource-collection>...
We made this change to this section of the web.xml:
<security-constraint>
<web-resource-collection>
<web-resource-name>WASN
Settlements</web-resource-name>
<url-pattern>*.html</url-pattern>
</web-resource-collection>...
Notice the difference...*.htm and *.html
With this change, everything started working. Does anybody have any idea
why that is? Is this something we should ask Oracle/Weblogic support?
Any insight would be greatly appreciated.
Thanks
Mark K
--
View this message in context:
http://click.1134972.n2.nabble.com/Deploy-to-Weblgic-10-3-Cluster-Issue-tp7181432p7181432.html
Sent from the click-user mailing list archive at Nabble.com.
