Glass Fish Application Server v3.01
Had a full working version of Glass Fish Application Server v3.01, configured with datasources, security configuration, custom resources, a couple of applications deployed. Left it overnight, and started adding new functionality to the application early in the morning with the new ideas collected overnight. While trying to test the very first idea, hit with the Glass Fish's application server automatic update defect. Can not open the admin console, can not deploy any application. The details of the errors are:
Can't Open the admin console
[#|2011-10-08T18:41:57.383-0400|SEVERE|glassfish3.0.1|javax.enterprise.system.tools.deployment.org.glassfish.deployment.common|_ThreadID=24;_ThreadName=Thread-23;|DPL8005: Deployment Descriptor parsing failure : [Ljava.lang.Object;@2fd6fc1b|#]
[#|2011-10-08T18:41:57.392-0400|SEVERE|glassfish3.0.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=24;_ThreadName=Thread-23;|Exception while deploying the app
java.io.IOException: Unable to locate the DTD to validate your deployment descriptor file [WEB-INF/web.xml] in archive [__admingui]. Please make sure the DOCTYPE is correct (no typo in public ID or system ID) and you have proper access to the Internet.
. . . . . .
. . . . . .
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
. . . . . .
. . . . . .
Can't deploy any application
[#|2011-10-08T18:45:28.686-0400|SEVERE|glassfish3.0.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=25;_ThreadName=AutoDeployer;|Exception while loading the app
java.lang.Exception: java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: org.apache.catalina.LifecycleException: org.apache.jasper.JasperException: PWC6177: XML parsing error on file file:/C:/Users/htotapally.IF-SWS-TESTLTP4/glassfishv3/glassfish/modules/jstl-impl.jar
While trying to figure out the problems why Glass Fish Application Server doesn't start, came across quite a few blogs, and none of them providing any clear solution. However the following two were useful:
Useful links
http://blogs.oracle.com/jluehe/entry/validate_your_tag_library_descriptor
http://thegreyblog.blogspot.com/2010/11/glassfish-30x-admin-console-not.html
Based on the error message:
org.apache.catalina.LifecycleException: org.apache.jasper.JasperException: PWC6177: XML parsing error on file file:/C:/Users/htotapally.IF-SWS-TESTLTP4/glassfishv3/glassfish/modules/jstl-impl.jar
unzipped the file, and the dtds were referring to java.sun.com and the update package application was trying to access pkg.glassfish.org. Both servers were not accessible. This lead me to believe that the update application caused the problem. Wasted about 10 hours trying to troubleshoot the problem, and finally no solution insight reinstalled the application server. After renaming console-updatecenter-plugin.jar to console-updatecenter-plugin.jar.old, restarted, and reconfigured the application server, redeployed the application, and every thing started working finally, but have to wait another day to implement last nights ideas. What a pain?
Had a full working version of Glass Fish Application Server v3.01, configured with datasources, security configuration, custom resources, a couple of applications deployed. Left it overnight, and started adding new functionality to the application early in the morning with the new ideas collected overnight. While trying to test the very first idea, hit with the Glass Fish's application server automatic update defect. Can not open the admin console, can not deploy any application. The details of the errors are:
Can't Open the admin console
[#|2011-10-08T18:41:57.383-0400|SEVERE|glassfish3.0.1|javax.enterprise.system.tools.deployment.org.glassfish.deployment.common|_ThreadID=24;_ThreadName=Thread-23;|DPL8005: Deployment Descriptor parsing failure : [Ljava.lang.Object;@2fd6fc1b|#]
[#|2011-10-08T18:41:57.392-0400|SEVERE|glassfish3.0.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=24;_ThreadName=Thread-23;|Exception while deploying the app
java.io.IOException: Unable to locate the DTD to validate your deployment descriptor file [WEB-INF/web.xml] in archive [__admingui]. Please make sure the DOCTYPE is correct (no typo in public ID or system ID) and you have proper access to the Internet.
. . . . . .
. . . . . .
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
. . . . . .
. . . . . .
Can't deploy any application
[#|2011-10-08T18:45:28.686-0400|SEVERE|glassfish3.0.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=25;_ThreadName=AutoDeployer;|Exception while loading the app
java.lang.Exception: java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: org.apache.catalina.LifecycleException: org.apache.jasper.JasperException: PWC6177: XML parsing error on file file:/C:/Users/htotapally.IF-SWS-TESTLTP4/glassfishv3/glassfish/modules/jstl-impl.jar
While trying to figure out the problems why Glass Fish Application Server doesn't start, came across quite a few blogs, and none of them providing any clear solution. However the following two were useful:
Useful links
http://blogs.oracle.com/jluehe/entry/validate_your_tag_library_descriptor
http://thegreyblog.blogspot.com/2010/11/glassfish-30x-admin-console-not.html
Based on the error message:
org.apache.catalina.LifecycleException: org.apache.jasper.JasperException: PWC6177: XML parsing error on file file:/C:/Users/htotapally.IF-SWS-TESTLTP4/glassfishv3/glassfish/modules/jstl-impl.jar
unzipped the file, and the dtds were referring to java.sun.com and the update package application was trying to access pkg.glassfish.org. Both servers were not accessible. This lead me to believe that the update application caused the problem. Wasted about 10 hours trying to troubleshoot the problem, and finally no solution insight reinstalled the application server. After renaming console-updatecenter-plugin.jar to console-updatecenter-plugin.jar.old, restarted, and reconfigured the application server, redeployed the application, and every thing started working finally, but have to wait another day to implement last nights ideas. What a pain?
