简体中文（ZH-CN）English（EN）繁体中文（ZH-TW）日本語（JA）한국어（KO）Melayu（MS）Français（FR）Deutsch（DE）
Maison
Article
Questions et réponses
Cours
Sujet
Télécharger
Jeu
Dictionnaire
mises à jour récentes

Maison  >  Article  >  base de données  >  服务器-jBoss7.1.1 as final与MySql5.7.16的配置

服务器-jBoss7.1.1 as final与MySql5.7.16的配置

PHP中文网
PHP中文网original
2016-12-05 13:27:362307parcourir

       服务器-jBoss7.1.1 as final与MySql5.7.16的配置

服务器mysqljava eejboss

  • 由于学年论文设计的缘由，现在开始零基础学Java EE。在最近的一段时间内，我搭建了java EE的开发环境，我用的JDK和Eclipse环境分别是jdk-7u79-windows-i586 、eclipse-jee-kepler-SR2-win32，jboss的环境是jboss-as-7.1.1.Final，配置好环境后，jboss可以正常启动，然后，我安装了Mysql,环境是mysql-5.7.16-win32.zip，通过命令行配置后Mysql可以正常启动。最后是jboss与Mysql的配置启动，其中jboss中的standalone.xml文件如下：图片说明
       在D:\jboss7.1.1\modules\com\mysql\main中，文件配置如下：
    图片说明
    module.xml服务器启动报错
       鉴于我是初学者，不懂配置，求大神指导，以解决问题。

回复内容：

http://blog.csdn.net/u012705000/article/details/51408007

初次使用jboss7.1.1.final部署项目，遇到了很多困难，最终通过查看官方文档和网上资料得以解决，特此记录一下。

error information

2016-05-12 12:53:20 JRebel: 
2016-05-12 12:53:20 JRebel:  #############################################################
2016-05-12 12:53:20 JRebel: 
2016-05-12 12:53:20 JRebel:  JRebel Legacy Agent 6.4.2a (201604061405)
2016-05-12 12:53:20 JRebel:  (c) Copyright ZeroTurnaround AS, Estonia, Tartu.
2016-05-12 12:53:20 JRebel: 
2016-05-12 12:53:20 JRebel:  Over the last 5 days JRebel prevented
2016-05-12 12:53:20 JRebel:  at least 386 redeploys/restarts saving you about 15.7 hours.
2016-05-12 12:53:20 JRebel: 
2016-05-12 12:53:20 JRebel:  Licensed to Lei Zhang (sinosoft)
2016-05-12 12:53:20 JRebel: 
2016-05-12 12:53:20 JRebel:  License type: evaluation
2016-05-12 12:53:20 JRebel:  Valid from: April 26, 2016
2016-05-12 12:53:20 JRebel:  Valid until: May 10, 2016
2016-05-12 12:53:20 JRebel: 
2016-05-12 12:53:20 JRebel:  Trial License expired.
2016-05-12 12:53:20 JRebel: 
2016-05-12 12:53:20 JRebel:  To extend your evaluation or purchase a license,
2016-05-12 12:53:20 JRebel:  contact sales@zeroturnaround.com.
2016-05-12 12:53:20 JRebel: 
2016-05-12 12:53:20 JRebel:  If you think this is an error, contact support@zeroturnaround.com.
2016-05-12 12:53:20 JRebel: 
2016-05-12 12:53:20 JRebel: 
2016-05-12 12:53:20 JRebel:  #############################################################
2016-05-12 12:53:20 JRebel: 
2016-05-12 12:53:20 JRebel:
2016-05-12 12:53:20 JRebel: A newer version '6.4.3' is available for download
2016-05-12 12:53:20 JRebel: from http://zeroturnaround.com/software/jrebel/download/
2016-05-12 12:53:20 JRebel:
WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager'or the '
java.util.logging.LogManager' service loader.
12:53:22,705 信息    [org.jboss.modules] JBoss Modules version 1.1.1.GA
12:53:22,941 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
12:53:23,032 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
12:53:29,465 INFO  [org.jboss.as.server] JBAS015888: 
Creating http management service using socket-binding 
(management-http)
12:53:29,514 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
12:53:29,531 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 52) 
JBAS010280: Activating Infinispan subsystem.
12:53:29,561 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 47) JBAS016200: Activating 
ConfigAdmin Subsystem
12:53:29,563 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 65) 
JBAS013101: Activating Security 
Subsystem
12:53:29,591 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 59) JBAS011800: Activating
 Naming 
Subsystem
12:53:29,593 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 69) JBAS015537: Activating 
WebServices Extension
12:53:29,611 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 60) JBAS011940: Activating OSGi
 Subsystem
12:53:29,613 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
12:53:29,624 INFO  [org.jboss.as.security] (MSC service thread 1-7) JBAS013100: Current PicketBox 
version=4.0.7.Final
12:53:29,770 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail 
session [java:jboss/mail/Default]
12:53:29,945 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1)
 JBoss Web Services - Stack CXF Server 4.0.2.GA
12:53:43,605 INFO  [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.3.GA
12:53:43,612 INFO  [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 
3.0.3.GA
12:53:43,623 INFO  [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.3.GA
12:53:50,679 INFO  [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA
 Subsystem 
(JBoss IronJacamar 1.0.9.Final)
12:53:50,912 WARN  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015005:
 Reliable
 deployment behaviour is not possible when auto-deployment of exploded content is enabled
  (i.e. deployment without use of ".dodeploy"' marker files). Configuration of auto-deployment
   of exploded 
  content is not recommended in any situation where reliability is desired. Configuring the
   deployment 
  scanner's auto-deploy-exploded setting to "false" is recommended.
12:53:50,916 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) 
JBAS015012: 
Started FileSystemDeploymentService for directory E:\Server\jboss-as-7.1.1.Final\standalone\deployments
12:53:50,925 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) 
JBAS015014: Re-attempting failed deployment CTPro.war
12:53:50,938 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100:
 Listening on /127.0.0.1:4447
12:53:50,938 INFO  [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100:
 Listening on /127.0.0.1:9999
12:53:51,410 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote 
HTTP/1.1 on http--127.0.0.1-9090
12:53:59,503 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774:
 Service status report
JBAS014775:    New missing/unsatisfied dependencies:
 service jboss.jdbc-driver.com_oracle (missing) 
 dependents: [service jboss.data-source.java:jboss/datasources/sinosoftDataSource]

12:53:59,515 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) 
Operation ("add") failed - address: ([("deployment" => "CTPro.war")]) - failure description: 
"JBAS014803: Duplicate resource [(\"deployment\" => \"CTPro.war\")]"
12:53:59,517 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1)
 JBAS014654: Composite operation was rolled back
12:53:59,519 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1)
 {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" =>
  {"Operation step-1" => "JBAS014803: Duplicate resource [(\"deployment\" => \"CTPro.war\")]"}}
12:53:59,588 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening
 on http://127.0.0.1:10990
12:53:59,589 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.1.Final
 "Brontes" started (with errors) in 37474ms - Started 129 of 206 services
  (2 services failed or missing dependencies, 74 services are passive or on-demand)

此时我的配置文件如下：

module.xml

<module xmlns="urn:jboss:module:1.1" name="com.oracle">

    <resources>
        <resource-root path="ojdbc6.jar"/>
    </resources>

    <dependencies>
        <module name="javax.api"/>
        <module name="javax.transaction.api"/>
        <module name="javax.servlet.api" optional="true"/>
    </dependencies>

</module>

standalone.xml

<subsystem xmlns="urn:jboss:domain:datasources:1.0">
            <datasources>
                <datasource jta="true" jndi-name="java:jboss/datasources/sinosoftDataSource"
                 pool-name="sinosoftDataSource" enabled="true" use-java-context="true">
                    <connection-url>jdbc:oracle:thin:@10.129.2.106:1521:devdb</connection-url>
                    <driver>oracle</driver>
                    <pool>
                        <prefill>false</prefill>
                        <use-strict-min>false</use-strict-min>
                        <flush-strategy>FailingConnectionOnly</flush-strategy>
                    </pool>
                    <security>
                        <user-name>NEWCORE</user-name>
                        <password>NEWCORE</password>
                    </security>
                </datasource>
                <drivers>
                    <driver name="oracle" module="com.oracle">
                        <driver-class>oracle.jdbc.OracleDriver</driver-class>
                        <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
                    </driver>
                </drivers>
            </datasources>
        </subsystem>

step1: 更改standalone.xml  5b829275eaf5f23df2c0f38f5593c4bdoracle.jdbc.driver.OracleDriver1095da8ba9a31cb5383b249253e2901e

17:33:35,590 信息    [org.jboss.modules] JBoss Modules version 1.1.1.GA
17:33:36,594 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
17:33:36,716 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
17:33:40,571 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
17:33:40,581 INFO  [org.xnio] XNIO Version 3.0.3.GA
17:33:40,601 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
17:33:40,611 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
17:33:40,669 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
17:33:40,712 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
17:33:40,714 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
17:33:40,723 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
17:33:40,951 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
17:33:40,955 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
17:33:40,956 INFO  [org.jboss.as.security] (MSC service thread 1-8) JBAS013100: Current PicketBox version=4.0.7.Final
17:33:41,128 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
17:33:41,455 INFO  [org.jboss.as.naming] (MSC service thread 1-6) JBAS011802: Starting Naming Service
17:33:41,465 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
17:33:41,465 INFO  [org.jboss.as.connector] (MSC service thread 1-7) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
17:33:42,594 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.driver.OracleDriver (version 11.2)
17:33:42,859 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--127.0.0.1-9090
17:33:44,122 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-6) JBoss Web Services - Stack CXF Server 4.0.2.GA
17:33:44,708 WARN  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) JBAS015005: Reliable deployment behaviour is not possible when auto-deployment of exploded content is enabled (i.e. deployment without use of ".dodeploy"&#39; marker files). Configuration of auto-deployment of exploded content is not recommended in any situation where reliability is desired. Configuring the deployment scanner&#39;s auto-deploy-exploded setting to "false" is recommended.
17:33:44,711 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) JBAS015012: Started FileSystemDeploymentService for directory E:\Server\jboss-as-7.1.1.Final\standalone\deployments
17:33:44,730 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /127.0.0.1:4447
17:33:44,730 INFO  [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on /127.0.0.1:9999
17:33:44,745 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment CTPro.war
17:33:45,107 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.jdbc-driver.oracle (missing) dependents: [service jboss.data-source.java:jboss/datasources/sinosoftDataSource]

17:33:45,128 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) Operation ("add") failed - address: ([("deployment" => "CTPro.war")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"CTPro.war\")]"
17:33:45,130 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back
17:33:45,132 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [(\"deployment\" => \"CTPro.war\")]"}}
17:33:45,226 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:10990
17:33:45,227 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 10514ms - Started 130 of 207 services (2 services failed or missing dependencies, 74 services are passive or on-demand)

STEP 2 ;

     改web.xml

context-param>
              <param-name>log4jConfigLocation</param-name>
              <param-value>/WEB-INF//log4j.xml</param-value>
       </context-param>

to:

 context-param>
              <param-name>log4jConfigLocation</param-name>
              <param-value>/WEB-INF/classes/log4j.xml</param-value>
       </context-param>
19:02:28,784 ERROR [org.springframework.web.context.ContextLoader] (MSC service thread 1-5) Context initialization failed:org.springframework.beans.factory.BeanCreationException: Error creating bean with name &#39;dataSource&#39; defined in ServletContext resource [/WEB-INF/app-config-context.xml]: Invocation of init method failed; nested exception isjavax.naming.NameNotFoundException: sinosoftDataSource -- service jboss.naming.context.java.sinosoftDataSource
       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1455) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:567) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:913) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:464) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:385) [org.springframework.web-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:284) [org.springframework.web-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111) [org.springframework.web-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.13.Final.jar:]
       at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.13.Final.jar:]
       at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
       at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
       at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]
       at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
Caused by:javax.naming.NameNotFoundException: sinosoftDataSource -- service jboss.naming.context.java.sinosoftDataSource
       at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)
       at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
       at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113)
       at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214)
       at javax.naming.InitialContext.lookup(InitialContext.java:392) [rt.jar:1.6.0_45]
       at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:154) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:87) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:152) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:178) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:95) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java:105) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.jndi.JndiObjectFactoryBean.lookupWithFallback(JndiObjectFactoryBean.java:201) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.jndi.JndiObjectFactoryBean.afterPropertiesSet(JndiObjectFactoryBean.java:187) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1514) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1452) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       ... 20 more

19:02:28,807 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener:org.springframework.beans.factory.BeanCreationException: Error creating bean with name &#39;dataSource&#39; defined in ServletContext resource [/WEB-INF/app-config-context.xml]: Invocation of init method failed; nested exception isjavax.naming.NameNotFoundException: sinosoftDataSource -- service jboss.naming.context.java.sinosoftDataSource
       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1455) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:567) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:913) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:464) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:385) [org.springframework.web-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:284) [org.springframework.web-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111) [org.springframework.web-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.13.Final.jar:]
       at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.13.Final.jar:]
       at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
       at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
       at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]
       at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
Caused by:javax.naming.NameNotFoundException: sinosoftDataSource -- service jboss.naming.context.java.sinosoftDataSource
       at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)
       at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
       at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113)
       at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214)
       at javax.naming.InitialContext.lookup(InitialContext.java:392) [rt.jar:1.6.0_45]
       at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:154) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:87) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:152) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:178) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:95) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java:105) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.jndi.JndiObjectFactoryBean.lookupWithFallback(JndiObjectFactoryBean.java:201) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.jndi.JndiObjectFactoryBean.afterPropertiesSet(JndiObjectFactoryBean.java:187) [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1514) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1452) [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
       ... 20 more

STEP:3

 几番周折最终部署成功 最终的配置文件

1）applicationContext.xml

<beanid="dataSource"class="org.springframework.jndi.JndiObjectFactoryBean">
              <propertyname="jndiName">
                     <value>java:jboss/datasources/test</value>
              </property>
 </bean>

2)module.xml

<module xmlns="urn:jboss:module:1.0" name="com.oracle.jdbc"> 
  <resources> 
    <resource-root path="ojdbc6.jar"/> 
  </resources> 
  <dependencies> 
    <module name="javax.api"/>
    <module name="javax.transaction.api"/>
    <module name="javax.servlet.api" optional="true"/>
  </dependencies> 
</module>

3)standalone.xml

<datasources>
                <datasource jta="true" jndi-name="java:jboss/datasources/test" pool-name="test" 
                enabled="true" use-java-context="false">
                    <connection-url>jdbc:oracle:thin:@localhost:1521:orcl</connection-url>
                    <driver>oracle</driver>
                    <pool>
                        <min-pool-size>3</min-pool-size>
                        <max-pool-size>10</max-pool-size>
                    </pool>
                    <security>
                        <user-name>scott</user-name>
                        <password>tiger</password>
                    </security>
                </datasource>
                <drivers>
                   <!-- <driver name="mysql" module="com.mysql">
                        <driver-class>com.mysql.jdbc.Driver</driver-class>
                        <xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource
                        </xa-datasource-class>
                    </driver>-->
                    <driver name="oracle" module="com.oracle.jdbc">
                        <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
                        <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
                    </driver>
                </drivers>
     </datasources>

4)web.xml

<resource-ref>
          <res-ref-name>test</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Container</res-auth>
              <lookup-name>java:jboss/datasources/test</lookup-name>
 </resource-ref>
 <context-param>
   <param-name>contextConfigLocation</param-name>
   <param-value>/WEB-INF/applicationContext.xml</param-value>
 </context-param>

以上就是服务器-jBoss7.1.1 as final与MySql5.7.16的配置的内容，更多相关内容请关注PHP中文网（www.php.cn）！


Déclaration：
Le contenu de cet article est volontairement contribué par les internautes et les droits d'auteur appartiennent à l'auteur original. Ce site n'assume aucune responsabilité légale correspondante. Si vous trouvez un contenu suspecté de plagiat ou de contrefaçon, veuillez contacter admin@php.cn
Article précédent：数据库-函数mysql_connect的使用Article suivant：有木有哪位前辈用mysql直接连接android的

Articles Liés

Voir plus