In an attempt to do something. I downloaded jboss3.2. The *-ds.xml files sure seem easier to work with :)
Even with this more simplified configuration, I get the same message. Here it is:
22:11:51,596 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
Incompletely deployed packages:
MBeans waiting for classes:
MBeans waiting for other MBeans:
I Depend On: jboss.jca:service=ManagedConnectionPool,name=FirebirdDS
Depends On Me: , ObjectName: jboss.jca:service=ManagedConnectionPool,name=FirebirdDS
I Depend On: jboss.jca:service=ManagedConnectionFactory,name=FirebirdDS
Depends On Me: jboss.jca:service=TxCM,name=FirebirdDS
, ObjectName: jboss.jca:service=ManagedConnectionFactory,name=FirebirdDS
I Depend On: jboss.jca:service=RARDeployment,name=Firebird Database Connector
Depends On Me: jboss.jca:service=ManagedConnectionPool,name=FirebirdDS
Are you sure the firebirdsql.rar file is properly deployed without errors? Make sure it is deployed before the firebird-ds.xml file.
I had this problem too. If you are using the newer firebird-ds.xml (the one that uses tx-connection-factory instead of xa-datasource in the xml) then your connectin manager will have an objectname of
which is why your dependency isn't working.
The references in his log excerpt are all to the new TxCM name. The only missing non-default mbean/object name is the one for the deployed resource adapter, which is why I asked if it was deployed correctly.