[急]...WSAD无法编译JSP...

Question

wsad5.0
jdk1.4
出错信息如下，jsp没有问题，因为在其它的机器上可以编译，请各位大哥大姐指教，非常感谢！！！
还需要提供其它信息请提出来。[06-8-11 10:49:28:625 CST] 60389e7c SystemOut     O ##############################1
[06-8-11 10:49:28:625 CST] 60389e7c SystemOut     O SectionCR: searchCR
[06-8-11 10:49:43:422 CST] 60389e7c WebGroup      E SRVE0026E: ［Servlet 错误］－［无法编译 JSP 类
E:\websphere\workspace\.metadata\.plugins\com.ibm.etools.server.core\tmp0\cache\localhost\server1\TMEAR\TM.war\web\underwriting\_eapp_2D_edit_2D_cr.java:55: JAVAC MESSAGE FILE IS BROKEN: key=javac.err.branch.too.big, arguments=null, null, null
public class _eapp_2D_edit_2D_cr extends com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase {
             ^
1 个错误
］：org.apache.jasper.JasperException: 无法编译 JSP 类
E:\websphere\workspace\.metadata\.plugins\com.ibm.etools.server.core\tmp0\cache\localhost\server1\TMEAR\TM.war\web\underwriting\_eapp_2D_edit_2D_cr.java:55: JAVAC MESSAGE FILE IS BROKEN: key=javac.err.branch.too.big, arguments=null, null, null
public class _eapp_2D_edit_2D_cr extends com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase {
             ^
1 个错误 at org.apache.jasper.compiler.Compiler.compile(Compiler.java:326)
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.loadJSP(JspServlet.java:861)
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.loadIfNecessary(JspServlet.java:278)
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:304)
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java:598)
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:696)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:258)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:872)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:491)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:173)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1014)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:417)
at org.apache.struts.action.RequestProcessor.processActionForward(RequestProcessor.java:390)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:271)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1292)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:258)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:872)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:491)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:173)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:199)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:331)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:432)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:343)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)

Answer 1

我也是用WSAD的，没遇到过这个问题啊。。是运行是报的？还是发布时报的？
会不会是文件编码问题？

Answer 2

运行时报的，编码问题指什么？因为这个jsp比较大，141k,但是在其他同事的机器上是可以编译的

Answer 3

你试试把他的代码copy出来，新建一个jsp文件，copy代码进去，运行新的jsp文件看看

Answer 4

我把这个jsp的代码全部删除，整个文件只有"aaa"，再访问页面就只显示 "aaa"我在想会不会是wsad的配置问题，但是不知道应该从哪里着手查找

Answer 5

在网上找到这样一个答案
64kb limit for a class size byte code for Websphere Application Server. 但是如果是这样的话，相同的代码为什么其他同事能编译？

Answer 6

就一个编译不了？
>>>是的，因为这个问题是在我去访问这个页面时才会出现的。