mysql -service config in Jboss 3.2.1
vadim_s Jun 12, 2003 3:08 PMI am trying to connect to mySql using the mysql-service.xml
I keep on getting the error below while starting JBoss. This config worked great on Jboss 3.0 and does not work with Jboss 3.2
----------------------------------
error is below:
----------------------------------
15:26:19,159 INFO [MainDeployer] Starting deployment of package: file:/D:/jboss/server/default/depl
oy/mysql-service.xml
15:26:19,589 INFO [ServiceConfigurator] Problem configuring service jboss.jca:service=LocalTxDS,nam
e=mysqlDS
org.jboss.deployment.DeploymentException: No Attribute found with name: JndiName
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:332)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:176)
at org.jboss.system.ServiceConfigurator.processDependency(ServiceConfigurator.java:437)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:350)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:176)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:118)
at org.jboss.system.ServiceController.install(ServiceController.java:225)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284
)
.............................
at org.jboss.Main$1.run(Main.java:388)
at java.lang.Thread.run(Thread.java:479)
+ nested throwable:
javax.management.AttributeNotFoundException: Writable attribute 'ManagedConnectionFactoryName' not f
ound
at org.jboss.mx.capability.ReflectedMBeanDispatcher.setAttribute(ReflectedMBeanDispatcher.ja
va:190)
at org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:503)
at org.jboss.system.ServiceConfigurator.setAttribute
(ServiceConfigurator.java:468)
.............................
at $Proxy6.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:365)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:272)
at org.jboss.Main.boot(Main.java:150)
at org.jboss.Main$1.run(Main.java:388)
at java.lang.Thread.run(Thread.java:479)
15:26:20,891 INFO [MainDeployer] Deployed package: file:/D:/jboss/server/default/deploy/mysql
-service.xml
----------------------------------
mysql-service.xml is below:
----------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<!-- ===================================================================== -->
<!-- -->
<!-- JBoss Server Configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- ==================================================================== -->
<!-- ConnectionManager setup for Oracle dbs -->
<!-- Build jmx-api (build/build.sh all) and view for config documentation -->
<!-- Thanks to Steven Coy -->
<!-- ==================================================================== -->
<!-- Include a login module configuration named OracleDbRealm.
Update your login-conf.xml, here is an example for a
ConfiguredIdentityLoginModule:
<application-policy name = "OracleDbRealm">
<login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
<module-option name = "principal">yourprincipal</module-option>
<module-option name = "userName">yourusername</module-option>
<module-option name = "password">yourpassword</module-option>
<module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=mysqlDS</module-option>
</login-module>
</application-policy>
NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
module-option name = "managedConnectionFactoryName"
must match the object name of the ConnectionManager you are configuring here.
-->
<!--uncomment out this line if you are using the OracleDbRealm above
OracleDbRealm
-->
<depends optional-attribute-name="ManagedConnectionFactoryName">
<!--embedded mbean-->
mysqlDS
<config-property name="ConnectionURL" type="java.lang.String">jdbc:mysql://ipAddressGoesHere:3306/user</config-property>
<config-property name="DriverClass" type="java.lang.String">org.gjt.mm.mysql.Driver</config-property>
<!--set these only if you want only default logins, not through JAAS -->
<config-property name="UserName" type="java.lang.String">user</config-property>
<config-property name="Password" type="java.lang.String">user</config-property>
<!--Below here are advanced properties -->
<!--hack-->
<depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper
<depends optional-attribute-name="ManagedConnectionPool">
<!--embedded mbean-->
0
50
5000
15
<!--criteria indicates if Subject (from security domain) or app supplied
parameters (such as from getConnection(user, pw)) are used to distinguish
connections in the pool. Choices are
ByContainerAndApplication (use both),
ByContainer (use Subject),
ByApplication (use app supplied params only),
ByNothing (all connections are equivalent, usually if adapter supports
reauthentication)-->
ByContainer
<depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager
<depends optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager
java:/TransactionManager
<!--make the rar deploy! hack till better deployment-->
jboss.jca:service=RARDeployer