Hi Joseph, there is of course no way how JMeter can interact directly with your forwarding-chain. So there must be parameters missing for your "whateveraction.do". Obviously some parameters are missing in your request and therefore are not set from inside your servlet prior to the JSP. You should check carefully where the missing parameter is set under "normal" circumstances and what conditions have to be met therefore. After that you should see what is missing from inside of JMeter. Maybe you have to tick "Encode" or to tick "Include Equals" (BTW: Haven't found anything on this one) to pass the parameters as wanted.
Greetings, Wolfram > -----Urspr�ngliche Nachricht----- > Von: Joseph chowalloor [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 22. Januar 2003 06:15 > An: JMeter Users List > Betreff: Re: AW: Jmeter -SESSION problem > > > Im calling the servlet alias(say blabla.do) only. > this jsp is the last member in the loop.its going through a > front controller > ,htmlAction class, ejbcontroller > coming back to frontcontroller then to template mechanism > then to the this > jsp. > Its going through all other classes perfectly fine but this jsp. > Thanks > Joseph > > > > ----- Original Message ----- > From: "Wolfram Rittmeyer" <[EMAIL PROTECTED]> > To: "'JMeter Users List'" <[EMAIL PROTECTED]> > Sent: Tuesday, April 01, 2003 9:15 PM > Subject: AW: AW: Jmeter -SESSION problem > > > > Well, obviously there is neither an attribute named > > "FilterEventResponse" > > nor one named "EventResponse". So where is it set? > > > > From your mail I guess you use forwarding from your servlet. So if > > that's > > the case you have to call the servlet (or its alias) not > the JSP-page > > from > > within JMeter. The servlet is than setting the request-attributes, > > forwards > > to your JSP and you get the contents of the JSP-page as the content > > displayed in JMeter. > > > > Greetings, > > > > Wolfram > > > > > > > > > > > > > -----Urspr�ngliche Nachricht----- > > > Von: Joseph chowalloor [mailto:[EMAIL PROTECTED] > > > Gesendet: Dienstag, 21. Januar 2003 16:28 > > > An: JMeter Users List; [EMAIL PROTECTED] > > > Betreff: Re: AW: Jmeter -SESSION problem > > > > > > > > > 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(_INTL > > > PP_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(St > > rictLifecycleServlet.java:317) > > > > > > at > > > com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(S > > trictLifecycleServlet.java:110) > > > > > > at > > > com.ibm.servlet.engine.webapp.ServletInstance.service(ServletM > > anager.java:472) > > > > > > at > > > com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispa > > > tch(ServletManager.java:1012) > > > > > > at > > > com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatc > > > h(ServletManager.java:913) > > > > > > at > > > com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWe > > > bAppDispatch(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.doEn > > > dTag(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(StrictL > > ifecycleServlet.java:297) > > > > > > at > > > com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(S > > trictLifecycleServlet.java:110) > > > > > > at > > > com.ibm.servlet.engine.webapp.ServletInstance.service(ServletM > > anager.java:472) > > > > > > at > > > com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispa > > > tch(ServletManager.java:1012) > > > > > > at > > > com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatc > > > h(ServletManager.java:913) > > > > > > at > > > com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWe > > > bAppDispatch(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.ins > > > ertTemplate(TemplateServlet.java:362) > > > > > > at > > > com.bla.bla.partspricing.waf.view.template.TemplateServlet.pro > > > cess(TemplateServlet.java:306) > > > > > > at > > > com.bla.bla.partspricing.waf.view.template.TemplateServlet.doP > > > ost(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(StrictL > > ifecycleServlet.java:297) > > > > > > at > > > com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(S > > trictLifecycleServlet.java:110) > > > > > > at > > > com.ibm.servlet.engine.webapp.ServletInstance.service(ServletM > > anager.java:472) > > > > > > at > > > com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispa > > > tch(ServletManager.java:1012) > > > > > > at > > > com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatc > > > h(ServletManager.java:913) > > > > > > at > > > com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWe > > > bAppDispatch(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.ScreenFlowMan > > > ager.forwardToNextScreen(ScreenFlowManager.java:179) > > > > > > at > > > com.bla.bla.partspricing.waf.controller.web.MainServlet.doProc > > > ess(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(StrictL > > ifecycleServlet.java:297) > > > > > > at > > > com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(S > > trictLifecycleServlet.java:110) > > > > > > at > > > com.ibm.servlet.engine.webapp.ServletInstance.service(ServletM > > anager.java:472) > > > > > > at > > > com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispa > > > tch(ServletManager.java:1012) > > > > > > at > > > com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatc > > > h(ServletManager.java:913) > > > > > > at > > > com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWe > > > bAppDispatch(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(WebAppInvok > > > er.java:91) > > > > > > at > > > com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook( > > WebAppInvoker.java:184) > > > > > > at > > > com.ibm.servlet.engine.invocation.CachedInvocation.handleInvoc > > > ation(CachedInvocation.java:67) > > > > > > at > > > com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByU > > > RI(ServletRequestProcessor.java:122) > > > > > > at > > > com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.servi > > > ce(OSEListener.java:315) > > > > > > at > > > com.ibm.servlet.engine.http11.HttpConnection.handleRequest(Htt > > pConnection.java:60) > > > > > > at > > > com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnec > > tion.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" <[EMAIL PROTECTED]> > > > To: "JMeter Users List" <[EMAIL PROTECTED]> > > > 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 > > > > [EMAIL PROTECTED] > > > > Yahoo IM: mstover_ya > > > > ICQ: 152975688 > > > > AIM: mstover777 > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
