Bugs item #648631, was opened at 2002-12-04 21:25
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=648631&group_id=22866
Category: JBossCX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Patrick Murphy (murphyp1)
>Assigned to: David Jencks (d_jencks)
Summary: Wrapped JDBC driver deployment fails
Initial Comment:
When deploying a wrapped JDBC driver with a opta-xa-
service.xml file, the RARDeployment fails with
a "org.jboss.deployment.DeploymentException:
expected one config-property-value tag" exception. I am
using the "default" configuration and have placed the
Opta2000.jar file in the lib directory. I am attaching the
opta-xa-service.xml file that I have written. The JBoss
Release ID: JBoss [WonderLand] 3.2.0RC1 (build:
CVSTag=JBoss_3_2_0_beta2 date=200212021314)
running on Windows2000 with Java VM: Java HotSpot
(TM) Client VM 1.4.1_01-b01,Sun Microsystems Inc.
The exception trace is:
2002-12-04 15:43:09,000 INFO
[org.jboss.deployment.MainDeployer] Starting
deployment of package:
file:/C:/bin/jboss/server/default/deploy/opta-xa-
service.xml
2002-12-04 15:43:09,000 INFO
[org.jboss.deployment.SARDeployer] looking for nested
deployments in :
file:/C:/bin/jboss/server/default/deploy/opta-xa-
service.xml
2002-12-04 15:43:09,031 DEBUG
[org.jboss.resource.connectionmanager.RARDeployment
] setManagedConnectionFactoryProperties
2002-12-04 15:43:09,046 INFO
[org.jboss.resource.connectionmanager.RARDeployment
] Creating
2002-12-04 15:43:09,046 INFO
[org.jboss.resource.connectionmanager.RARDeployment
] Created
2002-12-04 15:43:09,046 INFO
[org.jboss.resource.connectionmanager.JBossManagedC
onnectionPool] Creating
2002-12-04 15:43:09,046 INFO
[org.jboss.resource.connectionmanager.JBossManagedC
onnectionPool] Created
2002-12-04 15:43:09,046 INFO
[org.jboss.resource.connectionmanager.XATxConnection
Manager] Creating
2002-12-04 15:43:09,046 INFO
[org.jboss.resource.connectionmanager.XATxConnection
Manager] Created
2002-12-04 15:43:09,062 INFO
[org.jboss.resource.connectionmanager.RARDeployment
] Starting
2002-12-04 15:43:09,062 DEBUG
[org.jboss.resource.connectionmanager.RARDeployment
] setManagedConnectionFactoryClass
org.jboss.resource.adapter.jdbc.xa.XAManagedConnecti
onFactory
2002-12-04 15:43:09,062 DEBUG
[org.jboss.resource.connectionmanager.RARDeployment
] setMcfProperties
oldRarDeployment.ResourceAdapterElement
2002-12-04 15:43:09,078 DEBUG
[org.jboss.resource.connectionmanager.RARDeployment
] config-property-name=UserName
2002-12-04 15:43:09,078 ERROR
[org.jboss.resource.connectionmanager.RARDeployment
] Starting failed
org.jboss.deployment.DeploymentException: expected
one config-property-value tag
at
org.jboss.metadata.MetaData.getUniqueChild
(MetaData.java:95)
at
org.jboss.resource.connectionmanager.RARDeployment.
setMcfProperties(RARDeployment.java:697)
at
org.jboss.resource.connectionmanager.RARDeployment.
startService(RARDeployment.java:549)
at
org.jboss.system.ServiceMBeanSupport.start
(ServiceMBeanSupport.java:197)
at
sun.reflect.GeneratedMethodAccessor34.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.invok
e(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:549)
at
org.jboss.system.ServiceController$ServiceProxy.invoke
(ServiceController.java:953)
at $Proxy9.start(Unknown Source)
at org.jboss.system.ServiceController.start
(ServiceController.java:388)
at
sun.reflect.GeneratedMethodAccessor10.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.invok
e(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:549)
at org.jboss.util.jmx.MBeanProxy.invoke
(MBeanProxy.java:174)
at $Proxy5.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start
(SARDeployer.java:307)
at org.jboss.deployment.MainDeployer.start
(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:630)
at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:594)
at
sun.reflect.GeneratedMethodAccessor27.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.invok
e(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:549)
at org.jboss.util.jmx.MBeanProxy.invoke
(MBeanProxy.java:174)
at $Proxy7.deploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.
deploy(URLDeploymentScanner.java:400)
at
org.jboss.deployment.scanner.URLDeploymentScanner.
scanDirectory(URLDeploymentScanner.java:619)
at
org.jboss.deployment.scanner.URLDeploymentScanner.
scan(URLDeploymentScanner.java:472)
at
org.jboss.deployment.scanner.AbstractDeploymentScan
ner$ScannerThread.doScan
(AbstractDeploymentScanner.java:195)
at
org.jboss.deployment.scanner.AbstractDeploymentScan
ner$ScannerThread.loop
(AbstractDeploymentScanner.java:206)
at
org.jboss.deployment.scanner.AbstractDeploymentScan
ner$ScannerThread.run
(AbstractDeploymentScanner.java:185)
2002-12-04 15:43:09,093 WARN
[org.jboss.system.ServiceController] Problem starting
service jboss.jca:service=XATxDS,name=D6509FTUDS
org.jboss.deployment.DeploymentException: expected
one config-property-value tag
at
org.jboss.metadata.MetaData.getUniqueChild
(MetaData.java:95)
at
org.jboss.resource.connectionmanager.RARDeployment.
setMcfProperties(RARDeployment.java:697)
at
org.jboss.resource.connectionmanager.RARDeployment.
startService(RARDeployment.java:549)
at
org.jboss.system.ServiceMBeanSupport.start
(ServiceMBeanSupport.java:197)
at
sun.reflect.GeneratedMethodAccessor34.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.invok
e(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:549)
at
org.jboss.system.ServiceController$ServiceProxy.invoke
(ServiceController.java:953)
at $Proxy9.start(Unknown Source)
at org.jboss.system.ServiceController.start
(ServiceController.java:388)
at
sun.reflect.GeneratedMethodAccessor10.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.invok
e(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:549)
at org.jboss.util.jmx.MBeanProxy.invoke
(MBeanProxy.java:174)
at $Proxy5.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start
(SARDeployer.java:307)
at org.jboss.deployment.MainDeployer.start
(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:630)
at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:594)
at
sun.reflect.GeneratedMethodAccessor27.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.invok
e(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:549)
at org.jboss.util.jmx.MBeanProxy.invoke
(MBeanProxy.java:174)
at $Proxy7.deploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.
deploy(URLDeploymentScanner.java:400)
at
org.jboss.deployment.scanner.URLDeploymentScanner.
scanDirectory(URLDeploymentScanner.java:619)
at
org.jboss.deployment.scanner.URLDeploymentScanner.
scan(URLDeploymentScanner.java:472)
at
org.jboss.deployment.scanner.AbstractDeploymentScan
ner$ScannerThread.doScan
(AbstractDeploymentScanner.java:195)
at
org.jboss.deployment.scanner.AbstractDeploymentScan
ner$ScannerThread.loop
(AbstractDeploymentScanner.java:206)
at
org.jboss.deployment.scanner.AbstractDeploymentScan
ner$ScannerThread.run
(AbstractDeploymentScanner.java:185)
2002-12-04 15:43:09,109 INFO
[org.jboss.resource.connectionmanager.JBossManagedC
onnectionPool] Starting
2002-12-04 15:43:09,109 INFO
[org.jboss.resource.connectionmanager.JBossManagedC
onnectionPool] Started
2002-12-04 15:43:09,109 INFO
[org.jboss.deployment.MainDeployer] Deployed
package: file:/C:/bin/jboss/server/default/deploy/opta-xa-
service.xml
2002-12-04 15:43:09,125 ERROR
[org.jboss.deployment.scanner.URLDeploymentScanner]
MBeanException: Exception in MBean
operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
<none>
Incompletely deployed packages:
<none>
MBeans waiting for classes:
<none>
MBeans waiting for other MBeans:
[ObjectName:
jboss.jca:service=XATxCM,name=D6509FTUDS
state: CREATED
I Depend On: jboss.jca:service=RARDeployer
jboss.jca:service=CachedConnectionManager
jboss.jca:service=XATxDS,name=D6509FTUDS
jboss.jca:service=XATxPool,name=D6509FTUDS
Depends On Me: , ObjectName:
jboss.jca:service=XATxDS,name=D6509FTUDS
state: FAILED
I Depend On:
jboss.jca:service=RARDeployment,name=JBoss JDBC
XATransaction ResourceAdapter
Depends On Me:
jboss.jca:service=XATxCM,name=D6509FTUDS
org.jboss.deployment.DeploymentException: expected
one config-property-value tag]
You will notice some extra DEBUG logging that I added
to try an dfigure out what was going on. It appears that
the RARDeployment is trying to read the MCF
properties from the ra.xml file in the jboss-xa.rar file.
This xml file does not contain "config-property-value"
fields and is causing the exception.
I am not sure if I am wrapping the driver properly or if it is
an actual bug with trying to read properties from the
wrong place. Since my service sml file mimics the other
examples I have looked at I am inclined to think I have
hit on a bug.
Patrick Murphy
----------------------------------------------------------------------
>Comment By: David Jencks (d_jencks)
Date: 2002-12-16 05:11
Message:
Logged In: YES
user_id=60525
Maybe we need namespaces. There's a partial xml dtd for the
*-ds files, but since you can include normal mbean config as
well I don't think it is complete.
The dtd does specify xa-datasource.
----------------------------------------------------------------------
Comment By: Igor Fedorenko (igorfie)
Date: 2002-12-13 21:48
Message:
Logged In: YES
user_id=232950
I think it is more important to throw explicit exception saying
that element "xa-tx-datasource" is not allowed.
----------------------------------------------------------------------
Comment By: Patrick Murphy (murphyp1)
Date: 2002-12-13 20:32
Message:
Logged In: YES
user_id=63278
I have gotten through the code and found that the *-ds.xml
was not deploying properly due to a change in the XML tags.
The examples I was looking at (mssql-xa-ds.xml, generic-
ds.xml) was using a tag of <xa-tx-datasource> and the XSL
transformation is looking for <xa-datasource>. This condition
does not show any error messages, just messages about the
mbean/xml being monitored without the expected datasource
getting deployed. When I changed the XML tag, it all started
working.
I did notice that the local transaction uses the <local-tx-
datasource> tag. Shouldn't the tag naming be kept
consistent?
----------------------------------------------------------------------
Comment By: Igor Fedorenko (igorfie)
Date: 2002-12-05 21:49
Message:
Logged In: YES
user_id=232950
Hmm, very strange. For hard-core debugging you could try
setting logging priority to TRACE in conf/log4j.xml.
----------------------------------------------------------------------
Comment By: Patrick Murphy (murphyp1)
Date: 2002-12-05 20:31
Message:
Logged In: YES
user_id=63278
I updated the latest code and rebuilt the 3.2 server this
morning, but I am still not seeing the JNDI name being
registered when using the *-ds.xml syntax. The log snippet
from the deployment follows:
15:22:35,898 INFO [Server] JBoss (MX MicroKernel)
[3.2.0RC1 (build: CVSTag=JBoss_3_2_0_beta2
date=200212051055)] Started in 23s:109ms
15:24:51,039 INFO [MainDeployer] Starting deployment of
package: file:/C:/bin/jboss/server/default/deploy/d6509-xa-
ds.xml
15:24:51,070 INFO [XSLSubDeployer] transformed into doc:
[#document: null]
15:24:51,070 INFO [SARDeployer] looking for nested
deployments in : file:/C:/bin/jboss/server/default/deploy/d6509-
xa-ds.xml
15:24:51,085 INFO [MainDeployer] Deployed package:
file:/C:/bin/jboss/server/default/deploy/d6509-xa-ds.xml
Also, when I deploy as a service the connection is failing but I
am not getting any detail on why (other than the connection
failed exception). Is there a "debug" option that can be
turned on to see what is going on?
----------------------------------------------------------------------
Comment By: Igor Fedorenko (igorfie)
Date: 2002-12-05 15:10
Message:
Logged In: YES
user_id=232950
I should have mentioned that you need to get latest code from
cvs to get *-ds.xml working. Also use oracle-xa-ds.xml as an
inspiration.
I agree that examples need to be updated. I also think that
each db must have at least one (two is better) maintainer who
makes sure that all examples are up-to-date and actually
work.
----------------------------------------------------------------------
Comment By: Patrick Murphy (murphyp1)
Date: 2002-12-05 14:36
Message:
Logged In: YES
user_id=63278
The change you suggested did let the data source deploy. I
was following the examples that come with the build which
show the "OldRarDeployment" method. I have downloaded
and tried the MSSQL JDBC driver with the example and it
failed in exactly the same way. The change you suggested
also let that deployment work. I guess the examples need to
be updated.
I also tried the suggested *-ds.xml method. While the log
says that it deployed, I can not see the JNDI name in the jmx-
console JNDI namespace list. It does not appear to be
deploying correctly. I deployed for both my Opta driver and
used the example for MSSQL with the same results.
----------------------------------------------------------------------
Comment By: Igor Fedorenko (igorfie)
Date: 2002-12-04 21:55
Message:
Logged In: YES
user_id=232950
Try to replace
<depends optional-attribute-
name="OldRarDeployment">jboss.jca:service=RARDeployme
nt,name=JBoss JDBC XATransaction
ResourceAdapter</depends>
with
<attribute
name="ManagedConnectionFactoryClass">org.jboss.resource
.adapter.jdbc.xa.XAManagedConnectionFactory</attribute>
It is also a good idea to try simplified *-ds.xml format.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=648631&group_id=22866
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
