Closed muellerdo closed 3 years ago
Hi Dominik, thanks for reporting this. I had the same issue before but couldn't identify the cause so far. I was also checking for unclosed connections e.g.
I will further investigate this issue.
Hi @muellerdo, are you still working on this? If so, could you test it with the first stable release and check if the error still occurs?
Hey @christopher-mohr,
sorry for the late reply.
I'm currently in a strict grip of other projects, but I am quite curious and going to have a look to find some time next week for performing an independent setup of the first stable release.
I will keep your updated and will send you some feedback per mail or via GitHub.
Cheers, Dominik
Thanks for your reply! It would be great if you could test it with the release at some point.
According to @muellerdo this did not occur when using release 1.0.0. Thanks for the feedback!
Heyho QBiC team,
when running a previously packaged jar, I got the following error message, now.
It is interesting to know that I was able to successfully run the package a few month ago. Therefore, maybe it is related to some of the latest changes?
Additionally, I checked the process list in the database and saw some idled processes. Maybe, there is a connection which is missing a close() ?
Here is the error log:
Here is the process list from the database:
Thanks for your time.
Cheers, Dominik