此内容已被标记为最终。 显示 1 回复
Do you have multiple jndi names for the datasource?
I have seen this issue in this case:
On the console, in JNDI box, if you enter extra empty lines, wls does not trim the empty lines, and leave as many emtpy <jndi></jndi> entries in the jdbc config files.
Could you check the jdbc.xml under the domain_home/config/jdbc directory and remove the empty jndi entries manually?
If this doesn't help, can you check the logs to see if there are any jndi lookup problems?
Also when testing, create datasouce, deploy it on one server first
and then change the target to cluster,there may be some nested exception, this looks generic
Also you could post this under WLS -JDBC newsgroup at