• NoAccessSignal Exception thrown when trying to “Load More” in Mobile Controls view

    By Matt White 1 decade ago

     

    I have an XPages app running on 8.5.3 UP1 with a mobile controls interface. It works fine on my dev and test servers, but in production we're seeing the following intermittent error when a user clicks the "Load More" button in the view control:

    5/10/12 4:12 PM: Exception Thrown com.ibm.xsp.acl.NoAccessSignal at com.ibm.domino.xsp.module.nsf.NotesContext.checkAccess(NotesContext.java:1611) at com.ibm.domino.xsp.module.nsf.NotesContext.serverProcessSignedResource(NotesContext.java:955) at com.ibm.domino.xsp.module.nsf.NotesContext.setSignerSessionRights(NotesContext.java:926) at com.ibm.domino.xsp.module.nsf.ModuleClassLoader$DynamicClassLoader.loadClass(ModuleClassLoader.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:619) at com.ibm.domino.xsp.module.nsf.ModuleClassLoader.loadClass(ModuleClassLoader.java:171) at java.lang.ClassLoader.loadClass(ClassLoader.java:619) at com.ibm.designer.runtime.Application.loadClass(Application.java:708) at com.ibm.xsp.library.ApplicationFacesClassLoader.loadClass(ApplicationFacesClassLoader.java:54) at com.ibm.xsp.page.compiled.CompiledPageDriver.getClassForPageName(CompiledPageDriver.java:166) at com.ibm.xsp.page.compiled.CompiledPageDriver.loadPage(CompiledPageDriver.java:61) at com.ibm.xsp.application.ViewHandlerExImpl._createViewRoot(ViewHandlerExImpl.java:489) at com.ibm.xsp.application.ViewHandlerExImpl.createViewRoot(ViewHandlerExImpl.java:557) at com.ibm.xsp.application.ViewHandlerExImpl.doCreateView(ViewHandlerExImpl.java:141) at com.ibm.xsp.application.ViewHa ndlerEx.createView(ViewHandlerEx.java:90) at com.ibm.xsp.webapp.FacesServlet.serviceView(FacesServlet.java:238) at com.ibm.xsp.webapp.FacesServletEx.serviceView(FacesServletEx.java:200) at com.ibm.xsp.webapp.FacesServlet.service(FacesServlet.java:160) at com.ibm.xsp.webapp.FacesServletEx.service(FacesServletEx.java:137) at com.ibm.xsp.webapp.DesignerFacesServlet.service(DesignerFacesServlet.java:103) at com.ibm.designer.runtime.domino.adapter.ComponentModule.invokeServlet(ComponentModule.java:576) at com.ibm.domino.xsp.module.nsf.NSFComponentModule.invokeServlet(NSFComponentModule.java:1267) at com.ibm.designer.runtime.domino.adapter.ComponentModule$AdapterInvoker.invokeServlet(ComponentModule.java:847) at com.ibm.designer.runtime.domino.adapter.ComponentModule$ServletInvoker.doSe rvice(ComponentModule.java:796) at com.ibm.designer.runtime.domino.adapter.ComponentModule.doService(ComponentModule.java:565) at com.ibm.domino.xsp.module.nsf.NSFComponentModule.doService(NSFComponentModule.java:1251) at com.ibm.domino.xsp.module.nsf.NSFService.doServiceInternal(NSFService.java:598) at com.ibm.domino.xsp.module.nsf.NSFService.doService(NSFService.java:421) at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.doService(LCDEnvironment.java:341) at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.service(LCDEnvironment.java:297) at com.ibm.domino.xsp.bridge.http.engine.XspCmdManager.service(XspCmdManager.java:272)

    5/10/12 4:43 PM: Exception Thrown com.ibm.xsp.acl.NoAccessSignal at com.ibm.domino.xsp.module.nsf.NotesContext.checkAccess(NotesContext.java:1611) &nbsp ; at com.ibm.domino.xsp.module.nsf.NotesContext.serverProcessSignedResource(NotesContext.java:955) at com.ibm.domino.xsp.module.nsf.NotesContext.setSignerSessionRights(NotesContext.java:926) at com.ibm.domino.xsp.module.nsf.ModuleClassLoader$DynamicClassLoader.loadClass(ModuleClassLoader.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:619) at com.ibm.domino.xsp.module.nsf.ModuleClassLoader.loadClass(ModuleClassLoader.java:171) at java.lang.ClassLoader.loadClass(ClassLoader.java:619) at com.ibm.designer.runtime.Application.loadClass(Application.java:708) at com.ibm.xsp.library.ApplicationFacesClassLoader.loadClass(ApplicationFacesClassLoader.java:54) at com.ibm.xsp.page.compiled.CompiledPageDriver.getClassForPageName(CompiledPageDriver.java:166) at com.ibm .xsp.page.compiled.CompiledPageDriver.loadPage(CompiledPageDriver.java:61) at com.ibm.xsp.application.ViewHandlerExImpl._createViewRoot(ViewHandlerExImpl.java:489) at com.ibm.xsp.application.ViewHandlerExImpl.createViewRoot(ViewHandlerExImpl.java:557) at com.ibm.xsp.application.ViewHandlerExImpl.doCreateView(ViewHandlerExImpl.java:141) at com.ibm.xsp.application.ViewHandlerEx.createView(ViewHandlerEx.java:90) at com.ibm.xsp.webapp.FacesServlet.serviceView(FacesServlet.java:238) at com.ibm.xsp.webapp.FacesServletEx.serviceView(FacesServletEx.java:200) at com.ibm.xsp.webapp.FacesServlet.service(FacesServlet.java:160) at com.ibm.xsp.webapp.FacesServletEx.service(FacesServletEx.java:137) at com.ibm.xsp.webapp.DesignerFacesServlet.service(DesignerFacesServlet.java:103) & nbsp; at com.ibm.designer.runtime.domino.adapter.ComponentModule.invokeServlet(ComponentModule.java:576) at com.ibm.domino.xsp.module.nsf.NSFComponentModule.invokeServlet(NSFComponentModule.java:1267) at com.ibm.designer.runtime.domino.adapter.ComponentModule$AdapterInvoker.invokeServlet(ComponentModule.java:847) at com.ibm.designer.runtime.domino.adapter.ComponentModule$ServletInvoker.doService(ComponentModule.java:796) at com.ibm.designer.runtime.domino.adapter.ComponentModule.doService(ComponentModule.java:565) at com.ibm.domino.xsp.module.nsf.NSFComponentModule.doService(NSFComponentModule.java:1251) at com.ibm.domino.xsp.module.nsf.NSFService.doServiceInternal(NSFService.java:598) at com.ibm.domino.xsp.module.nsf.NSFService.doService(NSFService.java:421) at com.ibm.designer.runtime.domino.adapter. LCDEnvironment.doService(LCDEnvironment.java:341) at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.service(LCDEnvironment.java:297) at com.ibm.domino.xsp.bridge.http.engine.XspCmdManager.service(XspCmdManager.java:272)

    Any thoughts would be appreciated.

    Matt

    • Identified Problem.

      By Matt White 1 decade ago

      OK this turned out to be a very odd issue which affected iOS devices specifically. I had written some extra code to detect if the app was running in standalone mode (ie that the user had created a shortcut to the app on the home screen). This code loops through all tags that have an onclick event and stops them from launching Safari and forces them to run inside the standalone browser window. In the case of the load more button this is what was causing the error on the server. I still don't understand why that was an error, but it was an easy fix, simply don't process the Load More button when I loop through everything else in the page.

      • Great!

        By Philippe Riand 1 decade ago

        Didn't see your response before, so I'm happy that you found the solution!

    • This looks strange

      By Philippe Riand 1 decade ago

      It seems that the authentication is lost between the request. Can you isolate the problem, or send us a DB that reproduces it, with the steps? Is more being clicked after the session times out?