You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "sabitha gopal pandit (JIRA)" <de...@myfaces.apache.org> on 2009/04/08 14:41:13 UTC
[jira] Created: (TRINIDAD-1450) tag causes deadlock on
weblogic 9.2 cluster when used with el-impl-1.0.jar.
<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.
[jira] Commented: (TRINIDAD-1450) tag causes deadlock
on weblogic 9.2 cluster when used with el-impl-1.0.jar.
Posted by "Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698796#action_12698796 ]
Matthias Weßendorf commented on TRINIDAD-1450:
----------------------------------------------
looks like an issue in weblogic, as stated here:
http://markmail.org/message/d6jixem3tefuzuh6
and the entire thread.
> <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
> Attachments: createnewuser.jspx, nohup.rar
>
>
> 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, or on WAS Cluster.
>
>
> 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.
[jira] Commented: (TRINIDAD-1450) tag causes deadlock
on weblogic 9.2 cluster when used with el-impl-1.0.jar.
Posted by "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=12697068#action_12697068 ]
sabitha gopal pandit commented on TRINIDAD-1450:
------------------------------------------------
You're correct this <f:varbatim><script> tags also ended up with the same issue.
I used samurai tool to analyize the thread dump and found there is no deadlock, but the threads are in blocked state.
I have attached the thread dump report for your reference.
> <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.
[jira] Commented: (TRINIDAD-1450) tag causes deadlock
on weblogic 9.2 cluster when used with el-impl-1.0.jar.
Posted by "Max Starets (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697032#action_12697032 ]
Max Starets commented on TRINIDAD-1450:
---------------------------------------
I wonder if ithisis specific to trh:script...
Could you try using f:verbatim:
<f:varbatim>
<script type='text/javascript' src='your source '></;script>
</f:verbatim>
I expect that the result should be the same, in which case we need to ask WLS folks to see what is going
in with authentication hanging in a clustered environment.
Max
> <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.
[jira] Commented: (TRINIDAD-1450) tag causes deadlock
on weblogic 9.2 cluster when used with el-impl-1.0.jar.
Posted by "Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728010#action_12728010 ]
Matthias Weßendorf commented on TRINIDAD-1450:
----------------------------------------------
looks like this is a bug in the container. Trinidad can't do much here. sorry. I think you need to report the bug on a different channel
> <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
> Attachments: createnewuser.jspx, nohup.rar
>
>
> 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, or on WAS Cluster.
>
>
> 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.
[jira] Resolved: (TRINIDAD-1450) tag causes deadlock
on weblogic 9.2 cluster when used with el-impl-1.0.jar.
Posted by "Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Weßendorf resolved TRINIDAD-1450.
------------------------------------------
Resolution: Invalid
> <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
> Attachments: createnewuser.jspx, nohup.rar
>
>
> 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, or on WAS Cluster.
>
>
> 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.
[jira] Commented: (TRINIDAD-1450) tag causes deadlock
on weblogic 9.2 cluster when used with el-impl-1.0.jar.
Posted by "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=12698688#action_12698688 ]
sabitha gopal pandit commented on TRINIDAD-1450:
------------------------------------------------
The issue has became very critical for us, as the release cycle is about to be over in next 2 weeks. I appreciate if Trinidad updates us on this?
> <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
> Attachments: createnewuser.jspx, nohup.rar
>
>
> 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.
[jira] Commented: (TRINIDAD-1450) tag causes deadlock
on weblogic 9.2 cluster when used with el-impl-1.0.jar.
Posted by "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=12697770#action_12697770 ]
sabitha gopal pandit commented on TRINIDAD-1450:
------------------------------------------------
I tried removing the <trh:script> tag completely and it's reference from the jsp, and found it still the thread still gets stuck.
It means the issue is not with the <trh:script> or any other similar tags, but is some where else.
here are the logs:
<Apr 10, 2009 1:43:49 PM IST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "648" seconds working on the request "Http Request: /Advisor/faces/iAdvisorWeb/bundles/profilemanager/jsf/usersandgroups/createnewuser.jspx", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
java.lang.Object.wait(Native Method)
weblogic.rjvm.ResponseImpl.waitForData(ResponseImpl.java:73)
weblogic.rjvm.ResponseImpl.getTxContext(ResponseImpl.java:100)
weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:109)
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
weblogic.cluster.replication.ReplicationManager_920_WLStub.create(Unknown Source)
weblogic.cluster.replication.ReplicationManager.trySecondary(ReplicationManager.java:658)
weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java:630)
weblogic.cluster.replication.ReplicationManager.updateSecondary(ReplicationManager.java:556)
weblogic.servlet.internal.session.ReplicatedSessionData.syncSession(ReplicatedSessionData.java:516)
weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:82)
weblogic.servlet.internal.ServletRequestImpl$SessionHelper.syncSession(ServletRequestImpl.java:2485)
weblogic.servlet.internal.ServletRequestImpl$SessionHelper.syncSession(ServletRequestImpl.java:2460)
weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1279)
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1353)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
<Apr 10, 2009 1:43:49 PM IST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "608" seconds working on the request "Http Request: /Advisor/iAdvisorWeb/bundles/ic/skins/FND/images/cafebad.gif", 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)
> <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
> Attachments: createnewuser.jspx, nohup.rar
>
>
> 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.
[jira] Commented: (TRINIDAD-1450) tag causes deadlock
on weblogic 9.2 cluster when used with el-impl-1.0.jar.
Posted by "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.