• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Problem with application when accessed via IBM Http Server

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

We are facing problem some with the IBM HTTP Server.
We have developed an application using j2ee 1.2 running on Websphere 4.0.1 AE as the App Server and IBM Http Server 1.3.19 as the Http Server and Windows 2000 as the operating env.
The application runs smoothly On the uat cluster and the backup server but the application behavior is freaky on the Production Server i.e. if you try to submit a particular html form multiple times, about 1/3 of the times the request fails whereas on the remaining ones it succeeds
On investigating the problem, we found that the application behavior is normal when the Http Server is bypassed i.e. when the application is accessed by giving the port number in the url.
The following exceptions are logged into the log files (the logs are at diff. times and for same kind of requests):
1) Exception 1 (application log files)

java.lang.IllegalArgumentException
at
com.ibm.servlet.engine.webapp.RequestUtils.parseName(RequestUtils.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.RequestUtils.parseQueryString(RequestUtils.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.RequestUtils.parsePostData(RequestUtils.java:372)
at
com.ibm.servlet.engine.srt.SRTServletRequest.parseParameters(SRTServletRequest.java:624)
at
com.ibm.servlet.engine.srt.SRTServletRequest.getParameter(SRTServletRequest.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.HttpServletRequestProxy.getParameter(HttpServletRequestProxy.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.HttpServletRequestProxy.getParameter(HttpServletRequestProxy.java(Compiled
Code))
at
com.prompt.controller.ControllerServlet.service(ControllerServlet.java:92)
at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
at
com.ibm.servlet.dynacache.CacheHook.handleFragment(CacheHook.java(Compiled
Code))
at
com.ibm.servlet.dynacache.CacheHook.handleServlet(CacheHook.java(Compiled
Code))
at
com.ibm.servlet.dynacache.CacheProxyServlet.service(CacheProxyServlet.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java(Compiled
Code))
at
com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java(Compiled
Code))
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java(Compiled
Code))
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java(Compiled
Code))
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java(Compiled
Code))
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java(Compiled
Code))
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java(Compiled
Code))
at
com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java(Compiled
Code))
at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java(Compiled
Code))
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java(Compiled Code))
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122)


2) Exception 2 (App server log file)
AP000012784%3B13371%3BI=&TXTPARAMETER%3BMAP000012785%3B13371%3BI=&TXTPARAMETER%3BMAP000012786%3B13371%3BO=&TXTDAILY%3B13371=&TXTPARAMETER%3BTEMP_ID%3B13371%3BI=&TXTPARAMETER%3BMAP000012784%3B13621%3BI=&TXTPARAMETER%3BMAP000012785%3B13621%3BI=&TXTPARAMETER%3BMAP000012786%3B13621%3BO=&TXTDAILY%3B13621=&TXTPARAMETER%3BTEMP_ID%3B13621%3BI=&TXTPARAMETER%3BMAP 000012784%3B13651%3BI=&TXTPARAMETER%3BMAP000012785%3B13651%3BI=&TXTPARAMETER%3BMAP000012786%3B13651%3BO=&TXTDAILY%3B13651=&TXTPARAMETER%3BTEMP_ID%3B13651%3BI=&TXTPARAMETER%3BMAP000012784%3B13670%3BI=&TXTPARAMETER%3BMAP000012785%3B13670%3BI=&TXTPARAMETER%3BMAP000012786%3B13670%3BO=&TX
TDAILY%3B13670=&TXTPARAMETER%3BTEMP_ID%3B13670%3BI=&TXTPARAMETER%3BMAP000012784%3B13689%3BI=&TXTPARAMETER%3BMAP000012785%3B13689%3BI=&TXTPARAMETER%3BMAP000012786%3B13689%3BO=&TXTDAILY%3B13689=&TXTPARAMETER%3BTEMP_ID%3B13689%3BI=&TXTPARAMETER%3BMAP000012787%3B0%3BA=&TXTPARAMETER%3BMAP000012788%3B0%3BA=&TXTPARAMETER%3BMAP000012789%3B0%3BA=&TXTDAILY%3BT EMP_ID%3B0=&TXTPARAMETER%3BTEMP_ID%3B0%3BI=GET
is not defined in RFC 2068 and is not supported by the Servlet API
at
com.ibm.servlet.engine.webapp.WebAppDispatcherResponse.sendError(WebAppDispatcherResponse.java:97)
at
com.ibm.servlet.engine.webapp.HttpServletResponseProxy.sendError(HttpServletResponseProxy.java:66)
at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
at
com.ibm.servlet.dynacache.CacheHook.handleFragment(CacheHook.java(Compiled
Code))
at
com.ibm.servlet.dynacache.CacheHook.handleServlet(CacheHook.java(Compiled
Code))
at
com.ibm.servlet.dynacache.CacheProxyServlet.service(CacheProxyServlet.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java(Compiled
Code))
at
com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java(Compiled
Code))
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java(Compiled
Code))
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java(Compiled
Code))
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java(Compiled
Code))
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java(Compiled
Code))
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java(Compiled
Code))
at
com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java(Compiled
Code))
at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java(Compiled
Code))
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java(Compiled Code))
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122)

3) Exception 3 (in IBM Http Server access.log)
AP000012784%3B13371%3BI=&TXTPARAMETER%3BMAP000012785%3B13371%3BI=&TXTPARAMETER%3BMAP000012786%3B13371%3BO=&TXTDAILY%3B13371=&TXTPARAMETER%3BTEMP_ID%3B13371%3BI=&TXTPARAMETER%3BMAP000012784%3B13621%3BI=&TXTPARAMETER%3BMAP000012785%3B13621%3BI=&TXTPARAMETER%3BMAP000012786%3B13621%3BO=&TXTDAILY%3B13621=&TXTPARAMETER%3BTEMP_ID%3B13621%3BI=&TXTPARAMETER%3BMAP 000012784%3B13651%3BI=&TXTPARAMETER%3BMAP000012785%3B13651%3BI=&TXTPARAMETER%3BMAP000012786%3B13651%3BO=&TXTDAILY%3B13651=&TXTPARAMETER%3BTEMP_ID%3B13651%3BI=&TXTPARAMETER%3BMAP000012784%3B13670%3BI=&TXTPARAMETER%3BMAP000012785%3B13670%3BI=&TXTPARAMETER%3BMAP000012786%3B13670%3BO=&TX
TDAILY%3B13670=&TXTPARAMETER%3BTEMP_ID%3B13670%3BI=&TXTPARAMETER%3BMAP000012784%3B13689%3BI=&TXTPARAMETER%3BMAP000012785%3B13689%3BI=&TXTPARAMETER%3BMAP000012786%3B13689%3BO=&TXTDAILY%3B13689=&TXTPARAMETER%3BTEMP_ID%3B13689%3BI=&TXTPARAMETER%3BMAP000012787%3B0%3BA=&TXTPARAMETER%3BMAP000012788%3B0%3BA=&TXTPARAMETER%3BMAP000012789%3B0%3BA=&TXTDAILY%3BT EMP_ID%3B0=&TXTPARAMETER%3BTEMP_ID%3B0%3BI=GET method type is invalid

The above freaky behavior is there only when the Application is accessed via the HTTP Server. The application behavior is proper in the backup environment, in the uat environment, and in the Production environment when the application is accessed by bypassing the HTTP Server.

There are some other applications also which have been installed on the Production and the backup server. The following activities were carried out as part of problem resolution of the freaky application behavior when accessed via Http Server on the Production m/c:
1) The global CLASSPATH and PATH settings (Accessible via My Computer -> Properties -> Advanced -> Environment Variables) were removed and the HTTP Server was restarted. This made no difference and the freaky behavior continued when accessed via HTTP Server.
2) The processes running on the production server were compared with those running on the backup server. No process which seemingly could made a difference to the behavior of the HTTP Server was found.

The activities carried out till now and the observations made in the last few days suggest that the problem occurs only on the machine that is made the production server. This conclusion has been arrived at owing to the following observations:
a) The application runs smoothly on the uat and the backup environment.
b) When the Tech Team were facing some problems with other applications installed on the Production m/c, they tried reinstalling the App Server to see if the problems goes away, but when that didn't happen. They made a new Production Server and installed everything on that m/c, whereas, the previous Production m/c was made the backup server. After this was done, the freaky behavior problem was still there on the newly made Production m/c but was not found on the backup server (on backup server the Application Server was reinstalled as stated above).

Assuming the above to be correct, the question that arises is "What is it that is making application behave freakily? or What is it that is affecting the HTTP Server behavior?". To find the answer of these the activities listed above were tried but they were of no avail. Now what lefts to be seen is an introspection of the installation of the other applications on the Production M/c or an introspection of the installation of the App Server and other softwares installed on the m/c.
Please help us if you have faced this problem?
Kindly suggest as to what can be done to resolve the problem as we as support team do not have the privileges to do the introspection.
The freaky behavior has been identified/reported in only 3-4 screens and not all the screens.
The problem has been encountered by all users and is not browser specific

Regards,
Rahul
reply
    Bookmark Topic Watch Topic
  • New Topic