NullPointerException from oracle when flushing the session

ahmallah · **Joined:** Wed Mar 03, 2004 2:57 pm **Posts:** 4

Hi,

I just recently started using hibernate for my O/R mapping, after using Toplink for sometime.

I have some issues and questions hopefully can be cleared out.

Facts/environment:
1- We've created a simple thin layer around hibernate for the developer to interface with instead of going directly to hibernate APIs.
2- We are using Websphere studio 5.1.1 (WAS 5.1.0 and JRE 1.4.1)
3- hibernate 2.1
4- JTATransactionFactory, WebSphereTransactionManagerLookup,
DatasourceConnectionProvider, OracleDialect, TreeCacheProvider (JBoss)
5- Session fa

michael · **Posted:** Wed Mar 03, 2004 4:50 pm

Looks like your oracle driver has a problem with the way the websphere datasource does prepared statement caching. Try disabling this if possible.

spinodal · **Posted:** Wed Dec 22, 2004 4:47 am

Hi,
Our environment is same. And we are having prblems about WebspheretransactionManagerLookup class too.

You said:

Quote:

I realized now that other people fixed it in this forum. so skip this one.

Can you point the posts you have read about the soplution, cause I coludn't find any.

And since it was along afo you post this message, have you solved all of your problems and how.

If you have some time pls give a summary....

Thanks....

ahmallah · **Joined:** Wed Mar 03, 2004 2:57 pm **Posts:** 4

Basically, set the "Statement cache size" to "0" in the Datasource configuration (Default value is 10). and it will work fine.

Hadi

nminshew · **Joined:** Tue Oct 12, 2004 4:27 pm **Posts:** 2

I would not set the statement cache to "0", that will cause a fairly substantial performance hit. I was able to resolve this issue by updating the oracle driver from classes12 to ojdbc14 from the oracle site. I understand that you have already retrieved the new driver, but make sure you point your server to the new driver, otherwise you will continue to have this problem. I downloaded the driver and put it in the classpath, but forgot to update the Native Path in the server configurator. After changing the native path it works fine.

cunparis · **Posted:** Wed Jun 07, 2006 4:13 am

nminshew wrote:

I would not set the statement cache to "0", that will cause a fairly substantial performance hit. I was able to resolve this issue by updating the oracle driver from classes12 to ojdbc14 from the oracle site. I understand that you have already retrieved the new driver, but make sure you point your server to the new driver, otherwise you will continue to have this problem. I downloaded the driver and put it in the classpath, but forgot to update the Native Path in the server configurator. After changing the native path it works fine.

I'm having this problem too, setting the statement cache to 0 fixes it but I understand about the performance concern. We're using ojdbc14.jar in websphere.

What do you mean about the "Native Path in the server configurator"?

-Michael

cunparis · **Posted:** Wed Jun 07, 2006 9:00 am

Quote:

I'm having this problem too, setting the statement cache to 0 fixes it but I understand about the performance concern. We're using ojdbc14.jar in websphere.

What do you mean about the "Native Path in the server configurator"?

-Michael

9.2.0.5 fix it. had to put it both on the WAS server and in our WAR.

Thanks!
-Michael