Dependacy loading of JMX object.
scottski Dec 14, 2004 2:09 PMHi all, just a new JMX noob, and I've run into a problem which I hope someone else can help me with.
I have a JMX MBean that does some JDBC call in it on a periodic basis. When the MBean objects starts, a timer occurs wich periodically polls the database.
Now during the normal JBoss startup I set some attributes in my jboss-service.xml file for the containg .sar object, which delays the startup of my MBean
But I cannot find out which bean to set in my jboss-service.xml file so that when JBoss starts my MBean, JBoss 'delays' my MBean loading so that the nessesary JDBC resouces are set up. The one giving me a problem is an oracle-ds.xml datasource.
If anyone can help me with this I would appriciate it. Here is some console output.
The TrackingBoard-SAR is my distribute package.
The TrackingBoardDB is the JNDI name for my oracle datasource defined in the oracle-ds.xml
15:54:22,235 INFO [MainDeployer] Deployed package: file:/C:/devtools/jboss-3.2.3/server/default/deploy/TrackingBoard-SAR.sar
15:54:22,245 INFO [MainDeployer] Starting deployment of package: file:/C:/devtools/jboss-3.2.3/server/default/deploy/uuid-key-generator.sar
15:54:22,245 ERROR [STDERR] javax.naming.NameNotFoundException: TrackingBoardDB not bound
15:54:22,255 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:495)
15:54:22,255 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:503)
15:54:22,255 ERROR [STDERR] at org.jnp.server.NamingServer.getObject(NamingServer.java:509)
15:54:22,255 ERROR [STDERR] at org.jnp.server.NamingServer.lookup(NamingServer.java:282)
15:54:22,255 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:528)
15:54:22,255 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507)
15:54:22,255 ERROR [STDERR] at javax.naming.InitialContext.lookup(Unknown Source)
Here is my current jboss-service.xml file
<?xml version="1.0" encoding="UTF-8"?>
jboss.mq:service=DestinationManager
jboss:service=TransactionManager
jboss:service=Naming
jboss:service=JNDIView
name="DatabaseService">TrackingBoardDB
Now I have noticed that for JMX the optional name attribute tage would cause problems ...any comment on that I would like to hear about that as well.
Thanks for any help.
Scottski