10 Replies Latest reply on Mar 10, 2010 7:58 PM by Dean Hiller

    seam design flaw with db down or driver problem?

    Dean Hiller Expert

      In postgres, I can go straight to /web/error.xhtml when the db is offline.  In oracle, I cannot do this mainly because seam calls commit even though there is nothing to commit to the database but the commit results in a db call and the db is down so seam ends up in an infinite redirect loop which is extremely bad when you have IE users(firefox bumps people out of the loop and says it detected a redirect loop).

      Is this a seam design flaw or is oracle the ones that should fix this?

      on top of that issue, we had a work around driver for oracle when using simple driver but recently we started using an XA Datasource instead of the oracle jdbc driver....this datasource is even worse as seam(or maybe hibernate is the one) calls transaction begin which results in trying to get a connection even though we are just trying to go to a static page.  part of the stack trace here....

      Caused by: javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Cannot open connection
           at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:614)
           at org.hibernate.ejb.TransactionImpl.begin(TransactionImpl.java:41)
           at org.jboss.seam.transaction.EntityTransaction.begin(EntityTransaction.java:82)
           at org.jboss.seam.jsf.SeamPhaseListener.begin(SeamPhaseListener.java:593)
           ... 54 more

      At any rate, this is pretty bad as we can't seem to use seam with oracle at all as all static pages go dead(MOST notable the error.xhtml where we tell users to call support as they ran into a bug is not even displayed).

      thanks for any advice here,