[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=12507617#action_12507617 ] 

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

my two comments above are for the two attachments(I got confused on the upload attachment screen).

I forgot to mention, the DataSource api is quite crappy making it nearly impossible to create a proxy for all adapters.  In fact, I think bcel or something will have to be used so that one can extend the adapters because each datasource has different methods that must be called setHost vs. setServerName in another adapter...damn api...couldn't they just have a setProperties so a proxy would not need bcel or some library.  ie. jboss uses reflection to look up methods based on property names, so some byte code library would need to be used to solve this problem for everyone...this issue manifests itself in that SEAM by all accounts is broken when the database is down though so i filed this ticket against seam because seam doesn't work in this case....in fact, it makes our jboss servers go down in a db outage.

> 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