We have a web application which accesses 2 informix databases thru
Weblogic's JDBC driver. As one executes the application going from html
page to another , app open and closes connections. At each close ,
according to onstat -g sql a commit work is attempted which fails with
-255 ( no begin work - no transaction ). Simultaeousl or apaparantly
simultaneeus ly the java code seems to trigger a nullpointer exception.
The java code does not start any transaction processing ( no begin work ).
Does the JDBC driver? Is there any way to turn it off?
ciao
p
******************************************************************************
Peter Wages
pmwages@cais.com
Work: (703) 741-7436 Home: (703) 528-9569
******************************************************************************
↪ replying to Peter Wages
Peter,
JDBC's autocommit is turned on by default. You must explicitly turn it off
through the setAutoCommit method. For example:
con = DriverManager.getConnection(url, "red", "");
con.setAutoCommit(false);
Peter Wages wrote:
> We have a web application which accesses 2 informix databases thru
> Weblogic's JDBC driver. As one executes the application going from html
> page to another , app open and closes connections. At each close ,
> according to onstat -g sql a commit work is attempted which fails with
> -255 ( no begin work - no transaction ). Simultaeousl or apaparantly
> simultaneeus ly the java code seems to trigger a nullpointer exception.
>
> The java code does not start any transaction processing ( no begin work ).
> Does the JDBC driver? Is there any way to turn it off?
>
> ciao
> p
>
> ******************************************************************************
> Peter Wages
> pmwages@cais.com
> Work: (703) 741-7436 Home: (703) 528-9569
> ******************************************************************************