Caused by: java.sql.SQLException: Another instance of Derby may have already booted the database G:\eclipse projects\derby\PoonaCollegeTest\Login.
When an application accesses a Derby database using the Embedded Derby JDBC driver, the Derby engine does not run in a separate process, and there are no separate database processes to start up and shut down. Instead, the Derby database engine runs inside the same Java Virtual Machine (JVM) as the application. So, Derby becomes part of the application just like any other jar file that the application uses.
are you looking at any dat from the database in eclipse whilst trying to run your program... that will be 2 connections, or any other way the eclipse plugin could just be leaving itself connected.
Punit Jain wrote:i said derby plugin in eclipse..
and the just add the derby nature to eclipse..
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |