Berin Loritsch wrote:
Sam Ruby wrote:
Sam Ruby wrote:
I have a safety timeout in place to guard against runaway or deadlocked
builds. In this case, it kicked in and cancelled the build of excalibur
after twenty minutes on a reasonably fast machine. The same build
with JDK
1.3 took two minutes and eleven seconds.
And it looks like today's build with JDK 1.3.1 on Linux has the same
problem. Both complained about failures to get connections before
hanging...
??
Hmm. I will check the CVS logs to see if any changes to build.xml have
been reported.
Ok, I see what happened.
Didn't you use to have a target named dist-avalon-excalibur? That way
Cocoon would build from avalon-excalibur, and then the dist would use
Cocoon?
The project definition for avalon-excalibur has been changed to use the
"dist" target which runs the DataSource testing. The timeout is occuring
during that stage--which I have introduced a bug that I need to fix...
Instead of failing fast when no connections are available, the JdbcDataSource
is supposed to block for a specified number of milliseconds--problem is that
it looks like it is blocking forever.
I was hoping I could fix some other stuff first, but this may be a higher
priority. Thanks.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
