🚀 go-pugleaf

I had been working along happily for weeks on a servlet which I was running
using JRun and everything was fine. Suddenly yesterday I added a call to
destroy on my ConnectionPool class and that in turn called destroy on its
timer thread and things suddenly got sucked into an anti-matter blackhole. I
uncommented the code and attempted to rebuild it but when JRun's s/w noticed
the change and wanted to load the new version, it would call the destroy
function and we'd be off in the weeds again. I finally broke that circle by
deleting the class file and rebooting about 10x. Finally all I was getting
was java.lang.VerifyErrors. So then I upgraded to JRun 2.2 (totally
annihilating 2.1.x in the process) and my servlet is still spitting up
VerifyErrors, refusing to run. Seems like this must be a JBuilder problem!
Other servlets I've made are running fine.

--
Rob Williams
RobCo Incorporated