"Slava Imeshev" wrote in message
news:3f0c6bef$1@newsgroups.bea.com...
| Hi Milind,
|
| Petstore used to be not very thread safe, not to mention that
| it's main purpose is solely educational. I doubt it's a good
| application for comparing tools.
|
| As per this particular case - there can be a bug in Petstore. Also
| it's possible load runner uses the same JSESSIONID for all
| calls, so for petstore it will be the same client accessing it from
| multiple places. Though, as it fails on this situation, it's a bug
| in the petstore anyway.
|
| Regards,
|
| Slava Imeshev
|
|
| "Milind Prabhu" wrote in message
| news:3f0b4eea$1@newsgroups.bea.com...
| >
| > Hi,
| > We are using LoadRunner with the Java Petstore application on BEA 7.0 to
| compare
| > a few application monitoring tools, and we are stranded with a problem -
| When
| > we record a LoadRunner script to simply sign in, and then signoff, it
runs
| fine
| > for one user. However, when we simulate a load of 2 or more users it
fails
| with
| > an exception [details below]. It seems that the same session is being
used
| for
| > multiple users.
| >
| > Is there any special setting required in Load Runner / BEA to make this
| work?
| >
| > ================================================== ========
| > <101020>
| <[ServletContext(id=2634245
| > ,name=petstore,context-path=/petstore)] Servlet failed with Exception
| > java.lang.NullPointerException
| > at
| com.sun.j2ee.blueprints.petstore.controller.web.Si gnOnNotifier.attrib
| > uteAdded(SignOnNotifier.java:71)
| > at
| weblogic.servlet.internal.WebAppServletContext.not ifySessionAttribute
| > Change(WebAppServletContext.java:2327)
| > at
| weblogic.servlet.internal.session.SessionContext.n otifySessionAttribu
| > teChange(SessionContext.java:299)
| > at
| weblogic.servlet.internal.session.SessionData.setA ttribute(SessionDat
| > a.java:528)
| > at
| com.sun.j2ee.blueprints.signon.web.SignOnFilter.va lidateSignOn(SignOn
| > Filter.java:134)
| > at
| com.sun.j2ee.blueprints.signon.web.SignOnFilter.do Filter(SignOnFilter
| > java:84)
| > at
| weblogic.servlet.internal.FilterChainImpl.doFilter (FilterChainImpl.ja
| > va:27)
| > at
| com.sun.j2ee.blueprints.encodingfilter.web.Encodin gFilter.doFilter(En
| > codingFilter.java:46)
| > at
| weblogic.servlet.internal.FilterChainImpl.doFilter (FilterChainImpl.ja
| > va:27)
| > at
| weblogic.servlet.internal.WebAppServletContext$Ser vletInvocationActio
| > n.run(WebAppServletContext.java:5451)
| > at
| weblogic.security.service.SecurityServiceManager.r unAs(SecurityServic
| > eManager.java:780)
| > at
| weblogic.servlet.internal.WebAppServletContext.inv okeServlet(WebAppSe
| > rvletContext.java:3105)
| > at
| weblogic.servlet.internal.ServletRequestImpl.execu te(ServletRequestIm
| > pl.java:2588)
| > at weblogic.kernel.ExecuteThread.execute(ExecuteThrea d.java:213)
| > at weblogic.kernel.ExecuteThread.run(ExecuteThread.ja va:189)
| > >
| > ================================================== ============
| >
| > Thanks in anticipation.
| >
| > Regards,
| > Milind Prabhu
|
|

This is either the application design or a load runner scripting issue.
Comment out the line in your script that has the following:

web_add_cookie("JSESSIONID=2W9HghjJY2yN6p83N2Plv5r1w4MNDhejbvsGvIq zZ1EBeLXML
00h!-1677189251!-1407448204!7001!7002; DOMAIN={target_srv}");

Load Runner is set up to handle session cookies. You also probably want to
read the documentation and set up IP spoofing on the box to simulate
multiple machines.

ken k