Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Jubula » Problem connecting to Embedded Database(H2) (Problem connecting to Embedded Database(H2) )
Problem connecting to Embedded Database(H2) [message #884966] Tue, 12 June 2012 07:28 Go to next message
Ashish Sharma is currently offline Ashish SharmaFriend
Messages: 15
Registered: October 2011
Junior Member
Jubula works fine for few weeks. Then all of a sudden it starts giving error not able to connect to database. Looking at the log file it seems jubula is not able to find driver for the embedded database.
------------------------------
The contents of log file is mentioned below:

2012-06-12 12:51:08.075 [Worker-2] ERROR o.e.j.c.core.persistence.Persistor - no or wrong username or password
javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: No suitable driver found for jdbc:h2:~/.jubula/database/embedded;MVCC=TRUE;AUTO_SERVER=TRUE;DB_CLOSE_ON_EXIT=FALSE
Error Code: 0
at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:517) ~[org.eclipse.persistence.jpa_2.3.2.v20111125-r10461.jar:2.3.2.v20111125-r10461]
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.getDatabaseSession(EntityManagerFactoryDelegate.java:188) ~[org.eclipse.persistence.jpa_2.3.2.v20111125-r10461.jar:2.3.2.v20111125-r10461]
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.createEntityManagerImpl(EntityManagerFactoryDelegate.java:277) ~[org.eclipse.persistence.jpa_2.3.2.v20111125-r10461.jar:2.3.2.v20111125-r10461]
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:294) ~[org.eclipse.persistence.jpa_2.3.2.v20111125-r10461.jar:2.3.2.v20111125-r10461]
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:272) ~[org.eclipse.persistence.jpa_2.3.2.v20111125-r10461.jar:2.3.2.v20111125-r10461]
at org.eclipse.jubula.client.core.persistence.Persistor.buildSessionFactoryWithLoginData(Persistor.java:283) [org.eclipse.jubula.client.core_1.2.0.201203181048.jar:na]
at org.eclipse.jubula.client.core.persistence.Persistor.<init>(Persistor.java:157) [org.eclipse.jubula.client.core_1.2.0.201203181048.jar:na]
at org.eclipse.jubula.client.core.persistence.Persistor.instance(Persistor.java:598) [org.eclipse.jubula.client.core_1.2.0.201203181048.jar:na]
at org.eclipse.jubula.client.core.persistence.Persistor.access$4(Persistor.java:593) [org.eclipse.jubula.client.core_1.2.0.201203181048.jar:na]
at org.eclipse.jubula.client.core.persistence.Persistor$2.run(Persistor.java:191) [org.eclipse.jubula.client.core_1.2.0.201203181048.jar:na]
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) [org.eclipse.core.jobs_3.5.101.v20120113-1953.jar:na]
Caused by: org.eclipse.persistence.exceptions.DatabaseException:
Internal Exception: java.sql.SQLException: No suitable driver found for jdbc:h2:~/.jubula/database/embedded;MVCC=TRUE;AUTO_SERVER=TRUE;DB_CLOSE_ON_EXIT=FALSE
Error Code: 0
at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:324) ~[org.eclipse.persistence.core_2.3.2.v20111125-r10461.jar:2.3.2.v20111125-r10461]
at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:319) ~[org.eclipse.persistence.core_2.3.2.v20111125-r10461.jar:2.3.2.v20111125-r10461]
at org.eclipse.persistence.sessions.DefaultConnector.connect(DefaultConnector.java:138) ~[org.eclipse.persistence.core_2.3.2.v20111125-r10461.jar:2.3.2.v20111125-r10461]
at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162) ~[org.eclipse.persistence.core_2.3.2.v20111125-r10461.jar:2.3.2.v20111125-r10461]
at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:584) ~[org.eclipse.persistence.core_2.3.2.v20111125-r10461.jar:2.3.2.v20111125-r10461]
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:206) ~[org.eclipse.persistence.jpa_2.3.2.v20111125-r10461.jar:2.3.2.v20111125-r10461]
at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:488) ~[org.eclipse.persistence.jpa_2.3.2.v20111125-r10461.jar:2.3.2.v20111125-r10461]
... 10 common frames omitted
Caused by: java.sql.SQLException: No suitable driver found for jdbc:h2:~/.jubula/database/embedded;MVCC=TRUE;AUTO_SERVER=TRUE;DB_CLOSE_ON_EXIT=FALSE
at java.sql.DriverManager.getConnection(Unknown Source) ~[na:1.6.0_18]
at java.sql.DriverManager.getConnection(Unknown Source) ~[na:1.6.0_18]
at org.eclipse.persistence.sessions.DefaultConnector.connect(DefaultConnector.java:98) ~[org.eclipse.persistence.core_2.3.2.v20111125-r10461.jar:2.3.2.v20111125-r10461]
... 14 common frames omitted
Re: Problem connecting to Embedded Database(H2) [message #884979 is a reply to message #884966] Tue, 12 June 2012 08:00 Go to previous messageGo to next message
Alexandra Schladebeck is currently offline Alexandra SchladebeckFriend
Messages: 1613
Registered: July 2009
Senior Member
Hi,

Unfortunately, the error messages we get from the persistence layer usually say that, regardless of the actual problem Wink So the question is, what has changed? A few possibilities could be:

- The workspace you use with Jubula
- Permissions for the directory where the H2 database is stored
- Space problems in the database directory
- (This list is by no means exhaustive, but something must have changed to cause the problem)

If you are working with the ITE, then look in the preferences to see what is configured and make sure that everything is as it should be. If you are working with the testexec, then use the workspace you use there with the ITE to check the same.

HTH,
Alex
Re: Problem connecting to Embedded Database(H2) [message #898838 is a reply to message #884966] Fri, 27 July 2012 21:32 Go to previous message
Oscar Trejo-Soria is currently offline Oscar Trejo-SoriaFriend
Messages: 21
Registered: June 2012
Junior Member
This might be kind of late, but since I just had this problem in my Ubuntu VM, this is what I did to solve my problem. I first uninstalled Jubula, then I delete .jubula folder. Since everything related to Embedded Database(H2) is stored under .jubula, I deleted it. Make sure to delete .jubula after uninstalling Jubula because if not, after reinstalling you will experience the same issue.

Oscar Trejo

[Updated on: Fri, 27 July 2012 21:34]

Report message to a moderator

Previous Topic:Test Results taking too long to delete
Next Topic:TestExec Command Not Working
Goto Forum:
  


Current Time: Fri Mar 29 08:40:33 GMT 2024

Powered by FUDForum. Page generated in 0.03370 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top