6 | ObjectDB is opening too many sockets logging enabled: <logger name="server" level="debug" /> During sudden events of socket |
6 | First query takes 4+ minutes to complete); } return dtoList; } 1. What can we do to enable debugging/profiling information in the logs? 2 |
6 | Not Enhanced: ...: com.objectdb.o.TEX: Type ..._$$_javassist_1 is not found.agent" level="error" /> </general> The level of this message may change from WARNING to DEBUG in |
6 | Pre-detach loading: retrieval by navigation not working in if statement of it, preventing discovery of the real problem.) Similarly, using debug logging can also trigger loading |
6 | em.flush(); em.clear(); loosing data and not persisting managed objects) This is the last entries in the log with log level debug. awhawks Adam W. Hawks As far as |
6 | Query can't see recently persisted object.setParameter("oid", oid); if ("-62e6083d:1612795a01c:-6e65".equals(oid)) { logger.debug |
6 | can removing an entity throw an exception if the entity is in use? reports broken references so it could be very helpful during testing and debugging in identifying |
1 | Error on commit DEBUG level logging. As the result of the exception in #1 you should have in the log file lines |
1 | Memory leak in com.objectdb.o.CST if there is something I can log in the debug to output the connection pool settings to confirm? Trianglehead |
