Internal Website Search

without restart, which gave us a lot of problems and needed a lot of time for debugging and fixing

is only caused in our OSGi example. I believe you must debug the OSGi example to analyze the issue

on some debugging I came to the assumptions that: 1) ObjectDB calls update() based

Hi, If I put the .jar into /opt/Tomcat/lib/, then where the .conf should be in? And the .odb? When I debug the Eclipse web project, I export all things into a .war file. Then I use Tomcat's web deploy tool by the .war file. However, if I

of this message may change from WARNING to DEBUG in the future. support Support I understand. Thank you. zmirc Mircea Chirac

> Here is the log file in DEBUG mode, but there is nothing special or detailed error description

;logger name="server" level="debug" /> During sudden events of socket creations

seems to be healthy. These stack traces are normal when using DEBUG level logging. As the result

We encountered an issue with the logging mechanism. We enabled full logging (logger name="*" level="debug") and logged to a file with limited size. We did not configure a log-archive (log-archive path="" retain="0"). That caused an exception when the log file reached its size limit

> Here's the stacktrace (copy+paste from debug output): com