Chris Stewart

Over the weekend we applied SSL to a Tomcat 6 instance that runs a JSF/Guice application. After the update, we're noticing OutOfMemory exceptions on the machine and it has effectively gotten to a crawl in performance. The application hasn't changed so it's hard to suggest that's the problem. I imagine that SSL adds overhead to Tomcat but I wouldn't have thought it would be this bad. Can anyone suggest a place or two to investigate? I'm at a loss on where to look right now.

I'm attempting to create "selected row" functionality in a dataTable. I've seen a number of posts regarding problems with using h:selectOneRadio inside of a h:dataTable. Those were all from 4-5 years ago, however. I've yet to find anything more recent on the subject. I'm using JSF RI 1.2_12-b01-FCS and I was wondering if anyone knows the status of this issue, or has experienced it themselves? I've attempted the JavaScript based workarounds in the old threads, but they don't have any effect for me, for whatever reason.

Oh wow, good point. I never even put it together but we have seen OutOfMemory exceptions every 7 days or so. I'll set the timeout to something and see if I can handle that exception gracefully. Any tips on that?

I'm getting this error in my logs and cannot figure out why I'm seeing this. In my web.xml I have an element to specify no session timeout. I'll post that below as well.

org.apache.catalina.core.StandardWrapperValve invoke SEVERE: Servlet.service() for servlet Faces Servlet threw exception javax.faces.application.ViewExpiredException: viewId:/index.jsf - View /index.jsf could not be restored. at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:186) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:104) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:154) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:260) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:366) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:493) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:147) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263) at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:852) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:584) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1508) at java.lang.Thread.run(Unknown Source)

<session-config> <session-timeout>0</session-timeout> </session-config>

I come from an ASP.NET background and there was an event there called page load. It would be fired before the page actually rendered to the browser. I'm wondering if there is something similar in JSF. I'd like to check something in the database before displaying the initial page (index.jsf) to the user. Possible?

Anyone?

Here's my environment:

JSF RI 1.2
RichFaces 3.2.1
Facelets 1.1.13
Tomcat 6.0.14

The application runs very well for the first few days. Around 7-10 days in, we get an OutOfMemoryError thrown and here's the stack trace:

Sep 9, 2008 11:36:07 AM com.sun.faces.lifecycle.Phase doPhase SEVERE: JSF1054: (Phase ID: RESTORE_VIEW 1, View ID: ) Exception thrown during phase execution: javax.faces.event.PhaseEvent[source=com.sun.faces.lifecycle.LifecycleImpl@aaa10] Sep 9, 2008 11:40:41 AM org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler process SEVERE: Error reading request, ignored java.lang.OutOfMemoryError: Java heap space at org.apache.coyote.http11.InternalAprInputBuffer.<init>(InternalAprInputBuffer.java:59) at org.apache.coyote.http11.Http11AprProcessor.<init>(Http11AprProcessor.java:90) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.createProcessor(Http11AprProtocol.java:622) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:577) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1508) at java.lang.Thread.run(Unknown Source) Sep 9, 2008 11:42:08 AM org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler process SEVERE: Error reading request, ignored java.lang.OutOfMemoryError: Java heap space

Has anyone had problems like this? None of the errors point to specific points in the code. I can only imagine there are issues with the libraries we're using and possibly the mix of them working together. Any help is appreciated.

Same result. Man, this is killing me. It worked like a charm as little as a week ago. The 1st version of the app is in production now and having no issues.

Here's a piece from the JSF file:

<h:commandLink id="lnkLogout1" action="#{LoginController.logout}" value="Logout" />

The LoginController:

public class LoginController { // stuff... public void logout() throws IOException { // stuff... } }

faces-config.xml

<managed-bean> <managed-bean-name>LoginController</managed-bean-name> <managed-bean-class>com.company.product.controller.LoginController</managed-bean-class> <managed-bean-scope>session</managed-bean-scope> </managed-bean>

And for reference, I changed the method name to "getLogout()" and I'm still getting the same error.

Right, and it has been working that way for properties, but logout is an action. It's never been called "getLogout()". It's always been "logout()" and only now is it showing up as an error.

I went ahead and migrated to MyFaces 1.2.2 (issue in 1.2.3 with Tomahawk 1.1.6, go figure) since that's something I've been wanting to do. I'm getting the same error message even after the upgrade. Hmm...

I've been working on an application and everything has been running fine. Suddenly, a few days ago, I'm getting an exception thrown:

Aug 28, 2008 1:06:33 PM com.sun.facelets.FaceletViewHandler handleRenderException SEVERE: Error Rendering View[/index.xhtml] javax.el.PropertyNotFoundException: Property 'logout' not found on type com.company.product.controller.LoginController at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193) at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170) at javax.el.BeanELResolver.property(BeanELResolver.java:279) ...

It's kind of odd that "logout" is being referred to as a property when in fact it's a method of the LoginController class. It's declared in EL as an action for a commandlink.

I've been running this code for months with no problems. I think the only changes I made were upgrading to 1.2_09 from 1.2_08 of the JSF RI. Does anyone have any idea why this would be failing?

While that element looked promising, it ends up breaking the application I posted above. When you click the link from the index.jsp page, it does in fact forward to the detail.jsp page, but the ID value of the bean is 0 instead of the value set in the link. It works as expected without the element in the faces-config.xml file.

Anyone?