JNDI connection message

[johncena]

I've tried installing the JBOSS AS 4.0.4 GA, and it worked fine. I can view it to the 8080 port.... On my second part of my project... I've tried modifying the ds xmls to my db and I get this message from the console showing 3 JNDI connections. Is this the proper way to use Oracle as my datasource? The reason for this is that, I'll be using Jboss Portal and I've added portal-oracle-ds.xml in the deploy dir (as per instruction from J-portal), and apparently I've changed both xml (oracle-xa-ds and portal-oracle-xa) to my Oracle 10g configurations. Pls bear with me, I'm new to this App Server and hopefully you can give me tips on this.

Will these messages and configurations make some memory allocations to the portal executions? or any delay or conflict?

...
14:39:18,476 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
14:39:19,505 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=XAOracleDS' to JNDI name 'java:XAOracleDS'
14:39:19,674 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=PortalDS' to JNDI name 'java:PortalDS'

[jaikiran]

These messages mean that the respective datasources have been bound, to the JNDI tree, by the name specified in the logs. This means that later on whenever you do a lookup of the datasource, you will find it in the JNDI tree.