as follow-up of earlier question (see question), here's 1 more interesting case. sometimes, quite random, following error pops up:
16/07/15 10:00: exception thrown com.ibm.xsp.acl.noaccesssignal @ com.ibm.domino.xsp.module.nsf.notescontext.checkaccess(notescontext.java:1726) @ com.ibm.domino.xsp.module.nsf.notescontext.serverprocesssignedresource(notescontext.java:999) @ com.ibm.domino.xsp.module.nsf.notescontext.setsignersessionrights(notescontext.java:956) @ com.ibm.domino.xsp.module.nsf.moduleclassloader$dynamicclassloader.loadclass(moduleclassloader.java:407) @ com.ibm.domino.xsp.module.nsf.moduleclassloader.loadclass(moduleclassloader.java:218) @ com.ibm.designer.runtime.application.loadclass(application.java:708) @ com.ibm.xsp.library.applicationfacesclassloader.loadclass(applicationfacesclassloader.java:54) @ com.ibm.xsp.page.compiled.compiledpagedriver.getclassforpagename(compiledpagedriver.java:169) @ com.ibm.xsp.page.compiled.compiledpagedriver.loadpage(compiledpagedriver.java:61) @ com.ibm.xsp.application.viewhandlereximpl._createviewroot(viewhandlereximpl.java:499) @ com.ibm.xsp.application.viewhandlereximpl.createviewroot(viewhandlereximpl.java:567) @ com.ibm.xsp.application.viewhandlereximpl.docreateview(viewhandlereximpl.java:142) @ com.ibm.xsp.application.viewhandlerex.createview(viewhandlerex.java:90) @ com.ibm.xsp.webapp.facesservlet.serviceview(facesservlet.java:251) @ com.ibm.xsp.webapp.facesservletex.serviceview(facesservletex.java:157) @ com.ibm.xsp.webapp.facesservlet.service(facesservlet.java:160) @ com.ibm.xsp.webapp.facesservletex.service(facesservletex.java:138) @ com.ibm.xsp.webapp.designerfacesservlet.service(designerfacesservlet.java:103) @ com.ibm.designer.runtime.domino.adapter.componentmodule.invokeservlet(componentmodule.java:576) @ com.ibm.domino.xsp.module.nsf.nsfcomponentmodule.invokeservlet(nsfcomponentmodule.java:1335) @ com.ibm.designer.runtime.domino.adapter.componentmodule$adapterinvoker.invokeservlet(componentmodule.java:853) @ com.ibm.designer.runtime.domino.adapter.componentmodule$servletinvoker.doservice(componentmodule.java:796) @ com.ibm.designer.runtime.domino.adapter.componentmodule.doservice(componentmodule.java:565) @ com.ibm.domino.xsp.module.nsf.nsfcomponentmodule.doservice(nsfcomponentmodule.java:1319) @ com.ibm.domino.xsp.module.nsf.nsfservice.doserviceinternal(nsfservice.java:662) @ com.ibm.domino.xsp.module.nsf.nsfservice.doservice(nsfservice.java:482) @ com.ibm.designer.runtime.domino.adapter.lcdenvironment.doservice(lcdenvironment.java:357) @ com.ibm.designer.runtime.domino.adapter.lcdenvironment.service(lcdenvironment.java:313) @ com.ibm.domino.xsp.bridge.http.engine.xspcmdmanager.service(xspcmdmanager.java:272) the user logged in, has permissions, nothing out of ordinary, might have done same action many times in row (while testing, opening , saving documents, etc.) , error occurs. our application strange one: multiple active xpages in several windows or iframes, , data kept "in memory".
any idea?
one line jumps out:
at com.ibm.domino.xsp.module.nsf.notescontext.setsignersessionrights(notescontext.java:956)
does application use sessionassigner? if so, xpages-related design elements signed same id? if not, ensure are.
i'm not sure latest symptoms of are, in earlier releases caused crashes.
Comments
Post a Comment