This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


~Andy Rejumiskiobu
Feb 23, 2016, 3:51 PM
11 Posts

Domino Access Service Limit

  • Category: Application Development
  • Platform: All Platforms
  • Release: 9.0.1
  • Role: Administrator,Developer
  • Tags: rest access services limit
  • Replies: 2

I am using Domino Access Services to get data from a view. If I get a small or medium amount of data, everything works fine, but if i'm getting a large amount of data from a large view, the request simply stops after a while, sometimes with and sometimes without an error message on the Server.

Is there a timeout limit on the Server or some kind of amount limit? What might be the problem?

If there is an error on the server it looks like this one

HTTP JVM: java.io.IOException: HTTP: Internal error:
at com.ibm.domino.xsp.bridge.http.servlet.XspCmdHttpServletResponse.write(XspCmdHttpServletResponse.java:860)
at com.ibm.domino.xsp.bridge.http.servlet.XspCmdServletOutputStream.write(XspCmdServletOutputStream.java:72)
at com.ibm.commons.util.io.StreamUtil.copyStream(StreamUtil.java:137)
at com.ibm.commons.util.io.StreamUtil.copyStream(StreamUtil.java:118)
at com.ibm.domino.das.servlet.DasHttpResponseWrapper$EncodedOutputStream.flush(DasHttpResponseWrapper.java:255)
at com.ibm.domino.das.servlet.DasHttpResponseWrapper$EncodedOutputStream.close(DasHttpResponseWrapper.java:265)
at org.apache.wink.server.internal.handlers.FlushResultHandler$FlushHeadersOutputStream.close(FlushResultHandler.java:345)
at sun.nio.cs.StreamEncoder$CharsetSE.implClose(StreamEncoder.java:454)
at sun.nio.cs.StreamEncoder.close(StreamEncoder.java:183)
at java.io.OutputStreamWriter.close(OutputStreamWriter.java:282)
at com.ibm.domino.das.resources.ViewEntryCollectionResource$1.write(ViewEntryCollectionResource.java:224)
at org.apache.wink.common.internal.providers.entity.StreamingOutputProvider.writeTo(StreamingOutputProvider.java:60)
at org.apache.wink.common.internal.providers.entity.StreamingOutputProvider.writeTo(StreamingOutputProvider.java:35)
at org.apache.wink.server.internal.handlers.FlushResultHandler.handleResponse(FlushResultHandler.java:199)
at org.apache.wink.server.handlers.AbstractHandler.handleResponse(AbstractHandler.java:38)
at org.apache.wink.server.handlers.ResponseHandlersChain.handle(ResponseHandlersChain.java:26)
at org.apache.wink.server.handlers.ResponseHandlersChain.handle(ResponseHandlersChain.java:22)
at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:63)
at org.apache.wink.server.handlers.AbstractHandler.handleResponse(AbstractHandler.java:39)
at org.apache.wink.server.handlers.ResponseHandlersChain.handle(ResponseHandlersChain.java:26)
at org.apache.wink.server.handlers.ResponseHandlersChain.handle(ResponseHandlersChain.java:22)
at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:63)
at org.apache.wink.server.handlers.AbstractHandler.handleResponse(AbstractHandler.java:39)
at org.apache.wink.server.handlers.ResponseHandlersChain.handle(ResponseHandlersChain.java:26)
at org.apache.wink.server.handlers.ResponseHandlersChain.handle(ResponseHandlersChain.java:22)
at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:63)
at org.apache.wink.server.internal.log.Responses.handleResponse(Responses.java:90)
at org.apache.wink.server.handlers.ResponseHandlersChain.handle(ResponseHandlersChain.java:26)
at org.apache.wink.server.handlers.ResponseHandlersChain.handle(ResponseHandlersChain.java:22)
at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:63)
at org.apache.wink.server.handlers.AbstractHandlersChain.run(AbstractHandlersChain.java:48)
at org.apache.wink.server.internal.RequestProcessor.handleRequestWithoutFaultBarrier(RequestProcessor.java:212)
at org.apache.wink.server.internal.RequestProcessor.handleRequest(RequestProcessor.java:154)
at org.apache.wink.server.internal.servlet.RestServlet.service(RestServlet.java:119)
at com.ibm.domino.services.AbstractRestServlet.doService(AbstractRestServlet.java:75)
at com.ibm.domino.das.servlet.DasServlet.doService(DasServlet.java:232)
at com.ibm.domino.services.AbstractRestServlet.service(AbstractRestServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at com.ibm.domino.xsp.adapter.osgi.OSGIModule.invokeServlet(OSGIModule.java:167)
at com.ibm.domino.xsp.adapter.osgi.OSGIModule.access$0(OSGIModule.java:153)
at com.ibm.domino.xsp.adapter.osgi.OSGIModule$1.invokeServlet(OSGIModule.java:134)
at com.ibm.domino.xsp.adapter.osgi.AbstractOSGIModule.invokeServletWithNotesContext(AbstractOSGIModule.java:181)
at com.ibm.domino.xsp.adapter.osgi.OSGIModule.doService(OSGIModule.java:128)
at com.ibm.domino.xsp.adapter.osgi.OSGIService.doService(OSGIService.java:417)
at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.doService(LCDEnvironment.java:350)
at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.service(LCDEnvironment.java:306)
at com.ibm.domino.xsp.bridge.http.engine.XspCmdManager.service(XspCmdManager.java:272)

I already set the client timeout which should not be the Problem. Even if I call the URL in browser this happens.

any idea? thx

~Justin Chugerochekettu
Feb 23, 2016, 8:39 PM
19 Posts
Please provide a sample request ...
I'm not sure what you mean by a large amount of data.  Are you asking for hundreds of rows in each request?

By the way, the best practice is to page through a large view by requesting < 100 rows at a time.  That way each request completes relatively quickly and your Domino server can handle a greater number of simultaneous requests.  In other words, it will scale much better.

Thanks.

-- Dave
~Andy Rejumiskiobu
Feb 24, 2016, 8:14 AM
11 Posts
amount

Thanks for your suggestion. I' am talking about ~ 80.000 view entries with each ~20 cols.

Seems to be too much but it's unclear if it's too much data or too much time or whatever.

I added now

&compact=true&entrycount=false&systemcolumns=2058

to the URL which shortens the amount of data and it seems that the Server could manage to deliver the request.


This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal