[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2864) Injection not working with concurrent clients

Pete Muir (JIRA) jira-events at lists.jboss.org
Sat Oct 4 11:45:20 EDT 2008


     [ https://jira.jboss.org/jira/browse/JBSEAM-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir closed JBSEAM-2864.
-----------------------------

    Resolution: Out of Date


This is fixed in trunk, please test.

> Injection not working with concurrent clients
> ---------------------------------------------
>
>                 Key: JBSEAM-2864
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-2864
>             Project: Seam
>          Issue Type: Bug
>          Components: Core, Performance and Scalability
>    Affects Versions: 2.0.1.CR1, 2.0.1.CR2, 2.0.1.GA
>         Environment: Jboss AS 4.2.2.GA, Windows
>            Reporter: Marcell Barbacena
>         Attachments: myproject.zip, Performance.jmx
>
>
> When I was loading testing my application I was getting some NPE.
> I narrowed down the error and created the example app based on a seam-gen one (just stripped the lib directory).
> Basically, what I want to execute the place GET at the following URLs:
> http://localhost:8080/myproject/performance/startsession.seam
> http://localhost:8080/myproject/performance/start.seam
> http://localhost:8080/myproject/performance/search.seam?parameter=1&cid=2
> http://localhost:8080/myproject/performance/end.seam?cid=2
> If after you start jboss you execute the above it goes ok. The debug page shows that the long-running conversation is gone and everything is ok.
> Then I created a JMeter test, just capturing the "cid" from start, and use it at search and end page (see attached jmeter test). If you run the script with 1 thread no loop, it goes ok. If you run with 5 (in my pc) it goes ok. But when you put more then 20, it starts to get NPE at SimpleAction#search when it calls the DAO.
> The log at search.xhtml shows the error and the sysos at SimpleAction#search shows it as well.
> Please, provide a workaround in 2.0.1.CR1.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the seam-issues mailing list