First, please use a current jboss version. I recommend 3.2.1, the jca configuration is MUCH simpler than in 3.0.x
How does the KODO adapter know which datasource to use?
You should definitely use only one copy of the kodo .rar, with their ra.xml in it.
The connection factory deployments can be in one or 2 files, it makes no difference.
With 3.2.x, simply specifying different jndi names for the connection factories should work fine. For 3.0.x, you have to specify unique mbean names for all 3 mbeans for each connection factory.
To progress further with this I really need to know how kodo learns which db to connect to.
When you have something working, please contribute an example configuration.
It turns out that there is a bug in KODO's ManagedConnectionFactoryImpl.createConnectionFactory(ConnectionManager cm) method. So, it is returning a reference to a single instance of connectionFactory. I suspect that their code makes certain assumptions about the classloader in use (whatever that JBoss's UnifiedClassloader is doing, KODO folks did not account for, because KODO's RA works fine with Weblogic 7.0.1). KODO folks assured us that it will be fixed in their 2.5RC2 release.
BTW, KODO RA knows which ds to connect to via their config parameters. So, each RA was configured with different ds. And, yes, I did configure all six MBeans with unique instance names.
As for upgrading to 3.2.x, we will eventually do so, however, right now is not a good time for us. And, yes, I will post the example config file as soon as I can confirm that KODO 2.5RC2 functions correctly.
Thanks a bunch for your help.