Problema em configuração mysql em Jboss...

1. Problema em configuração mysql em Jboss...

Sidnei Júnior
smnj

(usa Ubuntu)

Enviado em 09/05/2012 - 02:23h

O lá pessoal, estou tendo um problema com a configuração de um server JBOSS AS 7.02 podem me ajduar?
bom, coloquei a lib do mysql na pasta /jboss-as-web-7.0.2.Final/modules/com/mysql/main;

alterei o bendito standalone deste modo

<?xml version='1.0' encoding='UTF-8'?>

<server name="administrador-P5KC" xmlns="urn:jboss:domain:1.0">
<extensions>
<extension module="org.jboss.as.clustering.infinispan" />
<extension module="org.jboss.as.connector" />
<extension module="org.jboss.as.deployment-scanner" />
<extension module="org.jboss.as.ee" />
<extension module="org.jboss.as.ejb3" />
<extension module="org.jboss.as.jaxrs" />
<extension module="org.jboss.as.jmx" />
<extension module="org.jboss.as.jpa" />
<extension module="org.jboss.as.logging" />
<extension module="org.jboss.as.naming" />
<extension module="org.jboss.as.osgi" />
<extension module="org.jboss.as.pojo" />
<extension module="org.jboss.as.remoting" />
<extension module="org.jboss.as.sar" />
<extension module="org.jboss.as.security" />
<extension module="org.jboss.as.threads" />
<extension module="org.jboss.as.transactions" />
<extension module="org.jboss.as.web" />
<extension module="org.jboss.as.weld" />
</extensions>
<management>
<security-realms>
<security-realm name="PropertiesMgmtSecurityRealm">
<authentication>
<properties path="mgmt-users.properties" relative-to="jboss.server.config.dir" />
</authentication>
</security-realm>
</security-realms>
<management-interfaces>
<native-interface interface="management" port="9999" />
<http-interface interface="management" port="9990" />
</management-interfaces>
</management>
<profile>
<subsystem xmlns="urn:jboss:domain:logging:1.1">
<console-handler name="CONSOLE" autoflush="true">
<level name="INFO" />
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n" />
</formatter>
</console-handler>
<periodic-rotating-file-handler name="FILE"
autoflush="true">
<level name="INFO" />
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n" />
</formatter>
<file relative-to="jboss.server.log.dir" path="server.log" />
<suffix value=".yyyy-MM-dd" />
<append value="true" />
</periodic-rotating-file-handler>
<logger category="com.arjuna">
<level name="WARN" />
</logger>
<logger category="org.apache.tomcat.util.modeler">
<level name="WARN" />
</logger>
<logger category="sun.rmi">
<level name="WARN" />
</logger>
<root-logger>
<level name="INFO" />
<handlers>
<handler name="CONSOLE" />
<handler name="FILE" />
</handlers>
</root-logger>
</subsystem>
<subsystem xmlns="urn:jboss:domain:datasources:1.0">
<datasources>
<datasource jndi-name="java:jboss/datasources/ExampleDS"
pool-name="H2DS" enabled="true" jta="true" use-java-context="true"
use-ccm="true">
<connection-url>
jdbc:h2:mem:test;DB_CLOSE_DELAY=-1
</connection-url>
<driver>
h2
</driver>
<pool>
<prefill>
false
</prefill>
<use-strict-min>
false
</use-strict-min>
<flush-strategy>
FailingConnectionOnly
</flush-strategy>
</pool>
<security>
<user-name>
sa
</user-name>
<password>
sa
</password>
</security>
</datasource>
<datasource jndi-name="java:jboss/datasources/lzaonline"
pool-name="lzaonline">
<connection-url>
jdbc:mysql://localhost:3306/lzaonline
</connection-url>
<transaction-isolation>TRANSACTION_READ_COMMITTED
</transaction-isolation>
<pool>
<min-pool-size>10</min-pool-size>
<max-pool-size>100</max-pool-size>
<prefill>true</prefill>
</pool>
<statement>
<prepared-statement-cache-size>
100
</prepared-statement-cache-size>
<share-prepared-statements />
</statement>
<security>
<user-name>
root
</user-name>
<password>
</password>
</security>
</datasource>
<drivers>
<driver name="com.mysql" module="com.mysql">
<xa-datasource-class>
com.mysql.jdbc.jdbc2.optional.MysqlXADataSource
</xa-datasource-class>
</driver>
<driver name="h2" module="com.h2database.h2">
<xa-datasource-class>
org.h2.jdbcx.JdbcDataSource
</xa-datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.0">
<deployment-scanner name="default" path="deployments"
scan-enabled="true" scan-interval="5000" relative-to="jboss.server.base.dir"
deployment-timeout="60" />
</subsystem>
<subsystem xmlns="urn:jboss:domain:ee:1.0" />
<subsystem xmlns="urn:jboss:domain:ejb3:1.1" lite="true">
<session-bean>
<stateless>
<bean-instance-pool-ref pool-name="slsb-strict-max-pool" />
</stateless>
</session-bean>
<pools>
<bean-instance-pools>
<strict-max-pool name="slsb-strict-max-pool"
max-pool-size="20" instance-acquisition-timeout="5"
instance-acquisition-timeout-unit="MINUTES" />
</bean-instance-pools>
</pools>
</subsystem>
<subsystem xmlns="urn:jboss:domain:infinispan:1.0"
default-cache-container="hibernate">
<cache-container name="hibernate" default-cache="local-query">
<local-cache name="entity">
<eviction strategy="LRU" max-entries="10000" />
<expiration max-idle="100000" />
</local-cache>
<local-cache name="local-query">
<eviction strategy="LRU" max-entries="10000" />
<expiration max-idle="100000" />
</local-cache>
<local-cache name="timestamps">
<eviction strategy="NONE" />
</local-cache>
</cache-container>
</subsystem>
<subsystem xmlns="urn:jboss:domain:jaxrs:1.0" />
<subsystem xmlns="urn:jboss:domain:jca:1.0">
<archive-validation enabled="false" />
<bean-validation enabled="false" />
<default-workmanager>
<short-running-threads blocking="true"
allow-core-timeout="false">
<core-threads count="10" per-cpu="20" />
<queue-length count="10" per-cpu="20" />
<max-threads count="10" per-cpu="20" />
<keepalive-time time="10" unit="SECONDS" />
</short-running-threads>
<long-running-threads blocking="true"
allow-core-timeout="false">
<core-threads count="10" per-cpu="20" />
<queue-length count="10" per-cpu="20" />
<max-threads count="10" per-cpu="20" />
<keepalive-time time="10" unit="SECONDS" />
</long-running-threads>
</default-workmanager>
</subsystem>
<subsystem xmlns="urn:jboss:domain:jmx:1.0">
<jmx-connector server-binding="jmx-connector-server"
registry-binding="jmx-connector-registry" />
</subsystem>
<subsystem xmlns="urn:jboss:domain:jpa:1.0">
<jpa default-datasource="" />
</subsystem>
<subsystem xmlns="urn:jboss:domain:naming:1.0" />
<subsystem xmlns="urn:jboss:domain:pojo:1.0" />
<subsystem xmlns="urn:jboss:domain:osgi:1.0" activation="lazy">
<configuration
pid="org.apache.felix.webconsole.internal.servlet.OsgiManager">
<property name="manager.root">
jboss-osgi
</property>
</configuration>
<properties>
<property name="org.jboss.osgi.system.modules">
org.apache.commons.logging,
org.apache.log4j,
org.jboss.as.osgi,
org.slf4j,
</property>
<property name="org.osgi.framework.startlevel.beginning">
1
</property>
<property name="org.osgi.framework.system.packages.extra">
org.apache.commons.logging;version=1.1.1,
org.apache.log4j;version=1.2,
org.jboss.as.osgi.service;version=7.0,
org.jboss.osgi.deployment.interceptor;version=1.0,
org.jboss.osgi.spi.capability;version=1.0,
org.jboss.osgi.spi.util;version=1.0,
org.jboss.osgi.testing;version=1.0,
org.jboss.osgi.vfs;version=1.0,
org.slf4j;version=1.5.10,
</property>
</properties>
<modules>
<module identifier="javaee.api" />
<module identifier="org.jboss.logging" />
<module identifier="org.apache.aries.util" />
<module identifier="org.jboss.osgi.webconsole" />
<module identifier="org.osgi.compendium" />
<module identifier="org.apache.felix.log" startlevel="1" />
<module identifier="org.jboss.osgi.logging" startlevel="1" />
<module identifier="org.apache.felix.configadmin" startlevel="1" />
<module identifier="org.jboss.as.osgi.configadmin"
startlevel="1" />
<module identifier="org.apache.aries.jmx" startlevel="2" />
<module identifier="org.apache.felix.eventadmin" startlevel="2" />
<module identifier="org.apache.felix.metatype" startlevel="2" />
<module identifier="org.apache.felix.scr" startlevel="2" />
<module identifier="org.apache.felix.webconsole" startlevel="2" />
<module identifier="org.jboss.osgi.jmx" startlevel="2" />
<module identifier="org.jboss.osgi.http" startlevel="2" />
<module identifier="org.jboss.osgi.blueprint" startlevel="3" />
<module identifier="org.jboss.osgi.webapp" startlevel="3" />
<module identifier="org.jboss.osgi.xerces" startlevel="3" />
</modules>
</subsystem>
<subsystem xmlns="urn:jboss:domain:remoting:1.0" />
<subsystem xmlns="urn:jboss:domain:resource-adapters:1.0" />
<subsystem xmlns="urn:jboss:domain:sar:1.0" />
<subsystem xmlns="urn:jboss:domain:security:1.0">
<security-domains>
<security-domain name="other" cache-type="default">
<authentication>
<login-module code="Disabled" flag="required" />
</authentication>
</security-domain>
</security-domains>
</subsystem>
<subsystem xmlns="urn:jboss:domain:threads:1.0" />
<subsystem xmlns="urn:jboss:domain:transactions:1.0">
<core-environment>
<process-id>
<uuid />
</process-id>
</core-environment>
<recovery-environment socket-binding="txn-recovery-environment"
status-socket-binding="txn-status-manager" />
<coordinator-environment default-timeout="300" />
<object-store />
</subsystem>
<subsystem xmlns="urn:jboss:domain:web:1.0"
default-virtual-server="default-host">
<connector name="http" protocol="HTTP/1.1" socket-binding="http"
scheme="http" />
<virtual-server name="default-host"
enable-welcome-root="true">
<alias name="localhost" />
<alias name="example.com" />
</virtual-server>
</subsystem>
<subsystem xmlns="urn:jboss:domain:weld:1.0" />
</profile>
<interfaces>
<interface name="management">
<inet-address value="${jboss.bind.address.management:127.0.0.1}" />
</interface>
<interface name="public">
<inet-address value="${jboss.bind.address:127.0.0.1}" />
</interface>
</interfaces>
<socket-binding-group name="standard-sockets"
default-interface="public">
<socket-binding name="http" port="8080" />
<socket-binding name="https" port="8443" />
<socket-binding name="jmx-connector-registry" port="1090"
interface="management" />
<socket-binding name="jmx-connector-server" port="1091"
interface="management" />
<socket-binding name="jndi" port="1099" />
<socket-binding name="osgi-http" port="8090" interface="management" />
<socket-binding name="remoting" port="4447" />
<socket-binding name="txn-recovery-environment" port="4712" />
<socket-binding name="txn-status-manager" port="4713" />
</socket-binding-group>
</server>


O persistence.xml está assim:

<?xml version="1.0" encoding="ISO-8859-1"?>

<persistence version="2.0"
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">;


<persistence-unit name="lzaonline" transaction-type="JTA">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<jta-data-source>java:/lzaonline</jta-data-source>
<properties>
<property name="hibernate.dialect" value="org.hibernate.dialect.MySQL5InnoDBDialect" />
<property name="hibernate.hbm2ddl.auto" value="update" />
<property name="javax.persistence.jdbc.driver" value="com.mysql.jdbc.Driver" />
<property name="javax.persistence.jdbc.user" value="root" />
<property name="javax.persistence.jdbc.password" value="" />
<property name="javax.persistence.jdbc.url" value="jdbc:mysql://localhost:3306/lzaonline" />
<property name="hibernate.show_sql" value="true" />
<property name="hibernate.format_sql" value="true" />
<property name="hibernate.generate_statistics" value="true" />
</properties>


</properties>
</persistence-unit>
</persistence>


Este é o module.xml na pasta /jboss-as-web-7.0.2.Final/modules/com/mysql/main;



<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="com.mysql">
<resources>
<resource-root path="mysql-connector-java-5.1.20-bin.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
</dependencies>
</module>



E obtenho este log:


02:04:12,261 Informações [org.jboss.modules] JBoss Modules version 1.0.2.GA
02:04:12,627 INFO [org.jboss.msc] JBoss MSC version 1.0.1.GA
02:04:12,683 INFO [org.jboss.as] JBoss AS 7.0.2.Final "Arc" starting
02:04:13,604 WARN [org.jboss.as] No security realm defined for native management service, all access will be unrestricted.
02:04:13,617 INFO [org.jboss.as] creating http management service using network interface (management) port (9990)
02:04:13,620 WARN [org.jboss.as] No security realm defined for http management service, all access will be unrestricted.
02:04:13,632 INFO [org.jboss.as.logging] Removing bootstrap log handlers
02:04:13,669 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
02:04:13,677 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
02:04:13,696 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
02:04:13,831 INFO [org.jboss.as.naming] (Controller Boot Thread) JBAS011800: Activating Naming Subsystem
02:04:13,847 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
02:04:13,858 INFO [org.jboss.as.osgi] (Controller Boot Thread) JBAS011910: Activating OSGi Subsystem
02:04:13,890 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
02:04:13,903 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.0.Beta2
02:04:13,937 INFO [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.0.Beta3
02:04:13,952 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.0.0.Beta3
02:04:14,180 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-3) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
02:04:14,202 INFO [org.jboss.as.remoting] (MSC service thread 1-2) Listening on /127.0.0.1:9999
02:04:14,204 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-2) Starting remote JMX connector
02:04:14,207 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
02:04:14,236 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-6) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
02:04:14,478 INFO [org.jboss.as.connector] (MSC service thread 1-5) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)
02:04:14,519 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) Bound data source [java:/lzaonline]
02:04:14,519 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) Bound data source [java:jboss/datasources/ExampleDS]
02:04:14,920 INFO [org.jboss.as.deployment] (MSC service thread 1-1) Started FileSystemDeploymentService for directory /home/administrador/Desenvolvimento/jboss-as-web-7.0.2.Final/standalone/deployments
02:04:14,924 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found LuzianiaOnline.war in deployment directory. To trigger deployment create a file called LuzianiaOnline.war.dodeploy
02:04:14,942 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.2.Final "Arc" started in 3044ms - Started 98 of 153 services (55 services are passive or on-demand)
02:04:18,241 WARN [org.jboss.as.protocol] (pool-2-thread-2) JBAS012100: Got error closing channel JBREM00206: Channel is not open
02:12:44,131 WARN [org.jboss.as.protocol] (pool-2-thread-8) JBAS012100: Got error closing channel JBREM00206: Channel is not open


mas nada acontece, não funciona nem com reza...
O que pode estar errado?

por favor, estou me interessando a estudar Jboss agora, e seria muito grato por uma ajuda...
muito obrigado.


  


2. Re: Problema em configuração mysql em Jboss...

Filippe
spolti

(usa Fedora)

Enviado em 09/05/2012 - 09:38h

Volte a configuração default e cloque o jar dentro da pasta lib da conf que vc está usando.


3. Re: Problema em configuração mysql em Jboss...

Sidnei Júnior
smnj

(usa Ubuntu)

Enviado em 09/05/2012 - 10:37h

Qual lugar ficaria essa pasta lib?


4. Re: Problema em configuração mysql em Jboss...

Filippe
spolti

(usa Fedora)

Enviado em 09/05/2012 - 11:22h

JBOSS_HOME/standalone/lib/
ou
$JBOSS_HOME/domain/lib/

dentro de cada tem uma pasta ext, ainda n tive experiencias com jboss 7, se não funcionar somente dentro da pasta lib, copie também pra dentro de ext.


5. Re: Problema em configuração mysql em Jboss...

Sidnei Júnior
smnj

(usa Ubuntu)

Enviado em 10/05/2012 - 01:52h

Cara, não funciona nem com reza...


6. Re: Problema em configuração mysql em Jboss...

Filippe
spolti

(usa Fedora)

Enviado em 10/05/2012 - 11:53h

Então coloca dentro da pasta WEB-INF/lib da sua aplicação.

Se n funcionar, cara, baixa um jboss 0 bala no jboss.org.


7. Re: Problema em configuração mysql em Jboss...

Sidnei Júnior
smnj

(usa Ubuntu)

Enviado em 10/05/2012 - 15:34h

Cara, já tem na lib da aplicação,
baixarei então um novo, e vou tentar...
ainda sou novo, aprendo...
muito obrigado até aqui, fica com Deus.






Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts