Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot invoke "jakarta.faces.webapp.FacesServlet.destroy()" because "this.delegate" is null #537

Closed
slapraik-intec opened this issue Jun 13, 2024 · 1 comment
Milestone

Comments

@slapraik-intec
Copy link

Domino 14 / Jakarta EE 3.0.0 / PrimeFaces 14.0.0.

Sometimes the following exception is being generated...

java.lang.NullPointerException: Cannot invoke "jakarta.faces.webapp.FacesServlet.destroy()" because "this.delegate" is null
at org.openntf.xsp.jakarta.faces.nsf.NSFFacesServlet.destroy(NSFFacesServlet.java:225)
at org.openntf.xsp.jakartaee.servlet.NewHttpServletWrapper.destroy(NewHttpServletWrapper.java:41)
at org.openntf.xsp.jakartaee.MappingBasedServletFactory.getExecutorServlet(MappingBasedServletFactory.java:152)
at org.openntf.xsp.jakartaee.MappingBasedServletFactory.getServletMatch(MappingBasedServletFactory.java:123)
at com.ibm.designer.runtime.domino.adapter.ComponentModule$ServletInvoker.doService(ComponentModule.java:811)
at com.ibm.designer.runtime.domino.adapter.ComponentModule.doService(ComponentModule.java:589)
at com.ibm.domino.xsp.module.nsf.NSFComponentModule.doService(NSFComponentModule.java:1336)
at com.ibm.domino.xsp.module.nsf.NSFService.doServiceInternal(NSFService.java:725)
at com.ibm.domino.xsp.module.nsf.NSFService.doService(NSFService.java:515)
at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.doService(LCDEnvironment.java:371)
at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.service(LCDEnvironment.java:327)
at com.ibm.domino.xsp.bridge.http.engine.XspCmdManager.service(XspCmdManager.java:302)

@jesse-gallagher
Copy link
Member

My best guess for what caused this is thread contention, which would be worth investigating specifically, but for now I added a null guard around the destroy() call to prevent this specific problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants