RE: Re: Re: UTF-8 support for WDSc 4 Websphere Test En

Hi,

Since I messed up my webserver configuration in WDSc, I had to recreate it
again from scratch.  After I did so, my first attempts still failed (no job
in QINTER, however a connection from my PC to port 4004 on iSeries).
Restarting the webfacing server on iSeries finally solved it.

I got my Webfacing application, and could test the screen (very simple
screen with two input fields that get summed together in an output field).
After pressing Enter, my program sums the two fields, but the progress
indication in IE keeps on moving (just like he's trying to get something
from the server... is this a timeout mechanism or so ?).

During my testing I also got quite often the error message below for
whatever reason.  My first attemp works now, but I can hardly imagine
putting something like this into production.  The next attempt will be to
publish it to an WAS 4... hope it goes better.

Anyone else the same behaviour... ?

Kind regards,
Paul

----------------------------------------------------------------------------
----

Additional information :

     WF0093: An unexpected exception occurred while building Host
Application Response.

Details :

java.lang.NullPointerException
at
com.ibm.as400ad.webfacing.runtime.httpcontroller.ControllerRequestHandler.pr
ocessBrowserRequest(ControllerRequestHandler.java:785)
at
com.ibm.as400ad.webfacing.runtime.httpcontroller.ControllerRequestHandler.pr
ocessStateTransition(ControllerRequestHandler.java:970)
at
com.ibm.as400ad.webfacing.runtime.httpcontroller.ControllerRequestHandler.ha
ndleRequest(ControllerRequestHandler.java:646)
at
com.ibm.as400ad.webfacing.runtime.httpcontroller.ControllerServlet.doPost(Co
ntrollerServlet.java:34)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager
.java:827)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycl
eServlet.java:167)
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java:297)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycle
Servlet.java:110)
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:47
2)
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java:1012)
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManag
er.java:913)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebAppRequestDispatcher.java:523)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequest
Dispatcher.java:282)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestD
ispatcher.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(CachedIn
vocation.java:67)
at
com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(Cacheabl
eInvocationContext.java:106)
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java:125)
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener
.java:315)
at
com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.ja
va:60)
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)