This content has been marked as final. Show 5 replies
That's an odd one. I would debug that by editing my own version of
java.util.Hashtable to reveal how that could happen, and putting that
class into the bootclasspath for the WLS JVM. It seems to hint at
non-threadsafe access to the Hashtable, so I would be sure to identify
which thread(s) are operating on the object at any time...
Does this reproduce every time? Open an official support case
about WebLogic/JDBC with this info. We can make a debug patch.
I can't get it to restart properly due to this error, so I would say that it's able to be reproduced. However this is only a sandbox environment, we are see what it will take for us to get from 10g to 11g. I didn't think that we could open support cases for sandbox environments
If you're a customer, why not? If not, it can't hurt to ask...
This error happens to me after i installed WebLogic and tried to deploy an application.
I added then a dataSource and connection pool using the WebLogic console.
After that i restared my machine, because it become so slow.
After that i was not able to restart WebLogic, i got the error:
Caused By: java.lang.ClassNotFoundException: oracle.jbo.server.DatabaseTransactionFactory
I modified the file config.xml, by commenting the entry <!-- jdbc-data-source-factory...
I renamed the name of the file JDBC_Data_Source-0-3407-jdbc.xml (may be the 3407 is a specific number for my installation)
After that i restarted the WebLogic, i now i can acces it by its console.