org.h2.jdbc.JdbcSQLException：Schema“DBO”未找到 [英] org.h2.jdbc.JdbcSQLException: Schema "DBO" not found

问题描述

这是 WildFly 10.0中Hibernate版本不匹配的后续问题

a>。

为了保持完整性，请简要说明问题。我有2个项目，一个是正常的java项目（使用maven）： core ，另一个是非maven动态web项目： webapi 。后者充当核心之上的休息层。

核心使用休眠没有任何问题。它定义了 persistence.xml （在 src / META-INF / 中），如下所示：

 <？xml version =1.0encoding =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_2_0.xsd
 version =2.0> 
 
< persistence-unit name =apptransaction-type =RESOURCE_LOCAL> 
 
< class> data.entities.Anything< / class> 
< class> data.entities.Something< / class> 
 
<属性> 
 < property name =javax.persistence.jdbc.urlvalue =jdbc：sqlserver：// localhost; databaseName = AppDb>< / property> 
< property name =javax.persistence.jdbc.uservalue =****>< / property> 
< property name =javax.persistence.jdbc.passwordvalue =****>< / property> 
< property name =hibernate.default_schemavalue =dbo>< / property> 
 < property name =hibernate.hbm2ddl.autovalue =update>< / property> 
< property name =jboss.as.jpa.providerModulevalue =org.hibernate：5.2.4.Final/> 
< / properties> 
< / persistence-unit> 
< /余辉> 
  

核心和 webapi 现在使用 hibernate-core 5.2.4.Final ，使用maven和WildFly模块安装，如这里。

然而，现在当我将 webapi 部署到WildFly 10.0时，出现以下错误：

[org.jboss.as.server.deployment]（MSC服务线程1-8）WFLYSRV0027：开始部署webapi.war（运行时名称：webapi.war）

[org.jboss.as.jpa]（MSC服务线程1-1）WFLYJPA0002：读取应用程序的persistence.xml

< WFLYJPA0010：启动持久性单元（第一阶段2）服务'webapi.war＃app'

（服务器服务线程池 - 67）

[org.hibernate.jpa.internal.util.LogHelper]（ServerService线程池 - 67）HHH000204：处理Persiste nceUnitInfo [
名称：应用程序
...]

[org.hibernate.orm.deprecation]（ServerService线程池 - 67）HHH90000001 ：找到用于指定扫描程序的弃用设置[hibernate.ejb.resource_scanner];改为使用[hibernate.archive.scanner]而不是
$ b [org.jboss.as.connector.deployers.jdbc]（MSC服务线程1-1）WFLYJCA0004：部署JDBC-兼容的驱动程序类com.microsoft.sqlserver.jdbc.SQLServerDriver（版本6.0）
$ b $ [org.jboss.as.connector.deployers.jdbc]（MSC服务线程1- 6）WFLYJCA0018：使用driver-name启动驱动程序服务= webapi.war_com.microsoft.sqlserver.jdbc.SQLServerDriver_6_0

[org.jboss.as.jpa]（ServerService线程Pool - 67）WFLYJPA0010：启动持久性单元（第2阶段）Service'webapi.war＃app'
$ b

[org.hibernate.dialect.Dialect]（ServerService线程池 - 67）HHH000400：使用方言：org.hibernate.dialect.SQLServer2008Dialect
$ b

[org.hibernate.envers.boot.internal.EnversServiceImpl]（ServerService线程池 - 67）启用Envers集成？ ：true
$ b

[org.hibernate.tool.schema.internal.ExceptionHandlerLoggedImpl]（ServerService线程池 - 67） GenerationTarget遇到异常接受命令：执行DDL时出错通过JDBC语句：org.hibernate.tool.schema.spi.CommandAcceptanceException：通过JDBC语句执行DDL时出错
在org.hibernate.tool.schema.internal.exec.GenerationTargetToDatabase.accept（GenerationTargetToDatabase.java ：67）
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.applySqlString（AbstractSchemaMigrator.java:524）
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.applySqlStrings（AbstractSchemaMigrator.java ：470）
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.createTable（AbstractSchemaMigrator.java:273）
at org.hibernate.tool.schema.internal.GroupedSchemaMigratorImpl.performTablesMigration（GroupedSchemaMigratorImpl.java ：71）
在org.hibernate.tool.schema.inter nal.AbstractSchemaMigrator.performMigration（AbstractSchemaMigrator.java:203）
位于org.hibernate.tool.schema.internal.AbstractSchemaMigrator.doMigration（AbstractSchemaMigrator.java:110）
位于org.hibernate.tool.schema。 spi.SchemaManagementToolCoordinator.performDatabaseAction（SchemaManagementToolCoordinator.java:177）
at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process（SchemaManagementToolCoordinator.java:66）
at org.hibernate.internal.SessionFactoryImpl。 （SessionFactoryImpl.java:309）
at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build（SessionFactoryBuilderImpl.java:445）
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build（EntityManagerFactoryBuilderImpl .java：877）
at org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build（TwoPhaseBootstrapImpl.java:44）
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl $ 1 $ 1.run （PersistenceUnitServiceImpl.java:154）
org.jboss.as.jpa.service.PersistenceUnitServiceImpl $ 1 $ 1.run（PersistenceUnitServiceImpl.java:117）
at org.wildfly.security.manager.WildFlySecurityManager.doChecked（WildFlySecurityManager.java:667）
在org.jboss.as.jpa.service.PersistenceUnitServiceImpl $ 1.run（PersistenceUnitServiceImpl.java:182）
at java.util.concurrent.ThreadPoolExecutor.runWorker（ThreadPoolExecutor.java:1142）
at java。 util.concurrent.ThreadPoolExecutor $ Worker.run（ThreadPoolExecutor.java:617）$ b $在java.lang.Thread.run（Thread.java:745）
在org.jboss.threads.JBossThread.run（ JBossThread.java:320）

引起：org.h2.jdbc.JdbcSQLException：未找到架构DBO; SQL语句：
创建表dbo.Anythings（Id二进制（255）不为空，CreatedOn日期时间不为空，IsActive位，主键（Id））[90079-173]
at org .h2.message.DbException.getJdbcSQLException（DbException.java:331）
at org.h2.message.DbException.get（DbException.java:171）
at org.h2.message.DbException.get （DbException.java:148）
at org.h2.command.Parser.getSchema（Parser.java:616）
at org.h2.command.Parser.getSchema（Parser.java:623）
在org.h2.command.Parser.parseCreateTable（Parser.java:5302）
在org.h2.command.Parser.parseCreate（Parser.java:3873）
在org.h2。 org.h2.command.Parser.parse（Parser.java:279）
org.h2.command.Parser.parse（Parser。 java：251）
at org.h2.command.Parser.prepareCommand（Parser.java:218）
at org.h2.engine.Session.prepareLocal（Session.java:428）
在org.h2.engine.Session.prepare命令（Session.java:377）
at org.h2.jdbc.JdbcConnection.prepareCommand（JdbcConnection.java:1138）
at org.h2.jdbc.JdbcStatement.executeInternal（JdbcStatement.java:168）
at org.h2.jdbc.JdbcStatement.execute（JdbcStatement.java:156）
at org.jboss.jca.adapters.jdbc.WrappedStatement.execute（WrappedStatement.java:198）
at org.hibernate.tool.schema.internal.exec.GenerationTargetToDatabase.accept（GenerationTargetToDatabase.java:54）
... 20 more

有无论如何这可以纠正？

更新：我认为，它无法连接数据库。当我使用 hibernate.hbm2ddl.auto 作为 validate 而不是 update ，我得到以下错误：

org.hibernate.tool.schema.spi.SchemaManagementException：架构验证：缺少表[ dbo.Anythings]

其他信息：我已经将 sqljdbc42.jar 位于 wildfly-10.0.0.Final \modules \system\layers\base\com\microsoft\sqlserver\main 和 module.xml 如下所示：

 < ;？xml version =1.0encoding =UTF-8？> 
 <！ -  JDBC Drivers module.xml文件来配置您的JDBC驱动程序 - > 
 
< module xmlns =urn：jboss：module：1.3name =com.microsoft.sqlserverslot =main> 
<资源> 
< resource-root path =sqljdbc42.jar/> 
< /资源> 
<依赖关系> 
< module name =javax.api/> 
< module name =javax.transaction.api/> 
< /依赖关系> 
< / module> 
  

我也尝试将 sqlserver 添加为全局子系统位于 standalone.xml ：

 < subsystem xmlns =urn ：JBoss的：域：EE：4.0\" > 
< global-modules> 
< module name =com.microsoft.sqlserverslot =main/> 
< / global-modules> 
 ... 
< / subsystem> 
  

然而，这些都没有奏效。

解决方案

这似乎是由您指定数据库连接的方式造成的。在EE环境中，您应该使用数据源定义，或者指定为 jta-data-source 或 non-jta-data-source 在你的 persistence.xml 中。正如JPA 2.1规范（第8.2.1.5节）所述，如果您没有指定其中的任何一个，那么您的wildfly将使用默认数据源（名为ExampleDS）部署您的应用程序，该数据源使用内存数据库h2。通过属性（ javax.persistence.jdbc.url 等）的连接参数将被忽略，因为它们是针对Java SE环境而不是Java EE。

You需要将新数据源定义添加到wildfly配置（standalone.xml或domain.xml，具体取决于您的设置）还是将您的应用程序中的数据源定义作为名为< something> -ds的文件提供。 xml 位于 WEB-INF 文件夹中。在这两种情况下，您都需要正确设置MSSQL驱动程序（部署到模块，添加 module.xml 并将驱动程序定义添加到widlfly config / subsytem = datasources）。这些操作也可以通过jboss-cli界面完成，以避免手动编辑配置文件。
之后，从persistence.xml中删除连接属性，并添加jta / non-jta-data-source元素以及新创建的DS的jndi名称。另外，请删除您的mssql模块的全局定义





这个链接可能对您有用：
Wildfly Hibernate +在应用程序数据源定义中

JBoss DB Driver +通过cli定义数据源

希望有所帮助。

This is a follow up question of Hibernate version mismatch in WildFly 10.0.

For completeness, restating the problem briefly. I have 2 projects, one is a normal java project (with maven): core, and the other is non-maven dynamic web project: webapi. The later acts as a rest layer on top of core.

core uses hibernate without any problem. It defines the persistence.xml (inside src/META-INF/) as follows:

<?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_2_0.xsd"
    version="2.0">

    <persistence-unit name="app" transaction-type="RESOURCE_LOCAL">

        <class>data.entities.Anything</class>
        <class>data.entities.Something</class>

        <properties>
            <property name="javax.persistence.jdbc.driver" value="com.microsoft.sqlserver.jdbc.SQLServerDriver"></property>
            <property name="javax.persistence.jdbc.url" value="jdbc:sqlserver://localhost;databaseName=AppDb"></property>
            <property name="javax.persistence.jdbc.user" value="****"></property>
            <property name="javax.persistence.jdbc.password" value="****"></property>
            <property name="hibernate.default_schema" value="dbo"></property>           
            <property name="hibernate.dialect" value="org.hibernate.dialect.SQLServer2008Dialect"></property>
            <property name="hibernate.hbm2ddl.auto" value="update"></property>
            <property name="jboss.as.jpa.providerModule" value="org.hibernate:5.2.4.Final" />
        </properties>
    </persistence-unit>
</persistence>

Both core and webapi is now using hibernate-core 5.2.4.Final, using maven, and WildFly module installation as described here, respectively.

However, now when I deploy webapi to WildFly 10.0, I get the following error:

[org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "webapi.war" (runtime-name: "webapi.war")

[org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Read persistence.xml for app

[org.jboss.as.jpa] (ServerService Thread Pool -- 67) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'webapi.war#app'

[org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 67) HHH000204: Processing PersistenceUnitInfo [ name: app ...]

[org.hibernate.orm.deprecation] (ServerService Thread Pool -- 67) HHH90000001: Found usage of deprecated setting for specifying Scanner [hibernate.ejb.resource_scanner]; use [hibernate.archive.scanner] instead

[org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0004: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 6.0)

[org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Started Driver service with driver-name = webapi.war_com.microsoft.sqlserver.jdbc.SQLServerDriver_6_0

[org.jboss.as.jpa] (ServerService Thread Pool -- 67) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'webapi.war#app'

[org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 67) HHH000400: Using dialect: org.hibernate.dialect.SQLServer2008Dialect

[org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 67) Envers integration enabled? : true

[org.hibernate.tool.schema.internal.ExceptionHandlerLoggedImpl] (ServerService Thread Pool -- 67) GenerationTarget encountered exception accepting command : Error executing DDL via JDBC Statement: org.hibernate.tool.schema.spi.CommandAcceptanceException: Error executing DDL via JDBC Statement at org.hibernate.tool.schema.internal.exec.GenerationTargetToDatabase.accept(GenerationTargetToDatabase.java:67) at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.applySqlString(AbstractSchemaMigrator.java:524) at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.applySqlStrings(AbstractSchemaMigrator.java:470) at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.createTable(AbstractSchemaMigrator.java:273) at org.hibernate.tool.schema.internal.GroupedSchemaMigratorImpl.performTablesMigration(GroupedSchemaMigratorImpl.java:71) at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.performMigration(AbstractSchemaMigrator.java:203) at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.doMigration(AbstractSchemaMigrator.java:110) at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:177) at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:66) at org.hibernate.internal.SessionFactoryImpl.(SessionFactoryImpl.java:309) at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:445) at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:877) at org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:154) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:117) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:667) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:182) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at org.jboss.threads.JBossThread.run(JBossThread.java:320)

Caused by: org.h2.jdbc.JdbcSQLException: Schema "DBO" not found; SQL statement: create table dbo.Anythings (Id binary(255) not null, CreatedOn datetime not null, IsActive bit, primary key (Id)) [90079-173] at org.h2.message.DbException.getJdbcSQLException(DbException.java:331) at org.h2.message.DbException.get(DbException.java:171) at org.h2.message.DbException.get(DbException.java:148) at org.h2.command.Parser.getSchema(Parser.java:616) at org.h2.command.Parser.getSchema(Parser.java:623) at org.h2.command.Parser.parseCreateTable(Parser.java:5302) at org.h2.command.Parser.parseCreate(Parser.java:3873) at org.h2.command.Parser.parsePrepared(Parser.java:324) at org.h2.command.Parser.parse(Parser.java:279) at org.h2.command.Parser.parse(Parser.java:251) at org.h2.command.Parser.prepareCommand(Parser.java:218) at org.h2.engine.Session.prepareLocal(Session.java:428) at org.h2.engine.Session.prepareCommand(Session.java:377) at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1138) at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:168) at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:156) at org.jboss.jca.adapters.jdbc.WrappedStatement.execute(WrappedStatement.java:198) at org.hibernate.tool.schema.internal.exec.GenerationTargetToDatabase.accept(GenerationTargetToDatabase.java:54) ... 20 more

Is there anyway this can be corrected?

Update: I think, it is not able to connect the database. When I use hibernate.hbm2ddl.auto as validate instead of update, I get the following error:

org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [dbo.Anythings]

Additional info: I have already placed sqljdbc42.jar in wildfly-10.0.0.Final\modules\system\layers\base\com\microsoft\sqlserver\main, and the module.xml looks like below:

<?xml version="1.0" encoding="UTF-8"?>
<!-- JDBC Drivers module.xml file to configure your JDBC drivers-->

<module xmlns="urn:jboss:module:1.3" name="com.microsoft.sqlserver" slot="main">
  <resources>
    <resource-root path="sqljdbc42.jar"/>
  </resources>
  <dependencies>
    <module name="javax.api"/>
    <module name="javax.transaction.api"/>
  </dependencies>
</module>

I also tried to add sqlserver as global subsystem in standalone.xml:

<subsystem xmlns="urn:jboss:domain:ee:4.0">
    <global-modules>
        <module name="com.microsoft.sqlserver" slot="main"/>
    </global-modules>
...
</subsystem>

However, none of these worked.

解决方案

It seems to be caused by the way how you specify DB connection. On EE environment, you are supposed to use data source definition, either specified as jta-data-source or non-jta-data-source in your persistence.xml. As stated in JPA 2.1 spec(ch. 8.2.1.5), if you do not specify any of them, your wildfly will deploy your app using its default datasource - named ExampleDS - which uses h2 in-memory DB. The connection parameters via properties(javax.persistence.jdbc.url etc) are ignored as they are intended for Java SE environment not Java EE.
You need to either add a new datasource definition to the wildfly configuration(standalone.xml or domain.xml depending on your setup) or provide the datasource definition within your app as a file named <something>-ds.xml located at WEB-INF folder. In both cases, you need to setup your MSSQL driver correctly(deploy to modules, add module.xml and add the driver definition to widlfly config /subsytem=datasources). These operations can also be done via jboss-cli interface to avoid manual edits of the configuration file. After that remove the connection properties from your persistence.xml and add the jta/non-jta-data-source element with the jndi name of your newly created DS. Also, please remove the global definition of your mssql module

This links might be useful for you: Wildfly Hibernate + In app datasource definition
JBoss DB Driver+Data source definition via cli

Hope that helps.

这篇关于org.h2.jdbc.JdbcSQLException：Schema“DBO”未找到的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！