Im using LdapExtLoginModule and in the code I can see that it in the
validatePassword() method stores the AuthenticationException from failed
validation in the super class.
Then in the super class UsernamePasswordLoginModule, the
AuthenticationException is retrieved again in the login() method
Im using JBoss 4.3 EAP and have the same problem. Is there a solution for this?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200144#4200144
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200144
___
this topic is related to filed support case:
https://support.redhat.com/jbossnetwork/restricted/caseDetail.html?caseId=245005
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194255#4194255
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=post
We would like to enqueue rmi calls on the server side to handle peak load which
could happen in short periods.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194081#4194081
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p
We need to limit the peek throughput so that we dont DDOS all of our sub
systems (db, external systems etc) that has a limit of how many clients calls
they may execute at the same time.
We are migrating a weblogic application to jboss. Weblogic has execution queues
that limit how many simultan
Any news on this topic? JBoss still doesnt support any form og execution queue
or any other method to limit the number of simultaneous rmi calls to a jboss
server. We need to limit the peek throughput so that we dont DDOS all of our
sub systems (db, external systems etc) that has a limit of how
>From what I have seen in the code, read-only-timeout is only used in commit
>option B. Does option A or D use it too?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191741#4191741
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mod
Im using exactly the same versions of jboss and seam,
Jboss 4.0.5 and Seam 1.2.1 GA, and experiencing exactly the same trouble. Any
news on this topic?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081993#4081993
Reply to the post :
http://www.jboss.com/in