You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@myfaces.apache.org by Sabitha Gopal Pandit <Sa...@Chordiant.com> on 2009/04/08 14:02:43 UTC

tag causes deadlock on weblogic 9.2 cluster

Hi ALL,

 

We are facing this strange issue. We are in the release phase of our
application. 

 

Any .jspx containing 

<trh:script> tag causes deadlock on weblogic 9.2 cluster when used with
el-impl-1.0.jar.

 

The same trinidad version is working fine when used with old
el-ri-1.0.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

 

Quick response is very highly appreciated 

 

Thanks,

Sabitha

Re: tag causes deadlock on weblogic 9.2 cluster

Posted by Matthias Wessendorf <ma...@apache.org>.

Sabitha,

I wonder if you could upload a simple re-producable test-case.
The Weblogic folks asked for that on an internal bug. Also is
this true on Weblogic 10? I guess you have not tried that,
which is fine ;-)

-Matthias

On Wed, Apr 8, 2009 at 4:22 PM, Matthias Wessendorf <ma...@apache.org> wrote:
> Sabitha,
>
> can you take a look at the bug ?
> Max Starets added a comment.
>
> Thx,
> Matthias
>
> On Wed, Apr 8, 2009 at 2:42 PM, Sabitha Gopal Pandit
> <Sa...@chordiant.com> wrote:
>> I have raised TRINIDAD-1450 for this issue
>>
>> Thanks,
>> Sabitha
>>
>> -----Original Message-----
>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>> Sent: Wednesday, April 08, 2009 6:08 PM
>> To: MyFaces Development
>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>
>> On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
>> <Sa...@chordiant.com> wrote:
>>> Can I know the URL to create the JIRA?
>>
>> https://issues.apache.org/jira/browse/TRINIDAD
>>
>> -M
>>
>>>
>>> Thanks,
>>> Sabitha
>>>
>>> -----Original Message-----
>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>>> Sent: Wednesday, April 08, 2009 6:02 PM
>>> To: MyFaces Development
>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>
>>> Hey Sabitha,
>>>
>>> can you create a JIRA ticket ?
>>> Once done, I'll ask our WLS folks to take a look...
>>>
>>> thanks,
>>> matthias
>>>
>>> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
>>> <Sa...@chordiant.com> wrote:
>>>> Hi Matthias,
>>>>
>>>> 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/t
>>>> rinidad-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.getSessionInt
>>>> ernal(ReplicatedSessionContext.java:375)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>>>> on(ServletRequestImpl.java:2521)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>>>> ernal(ServletRequestImpl.java:2090)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>>>> rvletRequestImpl.java:2057)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>>>> pl.java:1189)
>>>>
>>>> weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>>>> .run(SecurityModule.java:535)
>>>>
>>>> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>>>> bject.java:321)
>>>>
>>>> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>>>> )
>>>>
>>>> weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>>>> yModule.java:426)
>>>>
>>>> weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>>>> rvletSecurityManager.java:81)
>>>>
>>>> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>>>> letContext.java:1920)
>>>>
>>>> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>>>> ext.java:1890)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>>>> :1344)
>>>>            weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>>>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>>>
>>>> Thanks,
>>>> Sabitha
>>>>
>>>> -----Original Message-----
>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
>>>> Matthias Wessendorf
>>>> Sent: Wednesday, April 08, 2009 5:35 PM
>>>> To: MyFaces Development
>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>>
>>>> Hi,
>>>>
>>>> so, the "old" ri is "clean" ?
>>>> What is the dump ?
>>>>
>>>> can you post some more information ?
>>>>
>>>> Also, does this reproduce with a (simple) Trinidad page?
>>>>
>>>> Is it JSP(X) or Facelets ?
>>>>
>>>> -Matthias
>>>>
>>>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>>>> <Sa...@chordiant.com> wrote:
>>>>> Hi ALL,
>>>>>
>>>>>
>>>>>
>>>>> We are facing this strange issue. We are in the release phase of our
>>>>> application.
>>>>>
>>>>>
>>>>>
>>>>> Any .jspx containing
>>>>>
>>>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used
>>>> with
>>>>> el-impl-1.0.jar.
>>>>>
>>>>>
>>>>>
>>>>> The same trinidad version is working fine when used with old
>>>> el-ri-1.0.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
>>>>>
>>>>>
>>>>>
>>>>> Quick response is very highly appreciated
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Sabitha
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Re: tag causes deadlock on weblogic 9.2 cluster

Posted by Matthias Wessendorf <ma...@apache.org>.

so, it is perhaps an issue in the EL.
can you see where it fails ?

If it is an issue in the EL, I guess we can't do much here...


-Matthias

On Tue, Apr 14, 2009 at 10:38 AM, Sabitha Gopal Pandit
<Sa...@chordiant.com> wrote:
>
> Its very strange that only with the upgraded version of the EL jars we are facing this issue. With the earlier version of EL i.e el-ri.jar and el-api.jar everything worked fine.
> Both the versions of the jar were deployed on same version of the weblogic
>
> Thanks,
> Sabitha
>
> -----Original Message-----
> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
> Sent: Tuesday, April 14, 2009 2:05 PM
> To: MyFaces Development; Sabitha Gopal Pandit
> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>
> Hi,
>
> looks like the issue is not really tied to Trinidad.
> It occurs with vanilla JSF as well. Perhaps this
> is a problem in the weblogic core, and not the frameworks ?
>
> -Matthias
>
> On Thu, Apr 9, 2009 at 6:53 AM, Sabitha Gopal Pandit
> <Sa...@chordiant.com> wrote:
>> Hi Matthias,
>>
>> We tried the same but didn't work for us
>>
>> Thanks,
>> Sabitha
>>
>> -----Original Message-----
>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>> Sent: Wednesday, April 08, 2009 7:52 PM
>> To: MyFaces Development
>> Cc: Sabitha Gopal Pandit
>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>
>> Sabitha,
>>
>> can you take a look at the bug ?
>> Max Starets added a comment.
>>
>> Thx,
>> Matthias
>>
>> On Wed, Apr 8, 2009 at 2:42 PM, Sabitha Gopal Pandit
>> <Sa...@chordiant.com> wrote:
>>> I have raised TRINIDAD-1450 for this issue
>>>
>>> Thanks,
>>> Sabitha
>>>
>>> -----Original Message-----
>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>>> Sent: Wednesday, April 08, 2009 6:08 PM
>>> To: MyFaces Development
>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>
>>> On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
>>> <Sa...@chordiant.com> wrote:
>>>> Can I know the URL to create the JIRA?
>>>
>>> https://issues.apache.org/jira/browse/TRINIDAD
>>>
>>> -M
>>>
>>>>
>>>> Thanks,
>>>> Sabitha
>>>>
>>>> -----Original Message-----
>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>>>> Sent: Wednesday, April 08, 2009 6:02 PM
>>>> To: MyFaces Development
>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>>
>>>> Hey Sabitha,
>>>>
>>>> can you create a JIRA ticket ?
>>>> Once done, I'll ask our WLS folks to take a look...
>>>>
>>>> thanks,
>>>> matthias
>>>>
>>>> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
>>>> <Sa...@chordiant.com> wrote:
>>>>> Hi Matthias,
>>>>>
>>>>> 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/t
>>>>> rinidad-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.getSessionInt
>>>>> ernal(ReplicatedSessionContext.java:375)
>>>>>
>>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>>>>> on(ServletRequestImpl.java:2521)
>>>>>
>>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>>>>> ernal(ServletRequestImpl.java:2090)
>>>>>
>>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>>>>> rvletRequestImpl.java:2057)
>>>>>
>>>>> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>>>>> pl.java:1189)
>>>>>
>>>>> weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>>>>> .run(SecurityModule.java:535)
>>>>>
>>>>> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>>>>> bject.java:321)
>>>>>
>>>>> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>>>>> )
>>>>>
>>>>> weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>>>>> yModule.java:426)
>>>>>
>>>>> weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>>>>> rvletSecurityManager.java:81)
>>>>>
>>>>> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>>>>> letContext.java:1920)
>>>>>
>>>>> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>>>>> ext.java:1890)
>>>>>
>>>>> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>>>>> :1344)
>>>>>            weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>>>>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>>>>
>>>>> Thanks,
>>>>> Sabitha
>>>>>
>>>>> -----Original Message-----
>>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
>>>>> Matthias Wessendorf
>>>>> Sent: Wednesday, April 08, 2009 5:35 PM
>>>>> To: MyFaces Development
>>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>>>
>>>>> Hi,
>>>>>
>>>>> so, the "old" ri is "clean" ?
>>>>> What is the dump ?
>>>>>
>>>>> can you post some more information ?
>>>>>
>>>>> Also, does this reproduce with a (simple) Trinidad page?
>>>>>
>>>>> Is it JSP(X) or Facelets ?
>>>>>
>>>>> -Matthias
>>>>>
>>>>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>>>>> <Sa...@chordiant.com> wrote:
>>>>>> Hi ALL,
>>>>>>
>>>>>>
>>>>>>
>>>>>> We are facing this strange issue. We are in the release phase of our
>>>>>> application.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Any .jspx containing
>>>>>>
>>>>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used
>>>>> with
>>>>>> el-impl-1.0.jar.
>>>>>>
>>>>>>
>>>>>>
>>>>>> The same trinidad version is working fine when used with old
>>>>> el-ri-1.0.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
>>>>>>
>>>>>>
>>>>>>
>>>>>> Quick response is very highly appreciated
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Sabitha
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

RE: tag causes deadlock on weblogic 9.2 cluster

Posted by Sabitha Gopal Pandit <Sa...@Chordiant.com>.

Its very strange that only with the upgraded version of the EL jars we are facing this issue. With the earlier version of EL i.e el-ri.jar and el-api.jar everything worked fine. 
Both the versions of the jar were deployed on same version of the weblogic

Thanks,
Sabitha

-----Original Message-----
From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
Sent: Tuesday, April 14, 2009 2:05 PM
To: MyFaces Development; Sabitha Gopal Pandit
Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster

Hi,

looks like the issue is not really tied to Trinidad.
It occurs with vanilla JSF as well. Perhaps this
is a problem in the weblogic core, and not the frameworks ?

-Matthias

On Thu, Apr 9, 2009 at 6:53 AM, Sabitha Gopal Pandit
<Sa...@chordiant.com> wrote:
> Hi Matthias,
>
> We tried the same but didn't work for us
>
> Thanks,
> Sabitha
>
> -----Original Message-----
> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
> Sent: Wednesday, April 08, 2009 7:52 PM
> To: MyFaces Development
> Cc: Sabitha Gopal Pandit
> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>
> Sabitha,
>
> can you take a look at the bug ?
> Max Starets added a comment.
>
> Thx,
> Matthias
>
> On Wed, Apr 8, 2009 at 2:42 PM, Sabitha Gopal Pandit
> <Sa...@chordiant.com> wrote:
>> I have raised TRINIDAD-1450 for this issue
>>
>> Thanks,
>> Sabitha
>>
>> -----Original Message-----
>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>> Sent: Wednesday, April 08, 2009 6:08 PM
>> To: MyFaces Development
>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>
>> On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
>> <Sa...@chordiant.com> wrote:
>>> Can I know the URL to create the JIRA?
>>
>> https://issues.apache.org/jira/browse/TRINIDAD
>>
>> -M
>>
>>>
>>> Thanks,
>>> Sabitha
>>>
>>> -----Original Message-----
>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>>> Sent: Wednesday, April 08, 2009 6:02 PM
>>> To: MyFaces Development
>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>
>>> Hey Sabitha,
>>>
>>> can you create a JIRA ticket ?
>>> Once done, I'll ask our WLS folks to take a look...
>>>
>>> thanks,
>>> matthias
>>>
>>> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
>>> <Sa...@chordiant.com> wrote:
>>>> Hi Matthias,
>>>>
>>>> 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/t
>>>> rinidad-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.getSessionInt
>>>> ernal(ReplicatedSessionContext.java:375)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>>>> on(ServletRequestImpl.java:2521)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>>>> ernal(ServletRequestImpl.java:2090)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>>>> rvletRequestImpl.java:2057)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>>>> pl.java:1189)
>>>>
>>>> weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>>>> .run(SecurityModule.java:535)
>>>>
>>>> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>>>> bject.java:321)
>>>>
>>>> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>>>> )
>>>>
>>>> weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>>>> yModule.java:426)
>>>>
>>>> weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>>>> rvletSecurityManager.java:81)
>>>>
>>>> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>>>> letContext.java:1920)
>>>>
>>>> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>>>> ext.java:1890)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>>>> :1344)
>>>>            weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>>>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>>>
>>>> Thanks,
>>>> Sabitha
>>>>
>>>> -----Original Message-----
>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
>>>> Matthias Wessendorf
>>>> Sent: Wednesday, April 08, 2009 5:35 PM
>>>> To: MyFaces Development
>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>>
>>>> Hi,
>>>>
>>>> so, the "old" ri is "clean" ?
>>>> What is the dump ?
>>>>
>>>> can you post some more information ?
>>>>
>>>> Also, does this reproduce with a (simple) Trinidad page?
>>>>
>>>> Is it JSP(X) or Facelets ?
>>>>
>>>> -Matthias
>>>>
>>>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>>>> <Sa...@chordiant.com> wrote:
>>>>> Hi ALL,
>>>>>
>>>>>
>>>>>
>>>>> We are facing this strange issue. We are in the release phase of our
>>>>> application.
>>>>>
>>>>>
>>>>>
>>>>> Any .jspx containing
>>>>>
>>>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used
>>>> with
>>>>> el-impl-1.0.jar.
>>>>>
>>>>>
>>>>>
>>>>> The same trinidad version is working fine when used with old
>>>> el-ri-1.0.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
>>>>>
>>>>>
>>>>>
>>>>> Quick response is very highly appreciated
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Sabitha
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

RE: tag causes deadlock on weblogic 9.2 cluster

Posted by Rupak Kumar Sah <Ru...@Chordiant.com>.

Forgot to mention the jira no. It's
https://issues.apache.org/jira/browse/TRINIDAD-1450

-----Original Message-----
From: Rupak Kumar Sah [mailto:Rupak.Sah@chordiant.com] 
Sent: Tuesday, April 14, 2009 5:56 PM
To: MyFaces Development
Subject: RE: <trh:script> tag causes deadlock on weblogic 9.2 cluster

Thanks Simon,

This is really very useful information. I'll be raising this issue with
both Sun and Weblogic.

In the meanwhile I appreciate if you put all these information in the
raised jira issue along with the fact that the same issue is found with
Vanila implementation as well.

This would help us as well for any Users facing this issue.

Regards,
Rupak


-----Original Message-----
From: Simon Kitching [mailto:skitching@apache.org] 
Sent: Tuesday, April 14, 2009 4:10 PM
To: MyFaces Development
Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster

No, it seems clear to me that there is a bug in weblogic that is only
triggered under some conditions. The new EL library happens to trigger
these conditions, but the bug is still clearly in weblogic.

I suggest asking the Weblogic support team what datastructures in the
session are not supported for replication, and are expected to cause a
hang. I would expect the answer to be "none", in which case a hang is
*definitely* their problem. Circular references, weak/strong refs etc.
should all be handled by proper replication.

The only *possible* user-created problem I can imagine is with locks. If
perhaps session replication needs to obtain a lock on the Session
object, but the new EL library is obtaining a lock, then never releasing
it, that *would* be a user problem, not weblogic. However it seems
unlikely as it would almost certainly be a "monitor" lock, ie a
synchronized() block. And those locks are always released when the
thread leaves the block. So the only possible way to lock it would be
for a thread to enter an infinite loop or block - but that would be
pretty quickly spotted as it would have obvious effects. Still, it might
be worth looking at what locks are held when the problem occurs.

And anyway, nobody except you has reported this issue, so it doesn't
seem to be a problem on other servlet containers. So again, it's a
weblogic problem. Possibly the new EL code sets up the conditions for
this to be triggered, but the real bug is elsewhere.

Sorry, but the Myfaces list really doesn't seem the right place for this
to be investigated.

Regards, Simon


Matthias Wessendorf schrieb:
> hrm, when replacing the EL jars fixes it (or causes it on the other
direction)
> AND the same issue occurs with vanilla JSF, it is somewhat clear to me
> that the issue is in the EL layer. Do you see where it is deadlocked ?
> 
> -Matthias
> 
> On Tue, Apr 14, 2009 at 11:19 AM, Rupak Kumar Sah
> <Ru...@chordiant.com> wrote:
>> Yeah, it's clearly says the thread is stuck on session replication,
but
>> as the same version of Weblogic works fine with older version of EL
>> jars, hence they would never accept it as their issue at first place.
>>
>> I raised this issue with Sun also, and they says they suggests to
raise
>> it with Trinidad as the issue is with the trinidad components and the
>> same version of jars works fine else where.
>>
>> Suggest us what to do next.
>>
>> -----Original Message-----
>> From: simon.kitching@chello.at [mailto:simon.kitching@chello.at]
>> Sent: Tuesday, April 14, 2009 2:20 PM
>> To: MyFaces Development
>> Cc: Sabitha Gopal Pandit
>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>
>> The stacktrace clearly shows that this is a problem with Weblogic
>> session replication or network configuration and nothing whatsoever
to
>> do with JSF or Myfaces. Data is being stored into the session, and
then
>> when weblogic tries to replicate that data to other members of the
>> cluster a hang is occurring within Weblogic.
>>
>> So please take this discussion to the correct weblogic-specific list
or
>> forum.
>>
>> Thanks,
>> Simon
>>
>> Matthias Wessendorf schrieb:
>>> Hi,
>>>
>>> looks like the issue is not really tied to Trinidad.
>>> It occurs with vanilla JSF as well. Perhaps this
>>> is a problem in the weblogic core, and not the frameworks ?
>>>
>>> -Matthias
>>>
>>> On Thu, Apr 9, 2009 at 6:53 AM, Sabitha Gopal Pandit
>>> <Sa...@chordiant.com> wrote:
>>>> Hi Matthias,
>>>>
>>>> We tried the same but didn't work for us
>>>>
>>>> Thanks,
>>>> Sabitha
>>>>
>>>> -----Original Message-----
>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On
Behalf
>> Of Matthias Wessendorf
>>>> Sent: Wednesday, April 08, 2009 7:52 PM
>>>> To: MyFaces Development
>>>> Cc: Sabitha Gopal Pandit
>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
cluster
>>>>
>>>> Sabitha,
>>>>
>>>> can you take a look at the bug ?
>>>> Max Starets added a comment.
>>>>
>>>> Thx,
>>>> Matthias
>>>>
>>>> On Wed, Apr 8, 2009 at 2:42 PM, Sabitha Gopal Pandit
>>>> <Sa...@chordiant.com> wrote:
>>>>> I have raised TRINIDAD-1450 for this issue
>>>>>
>>>>> Thanks,
>>>>> Sabitha
>>>>>
>>>>> -----Original Message-----
>>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On
Behalf
>> Of Matthias Wessendorf
>>>>> Sent: Wednesday, April 08, 2009 6:08 PM
>>>>> To: MyFaces Development
>>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
>> cluster
>>>>> On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
>>>>> <Sa...@chordiant.com> wrote:
>>>>>> Can I know the URL to create the JIRA?
>>>>> https://issues.apache.org/jira/browse/TRINIDAD
>>>>>
>>>>> -M
>>>>>
>>>>>> Thanks,
>>>>>> Sabitha
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On
>> Behalf Of Matthias Wessendorf
>>>>>> Sent: Wednesday, April 08, 2009 6:02 PM
>>>>>> To: MyFaces Development
>>>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
>> cluster
>>>>>> Hey Sabitha,
>>>>>>
>>>>>> can you create a JIRA ticket ?
>>>>>> Once done, I'll ask our WLS folks to take a look...
>>>>>>
>>>>>> thanks,
>>>>>> matthias
>>>>>>
>>>>>> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
>>>>>> <Sa...@chordiant.com> wrote:
>>>>>>> Hi Matthias,
>>>>>>>
>>>>>>> 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/t
>>>>>>> rinidad-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.getSessionInt
>>>>>>> ernal(ReplicatedSessionContext.java:375)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>>>>>>> on(ServletRequestImpl.java:2521)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>>>>>>> ernal(ServletRequestImpl.java:2090)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>>>>>>> rvletRequestImpl.java:2057)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>>>>>>> pl.java:1189)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>>>>>>> .run(SecurityModule.java:535)
>>>>>>>
>>>>>>>
>>
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>>>>>>> bject.java:321)
>>>>>>>
>>>>>>>
>>
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>>>>>>> )
>>>>>>>
>>>>>>>
>>
weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>>>>>>> yModule.java:426)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>>>>>>> rvletSecurityManager.java:81)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>>>>>>> letContext.java:1920)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>>>>>>> ext.java:1890)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>>>>>>> :1344)
>>>>>>>
>> weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>>>>>>
weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sabitha
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On
>> Behalf Of
>>>>>>> Matthias Wessendorf
>>>>>>> Sent: Wednesday, April 08, 2009 5:35 PM
>>>>>>> To: MyFaces Development
>>>>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
>> cluster
>>>>>>> Hi,
>>>>>>>
>>>>>>> so, the "old" ri is "clean" ?
>>>>>>> What is the dump ?
>>>>>>>
>>>>>>> can you post some more information ?
>>>>>>>
>>>>>>> Also, does this reproduce with a (simple) Trinidad page?
>>>>>>>
>>>>>>> Is it JSP(X) or Facelets ?
>>>>>>>
>>>>>>> -Matthias
>>>>>>>
>>>>>>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>>>>>>> <Sa...@chordiant.com> wrote:
>>>>>>>> Hi ALL,
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> We are facing this strange issue. We are in the release phase
of
>> our
>>>>>>>> application.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Any .jspx containing
>>>>>>>>
>>>>>>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when
>> used
>>>>>>> with
>>>>>>>> el-impl-1.0.jar.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The same trinidad version is working fine when used with old
>>>>>>> el-ri-1.0.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
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Quick response is very highly appreciated
>>>>>>>>
> 
> 
>

RE: tag causes deadlock on weblogic 9.2 cluster

Posted by Rupak Kumar Sah <Ru...@Chordiant.com>.

Thanks Simon,

This is really very useful information. I'll be raising this issue with
both Sun and Weblogic.

In the meanwhile I appreciate if you put all these information in the
raised jira issue along with the fact that the same issue is found with
Vanila implementation as well.

This would help us as well for any Users facing this issue.

Regards,
Rupak


-----Original Message-----
From: Simon Kitching [mailto:skitching@apache.org] 
Sent: Tuesday, April 14, 2009 4:10 PM
To: MyFaces Development
Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster

No, it seems clear to me that there is a bug in weblogic that is only
triggered under some conditions. The new EL library happens to trigger
these conditions, but the bug is still clearly in weblogic.

I suggest asking the Weblogic support team what datastructures in the
session are not supported for replication, and are expected to cause a
hang. I would expect the answer to be "none", in which case a hang is
*definitely* their problem. Circular references, weak/strong refs etc.
should all be handled by proper replication.

The only *possible* user-created problem I can imagine is with locks. If
perhaps session replication needs to obtain a lock on the Session
object, but the new EL library is obtaining a lock, then never releasing
it, that *would* be a user problem, not weblogic. However it seems
unlikely as it would almost certainly be a "monitor" lock, ie a
synchronized() block. And those locks are always released when the
thread leaves the block. So the only possible way to lock it would be
for a thread to enter an infinite loop or block - but that would be
pretty quickly spotted as it would have obvious effects. Still, it might
be worth looking at what locks are held when the problem occurs.

And anyway, nobody except you has reported this issue, so it doesn't
seem to be a problem on other servlet containers. So again, it's a
weblogic problem. Possibly the new EL code sets up the conditions for
this to be triggered, but the real bug is elsewhere.

Sorry, but the Myfaces list really doesn't seem the right place for this
to be investigated.

Regards, Simon


Matthias Wessendorf schrieb:
> hrm, when replacing the EL jars fixes it (or causes it on the other
direction)
> AND the same issue occurs with vanilla JSF, it is somewhat clear to me
> that the issue is in the EL layer. Do you see where it is deadlocked ?
> 
> -Matthias
> 
> On Tue, Apr 14, 2009 at 11:19 AM, Rupak Kumar Sah
> <Ru...@chordiant.com> wrote:
>> Yeah, it's clearly says the thread is stuck on session replication,
but
>> as the same version of Weblogic works fine with older version of EL
>> jars, hence they would never accept it as their issue at first place.
>>
>> I raised this issue with Sun also, and they says they suggests to
raise
>> it with Trinidad as the issue is with the trinidad components and the
>> same version of jars works fine else where.
>>
>> Suggest us what to do next.
>>
>> -----Original Message-----
>> From: simon.kitching@chello.at [mailto:simon.kitching@chello.at]
>> Sent: Tuesday, April 14, 2009 2:20 PM
>> To: MyFaces Development
>> Cc: Sabitha Gopal Pandit
>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>
>> The stacktrace clearly shows that this is a problem with Weblogic
>> session replication or network configuration and nothing whatsoever
to
>> do with JSF or Myfaces. Data is being stored into the session, and
then
>> when weblogic tries to replicate that data to other members of the
>> cluster a hang is occurring within Weblogic.
>>
>> So please take this discussion to the correct weblogic-specific list
or
>> forum.
>>
>> Thanks,
>> Simon
>>
>> Matthias Wessendorf schrieb:
>>> Hi,
>>>
>>> looks like the issue is not really tied to Trinidad.
>>> It occurs with vanilla JSF as well. Perhaps this
>>> is a problem in the weblogic core, and not the frameworks ?
>>>
>>> -Matthias
>>>
>>> On Thu, Apr 9, 2009 at 6:53 AM, Sabitha Gopal Pandit
>>> <Sa...@chordiant.com> wrote:
>>>> Hi Matthias,
>>>>
>>>> We tried the same but didn't work for us
>>>>
>>>> Thanks,
>>>> Sabitha
>>>>
>>>> -----Original Message-----
>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On
Behalf
>> Of Matthias Wessendorf
>>>> Sent: Wednesday, April 08, 2009 7:52 PM
>>>> To: MyFaces Development
>>>> Cc: Sabitha Gopal Pandit
>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
cluster
>>>>
>>>> Sabitha,
>>>>
>>>> can you take a look at the bug ?
>>>> Max Starets added a comment.
>>>>
>>>> Thx,
>>>> Matthias
>>>>
>>>> On Wed, Apr 8, 2009 at 2:42 PM, Sabitha Gopal Pandit
>>>> <Sa...@chordiant.com> wrote:
>>>>> I have raised TRINIDAD-1450 for this issue
>>>>>
>>>>> Thanks,
>>>>> Sabitha
>>>>>
>>>>> -----Original Message-----
>>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On
Behalf
>> Of Matthias Wessendorf
>>>>> Sent: Wednesday, April 08, 2009 6:08 PM
>>>>> To: MyFaces Development
>>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
>> cluster
>>>>> On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
>>>>> <Sa...@chordiant.com> wrote:
>>>>>> Can I know the URL to create the JIRA?
>>>>> https://issues.apache.org/jira/browse/TRINIDAD
>>>>>
>>>>> -M
>>>>>
>>>>>> Thanks,
>>>>>> Sabitha
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On
>> Behalf Of Matthias Wessendorf
>>>>>> Sent: Wednesday, April 08, 2009 6:02 PM
>>>>>> To: MyFaces Development
>>>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
>> cluster
>>>>>> Hey Sabitha,
>>>>>>
>>>>>> can you create a JIRA ticket ?
>>>>>> Once done, I'll ask our WLS folks to take a look...
>>>>>>
>>>>>> thanks,
>>>>>> matthias
>>>>>>
>>>>>> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
>>>>>> <Sa...@chordiant.com> wrote:
>>>>>>> Hi Matthias,
>>>>>>>
>>>>>>> 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/t
>>>>>>> rinidad-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.getSessionInt
>>>>>>> ernal(ReplicatedSessionContext.java:375)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>>>>>>> on(ServletRequestImpl.java:2521)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>>>>>>> ernal(ServletRequestImpl.java:2090)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>>>>>>> rvletRequestImpl.java:2057)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>>>>>>> pl.java:1189)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>>>>>>> .run(SecurityModule.java:535)
>>>>>>>
>>>>>>>
>>
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>>>>>>> bject.java:321)
>>>>>>>
>>>>>>>
>>
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>>>>>>> )
>>>>>>>
>>>>>>>
>>
weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>>>>>>> yModule.java:426)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>>>>>>> rvletSecurityManager.java:81)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>>>>>>> letContext.java:1920)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>>>>>>> ext.java:1890)
>>>>>>>
>>>>>>>
>>
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>>>>>>> :1344)
>>>>>>>
>> weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>>>>>>
weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sabitha
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On
>> Behalf Of
>>>>>>> Matthias Wessendorf
>>>>>>> Sent: Wednesday, April 08, 2009 5:35 PM
>>>>>>> To: MyFaces Development
>>>>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
>> cluster
>>>>>>> Hi,
>>>>>>>
>>>>>>> so, the "old" ri is "clean" ?
>>>>>>> What is the dump ?
>>>>>>>
>>>>>>> can you post some more information ?
>>>>>>>
>>>>>>> Also, does this reproduce with a (simple) Trinidad page?
>>>>>>>
>>>>>>> Is it JSP(X) or Facelets ?
>>>>>>>
>>>>>>> -Matthias
>>>>>>>
>>>>>>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>>>>>>> <Sa...@chordiant.com> wrote:
>>>>>>>> Hi ALL,
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> We are facing this strange issue. We are in the release phase
of
>> our
>>>>>>>> application.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Any .jspx containing
>>>>>>>>
>>>>>>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when
>> used
>>>>>>> with
>>>>>>>> el-impl-1.0.jar.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The same trinidad version is working fine when used with old
>>>>>>> el-ri-1.0.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
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Quick response is very highly appreciated
>>>>>>>>
> 
> 
>

Re: tag causes deadlock on weblogic 9.2 cluster

Posted by Simon Kitching <sk...@apache.org>.

No, it seems clear to me that there is a bug in weblogic that is only
triggered under some conditions. The new EL library happens to trigger
these conditions, but the bug is still clearly in weblogic.

I suggest asking the Weblogic support team what datastructures in the
session are not supported for replication, and are expected to cause a
hang. I would expect the answer to be "none", in which case a hang is
*definitely* their problem. Circular references, weak/strong refs etc.
should all be handled by proper replication.

The only *possible* user-created problem I can imagine is with locks. If
perhaps session replication needs to obtain a lock on the Session
object, but the new EL library is obtaining a lock, then never releasing
it, that *would* be a user problem, not weblogic. However it seems
unlikely as it would almost certainly be a "monitor" lock, ie a
synchronized() block. And those locks are always released when the
thread leaves the block. So the only possible way to lock it would be
for a thread to enter an infinite loop or block - but that would be
pretty quickly spotted as it would have obvious effects. Still, it might
be worth looking at what locks are held when the problem occurs.

And anyway, nobody except you has reported this issue, so it doesn't
seem to be a problem on other servlet containers. So again, it's a
weblogic problem. Possibly the new EL code sets up the conditions for
this to be triggered, but the real bug is elsewhere.

Sorry, but the Myfaces list really doesn't seem the right place for this
to be investigated.

Regards, Simon


Matthias Wessendorf schrieb:
> hrm, when replacing the EL jars fixes it (or causes it on the other direction)
> AND the same issue occurs with vanilla JSF, it is somewhat clear to me
> that the issue is in the EL layer. Do you see where it is deadlocked ?
> 
> -Matthias
> 
> On Tue, Apr 14, 2009 at 11:19 AM, Rupak Kumar Sah
> <Ru...@chordiant.com> wrote:
>> Yeah, it's clearly says the thread is stuck on session replication, but
>> as the same version of Weblogic works fine with older version of EL
>> jars, hence they would never accept it as their issue at first place.
>>
>> I raised this issue with Sun also, and they says they suggests to raise
>> it with Trinidad as the issue is with the trinidad components and the
>> same version of jars works fine else where.
>>
>> Suggest us what to do next.
>>
>> -----Original Message-----
>> From: simon.kitching@chello.at [mailto:simon.kitching@chello.at]
>> Sent: Tuesday, April 14, 2009 2:20 PM
>> To: MyFaces Development
>> Cc: Sabitha Gopal Pandit
>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>
>> The stacktrace clearly shows that this is a problem with Weblogic
>> session replication or network configuration and nothing whatsoever to
>> do with JSF or Myfaces. Data is being stored into the session, and then
>> when weblogic tries to replicate that data to other members of the
>> cluster a hang is occurring within Weblogic.
>>
>> So please take this discussion to the correct weblogic-specific list or
>> forum.
>>
>> Thanks,
>> Simon
>>
>> Matthias Wessendorf schrieb:
>>> Hi,
>>>
>>> looks like the issue is not really tied to Trinidad.
>>> It occurs with vanilla JSF as well. Perhaps this
>>> is a problem in the weblogic core, and not the frameworks ?
>>>
>>> -Matthias
>>>
>>> On Thu, Apr 9, 2009 at 6:53 AM, Sabitha Gopal Pandit
>>> <Sa...@chordiant.com> wrote:
>>>> Hi Matthias,
>>>>
>>>> We tried the same but didn't work for us
>>>>
>>>> Thanks,
>>>> Sabitha
>>>>
>>>> -----Original Message-----
>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf
>> Of Matthias Wessendorf
>>>> Sent: Wednesday, April 08, 2009 7:52 PM
>>>> To: MyFaces Development
>>>> Cc: Sabitha Gopal Pandit
>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>>
>>>> Sabitha,
>>>>
>>>> can you take a look at the bug ?
>>>> Max Starets added a comment.
>>>>
>>>> Thx,
>>>> Matthias
>>>>
>>>> On Wed, Apr 8, 2009 at 2:42 PM, Sabitha Gopal Pandit
>>>> <Sa...@chordiant.com> wrote:
>>>>> I have raised TRINIDAD-1450 for this issue
>>>>>
>>>>> Thanks,
>>>>> Sabitha
>>>>>
>>>>> -----Original Message-----
>>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf
>> Of Matthias Wessendorf
>>>>> Sent: Wednesday, April 08, 2009 6:08 PM
>>>>> To: MyFaces Development
>>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
>> cluster
>>>>> On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
>>>>> <Sa...@chordiant.com> wrote:
>>>>>> Can I know the URL to create the JIRA?
>>>>> https://issues.apache.org/jira/browse/TRINIDAD
>>>>>
>>>>> -M
>>>>>
>>>>>> Thanks,
>>>>>> Sabitha
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On
>> Behalf Of Matthias Wessendorf
>>>>>> Sent: Wednesday, April 08, 2009 6:02 PM
>>>>>> To: MyFaces Development
>>>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
>> cluster
>>>>>> Hey Sabitha,
>>>>>>
>>>>>> can you create a JIRA ticket ?
>>>>>> Once done, I'll ask our WLS folks to take a look...
>>>>>>
>>>>>> thanks,
>>>>>> matthias
>>>>>>
>>>>>> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
>>>>>> <Sa...@chordiant.com> wrote:
>>>>>>> Hi Matthias,
>>>>>>>
>>>>>>> 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/t
>>>>>>> rinidad-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.getSessionInt
>>>>>>> ernal(ReplicatedSessionContext.java:375)
>>>>>>>
>>>>>>>
>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>>>>>>> on(ServletRequestImpl.java:2521)
>>>>>>>
>>>>>>>
>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>>>>>>> ernal(ServletRequestImpl.java:2090)
>>>>>>>
>>>>>>>
>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>>>>>>> rvletRequestImpl.java:2057)
>>>>>>>
>>>>>>>
>> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>>>>>>> pl.java:1189)
>>>>>>>
>>>>>>>
>> weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>>>>>>> .run(SecurityModule.java:535)
>>>>>>>
>>>>>>>
>> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>>>>>>> bject.java:321)
>>>>>>>
>>>>>>>
>> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>>>>>>> )
>>>>>>>
>>>>>>>
>> weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>>>>>>> yModule.java:426)
>>>>>>>
>>>>>>>
>> weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>>>>>>> rvletSecurityManager.java:81)
>>>>>>>
>>>>>>>
>> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>>>>>>> letContext.java:1920)
>>>>>>>
>>>>>>>
>> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>>>>>>> ext.java:1890)
>>>>>>>
>>>>>>>
>> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>>>>>>> :1344)
>>>>>>>
>> weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>>>>>>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sabitha
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On
>> Behalf Of
>>>>>>> Matthias Wessendorf
>>>>>>> Sent: Wednesday, April 08, 2009 5:35 PM
>>>>>>> To: MyFaces Development
>>>>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
>> cluster
>>>>>>> Hi,
>>>>>>>
>>>>>>> so, the "old" ri is "clean" ?
>>>>>>> What is the dump ?
>>>>>>>
>>>>>>> can you post some more information ?
>>>>>>>
>>>>>>> Also, does this reproduce with a (simple) Trinidad page?
>>>>>>>
>>>>>>> Is it JSP(X) or Facelets ?
>>>>>>>
>>>>>>> -Matthias
>>>>>>>
>>>>>>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>>>>>>> <Sa...@chordiant.com> wrote:
>>>>>>>> Hi ALL,
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> We are facing this strange issue. We are in the release phase of
>> our
>>>>>>>> application.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Any .jspx containing
>>>>>>>>
>>>>>>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when
>> used
>>>>>>> with
>>>>>>>> el-impl-1.0.jar.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The same trinidad version is working fine when used with old
>>>>>>> el-ri-1.0.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
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Quick response is very highly appreciated
>>>>>>>>
> 
> 
>

Re: tag causes deadlock on weblogic 9.2 cluster

Posted by Matthias Wessendorf <ma...@apache.org>.

hrm, when replacing the EL jars fixes it (or causes it on the other direction)
AND the same issue occurs with vanilla JSF, it is somewhat clear to me
that the issue is in the EL layer. Do you see where it is deadlocked ?

-Matthias

On Tue, Apr 14, 2009 at 11:19 AM, Rupak Kumar Sah
<Ru...@chordiant.com> wrote:
> Yeah, it's clearly says the thread is stuck on session replication, but
> as the same version of Weblogic works fine with older version of EL
> jars, hence they would never accept it as their issue at first place.
>
> I raised this issue with Sun also, and they says they suggests to raise
> it with Trinidad as the issue is with the trinidad components and the
> same version of jars works fine else where.
>
> Suggest us what to do next.
>
> -----Original Message-----
> From: simon.kitching@chello.at [mailto:simon.kitching@chello.at]
> Sent: Tuesday, April 14, 2009 2:20 PM
> To: MyFaces Development
> Cc: Sabitha Gopal Pandit
> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>
> The stacktrace clearly shows that this is a problem with Weblogic
> session replication or network configuration and nothing whatsoever to
> do with JSF or Myfaces. Data is being stored into the session, and then
> when weblogic tries to replicate that data to other members of the
> cluster a hang is occurring within Weblogic.
>
> So please take this discussion to the correct weblogic-specific list or
> forum.
>
> Thanks,
> Simon
>
> Matthias Wessendorf schrieb:
>> Hi,
>>
>> looks like the issue is not really tied to Trinidad.
>> It occurs with vanilla JSF as well. Perhaps this
>> is a problem in the weblogic core, and not the frameworks ?
>>
>> -Matthias
>>
>> On Thu, Apr 9, 2009 at 6:53 AM, Sabitha Gopal Pandit
>> <Sa...@chordiant.com> wrote:
>>> Hi Matthias,
>>>
>>> We tried the same but didn't work for us
>>>
>>> Thanks,
>>> Sabitha
>>>
>>> -----Original Message-----
>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf
> Of Matthias Wessendorf
>>> Sent: Wednesday, April 08, 2009 7:52 PM
>>> To: MyFaces Development
>>> Cc: Sabitha Gopal Pandit
>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>
>>> Sabitha,
>>>
>>> can you take a look at the bug ?
>>> Max Starets added a comment.
>>>
>>> Thx,
>>> Matthias
>>>
>>> On Wed, Apr 8, 2009 at 2:42 PM, Sabitha Gopal Pandit
>>> <Sa...@chordiant.com> wrote:
>>>> I have raised TRINIDAD-1450 for this issue
>>>>
>>>> Thanks,
>>>> Sabitha
>>>>
>>>> -----Original Message-----
>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf
> Of Matthias Wessendorf
>>>> Sent: Wednesday, April 08, 2009 6:08 PM
>>>> To: MyFaces Development
>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
> cluster
>>>>
>>>> On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
>>>> <Sa...@chordiant.com> wrote:
>>>>> Can I know the URL to create the JIRA?
>>>> https://issues.apache.org/jira/browse/TRINIDAD
>>>>
>>>> -M
>>>>
>>>>> Thanks,
>>>>> Sabitha
>>>>>
>>>>> -----Original Message-----
>>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On
> Behalf Of Matthias Wessendorf
>>>>> Sent: Wednesday, April 08, 2009 6:02 PM
>>>>> To: MyFaces Development
>>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
> cluster
>>>>>
>>>>> Hey Sabitha,
>>>>>
>>>>> can you create a JIRA ticket ?
>>>>> Once done, I'll ask our WLS folks to take a look...
>>>>>
>>>>> thanks,
>>>>> matthias
>>>>>
>>>>> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
>>>>> <Sa...@chordiant.com> wrote:
>>>>>> Hi Matthias,
>>>>>>
>>>>>> 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/t
>>>>>> rinidad-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.getSessionInt
>>>>>> ernal(ReplicatedSessionContext.java:375)
>>>>>>
>>>>>>
> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>>>>>> on(ServletRequestImpl.java:2521)
>>>>>>
>>>>>>
> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>>>>>> ernal(ServletRequestImpl.java:2090)
>>>>>>
>>>>>>
> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>>>>>> rvletRequestImpl.java:2057)
>>>>>>
>>>>>>
> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>>>>>> pl.java:1189)
>>>>>>
>>>>>>
> weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>>>>>> .run(SecurityModule.java:535)
>>>>>>
>>>>>>
> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>>>>>> bject.java:321)
>>>>>>
>>>>>>
> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>>>>>> )
>>>>>>
>>>>>>
> weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>>>>>> yModule.java:426)
>>>>>>
>>>>>>
> weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>>>>>> rvletSecurityManager.java:81)
>>>>>>
>>>>>>
> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>>>>>> letContext.java:1920)
>>>>>>
>>>>>>
> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>>>>>> ext.java:1890)
>>>>>>
>>>>>>
> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>>>>>> :1344)
>>>>>>
> weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>>>>>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>>>>>
>>>>>> Thanks,
>>>>>> Sabitha
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On
> Behalf Of
>>>>>> Matthias Wessendorf
>>>>>> Sent: Wednesday, April 08, 2009 5:35 PM
>>>>>> To: MyFaces Development
>>>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
> cluster
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> so, the "old" ri is "clean" ?
>>>>>> What is the dump ?
>>>>>>
>>>>>> can you post some more information ?
>>>>>>
>>>>>> Also, does this reproduce with a (simple) Trinidad page?
>>>>>>
>>>>>> Is it JSP(X) or Facelets ?
>>>>>>
>>>>>> -Matthias
>>>>>>
>>>>>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>>>>>> <Sa...@chordiant.com> wrote:
>>>>>>> Hi ALL,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> We are facing this strange issue. We are in the release phase of
> our
>>>>>>> application.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Any .jspx containing
>>>>>>>
>>>>>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when
> used
>>>>>> with
>>>>>>> el-impl-1.0.jar.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The same trinidad version is working fine when used with old
>>>>>> el-ri-1.0.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
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Quick response is very highly appreciated
>>>>>>>
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

RE: tag causes deadlock on weblogic 9.2 cluster

Posted by Rupak Kumar Sah <Ru...@Chordiant.com>.

Yeah, it's clearly says the thread is stuck on session replication, but
as the same version of Weblogic works fine with older version of EL
jars, hence they would never accept it as their issue at first place.

I raised this issue with Sun also, and they says they suggests to raise
it with Trinidad as the issue is with the trinidad components and the
same version of jars works fine else where.

Suggest us what to do next.

-----Original Message-----
From: simon.kitching@chello.at [mailto:simon.kitching@chello.at] 
Sent: Tuesday, April 14, 2009 2:20 PM
To: MyFaces Development
Cc: Sabitha Gopal Pandit
Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster

The stacktrace clearly shows that this is a problem with Weblogic
session replication or network configuration and nothing whatsoever to
do with JSF or Myfaces. Data is being stored into the session, and then
when weblogic tries to replicate that data to other members of the
cluster a hang is occurring within Weblogic.

So please take this discussion to the correct weblogic-specific list or
forum.

Thanks,
Simon

Matthias Wessendorf schrieb:
> Hi,
> 
> looks like the issue is not really tied to Trinidad.
> It occurs with vanilla JSF as well. Perhaps this
> is a problem in the weblogic core, and not the frameworks ?
> 
> -Matthias
> 
> On Thu, Apr 9, 2009 at 6:53 AM, Sabitha Gopal Pandit
> <Sa...@chordiant.com> wrote:
>> Hi Matthias,
>>
>> We tried the same but didn't work for us
>>
>> Thanks,
>> Sabitha
>>
>> -----Original Message-----
>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf
Of Matthias Wessendorf
>> Sent: Wednesday, April 08, 2009 7:52 PM
>> To: MyFaces Development
>> Cc: Sabitha Gopal Pandit
>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>
>> Sabitha,
>>
>> can you take a look at the bug ?
>> Max Starets added a comment.
>>
>> Thx,
>> Matthias
>>
>> On Wed, Apr 8, 2009 at 2:42 PM, Sabitha Gopal Pandit
>> <Sa...@chordiant.com> wrote:
>>> I have raised TRINIDAD-1450 for this issue
>>>
>>> Thanks,
>>> Sabitha
>>>
>>> -----Original Message-----
>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf
Of Matthias Wessendorf
>>> Sent: Wednesday, April 08, 2009 6:08 PM
>>> To: MyFaces Development
>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
cluster
>>>
>>> On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
>>> <Sa...@chordiant.com> wrote:
>>>> Can I know the URL to create the JIRA?
>>> https://issues.apache.org/jira/browse/TRINIDAD
>>>
>>> -M
>>>
>>>> Thanks,
>>>> Sabitha
>>>>
>>>> -----Original Message-----
>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On
Behalf Of Matthias Wessendorf
>>>> Sent: Wednesday, April 08, 2009 6:02 PM
>>>> To: MyFaces Development
>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
cluster
>>>>
>>>> Hey Sabitha,
>>>>
>>>> can you create a JIRA ticket ?
>>>> Once done, I'll ask our WLS folks to take a look...
>>>>
>>>> thanks,
>>>> matthias
>>>>
>>>> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
>>>> <Sa...@chordiant.com> wrote:
>>>>> Hi Matthias,
>>>>>
>>>>> 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/t
>>>>> rinidad-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.getSessionInt
>>>>> ernal(ReplicatedSessionContext.java:375)
>>>>>
>>>>>
weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>>>>> on(ServletRequestImpl.java:2521)
>>>>>
>>>>>
weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>>>>> ernal(ServletRequestImpl.java:2090)
>>>>>
>>>>>
weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>>>>> rvletRequestImpl.java:2057)
>>>>>
>>>>>
weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>>>>> pl.java:1189)
>>>>>
>>>>>
weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>>>>> .run(SecurityModule.java:535)
>>>>>
>>>>>
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>>>>> bject.java:321)
>>>>>
>>>>>
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>>>>> )
>>>>>
>>>>>
weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>>>>> yModule.java:426)
>>>>>
>>>>>
weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>>>>> rvletSecurityManager.java:81)
>>>>>
>>>>>
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>>>>> letContext.java:1920)
>>>>>
>>>>>
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>>>>> ext.java:1890)
>>>>>
>>>>>
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>>>>> :1344)
>>>>>
weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>>>>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>>>>
>>>>> Thanks,
>>>>> Sabitha
>>>>>
>>>>> -----Original Message-----
>>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On
Behalf Of
>>>>> Matthias Wessendorf
>>>>> Sent: Wednesday, April 08, 2009 5:35 PM
>>>>> To: MyFaces Development
>>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2
cluster
>>>>>
>>>>> Hi,
>>>>>
>>>>> so, the "old" ri is "clean" ?
>>>>> What is the dump ?
>>>>>
>>>>> can you post some more information ?
>>>>>
>>>>> Also, does this reproduce with a (simple) Trinidad page?
>>>>>
>>>>> Is it JSP(X) or Facelets ?
>>>>>
>>>>> -Matthias
>>>>>
>>>>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>>>>> <Sa...@chordiant.com> wrote:
>>>>>> Hi ALL,
>>>>>>
>>>>>>
>>>>>>
>>>>>> We are facing this strange issue. We are in the release phase of
our
>>>>>> application.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Any .jspx containing
>>>>>>
>>>>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when
used
>>>>> with
>>>>>> el-impl-1.0.jar.
>>>>>>
>>>>>>
>>>>>>
>>>>>> The same trinidad version is working fine when used with old
>>>>> el-ri-1.0.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
>>>>>>
>>>>>>
>>>>>>
>>>>>> Quick response is very highly appreciated
>>>>>>

Re: tag causes deadlock on weblogic 9.2 cluster

Posted by "simon.kitching@chello.at" <si...@chello.at>.

The stacktrace clearly shows that this is a problem with Weblogic
session replication or network configuration and nothing whatsoever to
do with JSF or Myfaces. Data is being stored into the session, and then
when weblogic tries to replicate that data to other members of the
cluster a hang is occurring within Weblogic.

So please take this discussion to the correct weblogic-specific list or
forum.

Thanks,
Simon

Matthias Wessendorf schrieb:
> Hi,
> 
> looks like the issue is not really tied to Trinidad.
> It occurs with vanilla JSF as well. Perhaps this
> is a problem in the weblogic core, and not the frameworks ?
> 
> -Matthias
> 
> On Thu, Apr 9, 2009 at 6:53 AM, Sabitha Gopal Pandit
> <Sa...@chordiant.com> wrote:
>> Hi Matthias,
>>
>> We tried the same but didn't work for us
>>
>> Thanks,
>> Sabitha
>>
>> -----Original Message-----
>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>> Sent: Wednesday, April 08, 2009 7:52 PM
>> To: MyFaces Development
>> Cc: Sabitha Gopal Pandit
>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>
>> Sabitha,
>>
>> can you take a look at the bug ?
>> Max Starets added a comment.
>>
>> Thx,
>> Matthias
>>
>> On Wed, Apr 8, 2009 at 2:42 PM, Sabitha Gopal Pandit
>> <Sa...@chordiant.com> wrote:
>>> I have raised TRINIDAD-1450 for this issue
>>>
>>> Thanks,
>>> Sabitha
>>>
>>> -----Original Message-----
>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>>> Sent: Wednesday, April 08, 2009 6:08 PM
>>> To: MyFaces Development
>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>
>>> On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
>>> <Sa...@chordiant.com> wrote:
>>>> Can I know the URL to create the JIRA?
>>> https://issues.apache.org/jira/browse/TRINIDAD
>>>
>>> -M
>>>
>>>> Thanks,
>>>> Sabitha
>>>>
>>>> -----Original Message-----
>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>>>> Sent: Wednesday, April 08, 2009 6:02 PM
>>>> To: MyFaces Development
>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>>
>>>> Hey Sabitha,
>>>>
>>>> can you create a JIRA ticket ?
>>>> Once done, I'll ask our WLS folks to take a look...
>>>>
>>>> thanks,
>>>> matthias
>>>>
>>>> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
>>>> <Sa...@chordiant.com> wrote:
>>>>> Hi Matthias,
>>>>>
>>>>> 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/t
>>>>> rinidad-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.getSessionInt
>>>>> ernal(ReplicatedSessionContext.java:375)
>>>>>
>>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>>>>> on(ServletRequestImpl.java:2521)
>>>>>
>>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>>>>> ernal(ServletRequestImpl.java:2090)
>>>>>
>>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>>>>> rvletRequestImpl.java:2057)
>>>>>
>>>>> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>>>>> pl.java:1189)
>>>>>
>>>>> weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>>>>> .run(SecurityModule.java:535)
>>>>>
>>>>> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>>>>> bject.java:321)
>>>>>
>>>>> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>>>>> )
>>>>>
>>>>> weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>>>>> yModule.java:426)
>>>>>
>>>>> weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>>>>> rvletSecurityManager.java:81)
>>>>>
>>>>> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>>>>> letContext.java:1920)
>>>>>
>>>>> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>>>>> ext.java:1890)
>>>>>
>>>>> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>>>>> :1344)
>>>>>            weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>>>>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>>>>
>>>>> Thanks,
>>>>> Sabitha
>>>>>
>>>>> -----Original Message-----
>>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
>>>>> Matthias Wessendorf
>>>>> Sent: Wednesday, April 08, 2009 5:35 PM
>>>>> To: MyFaces Development
>>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>>>
>>>>> Hi,
>>>>>
>>>>> so, the "old" ri is "clean" ?
>>>>> What is the dump ?
>>>>>
>>>>> can you post some more information ?
>>>>>
>>>>> Also, does this reproduce with a (simple) Trinidad page?
>>>>>
>>>>> Is it JSP(X) or Facelets ?
>>>>>
>>>>> -Matthias
>>>>>
>>>>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>>>>> <Sa...@chordiant.com> wrote:
>>>>>> Hi ALL,
>>>>>>
>>>>>>
>>>>>>
>>>>>> We are facing this strange issue. We are in the release phase of our
>>>>>> application.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Any .jspx containing
>>>>>>
>>>>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used
>>>>> with
>>>>>> el-impl-1.0.jar.
>>>>>>
>>>>>>
>>>>>>
>>>>>> The same trinidad version is working fine when used with old
>>>>> el-ri-1.0.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
>>>>>>
>>>>>>
>>>>>>
>>>>>> Quick response is very highly appreciated
>>>>>>

Re: tag causes deadlock on weblogic 9.2 cluster

Posted by Matthias Wessendorf <ma...@apache.org>.

Hi,

looks like the issue is not really tied to Trinidad.
It occurs with vanilla JSF as well. Perhaps this
is a problem in the weblogic core, and not the frameworks ?

-Matthias

On Thu, Apr 9, 2009 at 6:53 AM, Sabitha Gopal Pandit
<Sa...@chordiant.com> wrote:
> Hi Matthias,
>
> We tried the same but didn't work for us
>
> Thanks,
> Sabitha
>
> -----Original Message-----
> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
> Sent: Wednesday, April 08, 2009 7:52 PM
> To: MyFaces Development
> Cc: Sabitha Gopal Pandit
> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>
> Sabitha,
>
> can you take a look at the bug ?
> Max Starets added a comment.
>
> Thx,
> Matthias
>
> On Wed, Apr 8, 2009 at 2:42 PM, Sabitha Gopal Pandit
> <Sa...@chordiant.com> wrote:
>> I have raised TRINIDAD-1450 for this issue
>>
>> Thanks,
>> Sabitha
>>
>> -----Original Message-----
>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>> Sent: Wednesday, April 08, 2009 6:08 PM
>> To: MyFaces Development
>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>
>> On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
>> <Sa...@chordiant.com> wrote:
>>> Can I know the URL to create the JIRA?
>>
>> https://issues.apache.org/jira/browse/TRINIDAD
>>
>> -M
>>
>>>
>>> Thanks,
>>> Sabitha
>>>
>>> -----Original Message-----
>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>>> Sent: Wednesday, April 08, 2009 6:02 PM
>>> To: MyFaces Development
>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>
>>> Hey Sabitha,
>>>
>>> can you create a JIRA ticket ?
>>> Once done, I'll ask our WLS folks to take a look...
>>>
>>> thanks,
>>> matthias
>>>
>>> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
>>> <Sa...@chordiant.com> wrote:
>>>> Hi Matthias,
>>>>
>>>> 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/t
>>>> rinidad-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.getSessionInt
>>>> ernal(ReplicatedSessionContext.java:375)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>>>> on(ServletRequestImpl.java:2521)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>>>> ernal(ServletRequestImpl.java:2090)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>>>> rvletRequestImpl.java:2057)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>>>> pl.java:1189)
>>>>
>>>> weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>>>> .run(SecurityModule.java:535)
>>>>
>>>> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>>>> bject.java:321)
>>>>
>>>> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>>>> )
>>>>
>>>> weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>>>> yModule.java:426)
>>>>
>>>> weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>>>> rvletSecurityManager.java:81)
>>>>
>>>> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>>>> letContext.java:1920)
>>>>
>>>> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>>>> ext.java:1890)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>>>> :1344)
>>>>            weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>>>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>>>
>>>> Thanks,
>>>> Sabitha
>>>>
>>>> -----Original Message-----
>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
>>>> Matthias Wessendorf
>>>> Sent: Wednesday, April 08, 2009 5:35 PM
>>>> To: MyFaces Development
>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>>
>>>> Hi,
>>>>
>>>> so, the "old" ri is "clean" ?
>>>> What is the dump ?
>>>>
>>>> can you post some more information ?
>>>>
>>>> Also, does this reproduce with a (simple) Trinidad page?
>>>>
>>>> Is it JSP(X) or Facelets ?
>>>>
>>>> -Matthias
>>>>
>>>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>>>> <Sa...@chordiant.com> wrote:
>>>>> Hi ALL,
>>>>>
>>>>>
>>>>>
>>>>> We are facing this strange issue. We are in the release phase of our
>>>>> application.
>>>>>
>>>>>
>>>>>
>>>>> Any .jspx containing
>>>>>
>>>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used
>>>> with
>>>>> el-impl-1.0.jar.
>>>>>
>>>>>
>>>>>
>>>>> The same trinidad version is working fine when used with old
>>>> el-ri-1.0.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
>>>>>
>>>>>
>>>>>
>>>>> Quick response is very highly appreciated
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Sabitha
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

RE: tag causes deadlock on weblogic 9.2 cluster

Posted by Sabitha Gopal Pandit <Sa...@Chordiant.com>.

Hi Matthias,

We tried the same but didn't work for us

Thanks,
Sabitha

-----Original Message-----
From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
Sent: Wednesday, April 08, 2009 7:52 PM
To: MyFaces Development
Cc: Sabitha Gopal Pandit
Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster

Sabitha,

can you take a look at the bug ?
Max Starets added a comment.

Thx,
Matthias

On Wed, Apr 8, 2009 at 2:42 PM, Sabitha Gopal Pandit
<Sa...@chordiant.com> wrote:
> I have raised TRINIDAD-1450 for this issue
>
> Thanks,
> Sabitha
>
> -----Original Message-----
> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
> Sent: Wednesday, April 08, 2009 6:08 PM
> To: MyFaces Development
> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>
> On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
> <Sa...@chordiant.com> wrote:
>> Can I know the URL to create the JIRA?
>
> https://issues.apache.org/jira/browse/TRINIDAD
>
> -M
>
>>
>> Thanks,
>> Sabitha
>>
>> -----Original Message-----
>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>> Sent: Wednesday, April 08, 2009 6:02 PM
>> To: MyFaces Development
>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>
>> Hey Sabitha,
>>
>> can you create a JIRA ticket ?
>> Once done, I'll ask our WLS folks to take a look...
>>
>> thanks,
>> matthias
>>
>> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
>> <Sa...@chordiant.com> wrote:
>>> Hi Matthias,
>>>
>>> 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/t
>>> rinidad-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.getSessionInt
>>> ernal(ReplicatedSessionContext.java:375)
>>>
>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>>> on(ServletRequestImpl.java:2521)
>>>
>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>>> ernal(ServletRequestImpl.java:2090)
>>>
>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>>> rvletRequestImpl.java:2057)
>>>
>>> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>>> pl.java:1189)
>>>
>>> weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>>> .run(SecurityModule.java:535)
>>>
>>> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>>> bject.java:321)
>>>
>>> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>>> )
>>>
>>> weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>>> yModule.java:426)
>>>
>>> weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>>> rvletSecurityManager.java:81)
>>>
>>> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>>> letContext.java:1920)
>>>
>>> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>>> ext.java:1890)
>>>
>>> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>>> :1344)
>>>            weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>>
>>> Thanks,
>>> Sabitha
>>>
>>> -----Original Message-----
>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
>>> Matthias Wessendorf
>>> Sent: Wednesday, April 08, 2009 5:35 PM
>>> To: MyFaces Development
>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>
>>> Hi,
>>>
>>> so, the "old" ri is "clean" ?
>>> What is the dump ?
>>>
>>> can you post some more information ?
>>>
>>> Also, does this reproduce with a (simple) Trinidad page?
>>>
>>> Is it JSP(X) or Facelets ?
>>>
>>> -Matthias
>>>
>>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>>> <Sa...@chordiant.com> wrote:
>>>> Hi ALL,
>>>>
>>>>
>>>>
>>>> We are facing this strange issue. We are in the release phase of our
>>>> application.
>>>>
>>>>
>>>>
>>>> Any .jspx containing
>>>>
>>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used
>>> with
>>>> el-impl-1.0.jar.
>>>>
>>>>
>>>>
>>>> The same trinidad version is working fine when used with old
>>> el-ri-1.0.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
>>>>
>>>>
>>>>
>>>> Quick response is very highly appreciated
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Sabitha
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Re: tag causes deadlock on weblogic 9.2 cluster

Posted by Matthias Wessendorf <ma...@apache.org>.

saw it ;-)

thanks!

On Fri, Apr 10, 2009 at 11:12 AM, Matthias Wessendorf <ma...@apache.org> wrote:
> can you update the jira ticket with that information ?
>
> On Fri, Apr 10, 2009 at 10:42 AM, Rupak Kumar Sah
> <Ru...@chordiant.com> wrote:
>> I removed the <trh:script> tag that imports the js, and the js reference from the jsp, and found the same issue that is the thread again gets blocked.
>> This means the issue is not with <trh:script> tag as we suspected earlier, but it is somewhere 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)
>>
>>
>> -----Original Message-----
>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>> Sent: Wednesday, April 08, 2009 7:52 PM
>> To: MyFaces Development
>> Cc: Sabitha Gopal Pandit
>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>
>> Sabitha,
>>
>> can you take a look at the bug ?
>> Max Starets added a comment.
>>
>> Thx,
>> Matthias
>>
>> On Wed, Apr 8, 2009 at 2:42 PM, Sabitha Gopal Pandit
>> <Sa...@chordiant.com> wrote:
>>> I have raised TRINIDAD-1450 for this issue
>>>
>>> Thanks,
>>> Sabitha
>>>
>>> -----Original Message-----
>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>>> Sent: Wednesday, April 08, 2009 6:08 PM
>>> To: MyFaces Development
>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>
>>> On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
>>> <Sa...@chordiant.com> wrote:
>>>> Can I know the URL to create the JIRA?
>>>
>>> https://issues.apache.org/jira/browse/TRINIDAD
>>>
>>> -M
>>>
>>>>
>>>> Thanks,
>>>> Sabitha
>>>>
>>>> -----Original Message-----
>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>>>> Sent: Wednesday, April 08, 2009 6:02 PM
>>>> To: MyFaces Development
>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>>
>>>> Hey Sabitha,
>>>>
>>>> can you create a JIRA ticket ?
>>>> Once done, I'll ask our WLS folks to take a look...
>>>>
>>>> thanks,
>>>> matthias
>>>>
>>>> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
>>>> <Sa...@chordiant.com> wrote:
>>>>> Hi Matthias,
>>>>>
>>>>> 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/t
>>>>> rinidad-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.getSessionInt
>>>>> ernal(ReplicatedSessionContext.java:375)
>>>>>
>>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>>>>> on(ServletRequestImpl.java:2521)
>>>>>
>>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>>>>> ernal(ServletRequestImpl.java:2090)
>>>>>
>>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>>>>> rvletRequestImpl.java:2057)
>>>>>
>>>>> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>>>>> pl.java:1189)
>>>>>
>>>>> weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>>>>> .run(SecurityModule.java:535)
>>>>>
>>>>> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>>>>> bject.java:321)
>>>>>
>>>>> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>>>>> )
>>>>>
>>>>> weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>>>>> yModule.java:426)
>>>>>
>>>>> weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>>>>> rvletSecurityManager.java:81)
>>>>>
>>>>> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>>>>> letContext.java:1920)
>>>>>
>>>>> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>>>>> ext.java:1890)
>>>>>
>>>>> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>>>>> :1344)
>>>>>            weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>>>>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>>>>
>>>>> Thanks,
>>>>> Sabitha
>>>>>
>>>>> -----Original Message-----
>>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
>>>>> Matthias Wessendorf
>>>>> Sent: Wednesday, April 08, 2009 5:35 PM
>>>>> To: MyFaces Development
>>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>>>
>>>>> Hi,
>>>>>
>>>>> so, the "old" ri is "clean" ?
>>>>> What is the dump ?
>>>>>
>>>>> can you post some more information ?
>>>>>
>>>>> Also, does this reproduce with a (simple) Trinidad page?
>>>>>
>>>>> Is it JSP(X) or Facelets ?
>>>>>
>>>>> -Matthias
>>>>>
>>>>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>>>>> <Sa...@chordiant.com> wrote:
>>>>>> Hi ALL,
>>>>>>
>>>>>>
>>>>>>
>>>>>> We are facing this strange issue. We are in the release phase of our
>>>>>> application.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Any .jspx containing
>>>>>>
>>>>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used
>>>>> with
>>>>>> el-impl-1.0.jar.
>>>>>>
>>>>>>
>>>>>>
>>>>>> The same trinidad version is working fine when used with old
>>>>> el-ri-1.0.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
>>>>>>
>>>>>>
>>>>>>
>>>>>> Quick response is very highly appreciated
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Sabitha
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Re: tag causes deadlock on weblogic 9.2 cluster

Posted by Matthias Wessendorf <ma...@apache.org>.

can you update the jira ticket with that information ?

On Fri, Apr 10, 2009 at 10:42 AM, Rupak Kumar Sah
<Ru...@chordiant.com> wrote:
> I removed the <trh:script> tag that imports the js, and the js reference from the jsp, and found the same issue that is the thread again gets blocked.
> This means the issue is not with <trh:script> tag as we suspected earlier, but it is somewhere 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)
>
>
> -----Original Message-----
> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
> Sent: Wednesday, April 08, 2009 7:52 PM
> To: MyFaces Development
> Cc: Sabitha Gopal Pandit
> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>
> Sabitha,
>
> can you take a look at the bug ?
> Max Starets added a comment.
>
> Thx,
> Matthias
>
> On Wed, Apr 8, 2009 at 2:42 PM, Sabitha Gopal Pandit
> <Sa...@chordiant.com> wrote:
>> I have raised TRINIDAD-1450 for this issue
>>
>> Thanks,
>> Sabitha
>>
>> -----Original Message-----
>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>> Sent: Wednesday, April 08, 2009 6:08 PM
>> To: MyFaces Development
>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>
>> On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
>> <Sa...@chordiant.com> wrote:
>>> Can I know the URL to create the JIRA?
>>
>> https://issues.apache.org/jira/browse/TRINIDAD
>>
>> -M
>>
>>>
>>> Thanks,
>>> Sabitha
>>>
>>> -----Original Message-----
>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>>> Sent: Wednesday, April 08, 2009 6:02 PM
>>> To: MyFaces Development
>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>
>>> Hey Sabitha,
>>>
>>> can you create a JIRA ticket ?
>>> Once done, I'll ask our WLS folks to take a look...
>>>
>>> thanks,
>>> matthias
>>>
>>> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
>>> <Sa...@chordiant.com> wrote:
>>>> Hi Matthias,
>>>>
>>>> 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/t
>>>> rinidad-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.getSessionInt
>>>> ernal(ReplicatedSessionContext.java:375)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>>>> on(ServletRequestImpl.java:2521)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>>>> ernal(ServletRequestImpl.java:2090)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>>>> rvletRequestImpl.java:2057)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>>>> pl.java:1189)
>>>>
>>>> weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>>>> .run(SecurityModule.java:535)
>>>>
>>>> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>>>> bject.java:321)
>>>>
>>>> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>>>> )
>>>>
>>>> weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>>>> yModule.java:426)
>>>>
>>>> weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>>>> rvletSecurityManager.java:81)
>>>>
>>>> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>>>> letContext.java:1920)
>>>>
>>>> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>>>> ext.java:1890)
>>>>
>>>> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>>>> :1344)
>>>>            weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>>>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>>>
>>>> Thanks,
>>>> Sabitha
>>>>
>>>> -----Original Message-----
>>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
>>>> Matthias Wessendorf
>>>> Sent: Wednesday, April 08, 2009 5:35 PM
>>>> To: MyFaces Development
>>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>>
>>>> Hi,
>>>>
>>>> so, the "old" ri is "clean" ?
>>>> What is the dump ?
>>>>
>>>> can you post some more information ?
>>>>
>>>> Also, does this reproduce with a (simple) Trinidad page?
>>>>
>>>> Is it JSP(X) or Facelets ?
>>>>
>>>> -Matthias
>>>>
>>>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>>>> <Sa...@chordiant.com> wrote:
>>>>> Hi ALL,
>>>>>
>>>>>
>>>>>
>>>>> We are facing this strange issue. We are in the release phase of our
>>>>> application.
>>>>>
>>>>>
>>>>>
>>>>> Any .jspx containing
>>>>>
>>>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used
>>>> with
>>>>> el-impl-1.0.jar.
>>>>>
>>>>>
>>>>>
>>>>> The same trinidad version is working fine when used with old
>>>> el-ri-1.0.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
>>>>>
>>>>>
>>>>>
>>>>> Quick response is very highly appreciated
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Sabitha
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

RE: tag causes deadlock on weblogic 9.2 cluster

Posted by Rupak Kumar Sah <Ru...@Chordiant.com>.

I removed the <trh:script> tag that imports the js, and the js reference from the jsp, and found the same issue that is the thread again gets blocked.
This means the issue is not with <trh:script> tag as we suspected earlier, but it is somewhere 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)


-----Original Message-----
From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
Sent: Wednesday, April 08, 2009 7:52 PM
To: MyFaces Development
Cc: Sabitha Gopal Pandit
Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster

Sabitha,

can you take a look at the bug ?
Max Starets added a comment.

Thx,
Matthias

On Wed, Apr 8, 2009 at 2:42 PM, Sabitha Gopal Pandit
<Sa...@chordiant.com> wrote:
> I have raised TRINIDAD-1450 for this issue
>
> Thanks,
> Sabitha
>
> -----Original Message-----
> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
> Sent: Wednesday, April 08, 2009 6:08 PM
> To: MyFaces Development
> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>
> On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
> <Sa...@chordiant.com> wrote:
>> Can I know the URL to create the JIRA?
>
> https://issues.apache.org/jira/browse/TRINIDAD
>
> -M
>
>>
>> Thanks,
>> Sabitha
>>
>> -----Original Message-----
>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>> Sent: Wednesday, April 08, 2009 6:02 PM
>> To: MyFaces Development
>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>
>> Hey Sabitha,
>>
>> can you create a JIRA ticket ?
>> Once done, I'll ask our WLS folks to take a look...
>>
>> thanks,
>> matthias
>>
>> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
>> <Sa...@chordiant.com> wrote:
>>> Hi Matthias,
>>>
>>> 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/t
>>> rinidad-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.getSessionInt
>>> ernal(ReplicatedSessionContext.java:375)
>>>
>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>>> on(ServletRequestImpl.java:2521)
>>>
>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>>> ernal(ServletRequestImpl.java:2090)
>>>
>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>>> rvletRequestImpl.java:2057)
>>>
>>> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>>> pl.java:1189)
>>>
>>> weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>>> .run(SecurityModule.java:535)
>>>
>>> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>>> bject.java:321)
>>>
>>> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>>> )
>>>
>>> weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>>> yModule.java:426)
>>>
>>> weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>>> rvletSecurityManager.java:81)
>>>
>>> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>>> letContext.java:1920)
>>>
>>> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>>> ext.java:1890)
>>>
>>> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>>> :1344)
>>>            weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>>
>>> Thanks,
>>> Sabitha
>>>
>>> -----Original Message-----
>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
>>> Matthias Wessendorf
>>> Sent: Wednesday, April 08, 2009 5:35 PM
>>> To: MyFaces Development
>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>
>>> Hi,
>>>
>>> so, the "old" ri is "clean" ?
>>> What is the dump ?
>>>
>>> can you post some more information ?
>>>
>>> Also, does this reproduce with a (simple) Trinidad page?
>>>
>>> Is it JSP(X) or Facelets ?
>>>
>>> -Matthias
>>>
>>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>>> <Sa...@chordiant.com> wrote:
>>>> Hi ALL,
>>>>
>>>>
>>>>
>>>> We are facing this strange issue. We are in the release phase of our
>>>> application.
>>>>
>>>>
>>>>
>>>> Any .jspx containing
>>>>
>>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used
>>> with
>>>> el-impl-1.0.jar.
>>>>
>>>>
>>>>
>>>> The same trinidad version is working fine when used with old
>>> el-ri-1.0.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
>>>>
>>>>
>>>>
>>>> Quick response is very highly appreciated
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Sabitha
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Re: tag causes deadlock on weblogic 9.2 cluster

Posted by Matthias Wessendorf <ma...@apache.org>.

Sabitha,

can you take a look at the bug ?
Max Starets added a comment.

Thx,
Matthias

On Wed, Apr 8, 2009 at 2:42 PM, Sabitha Gopal Pandit
<Sa...@chordiant.com> wrote:
> I have raised TRINIDAD-1450 for this issue
>
> Thanks,
> Sabitha
>
> -----Original Message-----
> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
> Sent: Wednesday, April 08, 2009 6:08 PM
> To: MyFaces Development
> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>
> On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
> <Sa...@chordiant.com> wrote:
>> Can I know the URL to create the JIRA?
>
> https://issues.apache.org/jira/browse/TRINIDAD
>
> -M
>
>>
>> Thanks,
>> Sabitha
>>
>> -----Original Message-----
>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
>> Sent: Wednesday, April 08, 2009 6:02 PM
>> To: MyFaces Development
>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>
>> Hey Sabitha,
>>
>> can you create a JIRA ticket ?
>> Once done, I'll ask our WLS folks to take a look...
>>
>> thanks,
>> matthias
>>
>> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
>> <Sa...@chordiant.com> wrote:
>>> Hi Matthias,
>>>
>>> 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/t
>>> rinidad-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.getSessionInt
>>> ernal(ReplicatedSessionContext.java:375)
>>>
>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>>> on(ServletRequestImpl.java:2521)
>>>
>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>>> ernal(ServletRequestImpl.java:2090)
>>>
>>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>>> rvletRequestImpl.java:2057)
>>>
>>> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>>> pl.java:1189)
>>>
>>> weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>>> .run(SecurityModule.java:535)
>>>
>>> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>>> bject.java:321)
>>>
>>> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>>> )
>>>
>>> weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>>> yModule.java:426)
>>>
>>> weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>>> rvletSecurityManager.java:81)
>>>
>>> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>>> letContext.java:1920)
>>>
>>> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>>> ext.java:1890)
>>>
>>> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>>> :1344)
>>>            weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>>
>>> Thanks,
>>> Sabitha
>>>
>>> -----Original Message-----
>>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
>>> Matthias Wessendorf
>>> Sent: Wednesday, April 08, 2009 5:35 PM
>>> To: MyFaces Development
>>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>>
>>> Hi,
>>>
>>> so, the "old" ri is "clean" ?
>>> What is the dump ?
>>>
>>> can you post some more information ?
>>>
>>> Also, does this reproduce with a (simple) Trinidad page?
>>>
>>> Is it JSP(X) or Facelets ?
>>>
>>> -Matthias
>>>
>>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>>> <Sa...@chordiant.com> wrote:
>>>> Hi ALL,
>>>>
>>>>
>>>>
>>>> We are facing this strange issue. We are in the release phase of our
>>>> application.
>>>>
>>>>
>>>>
>>>> Any .jspx containing
>>>>
>>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used
>>> with
>>>> el-impl-1.0.jar.
>>>>
>>>>
>>>>
>>>> The same trinidad version is working fine when used with old
>>> el-ri-1.0.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
>>>>
>>>>
>>>>
>>>> Quick response is very highly appreciated
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Sabitha
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

RE: tag causes deadlock on weblogic 9.2 cluster

Posted by Sabitha Gopal Pandit <Sa...@Chordiant.com>.

I have raised TRINIDAD-1450 for this issue

Thanks,
Sabitha

-----Original Message-----
From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
Sent: Wednesday, April 08, 2009 6:08 PM
To: MyFaces Development
Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster

On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
<Sa...@chordiant.com> wrote:
> Can I know the URL to create the JIRA?

https://issues.apache.org/jira/browse/TRINIDAD

-M

>
> Thanks,
> Sabitha
>
> -----Original Message-----
> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
> Sent: Wednesday, April 08, 2009 6:02 PM
> To: MyFaces Development
> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>
> Hey Sabitha,
>
> can you create a JIRA ticket ?
> Once done, I'll ask our WLS folks to take a look...
>
> thanks,
> matthias
>
> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
> <Sa...@chordiant.com> wrote:
>> Hi Matthias,
>>
>> 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/t
>> rinidad-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.getSessionInt
>> ernal(ReplicatedSessionContext.java:375)
>>
>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>> on(ServletRequestImpl.java:2521)
>>
>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>> ernal(ServletRequestImpl.java:2090)
>>
>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>> rvletRequestImpl.java:2057)
>>
>> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>> pl.java:1189)
>>
>> weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>> .run(SecurityModule.java:535)
>>
>> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>> bject.java:321)
>>
>> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>> )
>>
>> weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>> yModule.java:426)
>>
>> weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>> rvletSecurityManager.java:81)
>>
>> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>> letContext.java:1920)
>>
>> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>> ext.java:1890)
>>
>> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>> :1344)
>>            weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>
>> Thanks,
>> Sabitha
>>
>> -----Original Message-----
>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
>> Matthias Wessendorf
>> Sent: Wednesday, April 08, 2009 5:35 PM
>> To: MyFaces Development
>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>
>> Hi,
>>
>> so, the "old" ri is "clean" ?
>> What is the dump ?
>>
>> can you post some more information ?
>>
>> Also, does this reproduce with a (simple) Trinidad page?
>>
>> Is it JSP(X) or Facelets ?
>>
>> -Matthias
>>
>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>> <Sa...@chordiant.com> wrote:
>>> Hi ALL,
>>>
>>>
>>>
>>> We are facing this strange issue. We are in the release phase of our
>>> application.
>>>
>>>
>>>
>>> Any .jspx containing
>>>
>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used
>> with
>>> el-impl-1.0.jar.
>>>
>>>
>>>
>>> The same trinidad version is working fine when used with old
>> el-ri-1.0.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
>>>
>>>
>>>
>>> Quick response is very highly appreciated
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Sabitha
>>>
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Re: tag causes deadlock on weblogic 9.2 cluster

Posted by Matthias Wessendorf <ma...@apache.org>.

On Wed, Apr 8, 2009 at 2:33 PM, Sabitha Gopal Pandit
<Sa...@chordiant.com> wrote:
> Can I know the URL to create the JIRA?

https://issues.apache.org/jira/browse/TRINIDAD

-M

>
> Thanks,
> Sabitha
>
> -----Original Message-----
> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
> Sent: Wednesday, April 08, 2009 6:02 PM
> To: MyFaces Development
> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>
> Hey Sabitha,
>
> can you create a JIRA ticket ?
> Once done, I'll ask our WLS folks to take a look...
>
> thanks,
> matthias
>
> On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
> <Sa...@chordiant.com> wrote:
>> Hi Matthias,
>>
>> 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/t
>> rinidad-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.getSessionInt
>> ernal(ReplicatedSessionContext.java:375)
>>
>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
>> on(ServletRequestImpl.java:2521)
>>
>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
>> ernal(ServletRequestImpl.java:2090)
>>
>> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
>> rvletRequestImpl.java:2057)
>>
>> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
>> pl.java:1189)
>>
>> weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
>> .run(SecurityModule.java:535)
>>
>> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>> bject.java:321)
>>
>> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>> )
>>
>> weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
>> yModule.java:426)
>>
>> weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
>> rvletSecurityManager.java:81)
>>
>> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
>> letContext.java:1920)
>>
>> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
>> ext.java:1890)
>>
>> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
>> :1344)
>>            weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>>
>> Thanks,
>> Sabitha
>>
>> -----Original Message-----
>> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
>> Matthias Wessendorf
>> Sent: Wednesday, April 08, 2009 5:35 PM
>> To: MyFaces Development
>> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>>
>> Hi,
>>
>> so, the "old" ri is "clean" ?
>> What is the dump ?
>>
>> can you post some more information ?
>>
>> Also, does this reproduce with a (simple) Trinidad page?
>>
>> Is it JSP(X) or Facelets ?
>>
>> -Matthias
>>
>> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
>> <Sa...@chordiant.com> wrote:
>>> Hi ALL,
>>>
>>>
>>>
>>> We are facing this strange issue. We are in the release phase of our
>>> application.
>>>
>>>
>>>
>>> Any .jspx containing
>>>
>>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used
>> with
>>> el-impl-1.0.jar.
>>>
>>>
>>>
>>> The same trinidad version is working fine when used with old
>> el-ri-1.0.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
>>>
>>>
>>>
>>> Quick response is very highly appreciated
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Sabitha
>>>
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

RE: tag causes deadlock on weblogic 9.2 cluster

Posted by Sabitha Gopal Pandit <Sa...@Chordiant.com>.

Can I know the URL to create the JIRA?

Thanks,
Sabitha

-----Original Message-----
From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of Matthias Wessendorf
Sent: Wednesday, April 08, 2009 6:02 PM
To: MyFaces Development
Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster

Hey Sabitha,

can you create a JIRA ticket ?
Once done, I'll ask our WLS folks to take a look...

thanks,
matthias

On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
<Sa...@chordiant.com> wrote:
> Hi Matthias,
>
> 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/t
> rinidad-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.getSessionInt
> ernal(ReplicatedSessionContext.java:375)
>
> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
> on(ServletRequestImpl.java:2521)
>
> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
> ernal(ServletRequestImpl.java:2090)
>
> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
> rvletRequestImpl.java:2057)
>
> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
> pl.java:1189)
>
> weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
> .run(SecurityModule.java:535)
>
> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
> bject.java:321)
>
> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
> )
>
> weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
> yModule.java:426)
>
> weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
> rvletSecurityManager.java:81)
>
> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
> letContext.java:1920)
>
> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
> ext.java:1890)
>
> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
> :1344)
>            weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>
> Thanks,
> Sabitha
>
> -----Original Message-----
> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
> Matthias Wessendorf
> Sent: Wednesday, April 08, 2009 5:35 PM
> To: MyFaces Development
> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>
> Hi,
>
> so, the "old" ri is "clean" ?
> What is the dump ?
>
> can you post some more information ?
>
> Also, does this reproduce with a (simple) Trinidad page?
>
> Is it JSP(X) or Facelets ?
>
> -Matthias
>
> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
> <Sa...@chordiant.com> wrote:
>> Hi ALL,
>>
>>
>>
>> We are facing this strange issue. We are in the release phase of our
>> application.
>>
>>
>>
>> Any .jspx containing
>>
>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used
> with
>> el-impl-1.0.jar.
>>
>>
>>
>> The same trinidad version is working fine when used with old
> el-ri-1.0.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
>>
>>
>>
>> Quick response is very highly appreciated
>>
>>
>>
>> Thanks,
>>
>> Sabitha
>>
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Re: tag causes deadlock on weblogic 9.2 cluster

Posted by Matthias Wessendorf <ma...@apache.org>.

Hey Sabitha,

can you create a JIRA ticket ?
Once done, I'll ask our WLS folks to take a look...

thanks,
matthias

On Wed, Apr 8, 2009 at 2:23 PM, Sabitha Gopal Pandit
<Sa...@chordiant.com> wrote:
> Hi Matthias,
>
> 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/t
> rinidad-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.getSessionInt
> ernal(ReplicatedSessionContext.java:375)
>
> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
> on(ServletRequestImpl.java:2521)
>
> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
> ernal(ServletRequestImpl.java:2090)
>
> weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
> rvletRequestImpl.java:2057)
>
> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
> pl.java:1189)
>
> weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
> .run(SecurityModule.java:535)
>
> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
> bject.java:321)
>
> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
> )
>
> weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
> yModule.java:426)
>
> weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
> rvletSecurityManager.java:81)
>
> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
> letContext.java:1920)
>
> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
> ext.java:1890)
>
> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
> :1344)
>            weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>            weblogic.work.ExecuteThread.run(ExecuteThread.java:181
>
> Thanks,
> Sabitha
>
> -----Original Message-----
> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
> Matthias Wessendorf
> Sent: Wednesday, April 08, 2009 5:35 PM
> To: MyFaces Development
> Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster
>
> Hi,
>
> so, the "old" ri is "clean" ?
> What is the dump ?
>
> can you post some more information ?
>
> Also, does this reproduce with a (simple) Trinidad page?
>
> Is it JSP(X) or Facelets ?
>
> -Matthias
>
> On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
> <Sa...@chordiant.com> wrote:
>> Hi ALL,
>>
>>
>>
>> We are facing this strange issue. We are in the release phase of our
>> application.
>>
>>
>>
>> Any .jspx containing
>>
>> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used
> with
>> el-impl-1.0.jar.
>>
>>
>>
>> The same trinidad version is working fine when used with old
> el-ri-1.0.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
>>
>>
>>
>> Quick response is very highly appreciated
>>
>>
>>
>> Thanks,
>>
>> Sabitha
>>
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

RE: tag causes deadlock on weblogic 9.2 cluster

Posted by Sabitha Gopal Pandit <Sa...@Chordiant.com>.

Hi Matthias,

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/t
rinidad-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.getSessionInt
ernal(ReplicatedSessionContext.java:375)
 
weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getValidSessi
on(ServletRequestImpl.java:2521)
 
weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInt
ernal(ServletRequestImpl.java:2090)
 
weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(Se
rvletRequestImpl.java:2057)
 
weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestIm
pl.java:1189)
 
weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction
.run(SecurityModule.java:535)
 
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bject.java:321)
 
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
)
 
weblogic.servlet.security.internal.SecurityModule.getUserSession(Securit
yModule.java:426)
 
weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Se
rvletSecurityManager.java:81)
 
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
letContext.java:1920)
 
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
ext.java:1890)
 
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
:1344)
            weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
            weblogic.work.ExecuteThread.run(ExecuteThread.java:181

Thanks,
Sabitha

-----Original Message-----
From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
Matthias Wessendorf
Sent: Wednesday, April 08, 2009 5:35 PM
To: MyFaces Development
Subject: Re: <trh:script> tag causes deadlock on weblogic 9.2 cluster

Hi,

so, the "old" ri is "clean" ?
What is the dump ?

can you post some more information ?

Also, does this reproduce with a (simple) Trinidad page?

Is it JSP(X) or Facelets ?

-Matthias

On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
<Sa...@chordiant.com> wrote:
> Hi ALL,
>
>
>
> We are facing this strange issue. We are in the release phase of our
> application.
>
>
>
> Any .jspx containing
>
> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used
with
> el-impl-1.0.jar.
>
>
>
> The same trinidad version is working fine when used with old
el-ri-1.0.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
>
>
>
> Quick response is very highly appreciated
>
>
>
> Thanks,
>
> Sabitha
>
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Re: tag causes deadlock on weblogic 9.2 cluster

Posted by Matthias Wessendorf <ma...@apache.org>.

Hi,

so, the "old" ri is "clean" ?
What is the dump ?

can you post some more information ?

Also, does this reproduce with a (simple) Trinidad page?

Is it JSP(X) or Facelets ?

-Matthias

On Wed, Apr 8, 2009 at 2:02 PM, Sabitha Gopal Pandit
<Sa...@chordiant.com> wrote:
> Hi ALL,
>
>
>
> We are facing this strange issue. We are in the release phase of our
> application.
>
>
>
> Any .jspx containing
>
> <trh:script> tag causes deadlock on weblogic 9.2 cluster when used with
> el-impl-1.0.jar.
>
>
>
> The same trinidad version is working fine when used with old el-ri-1.0.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
>
>
>
> Quick response is very highly appreciated
>
>
>
> Thanks,
>
> Sabitha
>
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf