[JBossWS] - jboss 4.2.3 is 200% slower than jboss 4.2.2
by peiguo
Hi,
I have some EJB code exposed as web service. The sole functionality of that piece of EJB code is to act as a middle layer, between our c# client and outside (ECCNET) web services: in other words, my client calls my EJB web service, which subsequently calls ECCNET web service.
I was hoping that I might get some performance gain, simply by migrating my EJB code from 4.2.2 to 4.2.3, but I got the opposite. 4.2.3 took double the time to respond.
The testing was done with SoapUI as client, three runs against 4.2.2, and three runs against 4.2.3. Each run lasts 20 minutes, with SoapUI simulates 5 clients. Here is the result:
JBoss 4.2.2 avegare response time in ms: 7062, 7609, 7478
JBoss 4.2.3 average response time in ms: 18823, 16356, 14573
What's the issue? Anybody had similar issues?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193613#4193613
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193613
16 years
[JBoss Portal] - Unauthenticated /sec Access with CAS enabled
by iliap
Hello All,
I'm having some trouble configuring what url patterns Portal deems worthy of CAS authentication. Specifically, I have a registration section of the portal that is SSL encrypted under a "/sec" URL, but does not require the user to be authenticated. This works fine with CAS disabled by commenting out the CAS Valve snippet in jboss-portal.sar/portal-server.war/WEB-INF/context.xml:
|
| <Valve className="org.jboss.portal.identity.sso.cas.CASAuthenticationValve"
| casLogin="https://MYHOST:8443/cas/login"
| casLogout="https://MYHOST:8443/cas/logout"
| casValidate="https://MYHOST:8443/cas/serviceValidate"
| casServerName="MYHOST:8443"
| authType="FORM"
| />
|
If I enable CAS, the user is redirected to the CAS login page once they hit a URL with "/sec" in it. In the logs, there is the following debug message:
| 2008-12-01 22:29:25,140 DEBUG [org.jboss.portal.identity.sso.cas.CASAuthenticationValve] Checking if requested uri '/portal/sec/portal/default/registration/Registration+Request' matches secured url patterns: [/sec/, /authsec/, /auth/]
|
Why would it try to authenticate on "/sec" with CAS enabled, but not when it is disabled?
Thanks,
Ilia
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193599#4193599
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193599
16 years