Bugs item #667492, was opened at 2003-01-14 01:40
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=667492&group_id=22866
Category: JBossCX
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Dave Marquard (lurp)
Assigned to: David Jencks (d_jencks)
Summary: ra.xml in jboss-xa.rar is missing config-property-value tags
Initial Comment:
JBoss 3.0.5 doesn't appear to be able to deploy any XA
jdbc datasources because the ra.xml file in
jboss-xa.rar is missing config-property-value tags. The
exeption at the bottom of this report is spit out
during deployment.
Steps to reproduce:
Attempt to deploy a XA jdbc datasource. Any one in the
jca examples directory will do.
JBoss Version: 3.0.5
JDK Version: 1.4.1_01
OS: Windows XP
Work around:
Replace the ra.xml file in jboss-xa.rar with the
attached one that includes the necessary
config-property-value tags.
The exception:
16:46:42,408 ERROR [XATxConnectionManager] Starting failed
org.jboss.deployment.DeploymentException: expected one
config-property-value tag
at
org.jboss.metadata.MetaData.getUniqueChild(MetaData.java:101)
at
org.jboss.resource.connectionmanager.RARDeployment.setMcfProperties(RARDeployment.java:787)
at
org.jboss.resource.connectionmanager.RARDeployment.startManagedConnectionFactory(RARDeployment.java:560)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at
org.jboss.resource.connectionmanager.BaseConnectionManager2.startService(BaseConnectionManager2.java:382)
at
org.jboss.resource.connectionmanager.XATxConnectionManager.startService(XATxConnectionManager.java:162)
at
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
at
sun.reflect.GeneratedMethodAccessor17.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1003)
at $Proxy4.start(Unknown Source)
at
org.jboss.system.ServiceController.start(ServiceController.java:413)
at
org.jboss.system.ServiceController.start(ServiceController.java:433)
at
org.jboss.system.ServiceController.start(ServiceController.java:433)
at
sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at
org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy9.start(Unknown Source)
at
org.jboss.resource.RARDeployer.start(RARDeployer.java:212)
at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:814)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
at
sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at
org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy3.deploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:435)
at
org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:656)
at
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:261)
at
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
at
sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1003)
at $Proxy0.start(Unknown Source)
at
org.jboss.system.ServiceController.start(ServiceController.java:413)
at
sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at
org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy2.start(Unknown Source)
at
org.jboss.deployment.SARDeployer.start(SARDeployer.java:229)
at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:814)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at
org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:325)
at
org.jboss.system.server.ServerImpl.start(ServerImpl.java:222)
at org.jboss.Main.boot(Main.java:148)
at org.jboss.Main$1.run(Main.java:381)
at java.lang.Thread.run(Thread.java:536)
----------------------------------------------------------------------
Comment By: Jakob Spies (jspies)
Date: 2003-03-15 12:14
Message:
Logged In: YES
user_id=121798
(1) This is clearly a bug since the DTD allows to omit the <config-property-value>
element.
(2) It is not fixed in the current JBoss 3.0.6, as can be seen in
RARDeployment.startManagedConnectionFactory:
value = MetaData.getElementContent(
MetaData.getUniqueChild(prop, "config-property-value"));
----------------------------------------------------------------------
Comment By: David Jencks (d_jencks)
Date: 2003-01-26 21:42
Message:
Logged In: YES
user_id=60525
fixed so config-property-value is not required and is ignored if present and empty.
This was not a problem in previous jboss versions only because I forgot to look at any
values from ra.xml!
fixed in 3.0/3.2, already not a problem in 4.
----------------------------------------------------------------------
Comment By: Marc Prud'hommeaux (mprudhom)
Date: 2003-01-26 17:42
Message:
Logged In: YES
user_id=33016
A preferable solution would be to allow no
<config-property-value> to be set at all, in which case
those MCF Properties would not be set. This is allowed in
the DTD (http://java.sun.com/dtd/connector_1_0.dtd), and
worked for JBoss 3.0.4. Furthermore, an ra.xml that leaves
these properties out will pass the J2EE verifier when
invoked on the .rar.
It is unclear if a blank <config-property-value> in the
ra.xml file will result in skipping the setter, or in
invoking the setter with a null argument, which is why we
would like to just leave the value tag out alltogether.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=667492&group_id=22866
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
