Topic
  • 2 replies
  • Latest Post - ‏2004-09-10T10:11:15Z by SystemAdmin
SystemAdmin
SystemAdmin
269 Posts

Pinned topic EJB Test Client does not work in Debug Mode

‏2002-07-25T15:23:12Z |
The EJB Test client does not work, when the server is started in the debug
mode. It gives the following error:

java.lang.InternalError: jzentry == 0
at java.util.zip.ZipFile$2.nextElement(ZipFile.java:305)
at sun.tools.java.ClassPath.getFiles(ClassPath.java:187)
at sun.tools.java.Package.exists(Package.java:98)
at sun.tools.java.Imports.resolve(Imports.java:150)
at sun.tools.javac.SourceClass.basicCheck(SourceClass.java:1079)
at
sun.tools.java.ClassDeclaration.getClassDefinition(ClassDeclaration.java:137)
at sun.tools.javac.Main.compile(Main.java:526)
at
org.apache.jasper.compiler.SunJavaCompiler.compile(SunJavaCompiler.java:183)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:303)
at org.apache.jasper.runtime.JspServlet.loadJSP(JspServlet.java:697)
at
org.apache.jasper.runtime.JspServlet$JspServletWrapper.loadIfNecessary(JspServle
t.java:244)
at
org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.java:2
61)
at
org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:430)
at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:565)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.jav
a:827)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleSer
vlet.java:167)
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.ja
va:297)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServ
let.java:110)
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472)
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager
.java:1012)
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.j
ava:913)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAp
pRequestDispatcher.java:523)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDisp
atcher.java:282)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispa
tcher.java:112)
at com.ibm.etools.utc.servlet.UTCServlet.forward(UTCServlet.java:58)
at
com.ibm.etools.utc.servlet.JNDILookupServlet.lookup(JNDILookupServlet.java:128)
at
com.ibm.etools.utc.servlet.JNDILookupServlet.doGet(JNDILookupServlet.java:35)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.jav
a:827)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleSer
vlet.java:167)
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.ja
va:297)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServ
let.java:110)
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472)
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager
.java:1012)
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.j
ava:913)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAp
pRequestDispatcher.java:523)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDisp
atcher.java:282)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispa
tcher.java:112)
at
com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:91)
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java
:184)
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvoca
tion.java:67)
at
com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(CacheableInv
ocationContext.java:106)
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestP
rocessor.java:125)
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.jav
a:315)
at
com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:6
0)
at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:323)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:252)
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122)
Updated on 2004-09-10T10:11:15Z at 2004-09-10T10:11:15Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    269 Posts

    RE: EJB Test Client does not work in Debug Mode

    ‏2002-07-25T21:03:47Z  
    Suman,

    This does not look like a problem in the test client, but rather a problem with
    the server or even a corrupt jar. I understand that you have contacted the
    support group, and that is the correct path for this problem.
    Updated on 2002-07-25T21:03:47Z at 2002-07-25T21:03:47Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    269 Posts

    Re: RE: EJB Test Client does not work in Debug Mode

    ‏2004-09-10T10:11:15Z  
    Suman,

    This does not look like a problem in the test client, but rather a problem with
    the server or even a corrupt jar. I understand that you have contacted the
    support group, and that is the correct path for this problem.
    Hi,

    I was facing a similiar issue. The WebSphere Commerce Server (WCS) started perfectly, but as soon as I access any of the JSP's it gives me error.

    After reading Tim's reply, I checked the jar files present in my classpath, and found out that classes12.jar was present twice (two different locations). One of them was getting used in starting the WCS server. I removed the other jar-file and the problem got resolved.

    On inspecting the other-jar I found that it was of a different version, thus giving errors.

    Regards,
    Dhiraj Agrawal