Wolf-Dieter Fink [http://community.jboss.org/people/wdfink] created the discussion "Re: Duplicate request threads are received at JBoss during Load Testing only for some value of maxThreads" To view the discussion, visit: http://community.jboss.org/message/568555#568555 -------------------------------------------------------------- Ok, you talk about HTTP requests. In this case the request is finished with sending the result, all transactions and entities should be persistent (exept if you use statefull session with extended persistence context). For me it sounds like a concurrency problem when generating the id, have you checked the load testing whether the id is duplicated here because of multithreading and the requests are send twice? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/568555#568555] Start a new discussion in Performance Tuning at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Rupesh Bhadeshiya [http://community.jboss.org/people/rupesh.bhadeshiya] created the discussion "Re: Duplicate request threads are received at JBoss during Load Testing only for some value of maxThreads" To view the discussion, visit: http://community.jboss.org/message/569236#569236 -------------------------------------------------------------- HI. We have got solution to this issue. The problem was within application: A spring bean was the cause of the issue: This spring beab was responsible for extracting data from HTTP request and forming application specific request and putting it in HttpSession (from which other business objects would take it and use it). It was declared as singleton="true" hence its only one instance would be created and shared by all the threads entering in the code. As soon as we changed its configuration to singleton="false" and in code wherever using it, always look up it from Spring bean context (and hence each time get a new instance of it), this issue got resolved. But to come to this conclusion, we took a lot of logs : Logs at Load-Testing client (Grinder in our case) - to know if it is sending duplicate requests, then took logs at Apache Load Balancer level (to know whether duplicate requests are reaching at its level), then at JBoss level (accessor logs) to know if there also duplicate requests are reaching, and then took logs at various classes at application level (in order of they receving request and processing it: Web Filter, WebWork based our interceptors, and then to finally action class). There we come to know that no duplicate requests were received upto a particular interceptor's intercept() method entry and duplicates were noted at exit of that method ... and further micro analysis revealed the above said spring bean. I thought posting answer to this issue might also help other people. Thanks a lot to all for all help. Thanks & BR, Rupesh -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/569236#569236] Start a new discussion in Performance Tuning at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]