[jira] Commented: (TRINIDAD-1450) tag causes deadlock on weblogic 9.2 cluster when used with el-impl-1.0.jar.

["sabitha gopal pandit (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/TRINIDAD-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697003#action_12697003 ] 

sabitha gopal pandit commented on TRINIDAD-1450:
------------------------------------------------

Release of the application is round the corner and this is a blocker for the release

> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used with el-impl-1.0.jar.
> ----------------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-1450
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1450
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Facelets
>         Environment: Weblogic 9.2 cluster
>            Reporter: sabitha gopal pandit
>            Priority: Blocker
>
> As part facelets1.1.14 the el jars which earlier was el-ri.jar is now el-impl.jar
> We have identified that any JSF page with the <trh:script> which is used to load javascripts  is causing this.
> Simple JSF page works.
> Error observed on console. In the JSF page we get an error when we try to load the pm.js using the tag
>  INFO: Added Library from: zip:/export/vol02/CFS_Cluster/user_projects/domains/Cluster_AutoDomain/./servers/ManagedServer_1/stage/chordiant/chordiant/Advisor/WEB-INF/lib/trinidad-impl-1.0.10.jar!/META-INF/trh.taglib.xml
> <Apr 3, 2009 5:03:36 PM IST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "616" seconds working on the request "Http Request: /Advisor/iAdvisorWeb/bundles/profilemanager/scripts/pm.js", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
>             weblogic.servlet.internal.session.ReplicatedSessionContext.getSessionInternal(ReplicatedSessionContext.java:375)
>             weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSession(ServletRequestImpl.java:2521)
>             weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInternal(ServletRequestImpl.java:2090)
>             weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(ServletRequestImpl.java:2057)
>             weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1189)
>             weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction.run(SecurityModule.java:535)
>             weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
>             weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
>             weblogic.servlet.security.internal.SecurityModule.getUserSession(SecurityModule.java:426)
>             weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:81)
>             weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1920)
>             weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890)
>             weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
>             weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>             weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>  
> The same trinidad version is working fine when used with old el-ri-1.0.jar part jsf-facelets-1.1.11.jar
>  
> Note: Every thing works fine if deployed on non-clustered weblogic environment.
>  
>  
> Environment Details:
>  
> trinidad-api-1.0.10.jar
> trinidad-impl-1.0.10.jar
> el-api-1.0.jar
> el-impl-1.0.jar
> jsf-facelets-1.1.14.jar

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.