Devan Lipsey

Greenhorn
+ Follow
since Jun 26, 2002
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Devan Lipsey

Sorry that didn't help... There is a security cache timeout setting that can be changed from the security console. You could set this to a low number to see if the server is truly returning to LDAP to get the latest information for caching. This mechanism seems to have trouble on the version we are running (4.03 on AIX), but you could try it...
19 years ago
It looks like you are using the wrong implementation class (oracle.jdbc.driver.OracleDriver). WebSphere's connection pool manager is expecting a DataSource class not a Driver class. I'm not working with Oracle right now so I can't give you specifics, but search around in the jar that contains your OracleDriver class and you should find a class that implements the DataSource interface. It will probably have a name like OracleDataSource...I hope this helps...
19 years ago
Bill,
We do have e-fixes applied over 4.03. They are:
PQ59543, PQ60281 and PQ62684
I hope this helps...
19 years ago
We are also running on AIX & 4.03 and get the same messages. We are going to look further into it next week and I'll post a reply if we figure it out.
19 years ago
This isn't really an answer to your problem, but I just wanted to note that what you are seeing is not an error message - it is a warning. We work in a similar environment -> WS 3.5.3 using JSQLConnect against a MSSQL 2000 DB and we occasionally see the same message in our logs, but it does not mean that a connection isn't made to the database. I think it's just the app server saying that the driver isn't one of the standard drivers it is familiar with... One other thing - you don't see these messages running on WS4.0.
19 years ago