Raible's Wiki

Raible Designs
Wiki Home
News
Recent Changes

AppFuse

Homepage
  - Korean
  - Chinese
  - Italian
  - Japanese

QuickStart Guide
  - Chinese
  - French
  - German
  - Italian
  - Korean
  - Portuguese
  - Spanish
  - Japanese

User Guide
  - Korean
  - Chinese

Tutorials
  - Chinese
  - German
  - Italian
  - Korean
  - Portuguese
  - Spanish

FAQ
  - Korean

Latest Downloads

Other Applications

Struts Resume
Security Example
Struts Menu

Set your name in
UserPreferences


Referenced by
AppFuseAntTasks
AppFuseAnthill
AppFuseAuthenticatio...
AppFuseCruiseControl
AppFuseDebug
AppFuseEclipse
AppFuseEclipse_es
AppFuseEclipse_pt
AppFuseOnDB2
AppFuseOnPostgreSQL
...and 56 more




JSPWiki v2.2.33

[RSS]


Hide Menu

AppFuse


Difference between version 33 and version 32:

At line 3 removed 28 lines.
!!__2003.11.21__ - Microsoft SQLServer 2000 & AutoCommit
I had problems with MSSQL and automatic transactions, the solution I have found:
\\__Use manual transaction!__
\\__Set auto-commit=false__ and control yourself the commit and rollback, closing all resources that you've used, including the Connection, preventing dead-lock in database and saving pooled connections. If you'll execute a single query, do the same, manual transaction.
!!__2003.11.19__ - AppFuse 0.9 with Microsoft SQLServer 2000
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.
__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}}}
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
!!__2003.10.26__ - Building AppFuse 0.9.9 with Mckoi
[I|Binkley] am having trouble building Appfuse 0.9.9 pulled off of SourceForge. Specifically, I am running against Mckoi 1.0.2 and setup-db fails complaining that there is no user_roles table. I'm willing to debug the problem, but first I'd like to check if there is some well-known fix.
__UPDATE__: First problem fixed — {{database.properties}} has an outdated name for the Mckoi dialect driver for hibernate. I read: {{{hibernate.dialect cirrus.hibernate.sql.MckoiDialect}}} It should read: {{{hibernate.dialect net.sf.hibernate.dialect.MckoiDialect}}} Now I'm working on a problem with the Mckoi JDBC driver not being found although both Mckoi jars are in the CLASSPATH.

Back to AppFuse, or to the Page History.