[JBoss Seam] - Property 'debug' not found on type org.jboss.seam.Namespace
by lcoetzee
Hi,
using a build from CVS 18/07/2007 I can no longer access the debug.jsf page. I get the following exception:
| 8:08:45,946 WARN [lifecycle] phase(RENDER_RESPONSE 6,com.sun.faces.context.FacesContextImpl@1b36a91) threw exception: javax.faces.FacesException: javax.el.PropertyNotFoundException: /file:/home/lcoetzee/app-servers/jboss-4.2.0.GA/server/default/tmp/deploy/tmp58806NAP.ear-contents/NAP-exp.war/WEB-INF/lib/jboss-seam-debug.jar!/META-INF/debug.xhtml @63,90 rendered="#{empty org.jboss.seam.debug.contexts.conversationEntries}": Property 'debug' not found on type org.jboss.seam.Namespace javax.el.PropertyNotFoundException: /file:/home/lcoetzee/app-servers/jboss-4.2.0.GA/server/default/tmp/deploy/tmp58806NAP.ear-contents/NAP-exp.war/WEB-INF/lib/jboss-seam-debug.jar!/META-INF/debug.xhtml @63,90 rendered="#{empty org.jboss.seam.debug.contexts.conversationEntries}": Property 'debug' not found on type org.jboss.seam.Namespace
| javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:373)
| com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:241)
| com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249)
| org.jboss.seam.debug.jsf.SeamDebugPhaseListener.beforePhase(SeamDebugPhaseListener.java:51)
| com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222)
| com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
| javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:147)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:82)
| org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
| org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68)
| org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68)
| org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68)
| org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85)
| org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68)
| org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:61)
| org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68)
| org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44)
| org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68)
| org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:149)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
| org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
| org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
| org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
| org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
| org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:543)
| org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
| org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:853)
| org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:579)
| org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1513)
| java.lang.Thread.run(Thread.java:619)
|
Any suggestions ?
Thanks
Louis
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065474#4065474
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065474
18Â years, 11Â months
[JBossCache] - Re: Could this be deadlock when modifying TreeCache
by ramdas
We have a newer version of JBoss cache and jgroups which we were suggested to download and use when we initially deployed this application in production along with JBoss 3.2.6.
Given below is the dump from the Manifest files from the JBoss cache/jgroups and Jboss AS.
The JBoss AS is clustered and we currently have 8 members in the cluster.
Almost all our work is handled within the Tomcat threads running within JBoss.
The application outages as a result of the threads blocking has become more frequent(every couple of days) in the last month. Given this scenario, we as a team are willing to be a bit more aggressive in terms of changes to the existing infrastructure software though changing the AS version would be a major one and be more difficult to test out and implement. I would prefer if we could tune the existing software version
Thanks for your time and attention on this issue.
-Ramdas
---------------JBoss cache---------------------------------
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.1
Created-By: 1.4.2-b28 (Sun Microsystems Inc.)
Built-By: bela
Created-On: June 1 2005
Main-Class: org.jboss.cache.Version
Name: JBossCache
Specification-Title: JBossCache
Specification-Version: 1.2.3
Specification-Vendor: JBoss Inc.
Implementation-Title: JBossCache
Implementation-Version: 1.2.3
Implementation-Vendor: JBoss Inc.
----------------------------JGroups----------------------
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.1
Created-By: Apache Ant 1.5Beta2
Main-Class: org.jgroups.Version
Implementation-Version: 2.2.9 beta
-------------------------JBoss AS(jboss.jar)--------------
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.2
Created-By: 1.4.2_07-b05 (Sun Microsystems Inc.)
Specification-Title: JBoss
Specification-Version: 3.2.6
Specification-Vendor: JBoss (http://www.jboss.org/)
Implementation-Title: JBoss [WonderLand]
Implementation-URL: http://www.jboss.org/
Implementation-Version: 3.2.6 (build: CVSTag=JBoss_3_2_6 date=20050802)
Implementation-Vendor: JBoss.org
Implementation-Vendor-Id: http://www.jboss.org/
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065461#4065461
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065461
18Â years, 11Â months