[EJB 3.0 Development] - Re: ThreadLocalPool - Is it working the way we think?
by andy.miller@jboss.com
"wolfc" wrote : Two issues:
| 1. the original ThreadlocalPool was designed incur zero thread contention. This changed when statistics were implemented. Right now that uses sync blocks, but it could be changed to atomics. Still it would incur a penalty.
| 2. a ThreadlocalPool servicing a ThreadPool with a size > 100 will always have a lower throughput than a StrictMaxPool with maximum size 100. The maximum size of ThreadlocalPool is not applicable.
|
| To really identify performance bottlenecks within enterprise beans you would need to know:
| - average queue size
| - average execution time
| - average wait time
|
| We also need to microbench all the pool implementations to see their effect on throughput & average response time.
Yes, the statistics require synchronization, which is part of the point. If you need the statistics, then you lose the benefits of it being a ThreadLocal.
I also seem to remember that it also synchronizes on the ArrayList for the instance references too though.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256419#4256419
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256419
16 years, 6 months
[JBoss Web Services Development] - Re: JBossSTS SOAP protocol handler
by anil.saldhana@jboss.com
Dan, the question was whether the SAML assertion can be used as the authentication construct rather than username/pwd or a X509 certificate (as supported by the WS-Security implementation in JBossWS). This was what Stefan and I were referring to.
At this time, I think you should forget about the authentication aspect and just focus on passing the saml assertion to the wst client and let the STS handle the token.
Maybe you can have a single username/pwd for the ESB layer with the STS to pass in the WS-S headers. Or better some type of X509 certificate that is mutually agreed on.
There are two different things:
1) There needs to be a security context for the client and the STS to interact. This is what is passed in the ws-s headers. Can be username/pwd or x509 cert.
2) And then there is the payload (in this case, the SAML assertion) that the STS will use to validate.
>From what I see, the item 1 is a trust association between the ESB and ESB client. We can set it up once.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256412#4256412
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256412
16 years, 6 months