I had a similar problem until I worked out the datasource configuration on my WSAD server configuration. I ended up adding a JAAS authentication userid/password for the Oracle 9i datasource (This may or may not be required...). The key, however, for my problem was getting the URL in the datasource correct.
For my datasource:
1) I filled in the database name.
2) Provided a URL in the correct format:
jdbcracle:thin:@localhost:1521:OEMREP
...where OEMREP is the service name, not the database.
3) gave in a portNumber: 1521
4) left the enableMultithreadedDetection set to false.
The key for me was the Service Name in the URL...
I started out using a sample database included with the Oracle 9i distribution. The service was OEMREP and contained a HR database/schema.
Before I completed this information correctly I received the same message that you are getting.
Good luck...
[ April 07, 2003: Message edited by: Byron Estes ]
[ April 07, 2003: Message edited by: Byron Estes ]
[ April 07, 2003: Message edited by: Byron Estes ]
[ April 07, 2003: Message edited by: Byron Estes ]