Probleme mit Hibernate Tools Installation

Tawarien

Mitglied
Hallo.

Ich versuche über den Eclipse Marktplace die Hibernate Tools zu laden und zu installieren.
Dummerweise bricht mir die Installation mit folgender Fehlermeldung immer ab:

Cannot complete the provisioning operation. Please change your selection and try again. See below for details.
Cannot complete the install because of a conflicting dependency.
Software being installed: Hibernate Tools 3.4.0.v20110729-2006-H171-Final (org.hibernate.eclipse.feature.feature.group 3.4.0.v20110729-2006-H171-Final)
Software currently installed: Eclipse IDE for Java EE Developers 1.4.0.20110615-0550 (epp.package.jee 1.4.0.20110615-0550)
Only one of the following can be installed at once:
Structured Source Editor 1.2.4.v201103231819 (org.eclipse.wst.sse.ui 1.2.4.v201103231819)
Structured Source Editor 1.2.2.v201008232126 (org.eclipse.wst.sse.ui 1.2.2.v201008232126)
Structured Source Editor 1.2.0.v201006030742 (org.eclipse.wst.sse.ui 1.2.0.v201006030742)
Structured Source Editor 1.3.0.v201105101529 (org.eclipse.wst.sse.ui 1.3.0.v201105101529)
Structured Source Editor 1.2.3.v201102102045 (org.eclipse.wst.sse.ui 1.2.3.v201102102045)
Only one of the following can be installed at once:
XSD Core Plugin 1.1.600.v201104070312 (org.eclipse.wst.xsd.core 1.1.600.v201104070312)
XSD Core Plugin 1.1.501.v201004110600 (org.eclipse.wst.xsd.core 1.1.501.v201004110600)
XSD Core Plugin 1.1.503.v201011121919 (org.eclipse.wst.xsd.core 1.1.503.v201011121919)
XSD Core Plugin 1.1.502.v201008201521 (org.eclipse.wst.xsd.core 1.1.502.v201008201521)
Cannot satisfy dependency:
From: Eclipse IDE for Java EE Developers 1.4.0.20110615-0550 (epp.package.jee 1.4.0.20110615-0550)
To: org.eclipse.epp.package.jee.feature.feature.group [1.4.0.20110615-0550]
Cannot satisfy dependency:
From: Java EE IDE Feature 1.4.0.20110615-0550 (org.eclipse.epp.package.jee.feature.feature.group 1.4.0.20110615-0550)
To: org.eclipse.jpt.jaxb.feature.feature.group 0.0.0
Cannot satisfy dependency:
From: Java EE IDE Feature 1.4.0.20110615-0550 (org.eclipse.epp.package.jee.feature.feature.group 1.4.0.20110615-0550)
To: org.eclipse.wst.xml_ui.feature.feature.group 0.0.0
Cannot satisfy dependency:
From: Dali Java Persistence Tools - JAXB Core 1.0.0.v201105240000 (org.eclipse.jpt.jaxb.core 1.0.0.v201105240000)
To: bundle org.eclipse.wst.xsd.core [1.1.600,2.0.0)
Cannot satisfy dependency:
From: Dali Java Persistence Tools - JAXB Support 1.0.0.v201104110000-508ZAkF7BB7OBM777A (org.eclipse.jpt.jaxb.feature.feature.group 1.0.0.v201104110000-508ZAkF7BB7OBM777A)
To: org.eclipse.jpt.jaxb.core [1.0.0.v201105240000]
Cannot satisfy dependency:
From: Dali Java Persistence Tools - UI 2.3.0.v201005190001 (org.eclipse.jpt.ui 2.3.0.v201005190001)
To: bundle org.eclipse.wst.sse.ui [1.1.0,1.3.0)
Cannot satisfy dependency:
From: Dali Java Persistence Tools - UI 2.3.2.v201008252310 (org.eclipse.jpt.ui 2.3.2.v201008252310)
To: bundle org.eclipse.wst.sse.ui [1.1.0,1.3.0)
Cannot satisfy dependency:
From: WST XML Core 3.2.0.v201005241510-7C7OFXTF7RZHQHHxO4IuKe (org.eclipse.wst.xml_core.feature.feature.group 3.2.0.v201005241510-7C7OFXTF7RZHQHHxO4IuKe)
To: org.eclipse.wst.xsd.core [1.1.501.v201004110600]
Cannot satisfy dependency:
From: WST XML Core 3.2.2.v201008170029-7C7OFXYF7RZHQHI5PyJwPT (org.eclipse.wst.xml_core.feature.feature.group 3.2.2.v201008170029-7C7OFXYF7RZHQHI5PyJwPT)
To: org.eclipse.wst.xsd.core [1.1.502.v201008201521]
Cannot satisfy dependency:
From: WST XML Core 3.2.3.v201102160550-7C7OFXcF7RZHQKIkMxMsW_ (org.eclipse.wst.xml_core.feature.feature.group 3.2.3.v201102160550-7C7OFXcF7RZHQKIkMxMsW_)
To: org.eclipse.wst.xsd.core [1.1.503.v201011121919]
Cannot satisfy dependency:
From: WST XML Core 3.2.4.v201103231834-7C7OFXfF7RZHQLInN2MhWd (org.eclipse.wst.xml_core.feature.feature.group 3.2.4.v201103231834-7C7OFXfF7RZHQLInN2MhWd)
To: org.eclipse.wst.xsd.core [1.1.503.v201011121919]
Cannot satisfy dependency:
From: Eclipse XML Editors and Tools 3.2.0.v201005241510-7H7AFUIDxumQGOb7ocjUR2Pvz-28 (org.eclipse.wst.xml_ui.feature.feature.group 3.2.0.v201005241510-7H7AFUIDxumQGOb7ocjUR2Pvz-28)
To: org.eclipse.wst.xml_core.feature.feature.group [3.2.0.v201005241510-7C7OFXTF7RZHQHHxO4IuKe]
Cannot satisfy dependency:
From: Eclipse XML Editors and Tools 3.2.2.v201008170029-7H7AFUQDxumQGOpBqffOY2f1qxDZ (org.eclipse.wst.xml_ui.feature.feature.group 3.2.2.v201008170029-7H7AFUQDxumQGOpBqffOY2f1qxDZ)
To: org.eclipse.wst.xml_core.feature.feature.group [3.2.2.v201008170029-7C7OFXYF7RZHQHI5PyJwPT]
Cannot satisfy dependency:
From: Eclipse XML Editors and Tools 3.2.3.v201102160550-7H7AFUWDxumQJOi9ghcTb5YgkwEZ (org.eclipse.wst.xml_ui.feature.feature.group 3.2.3.v201102160550-7H7AFUWDxumQJOi9ghcTb5YgkwEZ)
To: org.eclipse.wst.xml_core.feature.feature.group [3.2.3.v201102160550-7C7OFXcF7RZHQKIkMxMsW_]
Cannot satisfy dependency:
From: Eclipse XML Editors and Tools 3.2.4.v201103170600-7H7AFUaDxumQJOs8hggQZ6_jl1EOJGNlUsOsTM (org.eclipse.wst.xml_ui.feature.feature.group 3.2.4.v201103170600-7H7AFUaDxumQJOs8hggQZ6_jl1EOJGNlUsOsTM)
To: org.eclipse.wst.xml_core.feature.feature.group [3.2.4.v201103231834-7C7OFXfF7RZHQLInN2MhWd]
Cannot satisfy dependency:
From: Eclipse XML Editors and Tools 3.3.0.v201103310011-7H7EFZ-DxumTla66ahfUnHfpsz0u5Z92pU4TxSL (org.eclipse.wst.xml_ui.feature.feature.group 3.3.0.v201103310011-7H7EFZ-DxumTla66ahfUnHfpsz0u5Z92pU4TxSL)
To: org.eclipse.wst.sse.ui [1.3.0.v201105101529]
Cannot satisfy dependency:
From: Hibernate Tools 3.4.0.v20110729-2006-H171-Final (org.hibernate.eclipse.feature.feature.group 3.4.0.v20110729-2006-H171-Final)
To: org.jboss.tools.hibernate.jpt.ui [3.4.1.v20110729-2006-H171-Final]
Cannot satisfy dependency:
From: Hibernate Jdt UI 3.4.1.v20110729-2006-H171-Final (org.jboss.tools.hibernate.jpt.ui 3.4.1.v20110729-2006-H171-Final)
To: bundle org.eclipse.jpt.ui 0.0.0



Laut google lässt sich das Problem angeblich damit lösen, dass man Eclipse als Admin ausführt.
Hilft hier aber allerdings nix.
 
Hi
bitte Thema als erledigt markieren!

Werde ich tun, allerdings ist direkt das nächste Problem aufgetaucht und ich denke ich führe das in diesem Thread fort und eröffne keinen neuen dafür, da es immer noch mehr oder minder damit zusammenhängt.

Also, die Installation hat soweit geklappt und nun versuche ich eine kleine Struktur abzubilden.


"Reading schema error: Getting database metadata" ist die Fehlermeldung und ich steh grad aufm Schlauch.

Ich füge mal die jeweiligen Codes ein, vielleicht überseh ich einfach nur was blödes, kann gut sein.

hibernate-tools.properties
Code:
hibernate.hbm2ddl.auto=create-drop
hibernate.show_sql=false
hibernate.format_sql=false
hibernate.connection.username=root
hibernate.connection.password=admin
hibernate.connection.driver_class=org.gjt.mm.mysql.Driver
connection.driver_class=com.mysql.jdbc.Driver
hibernate.dialect=org.hibernate.dialect.MySQLDialect
hibernate.connection.url=jdbc:mysql://localhost/filmkritik?

persistence.xml
Code:
<!--?xml version="1.0" encoding="UTF-8"?-->
<persistence xmlns="http://java.sun.com/xml/ns/persistence"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
	http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
	version="1.0">
	<persistence-unit name="Filmkritik" transaction-type="RESOURCE_LOCAL">
		<provider>org.hibernate.ejb.HibernatePersistence</provider>
		<class>de.chruf.db.entities.Movie</class>
		<class>de.chruf.db.entities.Rating</class>
		<class>de.chruf.db.entities.User</class>
		<properties>
			<property name="hibernate.show_sql" value="false" />
			<property name="hibernate.archive.autodetection" value="class, hbm" />
			<property name="hibernate.connection.driver_class" value="com.mysql.jdbc.Driver" />
			<property name="hibernate.connection.url" value="jdbc:mysql://localhost:3306/filmkritik" />
			<property name="hibernate.connection.username" value="root" />
			<property name="hiberntae.connection.password" value="admin" />
			<property name="hibernate.c3p0.min_size" value="1" />
			<property name="hibernate.c3p0.max_size" value="1" />
			<property name="hibernate.c3p0.timeout" value="3000" />
			<property name="hiberntae.c3p0.max_statements" value="50" />
			<property name="hibernate.c3p0.idle_test_period" value="3000" />
			<property name="hibernate.dialect" value="org.hibernate.dialect.MySqlDialect" />
			<property name="hibernate.connection.useUnicode" value="true" />
			<property name="hibernate.connection.characterEncoding" value="UTF-8" />
 		</properties>
	</persistence-unit>
</persistence>

Java:
@Entity
@NamedQueries({
	@NamedQuery(name="test", query="SELECT * FROM User"),
	@NamedQuery(name="test2", query="SELECT * FROM User")})

public class User {
	
	private int id;
	private String nickname;
	private String firstname;
	private String lastname;
	private String password;
	private Movie movie;
	
	@Id
	@GeneratedValue
	public int getId() { return id; }	
	public void setId(int id) { this.id = id; }

	public String getNickname() { return nickname; }
	public void setNickname(String nickname) { this.nickname = nickname; }
		
	public String getFirstname() { return firstname; }
	public void setFirstname(String firstname) { this.firstname = firstname; }
	
	public String getLastname() { return lastname; }
	public void setLastname(String lastname) { this.lastname = lastname; }

	public String getPassword() { return password; }
	public void setPassword(String password) { this.password = password; }
	
	@OneToMany(mappedBy="user")
	public Movie getMovie() { return movie; }
	public void setMovie(Movie movie) { this.movie = movie; }

}

Die anderen beiden Entitys sind im Prinzip genauso aufgebaut.
 
org.gjt.mm.mysql.Driver sollte nicht mehr verwendet werden. Es ist lediglich eine Wrapper-Klasse für com.mysql.jdbc.Driver und existiert nur noch damit alte Applikationen die diese Klassen noch verwenden auch mit neueren Versionen des Drivers arbeiten.
 
Guten Morgen,

was du zunächst tun kannst, ist den Logger etwas granularer einzustellen - vll spuckt er dann mehr aus. Zweitens ist mir nicht ganz klar für was die hibernate.properties sein soll, da sich ja durch die persistence.xml eine Gewisse Redundanz ergibt.

Code:
hibernate.connection.url=jdbc:mysql://localhost/filmkritik?
entferne mal das ? am ende.

Poste außerdem bitte mal einen Stacktrace bzw wo und wann die Exception Auftritt. Beim Hochfahren des Persistence-Contexts?

*EDIT* Darf ich fragen für was du Hibernate-Tools benötigst? Ich habe erst einmal darauf zurückgreifen müssen und da ging es um einen ganz speziellen Sondernfall.

Gruß

Sebastian
 
Zuletzt bearbeitet:
org.gjt.mm.mysql.Driver sollte nicht mehr verwendet werden. Es ist lediglich eine Wrapper-Klasse für com.mysql.jdbc.Driver und existiert nur noch damit alte Applikationen die diese Klassen noch verwenden auch mit neueren Versionen des Drivers arbeiten.

Ändert leider nix.

Guten Morgen,

was du zunächst tun kannst, ist den Logger etwas granularer einzustellen - vll spuckt er dann mehr aus. Zweitens ist mir nicht ganz klar für was die hibernate.properties sein soll, da sich ja durch die persistence.xml eine Gewisse Redundanz ergibt.

Code:
hibernate.connection.url=jdbc:mysql://localhost/filmkritik?
entferne mal das ? am ende.

Poste außerdem bitte mal einen Stacktrace bzw wo und wann die Exception Auftritt. Beim Hochfahren des Persistence-Contexts?

Code:
Problems while reading database schema


Code:
org.hibernate.exception.GenericJDBCException: Getting database metadata

org.hibernate.exception.GenericJDBCException: Getting database metadata
	at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:140)
	at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:128)
	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.getMetaData(AbstractMetaDataDialect.java:63)
	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.caseForSearch(AbstractMetaDataDialect.java:163)
	at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:22)
	at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476)
	at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74)
	at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:126)
	at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
	at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:72)
	at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:115)
	at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:65)
	at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
	at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.sql.SQLException: Connections could not be acquired from the underlying database!
	at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:106)
	at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:529)
	at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:128)
	at org.hibernate.connection.C3P0ConnectionProvider.getConnection(C3P0ConnectionProvider.java:78)
	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.getConnection(AbstractMetaDataDialect.java:121)
	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.getMetaData(AbstractMetaDataDialect.java:60)
	... 12 more
Caused by: com.mchange.v2.resourcepool.CannotAcquireResourceException: A ResourcePool could not acquire a resource from its primary factory or source.
	at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1319)
	at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:557)
	at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:477)
	at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:525)
	... 16 more


Code:
com.mchange.v2.resourcepool.CannotAcquireResourceException: A ResourcePool could not acquire a resource from its primary factory or source.

com.mchange.v2.resourcepool.CannotAcquireResourceException: A ResourcePool could not acquire a resource from its primary factory or source.
	at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1319)
	at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:557)
	at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:477)
	at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:525)
	at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:128)
	at org.hibernate.connection.C3P0ConnectionProvider.getConnection(C3P0ConnectionProvider.java:78)
	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.getConnection(AbstractMetaDataDialect.java:121)
	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.getMetaData(AbstractMetaDataDialect.java:60)
	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.caseForSearch(AbstractMetaDataDialect.java:163)
	at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:22)
	at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476)
	at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74)
	at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:126)
	at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
	at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:72)
	at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:115)
	at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:65)
	at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
	at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Code:
java.sql.SQLException: Connections could not be acquired from the underlying database!

java.sql.SQLException: Connections could not be acquired from the underlying database!
	at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:106)
	at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:529)
	at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:128)
	at org.hibernate.connection.C3P0ConnectionProvider.getConnection(C3P0ConnectionProvider.java:78)
	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.getConnection(AbstractMetaDataDialect.java:121)
	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.getMetaData(AbstractMetaDataDialect.java:60)
	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.caseForSearch(AbstractMetaDataDialect.java:163)
	at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:22)
	at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476)
	at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74)
	at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:126)
	at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
	at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:72)
	at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:115)
	at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:65)
	at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
	at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: com.mchange.v2.resourcepool.CannotAcquireResourceException: A ResourcePool could not acquire a resource from its primary factory or source.
	at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1319)
	at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:557)
	at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:477)
	at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:525)
	... 16 more
Code:
org.hibernate.exception.GenericJDBCException: Getting database metadata

org.hibernate.exception.GenericJDBCException: Getting database metadata
	at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:140)
	at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:128)
	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.getMetaData(AbstractMetaDataDialect.java:63)
	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.caseForSearch(AbstractMetaDataDialect.java:163)
	at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:22)
	at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476)
	at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74)
	at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:126)
	at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
	at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:72)
	at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:115)
	at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:65)
	at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
	at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.sql.SQLException: Connections could not be acquired from the underlying database!
	at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:106)
	at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:529)
	at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:128)
	at org.hibernate.connection.C3P0ConnectionProvider.getConnection(C3P0ConnectionProvider.java:78)
	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.getConnection(AbstractMetaDataDialect.java:121)
	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.getMetaData(AbstractMetaDataDialect.java:60)
	... 12 more
Caused by: com.mchange.v2.resourcepool.CannotAcquireResourceException: A ResourcePool could not acquire a resource from its primary factory or source.
	at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1319)
	at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:557)
	at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:477)
	at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:525)
	... 16 more

*EDIT* Darf ich fragen für was du Hibernate-Tools benötigst? Ich habe erst einmal darauf zurückgreifen müssen und da ging es um einen ganz speziellen Sondernfall.

Gruß

Sebastian

Ich hab damit schon gearbeitet und es war ziemlich genial.
Leider hab ich es selbst noch nicht selbst aufgesetzt.
 

Neue Beiträge

Zurück