Hello,
I've been using BaseX (version 7.3.1 with Tomcat 8) to store an XML database from XML files and using XQuery to query the database. It works great before with simple Java servlet as I recall. After that, I updated to use Spring Boot (version 1.5.2) for this web application (only update from Java servlet to Spring Controller, the core to query BaseX doesn't change), and it seems this weird exception java.io.IOException: Stream Closed appears randomly by 100000 times in Tomcat's log (catalina.out).
I tried to catch this exception in my web application but it is not able to catch. My web application's log (secore.log) also couldn't catch this error, only Tomcat's log (catalina.out) logs this error but with 100000 times (the log file is huge).
Any idea to solve this problem will help me a lot?
Here is the stack trace in catalina.out for 1 exception: https://pastebin.com/XGu7Vr2f
And here is the configuration for log4j to log to both console and file (secore.log) and only console (catalina.out) contains this exception: https://pastebin.com/09ma3eyw
Thanks,
Hello Bang,
I am going to assume that you use the quite outdated version 7.3.1 because it was the only one in the Maven Central repository at the time. Since a few months we improved the build process and new release are now also available in Maven Central (but also in the BaseX internal Maven Repository).
So the first thing I would recommend is for you to upgrade to a recent 8.6.x version. Maybe this bug is already solved in the meantime.
Cheers Dirk
Senacor Technologies Aktiengesellschaft - Sitz: Eschborn - Amtsgericht Frankfurt am Main - Reg.-Nr.: HRB 105546 Vorstand: Matthias Tomann, Marcus Purzer - Aufsichtsratsvorsitzender: Daniel Gr?zinger
-----Urspr?ngliche Nachricht----- Von: basex-talk-bounces@mailman.uni-konstanz.de [mailto:basex-talk-bounces@mailman.uni-konstanz.de] Im Auftrag von Bang Pham Huu Gesendet: Donnerstag, 4. Januar 2018 10:30 An: basex-talk@mailman.uni-konstanz.de Betreff: [basex-talk] Hundreds of thousands of java.io.IOException: Stream Closed in BaseX 7.3.1 from only catalina.out of Tomcat's log?
Hello,
I've been using BaseX (version 7.3.1 with Tomcat 8) to store an XML database from XML files and using XQuery to query the database. It works great before with simple Java servlet as I recall. After that, I updated to use Spring Boot (version 1.5.2) for this web application (only update from Java servlet to Spring Controller, the core to query BaseX doesn't change), and it seems this weird exception java.io.IOException: Stream Closed appears randomly by 100000 times in Tomcat's log (catalina.out).
I tried to catch this exception in my web application but it is not able to catch. My web application's log (secore.log) also couldn't catch this error, only Tomcat's log (catalina.out) logs this error but with 100000 times (the log file is huge).
Any idea to solve this problem will help me a lot?
Here is the stack trace in catalina.out for 1 exception: https://pastebin.com/XGu7Vr2f
And here is the configuration for log4j to log to both console and file (secore.log) and only console (catalina.out) contains this exception: https://pastebin.com/09ma3eyw
Thanks,
basex-talk@mailman.uni-konstanz.de