[JBoss JIRA] Created: (JBSEAM-4528) static pages don't work at all with database down and XA datasource used
by deanhiller (JIRA)
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
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
12 years, 5 months
[JBoss JIRA] Created: (SEAMREMOTING-4) Optimize Seam Remoting XML Marshalling
by Joshua Davis (JIRA)
Optimize Seam Remoting XML Marshalling
--------------------------------------
Key: SEAMREMOTING-4
URL: https://jira.jboss.org/browse/SEAMREMOTING-4
Project: Seam Remoting
Issue Type: Feature Request
Reporter: Joshua Davis
The XML marshalling used by Seam Remoting can be optimized significantly by making a few, relatively simple, changes.
1. Making some element names shorter, specifically 'member'.
2. Resolving object fields by position instead of by name. This eliminates the need for the 'name' attribute of the 'member' element.
3. Handling nulls pointers in structures in a simpler way: Use an empty 'member' element.
4. Removing some of the wrapper elements around primitive types.
In our examples we've seen that the optimized XML is less than 40% of the size of the original XML.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] Created: (SEAMFACES-28) ObjectConverter and EntityConverter
by Pete Muir (JIRA)
ObjectConverter and EntityConverter
-----------------------------------
Key: SEAMFACES-28
URL: https://jira.jboss.org/browse/SEAMFACES-28
Project: Seam Faces
Issue Type: Feature Request
Components: Transactions & Persistence, Validation & Conversion
Reporter: Pete Muir
Priority: Critical
Given
class Foo {
Bar bar;
// Getters and setters
List<Bar> bars;
// Getters and setters
}
<h:selectOneMenu value="#{foo.bar}" >
<f:selectItems value="#{foo.bars}" var="bar" itemLabel="#{bar.label}" itemValue="#{bar}" />
<s:convertEntity /> || <s:convertObject />
</h:selectOneMenu>
I want to be able to have my setter/getter reference an object and not write the boilerplate for converting to/from a string.
I also want to reference a managed entity, and have that managed entity set back into the setter so I can see the changes updated in the database with no boilerplate, and avoid LIEs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months