[JBoss Seam] - Errors leading up to an out of memory situation
by modoc
My Seam app has been running for almost a month without issue. This morning it ran into any out of memory situation. As it was a live site I had to just reboot instead of trying to figure out where the memory was being allocated or doing any diagnostics. In the logs I see the following errors just before the out of memory situation happens.
I don't know that it is a cause and effect situation but the sequence is suspicious. Any idea what this error means?
java.lang.NullPointerException
| at com.sun.faces.context.ApplicationMap.get(ExternalContextImpl.java:858)
| at org.jboss.seam.contexts.BasicContext.get(BasicContext.java:48)
| at org.jboss.seam.contexts.Contexts.startup(Contexts.java:272)
| at org.jboss.seam.contexts.Lifecycle.beginSession(Lifecycle.java:187)
| at org.jboss.seam.contexts.ServletLifecycle.beginSession(ServletLifecycle.java:124)
| at org.jboss.seam.servlet.SeamListener.sessionCreated(SeamListener.java:44)
| at org.apache.catalina.session.StandardSession.tellNew(StandardSession.java:397)
| at org.apache.catalina.session.StandardSession.setId(StandardSession.java:369)
| at org.apache.catalina.session.ManagerBase.createSession(ManagerBase.java:827)
| at org.apache.catalina.session.StandardManager.createSession(StandardManager.java:291)
| at org.apache.catalina.connector.Request.doGetSession(Request.java:2295)
| at org.apache.catalina.connector.Request.getSession(Request.java:2066)
| at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:833)
| at com.sun.faces.context.SessionMap.getSession(ExternalContextImpl.java:995)
| at com.sun.faces.context.SessionMap.get(ExternalContextImpl.java:955)
| at org.jboss.seam.contexts.BasicContext.get(BasicContext.java:48)
| at org.jboss.seam.Component.getInstance(Component.java:1836)
| at org.jboss.seam.Component.getInstance(Component.java:1814)
| at org.jboss.seam.web.Session.getInstance(Session.java:122)
| at org.jboss.seam.contexts.FacesLifecycle.beginRequest(FacesLifecycle.java:54)
| at org.jboss.seam.jsf.SeamPhaseListener.beforeRestoreView(SeamPhaseListener.java:361)
| at org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:139)
| at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:116)
| at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222)
| at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:82)
| at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68)
| at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68)
| at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68)
| at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68)
| at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:127)
| at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:277)
| at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68)
| at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68)
| at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:149)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| 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:230)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:595)
I also see several of these:
08:24:28,112 ERROR [[/10MinuteMail]] Session event listener threw exception
| java.lang.ArrayIndexOutOfBoundsException
Any help would be appreciated.
Thanks!
Devon
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081770#4081770
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081770
18 years, 7 months
[JBoss Tools (users)] - Re: EJB3 Support
by rob.stryker＠jboss.com
The EJB3-project was nothing more than a regular old java project that added certain jars to a classpath. It provided no other functionality at all other than adding jars to a classpath.
It served two purposes during its lifespan. Originally back in the old JBoss IDE, it was the only ejb3 tools implementation around. After we starated moving forward from there, it served as a stop-gap mechanism until webtools implemented an ejb3 facet in their EJB Project.
The only other purpose it served was to try to be a "module" without being a module. The goal behind it was to allow both an ejb3 module and a web module to live in the same project for what would become our seam project. That's no longer an issue, as the seam project has now been implemented in another way.
So to summarize, it's purposes were to wait for WTP to get ejb3 out, and to potentially create a seam project. As WTP now has ejb 3.0 facets available and a Seam project has been created in another way, the EJB3 project needed to go.
Your options are basically to use the WTP EJB project with a 3.0 facet, or use a plain java project but add the ejb3 libraries to your project's build path yourself. (right click on project, select build path, go to the Libraries tab, select Add Library, and there should be a jboss ejb3 library there. )
I realize this is slightly inconvenient, but the idea of keeping around a project who's entire reason for existing had disappeared was not a good one to entertain.
- Rob
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081766#4081766
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081766
18 years, 7 months
[JBoss Portal] - Edit Mode problem
by forgoodorforawesome
I've created a new portlet, and I cannot get the edit mode working correctly. When a user clicks the 'Edit' link on the top of the window nothing shows up in the window. I have two jsps, view.jsp and edit.jsp. view.jsp shows up correctly in view mode, but edit.jsp is not being shown in edit mode.
Here is my portlet.xml file:
<portlet>
| <portlet-name>EmmiPortlet</portlet-name>
| <portlet-class>com.rightfield.testing.portlet.EmmiPortlet</portlet-class>
| <supports>
| <mime-type>text/html</mime-type>
| <portlet-mode>VIEW</portlet-mode>
| <portlet-mode>EDIT</portlet-mode>
| </supports>
| <portlet-info>
| <title>Emmi Portlet</title>
| </portlet-info>
| </portlet>
so, I do have the Edit mode enabled for this portlet.
I have two jsps, view and edit. In my portlet class, the doView() method, I use the portlet request dispatcher to show the view.jsp:
PortletRequestDispatcher prd = getPortletContext().getRequestDispatcher("/WEB-INF/jsp/view.jsp");
| prd.include(request, response);
in doEdit(), I do the same:
PortletRequestDispatcher prd = getPortletContext().getRequestDispatcher("/WEB-INF/jsp/edit.jsp");
| prd.include(request, response);
The edit.jsp file is included inside the war file that is deployed. It is quite simple:
<%@ taglib uri="http://java.sun.com/portlet" prefix="portlet" %>
| <%@ taglib uri="/WEB-INF/tlds/c.tld" prefix="c" %>
| <%@ page contentType="text/html" isELIgnored="false"%>
| <portlet:defineObjects/>
| edit portlet
|
Am I missing something here? I thought if I enabled it in portlet.xml that it should work. I'm not seeing any exceptions in the log files, so I think I must be missing a step.
Here are my specs:
JBoss Portal Version: 2.6.1
Did you get Portal from CVS? or download it? download
JBoss AS Version: 4.0.5
Database Vendor and Version: hypersonic
JDBC Connector and Version
OS Platform: XP
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081759#4081759
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081759
18 years, 7 months