Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Jubula » Problem connecting to the database
Problem connecting to the database [message #759424] Mon, 28 November 2011 16:05 Go to next message
Richard Skoog is currently offline Richard SkoogFriend
Messages: 62
Registered: October 2011
Member
Hi,

I have problems conecting to the Jubula database. I can't open the database which I have used since installig Jubula (ver. 1.1.0) and I can't create a new database.

This is the client log:

2011-11-28 16:57:58.229 [Worker-6] ERROR o.e.j.c.core.persistence.Persistor - no or wrong username or password
javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.2.0.v20110202-r8913): 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:422) ~[org.eclipse.persistence.jpa_2.2.0.v20110202-r8913.jar:2.2.0.v20110202-r8913]
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:185) ~[org.eclipse.persistence.jpa_2.2.0.v20110202-r8913.jar:2.2.0.v20110202-r8913]
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:242) ~[org.eclipse.persistence.jpa_2.2.0.v20110202-r8913.jar:2.2.0.v20110202-r8913]
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:230) ~[org.eclipse.persistence.jpa_2.2.0.v20110202-r8913.jar:2.2.0.v20110202-r8913]
at org.eclipse.jubula.client.core.persistence.Persistor.buildSessionFactoryWithLoginData(Persistor.java:281) [org.eclipse.jubula.client.core_1.1.0.201109140653.jar:na]
at org.eclipse.jubula.client.core.persistence.Persistor.<init>(Persistor.java:156) [org.eclipse.jubula.client.core_1.1.0.201109140653.jar:na]
at org.eclipse.jubula.client.core.persistence.Persistor.instance(Persistor.java:596) [org.eclipse.jubula.client.core_1.1.0.201109140653.jar:na]
at org.eclipse.jubula.client.core.persistence.Persistor.access$4(Persistor.java:591) [org.eclipse.jubula.client.core_1.1.0.201109140653.jar:na]
at org.eclipse.jubula.client.core.persistence.Persistor$2.run(Persistor.java:192) [org.eclipse.jubula.client.core_1.1.0.201109140653.jar:na]
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) [org.eclipse.core.jobs_3.5.1.R36x_v20100824.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.2.0.v20110202-r8913.jar:2.2.0.v20110202-r8913]
at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:319) ~[org.eclipse.persistence.core_2.2.0.v20110202-r8913.jar:2.2.0.v20110202-r8913]
at org.eclipse.persistence.sessions.DefaultConnector.connect(DefaultConnector.java:138) ~[org.eclipse.persistence.core_2.2.0.v20110202-r8913.jar:2.2.0.v20110202-r8913]
at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162) ~[org.eclipse.persistence.core_2.2.0.v20110202-r8913.jar:2.2.0.v20110202-r8913]
at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:592) ~[org.eclipse.persistence.core_2.2.0.v20110202-r8913.jar:2.2.0.v20110202-r8913]
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:233) ~[org.eclipse.persistence.jpa_2.2.0.v20110202-r8913.jar:2.2.0.v20110202-r8913]
at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:394) ~[org.eclipse.persistence.jpa_2.2.0.v20110202-r8913.jar:2.2.0.v20110202-r8913]
... 9 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.2.0.v20110202-r8913.jar:2.2.0.v20110202-r8913]
... 13 common frames omitted



Any suggestions? I haven't changed anything in the installation of Jubula.

Regards Richard

Report message to a moderator

Re: Problem connecting to the database [message #759573 is a reply to message #759424] Tue, 29 November 2011 08:53 Go to previous messageGo to next message
Alexandra Schladebeck is currently offline Alexandra SchladebeckFriend
Messages: 1613
Registered: July 2009
Senior Member
Hi,

Are you using the standalone or Jubula as a plugin? In the latter case, have you added any other plugins since your last successful connect?
Are the directory and files where the embedded database is saved still the same and do they have enough space?

Does the problem still occur when you try to connect after restarting Jubula?

If none of this helps, then you could open a bug, attaching your database if you feel comfortable doing so, and adding as much information as possible.

Regards,
Alex

Report message to a moderator

Re: Problem connecting to the database [message #759625 is a reply to message #759573] Tue, 29 November 2011 11:56 Go to previous messageGo to next message
Richard Skoog is currently offline Richard SkoogFriend
Messages: 62
Registered: October 2011
Member
Bug created:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=365031

Report message to a moderator

Re: Problem connecting to the database [message #763304 is a reply to message #759625] Fri, 09 December 2011 14:37 Go to previous message
Alexandra Schladebeck is currently offline Alexandra SchladebeckFriend
Messages: 1613
Registered: July 2009
Senior Member
For anyone who doesn't read the whole bug entry, it turned out that the H2 database was experiencing out of memory problems. If you're currently using the H2 database productively for your tests, we would recommend switching to a non-in-memory-database (Oracle or Oracle XE (the free version)) so that you don't run into these kind of problems.

Best regards,
Alex

Report message to a moderator

Previous Topic:Error on connecting to either MySQL or PostgreSQL database
Next Topic:Context menu problem
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Thu Apr 25 12:50:31 GMT 2024

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

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

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly