[seam-issues] [JBoss JIRA] Commented: (JBSEAM-4528) static pages don't work at all with database down and XA datasource used

[deanhiller (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBSEAM-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12518454#action_12518454 ] 

deanhiller commented on JBSEAM-4528:
------------------------------------

OHHHHH, hold up there.  Jboss 5.1 / postgres will HALF work if you turn the <check-valid-connection-sql> on BUT then it breaks recovery and jboss can never recover from database outage :( so you can solve jboss postgres static pages keep working on database being down, but then when db comes back online jboss is hosed up for good :(.

So This ticket MUST MUST test this FULL scenario...
1. jboss / database is up
2. bring database down(kill -9 does the trick)
3. go to a page with forms(NOT login page, it behaves weird) (you shold be able to get to this page if half the bug is fixed)
4. now submit the form
RESULT: no infinite redirect and goes to error.xthml properly (FAIL with oracle or postgres and check valid connection set)
5. now bring the database back up
6. now go back to the form and submit it
RESULT: fails if check-valid-connection is not set up

ps. I would rather check valid connection happen AFTER some call to jdbc fails to check if we ran it on a bad connection so on the sunny day scenario we are not constantly running this jdbc call which is to a remote system.  Slwo down the cloudy day(ie. bug or db down) in that make sure the connection is valid after a failure on setAutoCommit or exectue or whatever can call the database.  I guess that is more a jboss issue though, but if you know someone at jboss ;).

thanks,
Dean






> static pages don't work at all with database down and XA datasource used
> ------------------------------------------------------------------------
>
>                 Key: JBSEAM-4528
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4528
>             Project: Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.2.0.GA
>         Environment: postgres or oracle with postgres or oracle XADatasource.  postgres jdbc driver is fine while oracle driver is not
>            Reporter: deanhiller
>            Priority: Critical
>         Attachments: oracleBAD.log, postgres.log
>
>
> If this is a hibernate bug, please report hibernate issue and ticket here as other seam users will run into this problem and it looks like a seam framework problem(or at least could be solved in seam but it may be possible to solve in hibernate too and could be solved in each and every driver datasource as well).
> Steps to reproduce
> 1. start up the jboss 5.1.0 with latest seam
> 2. pull your internet connection so the db is gone
> 3. have all your customers go to a static page like /web/error.xhtml
> RESULT: jboss goes to it's knees as users in IE end up in infinite redirects to your server causing more and more load on the server.  The drivers talk to the database when they should not be.  I have a work around proxy driver for oracle's jdbc driver.  I do not however have a fix for oracle's datasource or postgres datasource.
> I imagine someone could write a proxy datasource that would solve this problem for all people, hibernate, seam and all xa drivers.  I will attach logs of postgres xa driver and oracle one but basically they are trying to open a connection to database when ANY http request comes in until waiting to see if we actually do any select statements or updates or inserts.  For some reason, the postgres driver and oracle driver where fine here...they did not make db requests when an http request came in.  The oracle driver however did make a request to the db when commit is called even if no sql was done against the db where postgres driver ignored the commit since no sql was done.  I will try to attach files or more comments here.  PLEASE if you report a tic in hibernate put it in here for others to find when they hit this issue.
> keyphrases:
> seam doesn't work when database goes down
> seam infinite redirect on db outage
> database failure causes seam to not work

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira