JBoss 3.2.3 / Oracle 8.1.7.4 / JDBC/ blank username and pass

[danhobbs75]

Hello there.

Relative newbie to JBoss desperately seeking advice...!

We have a client with a Windows NT 4 client running JBoss 3.2.3 (JDK 1.3.1)

The target DB is Oracle 8.1.7.4 running on Linux.

I have an EJB which uses JDBC to connect to the database. The EJB works with no problems (on my PC here) connecting to MSSQL2000 (with config in mssql-ds.xml).

On the client's JBoss deployment, I have put in an oracle-ds.xml with the relevant connection-url, user-name and password set.

The EJB initiates a JDBC connection but the Oracle server returns an invalid username/password error, because the username and password are coming through blank (I am told this by their Oracle admin).

I have used classes12.zip (also tried renaming to .jar) which is in the server/default/deploy/lib folder. I also tried using ojdbc14.jar with JDK 1.4.2 and I received the same error.

Any advice or pointers greatly appreciated.

Regards,

Dan

P.S. I am at liberty to use a different version of JBoss, but I am told there are compatibility issues with Oracle JDBC drivers and Oracle 8i - which I can't ask them to change! :-)

P.P.S. I have a very nerve-wracking trip to the Netherlands tomorrow to do this so if anyone has any ideas for me to pursue please don't hold back! :-)

[ricardoarguello]

You need to copy the JDBC driver to server/default/lib.

Use the ojdbc14.jar instead of the classes12.zip one.

Ricardo

[danhobbs75]

Thanks for your suggestions, Ricardo.

I did mean server/default/lib rather than server/default/deploy/lib (sorry about that.)

Also, I have tried the ojdbc14.jar driver (with both JBoss 3.2.3 and JBoss 4.0.0) and had the same result.

Dan

[ricardoarguello]

Try to raise the logging level for "org.jboss.resource" and "org.jboss.ejb.plugins.cmp" to TRACE. Then check the server/default/log/server.log file for some clues.

Read the server/default/conf/log4j.xml file for examples.

Also http://www.jboss.org/wiki/Wiki.jsp?page=Logging

[danhobbs75]

Just to close this, I found out when I visited the client that the Oracle people had misled me - the username and password were not blank at all; they were wrong! There are two places where logon can be configured and the user had not checked one of them, which was overriding the JNDI settings.

D'oh! :-)

Regards,

Dan