jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph chowalloor" <joseph_chowall...@usswi.com>
Subject Re: AW: Jmeter -SESSION problem
Date Tue, 21 Jan 2003 15:27:59 GMT
Hi
Im using jmeter to test a j2ee application
If i call the program through the browser it works perferctly fine...problem comes when i
test using the Jmeter

here is the jsp code that creating problem

//*******************************
    if(request.getAttribute("FilterEventResponse") != null)
    {
        eventResponse = (EventResponse)request.getAttribute("FilterEventResponse");
        
    }
    else  
    {
        eventResponse = (EventResponse)request.getAttribute("EventResponse");
        
    }
    String eventName = eventResponse.getEventName();

//****************************************

the problem is  eventResponse in the above code when im running jmeter is null so when in
call eventResponse.getEventName(); it will create problem
is there any restriction in getting request.getAttribute() ?
It is set from a servlet in the execution loop,So im not setting it from the testplan

here is the error im getting.
javax.servlet.ServletException

at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:604)

at bla.bla._INTLPP_0005fpartsPricingTitle_jsp_3._jspService(_INTLPP_0005fpartsPricingTitle_jsp_3.java:258)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:142)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.java:300)

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.java:827)

at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:167)

at com.ibm.servlet.engine.webapp.ServicingServletState.service(StrictLifecycleServlet.java:317)

at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.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.java:913)

at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:523)

at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:282)

at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.include(WebAppRequestDispatcher.java:119)

at com.bla.bla.partspricing.waf.view.template.tags.InsertTag.doEndTag(InsertTag.java:112)

at _templateIntl_jsp_1._jspService(_templateIntl_jsp_1.java:129)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:142)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.java:300)

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.java:827)

at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:167)

at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:297)

at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.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.java:913)

at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:523)

at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:282)

at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:112)

at com.bla.bla.partspricing.waf.view.template.TemplateServlet.insertTemplate(TemplateServlet.java:362)

at com.bla.bla.partspricing.waf.view.template.TemplateServlet.process(TemplateServlet.java:306)

at com.bla.bla.partspricing.waf.view.template.TemplateServlet.doPost(TemplateServlet.java:160)

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(StrictLifecycleServlet.java:167)

at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:297)

at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.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.java:913)

at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:523)

at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:282)

at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:112)

at com.bla.bla.partspricing.waf.controller.web.flow.ScreenFlowManager.forwardToNextScreen(ScreenFlowManager.java:179)

at com.bla.bla.partspricing.waf.controller.web.MainServlet.doProcess(MainServlet.java:160)

at com.bla.bla.partspricing.waf.controller.web.MainServlet.doPost(MainServlet.java:134)

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(StrictLifecycleServlet.java:167)

at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:297)

at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.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.java:913)

at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:523)

at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:282)

at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.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(CachedInvocation.java:67)

at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:122)

at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:315)

at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java: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)

Thanks

Joseph





----- Original Message ----- 
From: "Mike Stover" <mstover1@apache.org>
To: "JMeter Users List" <jmeter-user@jakarta.apache.org>
Sent: Tuesday, April 01, 2003 6:50 PM
Subject: Re: AW: Jmeter -SESSION problem


> Except there's no need to know the cookie name or anything.  The cookiemanager 
> receives and returns cookies just like your browser.  The only time you need to 
> manually add cookies to the cookie manager is if you have a specific need to 
> initialize the cookies to some particular value
> 
> -Mike
> 
> On 1 Apr 2003 at 13:14, Wolfram Rittmeyer wrote:
> 
> > There are two ways how a servlet-container can deal with HttpSessions: The
> > one way is to transfer a cookie with each request (you do not have to
> > programm this, this is the default behaviour of at least most of the
> > JSP-/Servlet-Containers) or you have to use URL-Rewriting which needs
> > additional programming but has the advantage of not relying on cookies on
> > the client-side.
> > 
> > Therefore it is highly probable that you are using cookies as a means to
> > deal with cookies. For the CookieyManager to work properly you have to know
> > the cooky-name. Tomcat and JRun use "jsessionid" as the name of the cooky by
> > default. You should try with this one in the CookyManager.
> > 
> > Greetings,
> > 
> > Wolfram
> > 
> 
> 
> 
> --
> Michael Stover
> mstover1@apache.org
> Yahoo IM: mstover_ya
> ICQ: 152975688
> AIM: mstover777
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> 
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message