【问题标题】:Issue migrating to JBOSS 6.2 - application must supply JDBC connection迁移到 JBOSS 6.2 的问题 - 应用程序必须提供 JDBC 连接
【发布时间】:2014-10-07 13:07:38
【问题描述】:

我有一个在 JBOSS 6.0 上运行良好的应用程序。

然后我开始使用 6.2 by:

  • 复制应用程序 .war 文件
  • 更改 myy jboss_home 环境变量
  • 将standalone.xml文件从6.0复制到6.2

我无法在 JBOSS 6.2 上启动应用程序。请参阅下面的服务器日志。有什么想法吗?

提前谢谢你!

C:\Users\tfirmino\Desktop>cd C:\jboss-eap-6.2\bin

C:\jboss-eap-6.2\bin>standalone.sh -Dorg.jboss.as.logging.per-deployment=false
Welcome to Git (version 1.8.3-preview20130601)


Run 'git help git' to display the help index.
Run 'git help <command>' to display help for specific commands.
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: C:\jboss-eap-6.2

  JAVA: C:\jdk1.7.0_07/bin/java

  JAVA_OPTS:  -server -XX:+UseCompressedOops -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -D
jboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

11:00:53,201 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final-redhat-2
11:00:53,342 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
11:00:53,405 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) sta
rting
11:00:55,111 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting fa
iled deployment tar.war
11:00:55,126 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found tar.war in
 deployment directory. To trigger deployment create a file called tar.war.dodeploy
11:00:55,142 INFO  [org.xnio] (MSC service thread 1-7) XNIO Version 3.0.7.GA-redhat-1
11:00:55,142 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using soc
ket-binding (management-http)
11:00:55,142 INFO  [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
11:00:55,158 INFO  [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 3.2.18.GA-redhat-1
11:00:55,173 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 27) JBAS016200: Activating ConfigAdmin Subsy
stem
11:00:55,173 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinis
pan subsystem.
11:00:55,189 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 45) JBAS013171: Activating Security Subsystem
11:00:55,205 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 39) JBAS011800: Activating Naming Subsystem
11:00:55,189 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 40) JBAS011906: Activating OSGi Subsystem
11:00:55,220 INFO  [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.19.SP2-red
hat-1
11:00:55,220 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 50) JBAS015537: Activating WebServices Exten
sion
11:00:55,236 INFO  [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
11:00:55,236 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 49) JBAS012605: Activated the following JSF Implemen
tations: [main, 1.2]
11:00:55,252 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mai
l/Default]
11:00:55,283 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (IronJac
amar 1.0.23.Final-redhat-1)
11:00:55,283 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 28) JBAS014613: Operatio
n ("add") failed - address: ([
    ("subsystem" => "datasources"),
    ("jdbc-driver" => "rdbthin.jar")
]) - failure description: "JBAS010441: Failed to load module for driver [oracle.rdb]"
11:00:55,299 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 28) JBAS014613: Operatio
n ("add") failed - address: ([
    ("subsystem" => "datasources"),
    ("jdbc-driver" => "ojdbc6-11.2.0.3.jar")
]) - failure description: "JBAS010441: Failed to load module for driver [com.oracle.db]"
11:00:55,330 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deployi
ng JDBC-compliant driver class org.h2.Driver (version 1.3)
11:00:55,393 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 28) JBAS014613: Operatio
n ("add") failed - address: ([
    ("subsystem" => "datasources"),
    ("jdbc-driver" => "OracleJDBCDriver")
]) - failure description: "JBAS010441: Failed to load module for driver [com.oracle.ojdbc6]"
11:00:55,533 INFO  [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003001: Coyote HTTP/1.1 initializing on : ht
tp-/127.0.0.1:8080
11:00:55,549 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data sourc
e [java:jboss/datasources/ExampleDS]
11:00:55,549 INFO  [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003000: Coyote HTTP/1.1 starting on: http-/1
27.0.0.1:8080
11:00:55,627 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:4447
11:00:55,627 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) JBAS015012: Started FileSystemDeplo
ymentService for directory C:\jboss-eap-6.2\standalone\deployments
11:00:55,627 INFO  [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on 127.0.0.1:9999
11:00:55,627 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "tar.war
" (runtime-name: "tar.war")
11:00:55,643 INFO  [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - S
tack CXF Server 4.2.3.Final-redhat-1
11:00:55,894 INFO  [org.jboss.as.jpa] (MSC service thread 1-5) JBAS011401: Read persistence.xml for APP_SOURCE
11:00:56,034 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 52) JBAS011402: Starting Persistence Unit Service 't
ar.war#APP_SOURCE'
11:00:56,097 INFO  [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 52) HCANN000001: Hibernate C
ommons Annotations {4.0.1.Final-redhat-2}
11:00:56,113 INFO  [org.hibernate.Version] (ServerService Thread Pool -- 52) HHH000412: Hibernate Core {4.2.7.SP1-redhat
-3}
11:00:56,113 INFO  [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 52) HHH000206: hibernate.properties not
 found
11:00:56,113 INFO  [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 52) HHH000021: Bytecode provider name :
 javassist
11:00:56,128 INFO  [org.hibernate.ejb.Ejb3Configuration] (ServerService Thread Pool -- 52) HHH000204: Processing Persist
enceUnitInfo [
        name: APP_SOURCE
        ...]
11:00:56,316 WARN  [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (ServerService Thread P
ool -- 52) HHH000181: No appropriate connection provider encountered, assuming application will be supplying connections

11:00:56,332 INFO  [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 52) HHH000400: Using dialect: org.hiber
nate.dialect.Oracle10gDialect
11:00:56,332 INFO  [org.hibernate.engine.jdbc.internal.LobCreatorBuilder] (ServerService Thread Pool -- 52) HHH000422: D
isabling contextual LOB creation as connection was null
11:00:56,535 WARN  [org.hibernate.mapping.RootClass] (ServerService Thread Pool -- 52) HHH000038: Composite-id class doe
s not override equals(): myApp.entity.StudentUnitAuditPK
11:00:56,551 INFO  [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (ServerService Thread Pool --
 52) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
11:00:56,551 INFO  [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 52) HHH00039
7: Using ASTQueryTranslatorFactory
11:00:56,582 INFO  [org.hibernate.validator.internal.util.Version] (ServerService Thread Pool -- 52) HV000001: Hibernate
 Validator 4.3.1.Final-redhat-1
11:00:56,989 INFO  [org.hibernate.tool.hbm2ddl.SchemaValidator] (ServerService Thread Pool -- 52) HHH000229: Running sch
ema validator
11:00:56,989 INFO  [org.hibernate.tool.hbm2ddl.SchemaValidator] (ServerService Thread Pool -- 52) HHH000102: Fetching da
tabase metadata
11:00:56,989 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 52) MSC000001: Failed to start service jbo
ss.persistenceunit."tar.war#APP_SOURCE": org.jboss.msc.service.StartException in service jboss.persistenceunit."tar.war#APP_SOURCE": java.lang.UnsupportedOperationException: The application must supply JDBC connections
        at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:103) [jboss-as-jpa-
7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
        at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
        at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final-redhat-1.jar:2.1.1.Final-r
edhat-1]
Caused by: java.lang.UnsupportedOperationException: The application must supply JDBC connections
        at org.hibernate.service.jdbc.connections.internal.UserSuppliedConnectionProviderImpl.getConnection(UserSupplied
ConnectionProviderImpl.java:62)
        at org.hibernate.tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.prepare(SuppliedConnectionProviderConne
ctionHelper.java:51)
        at org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:146)
        at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:509)
        at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1794)
        at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:96)
        at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:914)
        at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:899)
        at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:76)
        at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServic
eImpl.java:200) [jboss-as-jpa-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
        at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$600(PersistenceUnitServiceImpl.java:57) [jboss-as-
jpa-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
        at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:99) [jboss-as-jpa-7
.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
        ... 4 more

11:00:59,447 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 29) JBAS018559: Deployed "tar.war" (runtime-name
: "tar.war")
11:00:59,447 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.jdbc-driver.OracleJDBCDriver (missing) dependents: [service jboss.driver-demander.java:jboss/datasou
rces/ESS_SCIDS, service jboss.driver-demander.java:jboss/datasources/ldCommonds-u, service jboss.data-source.java:jboss/
datasources/ldCommonds, service jboss.data-source.java:jboss/datasources/ESS_SCIDS, JBAS014799: ... and 7 more ]
JBAS014777:   Services which failed to start:      service jboss.persistenceunit."tar.war#APP_SOURCE": org.jboss.msc.servic
e.StartException in service jboss.persistenceunit."tar.war#APP_SOURCE": java.lang.UnsupportedOperationException: The applic
ation must supply JDBC connections

11:00:59,463 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127
.0.0.1:9990/management
11:00:59,463 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
11:00:59,463 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) sta
rted (with errors) in 6544ms - Started 173 of 282 services (24 services failed or missing dependencies, 79 services are
passive or on-demand)

【问题讨论】:

  • 你能用你的休眠配置更新你的问题吗?看看this post,好像这个错误可能和你的一些配置有关,如果你把你的一些代码和结构贴出来,我们就能找出问题所在。

标签: java jboss


【解决方案1】:

看起来您的 JBossEAP 6.0 系统有一个包含 Oracle JDBC 驱动程序的自定义模块。

您还需要将其迁移到新服务器中。

此外,将整个standalone.xml 文件向前迁移到新版本的JBossAS/Wildfly 通常是个坏主意。一个更好的主意是编写一个 CLI 脚本来进行配置并使用它来配置每个新环境。

【讨论】:

  • 感谢史蒂夫,我为驱动程序添加了模块并隐藏了该错误。我还返回了原始的standalone.xml 并放入了我需要的信息,而不是从 JBOSS 6 剪切/过去到 JBOSS 6.2 但我在这篇文章中提到的原始错误仍然存​​在......它仍然抱怨应用程序必须提供 JDBC 连接。 ..
【解决方案2】:

问题出在这里:

11:00:55,393 错误 [org.jboss.as.controller.management-operation] (ServerService 线程池 -- 28) JBAS014613: 操作 ("add") 失败 - 地址:([ (“子系统”=>“数据源”), ("jdbc-driver" => "OracleJDBCDriver") ]) - 失败描述:“JBAS010441: 无法加载驱动程序 [com.oracle.ojdbc6] 的模块”

您的 Oracle JDBC 模块似乎丢失或失败。

【讨论】:

  • 感谢 Evandro,我为驱动程序添加了模块并隐藏了该错误,但我在这篇文章中提到的原始错误仍然存​​在......它仍然抱怨应用程序必须提供 JDBC 连接.. .
  • 能否用当前日志更新您的问题?只是为了确保我们使用与您相同的日志。
猜你喜欢
  • 2013-05-05
  • 2014-06-07
  • 2014-07-26
  • 2016-12-04
  • 2015-12-04
  • 2013-06-25
  • 2017-07-02
  • 2014-09-25
相关资源
最近更新 更多