Sorry if this is covered elsewhere, I tried searching around without much luck
so...
Since Stripes ActionBeans have getters/setters for the request params, and if
we want to get at the resulting DAO object in the ForwardResolution JSP, we
also need getter/setter for that object in the Action as well, then there
cannot be thread safety it seems, under load.
Using JMeter I get multiple threads(users) calling common Stripes Action Beans
with different values in the request parameters. Inspecting the XML responses,
which are created by the ForwardResolution JSP, it appears that the data
referenced with EL in the JSP, shows that the data belongs to another thread
and not the one that issued the request I am inspecting. This is likely due to
race condition and at the moment the JSP produces the response, another thread
may have already caused changes to the request parameters and/or the DAO object
contained in the Action as well.
Even while the JMeter tests are running, I can invoke similar requests using a
browser and sometimes see data in the response that only could have been
supplied by the JMeter test and not what I submitted in the browser.
I'm expecting I'm missing something obvious, but would like a little help
finding what that is.
Thanks,
Jeff
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
