Oracle Service - broken by CVS HEAD?

[stevee]

I had an ejb app working with the JBoss3.* download. I'm trying to test clustering, and so have been told to get out CVS HEAD and try to run that (as clustering doesn't work with the standard download).

Now my app is broken, not just with the 'all' config, but with 'default' too.

I am using exactly the same oracle-service.xml and exactly the same ear. Whereas this worked before I now get this at startup:

11:27:45,225 INFO [MainDeployer] Starting deployment of package: file:/E:/serve
r/footy-default/deploy/oracle-service.xml
11:27:45,275 INFO [SARDeployer] looking for nested deployments in : file:/E:/se
rver/footy-default/deploy/oracle-service.xml
11:27:45,355 INFO [ServiceConfigurator] Problem configuring service jboss.jca:s
ervice=LocalTxDS,name=OracleDS
org.jboss.deployment.DeploymentException: No Attribute found with name: JndiName

at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.ja
va:347)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigura
tor.java:188)
at org.jboss.system.ServiceConfigurator.processDependency(ServiceConfigu
rator.java:452)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.ja
va:365)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigura
tor.java:188)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java
:131)
at org.jboss.system.ServiceController.install(ServiceController.java:225
)
at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
....


From oracle-service.xml


jdbc/oracleserverpool

....


I got my classes12.jar in the lib too



any thoughts?

[davidjencks]

Yes, ALWAYS start with a configuration file that comes with your new jboss version and check if it matches your old one.

You can still use *-service.xml files in 3.1, although you will have to move the jndi name attribute to the connection manager mbean, but I recommend you use the simplified *-ds.xml file format.

[stevee]

Thanks.

Is there any documentition on this? (There's none in the All Docs Dumscription from a couple of days ago.)

I tried editing the oracle-ds.xml, removing the oracle-service.xml and restarting. No exception on startup, but still couldn't get a DB excpetion. Probably my guesswork as to how to use the new config style is wrong.

steve

[stevee]

Should have said that I put the oracle-ds.xml in the deply dir