Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Shutdown and  reconnection results in "No suitable Driver"
Date: Fri, 25 Feb 2005 15:33:57 -0600
Message-ID: 
 <1B37BEFB3456F1428E01932AFA147822E1A4F5@HOUEXCH902.landmark.lgc.com>
Thread-Topic: Shutdown and  reconnection results in "No suitable Driver"
Thread-Index: AcUbfZIQ3jU28SuJT4yhnb+1t96ObAAA4b2w
From: "Bernd Ruehlicke" <BRuehlicke@lgc.com>
To: "Derby Discussion" <derby-user@db.apache.org>

Maybe the question is leading to a more general question.

Can I use the same Derby database instance from 2 JVM's ?  The scenario
would be a controlling JVM which one in a while need to connect to derby
- than disconnect. While the (still running) first JVM has disconnected
a second JVM will try to access the same Derby database - and releases
the connection simply when the JVM ends, whereafter again the
controlling JVM want to open a connection to this Derby instance.

I thought by doing the shutdown this was the way - but it seams that if
you first have done a shutdown once - you are done for this JVM and need
to restart the JVM to be able to establish a new frsh connection.


B-)=20

> -----Original Message-----
> From: Bernd Ruehlicke [mailto:BRuehlicke@lgc.com]=20
> Sent: Friday, February 25, 2005 3:04 PM
> To: Derby Discussion
> Subject: Shutdown and reconnection results in "No suitable Driver"
>=20
> Here a strange situation. I have a main JVM which has a Derby=20
> Embedded connection. It spinns off to call a script which=20
> again will make a Derby Connection. To allow this Embedded I=20
> have to disconnect from Derby in the first JVM. It turned out=20
> I had to use Shutdown in th efirsyt to let the second jvm=20
> allow to connect
> =20
> // shutting down a database from your application=20
> DriverManager.getConnection(
>     "jdbc:derby:;shutdown=3Dtrue");
> =20
> So far so good. Now when JVM number one want to reestablish=20
> it's connection via the usual Class.forName(...) ...=20
> DriverGetConnection(url,user,passw)=20
> =20
> I get
> =20
> a java.sql.SQLException: No suitable Driver=20
> =20
> =20
> I have created a JUnit test which simply just Loops over a=20
> connection , a shutdown and a new connection - it fails with=20
> the 2. connection. see code snipled below. Trust me that the=20
> url is correct and that the first time it goes via the loop=20
> it connect correctly.
> =20
> =20
> Any thoughts ?!!
> =20
> B-)
> =20
>    .....
>          for(int tal=3D0;tal<10;tal=3Dtal+1)
>          {
>              Class.forName(driver);
>              System.out.println("Running for number : "+tal);
>              System.out.println("Loaded the appropriate driver.");
>                  =20
>              _connection =3D DriverManager.getConnection(url +=20
> ";create=3Dtrue", user, pass);
>             =20
>              if(tal<9)this.tearDown();
>          }
>=20
> ......
> =20
> =20
> where tearDown() is
>      protected void tearDown()
>      {
>          try
>          {
>              // Now try to disconnect
>              _connection.close();
>              _connection =3D null;
>              System.out.println("Closed connection");
> =20
>              /*
>                 In embedded mode, an application should shut=20
> down Derby.
>                 If the application fails to shut down Derby=20
> explicitly,
>                 the Derby does not perform a checkpoint when=20
> the JVM shuts down, which means
>                 that the next connection will be slower.
>                 Explicitly shutting down Derby with the URL=20
> is preferred.
>                 This style of shutdown will always throw an=20
> "exception".
>               */
>              boolean gotSQLExc =3D false;
> =20
>              try
>              {
>                 =20
> DriverManager.getConnection("jdbc:derby:;shutdown=3Dtrue");
>              }
>              catch(SQLException se)
>              {
>                  gotSQLExc =3D true;
>              }
> =20
>              if(!gotSQLExc)
>              {
>                  _logger.fine("Database did not shut down normally");
>              }
>              else
>              {
>                  _logger.fine("Database shut down normally");
>              }
>          }
>          catch (Throwable e)
>          {
>              _logger.fine("exception thrown:"+e.getMessage());
>                  e.printStackTrace();
>          }
> =20
>          System.out.println("TestDerby finished");
> =20
>      }
>=20
> =20
>=20