Erro ao criar o DataSource do Mysql no Jboss

Programação Java
#1

Pessoal, estou com um problema para criar a conexão do Mysql no Jboss.
Já peguei diversos tutoriais mas não encontrei algum que me ajude para corrigir o erro…

Segue abaixo o meu DS e o Strack Trace do Jboss.

<?xml version="1.0" encoding="UTF-8"?>
<datasources>
    <local-tx-datasource>
        <jndi-name>MySqlDS</jndi-name>
        <connection-url>jdbc:mysql://localhost:3306/db_siscont</connection-url>
        <driver-class>com.mysql.jdbc.Driver</driver-class>
        <user-name>...</user-name>
        <password>...</password>
    </local-tx-datasource>
</datasources>
23:33:21,180 INFO  [Server] Starting JBoss (MX MicroKernel)...
23:33:21,195 INFO  [Server] Release ID: JBoss [Trinity] 4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)
23:33:21,196 INFO  [Server] Home Dir: /usr/local/java/jboss-4.2.1.GA
23:33:21,196 INFO  [Server] Home URL: file:/usr/local/java/jboss-4.2.1.GA/
23:33:21,198 INFO  [Server] Patch URL: null
23:33:21,198 INFO  [Server] Server Name: default
23:33:21,198 INFO  [Server] Server Home Dir: /usr/local/java/jboss-4.2.1.GA/server/default
23:33:21,198 INFO  [Server] Server Home URL: file:/usr/local/java/jboss-4.2.1.GA/server/default/
23:33:21,198 INFO  [Server] Server Log Dir: /usr/local/java/jboss-4.2.1.GA/server/default/log
23:33:21,198 INFO  [Server] Server Temp Dir: /usr/local/java/jboss-4.2.1.GA/server/default/tmp
23:33:21,199 INFO  [Server] Root Deployment Filename: jboss-service.xml
23:33:22,655 INFO  [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc.
23:33:22,656 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-b105,Sun Microsystems Inc.
23:33:22,656 INFO  [ServerInfo] OS-System: Linux 2.6.20-16-386,i386
23:33:24,213 INFO  [Server] Core system initialized
23:33:28,272 INFO  [WebService] Using RMI server codebase: http://127.0.0.1:8083/
23:33:28,275 INFO  [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
23:33:29,991 INFO  [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
23:33:29,992 INFO  [TransactionManagerService] Setting up property manager MBean and JMX layer
23:33:30,356 INFO  [TransactionManagerService] Starting recovery manager
23:33:30,709 INFO  [TransactionManagerService] Recovery manager started
23:33:30,710 INFO  [TransactionManagerService] Binding TransactionManager JNDI Reference
23:33:36,722 INFO  [EJB3Deployer] Starting java:comp multiplexer
23:33:39,760 INFO  [ServiceEndpointManager] jbossws-1.2.1.GA (build=200704151756)
23:33:42,818 INFO  [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-6-sun-1.6.0.00/jre/lib/i386/client:/usr/lib/jvm/java-6-sun-1.6.0.00/jre/lib/i386:/usr/lib/jvm/java-6-sun-1.6.0.00/jre/../lib/i386:/usr/lib/jvm/java-6-sun-1.6.0.00/jre/lib/i386/client::/usr/lib/jvm/java-6-sun-1.6.0.00/jre/lib/i386::/usr/lib/mozilla-firefox:/usr/lib/mozilla-firefox:/usr/java/packages/lib/i386:/lib:/usr/lib
23:33:42,994 INFO  [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
23:33:42,995 INFO  [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8010
23:33:42,996 INFO  [Catalina] Initialization processed in 729 ms
23:33:42,996 INFO  [StandardService] Starting service jboss.web
23:33:43,000 INFO  [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.0.GA
23:33:43,117 INFO  [Catalina] Server startup in 120 ms
23:33:43,625 INFO  [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
23:33:45,386 INFO  [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
23:33:45,737 INFO  [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp7114jbossws-context-exp.war/
23:33:45,950 INFO  [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
23:33:47,919 INFO  [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
23:33:48,952 INFO  [MailService] Mail Service bound to java:/Mail
23:33:49,254 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
23:33:49,465 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
23:33:49,676 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
23:33:49,723 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
23:33:49,815 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
23:33:49,867 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
23:33:49,909 INFO  [QuartzResourceAdapter] start quartz!!!
23:33:50,288 INFO  [SimpleThreadPool] Job execution threads will use class loader of thread: main
23:33:50,359 INFO  [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
23:33:50,368 INFO  [RAMJobStore] RAMJobStore initialized.
23:33:50,368 INFO  [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
23:33:50,369 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.5.2
23:33:50,369 INFO  [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
23:33:52,794 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
23:33:53,503 INFO  [A] Bound to JNDI name: queue/A
23:33:53,507 INFO  [B] Bound to JNDI name: queue/B
23:33:53,510 INFO  [C] Bound to JNDI name: queue/C
23:33:53,514 INFO  [D] Bound to JNDI name: queue/D
23:33:53,520 INFO  [ex] Bound to JNDI name: queue/ex
23:33:53,636 INFO  [testTopic] Bound to JNDI name: topic/testTopic
23:33:53,640 INFO  [securedTopic] Bound to JNDI name: topic/securedTopic
23:33:53,643 INFO  [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
23:33:53,649 INFO  [testQueue] Bound to JNDI name: queue/testQueue
23:33:53,799 INFO  [UILServerILService] JBossMQ UIL service available at : /127.0.0.1:8093
23:33:53,891 INFO  [DLQ] Bound to JNDI name: queue/DLQ
23:33:54,162 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
23:33:54,402 INFO  [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
23:33:54,716 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@196762bc { url=file:/usr/local/java/jboss-4.2.1.GA/server/default/deploy/SistCont-DS.xml }
  deployer: null
  status: null
  state: INIT_WAITING_DEPLOYER
  watch: file:/usr/local/java/jboss-4.2.1.GA/server/default/deploy/SistCont-DS.xml
  altDD: null
  lastDeployed: 1192761234714
  lastModified: 1192761234000
  mbeans:

--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@196762bc { url=file:/usr/local/java/jboss-4.2.1.GA/server/default/deploy/SistCont-DS.xml }
  deployer: null
  status: null
  state: INIT_WAITING_DEPLOYER
  watch: file:/usr/local/java/jboss-4.2.1.GA/server/default/deploy/SistCont-DS.xml
  altDD: null
  lastDeployed: 1192761234714
  lastModified: 1192761234000
  mbeans:


23:33:54,947 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
23:33:55,014 INFO  [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8010
23:33:55,034 INFO  [Server] JBoss (MX MicroKernel) [4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)] Started in 33s:832ms
#2

Olá,

Estava vendo o nome do seu arquivo: terminava em “-DS.xml”, sendo “-DS” em maiúsculo. Uma das exigências do JBOSS para gerar datasources é que o arquivo de configuração do datasource termine em “-ds”. Como vc colocou em maiúsculo, pode ser aí onde esteja o erro.

Segundo, vc colocou o jar contendo o driver MySQL no diretório “server/default/lib”. Se não, o JBOSS não gerará o datasource para vc.

Além disso, vc ressalvar que o arquivo de configuração do datasource é “hot-deployment”, o que significa que é só jogar esse arquivo no diretório “server/default/deploy” e o resto deixe por conta do JBOSS.

Abraços

#3

Muito legal a sua dica só para acrescentar minha aplicação também apresentava muitos erros e acrescentei o parâmetro em negrito e funcionou muito bem connection-url>jdbc:mysql://LOCALHOST/base?autoReconnect=true
FLW

#4