Prudence 2.0-beta6, Sincerity 1.0-beta6
7 views
Skip to first unread message
Tal Liron
Jul 23, 2014, 4:19:26 AM7/23/14
to prudence-...@googlegroups.com
This release of Sincerity incorporates the final release of Log4j 2.0, which included a great many bug fixes.
It required quite a bit of work for me: there were many final changes to the Log4j API during the release candidate process. Annoyingly for me, they decided to remove NoSQL support, after I devoted quite a bit of time to debugging the Log4j code and submitting patches. I think they made the right decision: they were not able to properly support this API with testing. However, I did waste time on it.
In order to properly support Sincerity's MongoDB addon to the Logging Plugin, I wrote specialized support for MongoDB. It is incorporated in this release, so that logging to MongoDB should work fine.
This release of Prudence incorporates a special mechanism to detect and avoid recursive server-side redirects, which should increase robustness.
We still have not solved the bug in Prudence in which we get hanging JVMs, although we've made some progress on it. It seems more and more likely that it is a Restlet bug: other Restlet (non-Prudence) users have reported similar issues. Again: this bug seems to happen only to specific users, not all. Several Prudence deployment do not exhibit this bug.
It required quite a bit of work for me: there were many final changes to the Log4j API during the release candidate process. Annoyingly for me, they decided to remove NoSQL support, after I devoted quite a bit of time to debugging the Log4j code and submitting patches. I think they made the right decision: they were not able to properly support this API with testing. However, I did waste time on it.
In order to properly support Sincerity's MongoDB addon to the Logging Plugin, I wrote specialized support for MongoDB. It is incorporated in this release, so that logging to MongoDB should work fine.
This release of Prudence incorporates a special mechanism to detect and avoid recursive server-side redirects, which should increase robustness.
We still have not solved the bug in Prudence in which we get hanging JVMs, although we've made some progress on it. It seems more and more likely that it is a Restlet bug: other Restlet (non-Prudence) users have reported similar issues. Again: this bug seems to happen only to specific users, not all. Several Prudence deployment do not exhibit this bug.
Adrian M
Aug 25, 2014, 10:33:36 AM8/25/14
to prudence-...@googlegroups.com
Really nice to see progress.
Reply all
Reply to author
Forward
0 new messages