Post reply

sql server 2003 possible problem?

  • June 2, 2009 at 3:20 am

    #210222

    hi everyone, one of our java developers is having a problem connecting to a database on my pc. thing is, he's never had a problem before and the only thing thats changed is the installation of Service Pack 3 which ive done.

    is it possible that Service pack 3 is causing the problem?

    this is he's stack trace...

    [java] java.sql.SQLException: No suitable driver

    [java] at java.sql.DriverManager.getDriver(DriverManager.java:264)

    [java] at com.mchange.v2.c3p0.DriverManagerDataSource.driver(DriverManagerDataSource.java:223)

    [java] at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)

    [java] at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)

    [java] at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)

    [java] at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.jav

    a:137)

    [java] at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)

    [java] at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)

    [java] at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810)

    [java] at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)

    [java] 2009-06-02 10:49:59,391 WARN [com.mchange.v2.resourcepool.BasicResourcePool] - com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1

    c7f37d -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the m

    aximum number of allowed acquisition attempts (30). Last acquisition attempt exception:

    [java] java.sql.SQLException: No suitable driver

    [java] at java.sql.DriverManager.getDriver(DriverManager.java:264)

    [java] at com.mchange.v2.c3p0.DriverManagerDataSource.driver(DriverManagerDataSource.java:223)

    [java] at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)

    [java] at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)

    [java] at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)

    [java] at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool

  • June 2, 2009 at 3:47 am

    #1003255

    Do you mean SQL Server 2005? There is no version 2003.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • June 2, 2009 at 3:53 am

    #1003262

    oops, my bad... SQL Server 2005

  • June 2, 2009 at 4:03 am

    #1003271

    Can you try reinstalling the java drivers?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • June 2, 2009 at 4:09 am

    #1003276

    should i try on my side?

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply