Unhandled Servlet exception in WAS3.5.5

[Veni Garg]

Hi,

I am getting the following error when I try ot run my Servlet which in turn
invokes a JSP in WAS3.5.5 on a win2K platform-- Any ideas/suggestions will
be helpful--

My login page shows up corretly, when I enter the user -id /password and try
to login it should invke a servlet LL000S which in turn should invoke
LL000ServletResults.jsp. But as soon as my servblet stars to get executed, I
get this error.

This application ran fine in the WTE environment on VAJ 3.5.

Please advice!

Thanks & Regards,
V.

[02.04.18 15:44:23:649 PDT] 565533e6 WebGroup A
[Servlet.LOG]:."com.sun.jsp.runtime.JspServlet: init"
[02.04.18 15:44:23:789 PDT] 565533e6 ServletInstan A
Servlet.available.for.service:."JSP 1.0 Processor"
[02.04.18 15:46:02:471 PDT] 26d7b3e1 ServletInstan A
Loading.servlet:."com.xxx.clcs.test.LL000S"
[02.04.18 15:46:02:481 PDT] 26d7b3e1 WebGroup A
[Servlet.LOG]:."com.xxx.clcs.test.LL000S: init"
[02.04.18 15:46:02:551 PDT] 26d7b3e1 WebGroup A
[Servlet.LOG]:."com.xxx.clcs.test.LL000S: init"
[02.04.18 15:46:02:581 PDT] 26d7b3e1 WebGroup A
[Servlet.LOG]:."com.xxx.clcs.test.LL000S: init"
[02.04.18 15:46:02:631 PDT] 26d7b3e1 WebGroup A
[Servlet.LOG]:."com.xxx.clcs.test.LL000S: init"
[02.04.18 15:46:02:681 PDT] 26d7b3e1 WebGroup A
[Servlet.LOG]:."com.ibm.servlet.engine.webapp.SingleThreadModelServlet:
init"
[02.04.18 15:46:02:731 PDT] 26d7b3e1 ServletInstan A
Servlet.available.for.service:."com.xxx.clcs.test.LL000S"
[02.04.18 15:46:03:833 PDT] 26d7b3e1 WebGroup A
[Servlet.LOG]:."com.xxx.clcs.test.LL000S: init"
[02.04.18 15:46:03:943 PDT] 26d7b3e1 ServletInstan X Uncaught service()
exception thrown by servlet {0}: {1}
"com.xxx.clcs.test.LL000S"
javax.servlet.ServletException:
javax.servlet.http.HttpSession: method
setAttribute(Ljava/lang/String;Ljava/lang/Object;)V not found
at
com.ibm.servlet.engine.webapp.SingleThreadModelServlet.service(SingleThreadM
odelServlet.java:66)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager
.java:580)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycl
eServlet.java:160)
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java:287)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycle
Servlet.java:105)
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:35
3)
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java:729)
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManag
er.java:655)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebApp.java:1269)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebApp.java:1
106)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebApp.java:10
39)
at
com.ibm.servlet.engine.webapp.InvokerServlet.service(InvokerServlet.java:199
)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:639)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager
.java:580)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycl
eServlet.java:160)
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java:287)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycle
Servlet.java:105)
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:35
3)
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java:729)
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManag
er.java:655)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebApp.java:1269)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebApp.java:1
106)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebApp.java:10
39)
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebGroup.java:
646)
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedIn
vocation.java:67)
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java:155)
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener
.java:300)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp$ServiceRunnable.run(SQ
EventListenerImp.java:230)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp.notifySQEvent(SQEventL
istenerImp.java:104)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQEventSource.notifyEvent(SQE
ventSource.java:202)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.notifyService(SQWrapperEventSource.java:347)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.run(SQWrapperEventSource.java:216)
at
com.ibm.servlet.engine.oselistener.outofproc.OutOfProcThread$CtlRunnable.run
(OutOfProcThread.java:248)
at java.lang.Thread.run(Thread.java:481)

[02.04.18 15:46:03:973 PDT] 26d7b3e1 ServletInstan X Uncaught service()
exception root cause {0}: {1}
"com.xxx.clcs.test.LL000S"
java.lang.NoSuchMethodError:
javax.servlet.http.HttpSession: method
setAttribute(Ljava/lang/String;Ljava/lang/Object;)V not found
at com.xxx.clcs.test.LL000S.performTask(LL000S.java)
at com.xxx.clcs.test.LL000S.doPost(LL000S.java)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:566)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:639)
at
com.ibm.servlet.engine.webapp.SingleThreadModelServlet.service(SingleThreadM
odelServlet.java:61)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager
.java:580)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycl
eServlet.java:160)
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java:287)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycle
Servlet.java:105)
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:35
3)
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java:729)
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManag
er.java:655)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebApp.java:1269)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebApp.java:1
106)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebApp.java:10
39)
at
com.ibm.servlet.engine.webapp.InvokerServlet.service(InvokerServlet.java:199
)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:639)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager
.java:580)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycl
eServlet.java:160)
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java:287)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycle
Servlet.java:105)
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:35
3)
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java:729)
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManag
er.java:655)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebApp.java:1269)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebApp.java:1
106)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebApp.java:10
39)
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebGroup.java:
646)
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedIn
vocation.java:67)
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java:155)
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener
.java:300)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp$ServiceRunnable.run(SQ
EventListenerImp.java:230)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp.notifySQEvent(SQEventL
istenerImp.java:104)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQEventSource.notifyEvent(SQE
ventSource.java:202)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.notifyService(SQWrapperEventSource.java:347)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.run(SQWrapperEventSource.java:216)
at
com.ibm.servlet.engine.oselistener.outofproc.OutOfProcThread$CtlRunnable.run
(OutOfProcThread.java:248)
at java.lang.Thread.run(Thread.java:481)

[02.04.18 15:46:04:003 PDT] 26d7b3e1 ServletInstan X Uncaught service()
exception thrown by servlet {0}: {1}
"Auto-Invoker"

com.ibm.servlet.engine.webapp.UncaughtServletException: Server caught
unhandled exception from servlet [com.xxx.clcs.test.LL000S]
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebApp.java:1286)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebApp.java:1
106)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebApp.java:10
39)
at
com.ibm.servlet.engine.webapp.InvokerServlet.service(InvokerServlet.java:199
)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:639)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager
.java:580)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycl
eServlet.java:160)
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java:287)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycle
Servlet.java:105)
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:35
3)
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java:729)
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManag
er.java:655)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebApp.java:1269)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebApp.java:1
106)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebApp.java:10
39)
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebGroup.java:
646)
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedIn
vocation.java:67)
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java:155)
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener
.java:300)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp$ServiceRunnable.run(SQ
EventListenerImp.java:230)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp.notifySQEvent(SQEventL
istenerImp.java:104)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQEventSource.notifyEvent(SQE
ventSource.java:202)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.notifyService(SQWrapperEventSource.java:347)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.run(SQWrapperEventSource.java:216)
at
com.ibm.servlet.engine.oselistener.outofproc.OutOfProcThread$CtlRunnable.run
(OutOfProcThread.java:248)
at java.lang.Thread.run(Thread.java:481)

[Ken Hygh]

It looks like you may be mixing levels of the servlet spec supported
between the IDE and the Runtime, which is why you're getting the
HttpSession.setAttribute(String,Object) not found.
Ken

[Veni Garg]

Hi (Ken),

The servlet spec being used in VAJ EE3.5 is I think ServletAPI 2.2 . It also
runs WAS3.5.3 in its version of WTE.

I just realizes that we are running WAS3.5 NOT WAS3.5.5 It is interesting
because the box in which the CDs were shipped says version3.5.5 but when I
go to Help--> About in the WAS console it says Version3 release 5 and no
fixpacks, so I think we are runnign3.5.0---which means the servletAPI
supported by this version is 2.1 and that may be the reason for the error
below.

I founf Fixpack 3 available ont he IBM site which will make it WAS3.5.3 and
that should support ServletAPI2.2 . But I would like to find the download
for Fixpack5 for WAS3.5 which will hopefully solve the issue.

From what I figure, Insatllling Fixpack(3) or 5 should fix the issue of the
Servlet API compatibility. Does this approach sound about right????????

If anyone finds the download to Fixpack5 that would be very helpful also.

Thanks very much!

Veni.

"Ken Hygh" <ken...@nc.rr.com> wrote in message
news:a9rp8k$18lg$3...@news.boulder.ibm.com...

[Ken Hygh]

Sounds like you're on the right track. 3.5 Fixpack 5 should be in the
same place as fixpack 3.

Ken