903/902/BC4J can't get OC4J data-sources.xml conn pooling to work in production: help

Question

[cross posted to the j2ee forum]
I have several BC4J ears deployed to a 903 instance of OC4J being configured as a standalone
instance. I've had this problem since I started deploying in development on 902. So it's
some basic problem that I've not mastered.
I can't get data-sources.xml managed connection pooling to actually pool conn's. I'm wanting
to declare my jndi jdbc source connection pool in j2ee/home/config/data-sources.xml and
have all BC4J apps get conns from this JNDI JDBC pool. I've removed all data-sources.xml from
my BC4J ears, and published the jndi jdbc source in my oc4j common data-sources.xml.
I've tested that this is the place controlling the conn URL/login passwd by commenting it
out of config/data-sources.xml and my BC4J apps then throw exceptions, can't get conn.
I've set the oc4j startup cmd line with the BC4J property to enabled connection pooling:
-Djbo.doconnectionpooling=true
symptom
Connections are created and closed. Instead of being put back into the pool managed by oc4j,
what ever BC4J is doing or my data-sources.xml is doing, the connections are just being created and
closed.
I can verify this via (solaris) lsof and netstat, where I see my oc4j instance under test load
with only 1 or 2 conns to the db box, and the ephemeral port is tumbling, meaning a new socket is
being opened for each conn. ;( grrrrrrr
Does anyone have a clue as to why this is happening?
Thanks, curt
my data-sources.xml
<data-sources>
     <data-source
        class="com.evermind.sql.DriverManagerDataSource"
        connection-driver="oracle.jdbc.driver.OracleDriver"
        ejb-location="jdbc/DEVDS"
        location="jdbc/DEVCoreDS"
        name="DEVDS"
        password="j2train"
        pooled-location="jdbc/DEVPooledDS"
        url="jdbc:oracle:thin:@10.2.1.30:1521:GDOC"
        username="jscribe"
        xa-location="jdbc/xa/DEVXADS"
        inactivity-timeout="300"
        max-connections="50"
        min-connections="40"
    />
</data-sources>

Answer 1

Thanks Leif,
Yes, set it to the location jndi path.
A piece of info is that the 903 oc4j release notes states that global conn pooling doesn't
work. Infering that the j2ee/home/config/data-sources.xml data sources aren't pooled or ??
I just tested so called local connection pooling, where I edited the data-sources.xml that
gets packaged in the ear, to include the min/max params and re-ran my test.
Still, the AM creates a new conn, it's to a new socket, and closes the conn when done. Causing
each conn to not be pooled, rather opened then closed to the DB box. As verified with lsof and
netstat, checking the ephemeral port # on the DB box side, always changes, meaning it's a
new socket and not an old pooled conn socket.
???? What the heck??
Surely if the AM conn check out / return code works properly, OC4J's pooling JDBC driver would
pool and not close the socket??
Has anywone gotten JDBC Datasource connections in BC4J to actually be pooled under OC4J??
Since I couldn't get this to work in my early 902 oc4j testing, and now can't get it to work
still under 903 OC4J, either it's my config or BC4J AM's code or OC4J?
Any thoughts on how to figure out what's not configed correctly or has a bug?
Thanks, curt