[jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1401) Portal Unresponsiveness With Conection Pool Bottleneck

[Mike Millson (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1401?page=comments#action_12364096 ] 
            
Mike Millson commented on JBPORTAL-1401:
----------------------------------------

The test is able to complete without error some times when the test is run after access the default page. The customer noted in the related support case that one way of reproducing the error is to run the test without first accessing the default page in the browser. However, they were able to reproduce it even after priming the default page. I was also, however, not consistently. So maybe reproducing it after priming the default page is dependent on other factors such as system load.

I ran the test without priming the default page and was able to reproduce the issue. Then I removed the CMS components as we discussed and ran the test without first accessing the default page, and the test ran without error. I ran the test several more times, all without error.

> Portal Unresponsiveness With Conection Pool Bottleneck
> ------------------------------------------------------
>
>                 Key: JBPORTAL-1401
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1401
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Security
>    Affects Versions: 2.4.1 SP1
>         Environment: RHEL 5
> Windows XP
>            Reporter: Mike Millson
>         Assigned To: Julien Viet
>         Attachments: JDBCConnectionPoolTest.java, mgm-thread-dump.txt, portal-mysql-ds.xml, portal-oracle-ds.xml
>
>
> Observed Behavior:
> When the connection pool is not adequately sized, the portal freezes. A thread dump shows that a single http connector thread holds the lock to java.security.Permissions.implies(Permission) and is waiting BlockingTimeoutMillis to get a connection. Almost all the other http threads are blocked waiting to aquire the lock to java.security.Permissions.implies(Permission). Apparently the thread waiting for a connection needs a connection to look up the permissions in the database.
> Expected Behavior:
> The portal should not become unresponsive. Portal 2.6 CR2 does not freeze up when the same test is run.
> I will attach the test case, thread dump, and datasource.

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