[JBoss JIRA] Created: (SECURITY-573) Improve handling of IOException thrown from NegotiationAuthenticator
by Marek Posolda (JIRA)
Improve handling of IOException thrown from NegotiationAuthenticator
--------------------------------------------------------------------
Key: SECURITY-573
URL: https://issues.jboss.org/browse/SECURITY-573
Project: PicketBox (JBoss Security and Identity Management)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Negotiation
Affects Versions: Negotiation_2.0.3.GA
Environment: JBoss EPP 5.1.GA with SPNEGO support, JBoss Negotiation 2.0.3, commons-http-client 3.1 used as HTTP client
Reporter: Marek Posolda
Assignee: Darran Lofthouse
Fix For: Negotiation_2.0.4
Currently if IOException is thrown from NegotiationAuthenticator (For example from line 123 from statement: NegotiationMessage requestMessage = mf.createMessage(authTokenIS); )
then this exception is never logged but it's catched and ignored in CoyoteAdapter.service. Result is that client receives response code 200 OK and emtpy HTTP response. And there is nothing in server log, which can be used to recognize error. So I need to debug if I want to find the real cause of IO issue.
Example for simulating of this issue can be using of Kerberos OID instead of SPNEGO OID as described in Jira SECURITY-572
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JBWEB-236) JSF Mojarra has serious performance issues, add MyFaces integration
by Adrian Everett (JIRA)
Adrian Everett created JBWEB-236:
------------------------------------
Summary: JSF Mojarra has serious performance issues, add MyFaces integration
Key: JBWEB-236
URL: https://issues.jboss.org/browse/JBWEB-236
Project: JBoss Web
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Core
Affects Versions: JBossWeb-7.0.13.GA
Environment: JBoss 7.1.1 AS, Windows 7 64 bit
Reporter: Adrian Everett
Assignee: Remy Maucherat
Please add MyFaces support to JBoss AS7 as an alternative to JSF Mojarra, because Mojarra has serious performance issues.
For large data sets, a really bad JSF performance issue regarding AJAX requests has been identified. An issue ticket was created for this on the Mojarra issues tracker, but it might be quite a long time before they fix it, if it ever does get fixed.
Here is the link:
http://java.net/jira/browse/JAVASERVERFACES-2334
For every large data sets, the performance of a simple f:ajax calls slows down to the point it becomes as slow as a full page post. An f:ajax call passing 300 bytes of data could take 3+ seconds to perform a round trip, where the same exact f:ajax call might only take a 200ms if the page is smaller. The only difference between the big page and the small page might be several thousand h:outputText components that have no relation with the component associated with the f:ajax call.
This is a serious problem for a site such as the one I'm working on, where we sometimes have to load large amounts of data in an un-paginated manner, and also perform AJAX requests on the same page.
I took the example code attached to the Mojarra ticket and will be attaching it to this one. I have verified that it causes the problem by running the code on JBoss AS, the latest Glassfish server and even Tomcat. The problem isn't with JBoss, it's with the Mojarra implementation of JSF, so support for MyFaces would greatly benefit projects with large data sets.
Finally, as seen in the Mojarra ticket, the author of the PrimeFaces component library has also performed some tests with the attached code and found that the MyFaces JSF stack doesn't have the problem. His comments can be seen in the reference ticket.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months