• Type: Bug
    • Status: Closed
    • Resolution: Fixed
    • Affects Version/s: 7.4.2, 7.4.3
    • Fix Version/s: 7.5.2
    • Labels:
    • Environment:

      tested on Windows 7, Bonita Studio

    • Edition:
    • Reference:
    • Steps to reproduce:
      1. Import attached RestApiTestPage
      2. Install attached
      3. Preview page - random page parts are not loaded correctly
      1. Import attached RestApiTestPage 2. Install attached 3. Preview page - random page parts are not loaded correctly



      I am struggling with the REST API extension issue.

      When multiple requests to API are sent at the same time, some of them are not executed properly. In the example I am sharing, API should return paged list of natural numbers. On the test page I declare 6 external API variables for 6 subsequent pages and I am listing them in 6 colums. Some responses contain an array of numbers as expected. Some of them just contain a file system error "The system cannot find the path specified" or "Low disk space". There is also an entry in catalina.log:

      INFO: org.apache.coyote.http11.Http11Processor An error occurred in processing while on a non-container thread. The connection will be closed immediately Software caused connection abort: socket write error
      	at Method)
      	at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(
      	at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(
      	at org.apache.coyote.http11.InternalOutputBuffer.flush(
      	at org.apache.coyote.http11.AbstractHttp11Processor.action(
      	at org.apache.coyote.Response.action(
      	at org.apache.catalina.connector.OutputBuffer.doFlush(
      	at org.apache.catalina.connector.OutputBuffer.flush(
      	at org.apache.catalina.connector.Response.flushBuffer(
      	at org.apache.catalina.connector.ResponseFacade.flushBuffer(
      	at org.springframework.http.server.ServletServerHttpResponse.flush(
      	at org.springframework.web.socket.sockjs.transport.session.AbstractHttpSockJsSession.writeFrameInternal(
      	at org.springframework.web.socket.sockjs.transport.session.AbstractSockJsSession.writeFrame(
      	at org.springframework.web.socket.sockjs.transport.session.AbstractSockJsSession.sendHeartbeat(
      	at org.springframework.web.socket.sockjs.transport.session.AbstractSockJsSession$
      	at java.util.concurrent.Executors$
      	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(
      	at java.util.concurrent.ScheduledThreadPoolExecutor$
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(
      	at java.util.concurrent.ThreadPoolExecutor$

      I have also noticed that every request creates a folder like tomcat\server\temp\bonita_portal_12724@hostname\tenants\1\custompage_restExtension1491231062900
      The entry in bonita.log says that I can remove it after restart:

      WARNING: The custom page temporary lib directory C:\BonitaBPMCommunity-7.4.2\workspace\tomcat\server\temp\bonita_portal_12724@hostname\tenants\1\custompage_restExtension1491231928852 cannot be deleted. This is likely to be due to a JDK bug on Windows. You can safely delete it after a server restart.

      But simple calculation tells me that if I have a ~10MB extension and 1 request per second I'll be forced to restart the system every day if I had a 1TB disk space only for requests temp data (which is exactly the same all the time). I assume, the issue does not occur on Unix systems but still I would not expect dropping the classloader content to the filesystem.

      Why does it behave like that? It is making REST API Extension unusable and littering the filesystem with tons of redundant data.




            • Assignee:
              antoine.mottier Antoine Mottier
              mmichalak Maciej Michalak
            • Watchers:
              3 Start watching this issue


              • Created: