Subject | Re: [Firebird-Java] TestPoolingConnectionManager error |
---|---|
Author | Rick Fincher |
Post date | 2002-12-17T19:51:09Z |
Hi Ludek,
That is a bogus error message that is caused by a timing problem in the test
code when running on some systems. The developers are aware of it.
You probably see something like this in the build window:
[junit] Running org.firebirdsql.jca.TestPoolingConnectionManager
[junit] Tests run: 4, Failures: 1, Errors: 0, Time elapsed: 90.711 sec
[junit] TEST org.firebirdsql.jca.TestPoolingConnectionManager FAILED
That's what I get under windows 2000.
Your compiled code is OK to use.
Rick
That is a bogus error message that is caused by a timing problem in the test
code when running on some systems. The developers are aware of it.
You probably see something like this in the build window:
[junit] Running org.firebirdsql.jca.TestPoolingConnectionManager
[junit] Tests run: 4, Failures: 1, Errors: 0, Time elapsed: 90.711 sec
[junit] TEST org.firebirdsql.jca.TestPoolingConnectionManager FAILED
That's what I get under windows 2000.
Your compiled code is OK to use.
Rick
----- Original Message -----
> Hi,
>
> I downloaded the latest version of the firebird jca jdbc driver and after
> compilation at the TestPoolingConnectionManager I got the error:
>
> testShortBlocking Failure Blocking Timeout occurred in
> ShortBlocking test.
>
> junit.framework.AssertionFailedError: Blocking Timeout occurred
> in ShortBlocking test
> at
> org.firebirdsql.jca.TestPoolingConnectionManager.testShortBlocking(TestP
> oolingConnectionManager.java:143)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.java:25)
>
> Java Version 1.4.0
> Java Vendor Sun Microsystems Inc.
> Java VM Name Java HotSpot(TM) Client VM
> Java VM Version 1.4.0-b92
> Java VM Info mixed mode
> OS Name Red Hat Linux 7.1
> OS Version 2.4.18-17.7.x
> OS Arch i386
>
> What I have to do to fix it?
>
> Best regards
>
> Ludek Falta