Vote failed; a new release candidate with a fix is being respun. This will be RC1. Karl
On Thu, Mar 31, 2011 at 1:57 PM, Karl Wright <daddy...@gmail.com> wrote: > Looking at it in depth, it's likely that it's a Derby bug. I've filed > ticket DERBY-5169 accordingly, and marked CONNECTORS-172 as a blocker > for 0.2-incubating. > > Karl > > On Thu, Mar 31, 2011 at 1:11 PM, Karl Wright <daddy...@gmail.com> wrote: >> Yes, this does sound like CONNECTORS-172. It's intermittent; if you >> run the tests again it will likely pass. >> >> The problem appeared with either the new Derby or the new Jetty. >> Jetty changed its shutdown so that I can no longer guarantee that it >> shuts down before the rest of the process shuts down - it could be >> related to that. The Derby changes involve having more queries (so >> that they use indexes rather than scans), so it is possible that >> something is taking a bit longer than before and causing an occasional >> timeout. >> >> I've not seen any evidence that the problem is other than test >> related, though. But I think it's worth trying to understand the >> issue more completely before deciding whether to respin or accept the >> RC as it stands. >> >> Karl >> >> >> On Thu, Mar 31, 2011 at 12:50 PM, Koji Sekiguchi <k...@r.email.ne.jp> wrote: >>> (11/03/21 9:32), Karl Wright wrote: >>>> >>>> The tag is >>>> https://svn.apache.org/repos/asf/incubator/lcf/tags/release-0.2-incubating-RC0. >>>> You can download the candidate from >>>> http://people.apache.org/~kwright/apache-manifoldcf-0.2-incubating. >>> >>> Hi Karl, >>> >>> I downloaded apache-manifoldcf-0.2-incubating-bin.tar.gz and did >>> ant test, but I got "Database exception: Exception doing query: No current >>> connection." >>> exception during the test. I'm not sure it is same as CONNECTORS-172. >>> >>> Are you digging in the issue and planning to respin the RC? >>> >>> Koji >>> -- >>> http://www.rondhuit.com/en/ >>> >> >
