Migration to 7.8.4 now throwing RestletServlet Exception


Out middleware (TicketService) uses the HTTP API to get case and ticket details based on a case ID and since we upgraded we are now seeing the following in the error message and no ticket details are returned to the middleware.

==> server/logs/bonita.2019-10-09.log <==
2019-10-09 14:42:57.900 -0400 INFO: org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/bonita] RestletServlet: [Restlet] Attaching application: org.bonitasoft.web.rest.server.BonitaRestletApplication@508124ca to URI: /bonita/API
2019-10-09 14:42:57.917 -0400 INFO: org.restlet.Component.BonitaRestletApplication Starting org.bonitasoft.web.rest.server.BonitaRestletApplication application
2019-10-09 14:43:01.458 -0400 SEVERE: org.bonitasoft.rest.context.RestContextCaseId org.bonitasoft.rest.context: Error during get Business Data Information: java.lang.IllegalArgumentException: org.bonitasoft.engine.exception.BonitaRuntimeException: USERNAME=mike.norris | org.bonitasoft.engine.commons.exceptions.SRetryableException: javax.persistence.PersistenceException: org.hibernate.HibernateException: Unable to access lob stream

==> server/logs/catalina.out <==
2019-10-09 14:43:01.557 ERROR 126949 --- [nio-8080-exec-3] c.m.services.ticket.TicketService        : Could not retrieve ticket caseid: 77040
2019-10-09 14:43:01.578  INFO 126949 --- [nio-8080-exec-7] c.m.s.a.i.AuthenticateInterceptor        : Attempting to authenticate with x-bonita-api-token: b364dc03-60d6-4f82-a7a3-20b717312694
2019-10-09 14:43:01.601  INFO 126949 --- [nio-8080-exec-7] c.m.s.a.i.AuthenticateInterceptor        : Authenticated  with user: user.alpha1 and x-bonita-api-token: b364dc03-60d6-4f82-a7a3-20b717312694

We've seen "Unable to access lob stream" before in other apps when code inappropriately handles autocommit in postgresql. We've disabled autocommit on postgresql but that made no difference to finding a resolution. Has anyone else ever experienced this issue?

1 answer


could you please tell us what is the postgres database version you are using?
don't you see any engine logs related to the issue?