求救JSP页面处于响应状态，无法访问原因

在MYECLIPSE启动TOMCAT,后台日志没有报错，但访问登陆界面一直处于响应的状态。从其它机器拷了一个可发布的WEB项目，在别处能正常启动，一到我的机器，启动也正常，但也是访问登陆界面一直处于响应的状态。在TOMCAT的WORK路径下，查看不到浏览器访问路径JSP对应的JAVA,CLASS文件，请问这是什么原因造成的？

解决方案 »

免费领取超大流量手机卡，每月29元包185G流量+100分钟通话, 中国电信官方发货

换个浏览器试试，不行换个tomcat.
那就是你服务器的问题了，先访问下静态文件试试
不行换tomcat。
新建一个HTML能访问！
运行了半个钟访问JSP页面出现错误：org.apache.jasper.JasperException: Unable to compile class for JSPAn error occurred at line: -1 in the jsp file: nullGenerated servlet error:
    [javac] Compiling 1 source fileThe system is out of resources.
Consult the following stack trace for details.
java.lang.OutOfMemoryError
同时TOMCAT也报了错：WebappClassLoader: Lifecycle error : CL stopped
WebappClassLoader: Lifecycle error : CL stopped
WebappClassLoader: Lifecycle error : CL stopped
java.lang.Exception: Stack trace
at java.lang.Thread.dumpStack(Thread.java:1064)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1292)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1252)
at org.apache.commons.logging.impl.LogFactoryImpl$1.run(LogFactoryImpl.java:460)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.commons.logging.impl.LogFactoryImpl.loadClass(LogFactoryImpl.java:454)
at org.apache.commons.logging.impl.LogFactoryImpl.isLog4JAvailable(LogFactoryImpl.java:501)
at org.apache.commons.logging.impl.LogFactoryImpl.getLogClassName(LogFactoryImpl.java:364)
at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:401)
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)
at com.ai.appframe2.web.action.CentralControlServlet.<clinit>(CentralControlServlet.java:31)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:856)
at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:621)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:163)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:144)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2358)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:133)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:118)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:116)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:127)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:152)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)
WebappClassLoader: Lifecycle error : CL stopped
你可以自己写一个最简单的servlet来测试你的tomcat是否正常，如果不想直接换tomcat的话，更想查一下原因的话。
因为work下为空说明没有产生工作代码，但还是要好好确认一下。The work directory, as its name suggests, is where Tomcat writes any files that it needs during run time, such as the generated servlet code for JSPs, the class files for the same after they are compiled, the serialized sessions during restarts or shutdowns (SESSIONS.ser).
It is also where your application's tmpdir is located context scoped attribute with name "javax.servlet.context.tempdir".
这个问题是tomcat的问题，以前遇到过。应对方案：将tomcat中的项目，先全部move掉。重新部署，看行不行的通。再不行，tomcat出了问题，重新安装tomcat.
An error occurred at line: -1 in the jsp file: null奇怪的错误还真不少，-1行是哪一行？楼主tomcat,jdk是什么版本是有类似一个bug
https://issues.apache.org/bugzilla/show_bug.cgi?id=3888
没有生成JSP对应的JAVA类
TOMCAT4.1 JDK1.4
这是一个用JDK1.4写的系统的，其它同事都用TOMCAT4能跑
其他同事能跑的话就找与其他同事之间的区别吧，jvm的内存分配是不是小了，因为有out of memory（先不管根源是由什么问题引起的）
具体设置：
http://stackoverflow.com/questions/286007/how-to-tune-tomcat-5-5-jvm-memory-settings-without-using-the-configuration-progr不过也要对比一下你同事那边的做法
问题已经得到解决：我原来发布是通过配置tomcat/conf/server.xml中<Context path="/xxx" docBase="E:/workdir/gx_workspace/xxx"  debug="1"
                 reloadable="true" >
</Context>
现改为直接把发布项目发布到tomcat下的webapps就可以了！