Difference between
version 31
and
version 30:
At line 5 changed 1 line. |
[I|D33nar] am having trouble running Appfuse 0.9 as well as struts resume. After successfully compiling and building Appfuse, I can start the application on tomcat and get it running, logon with tomcat/tomcat. The problem arises whenever I try modifying data, the JDBC connection performing the update never finishes and all subsequent JDBC connections are blocked by the update connection. I tried using Microsoft and weblogic drivers for JDBC, but face the same problem.. I have spent significant time and am continuing to debug the problem, but would like to hear from anyone out there who has got Appfuse or struts-resume running on SQLServer. |
I (D33nar) am having trouble running Appfuse 0.9 as well as struts resume. After successfully compiling and building Appfuse, I can start the application on tomcat and get it running, logon with tomcat/tomcat. The problem arises whenever I try modifying data, the JDBC connection performing the update never finishes and all subsequent JDBC connections are blocked by the update connection. I tried using Microsoft and weblogic drivers for JDBC, but face the same problem.. I have spent significant time and am continuing to debug the problem, but would like to hear from anyone out there who has got Appfuse or struts-resume running on SQLServer. |
At line 7 added 2 lines. |
__UPDATE__: I have traced the problem to JDBC auto-commit. I put a trace on the SQL sent to the server. A transaction is begun, but never committed, sometimes the driver/pool rolls it back with something like |
{{{IF @@TRANCOUNT>0 ROLLBACK TRAN BEGIN TRAN}}} |
At line 10 added 8 lines. |
I am not sure if it is |
* the driver implementation (unlikely as I tried 3 different ones bea, ms and inet) |
* something do the connection pool used |
* transaction semantics in the hibernate |
* or the appfuse code |
|
I also found that everthing works fine with __auto-commit=true__, which is not a solution |
|
Back to AppFuse,
or to the Page History.
|