Comments on: Clustering Acegi via JGroups (DistributedHashtable) http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/ Mert Can Akkan's java tips,options, news... Wed, 03 Mar 2010 10:08:16 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Sagara http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-930 Sagara Fri, 29 May 2009 07:36:25 +0000 http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-930 In JBoss 4.2.1.GA (JGroup 2.4.1-sp3) cluster i got some version mismatch problems for DistributedHashtable but after some slight modification with ReplicatedHashtable i got successful results . If any one facing to same problem ,refer this post http://ssagara.blogspot.com/2009/05/acegi-clustering-on-jboss.html In JBoss 4.2.1.GA (JGroup 2.4.1-sp3) cluster i got some version mismatch problems for DistributedHashtable but after some slight modification with ReplicatedHashtable i got successful results . If any one facing to same problem ,refer this post http://ssagara.blogspot.com/2009/05/acegi-clustering-on-jboss.html

]]> By: altuure http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-917 altuure Mon, 27 Apr 2009 14:20:15 +0000 http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-917 Hi Sarath, As far as I remember the configuration of 1.0+ is mostly different than previous versions so you can look at upgrade guides and http://www.acegisecurity.org/guide/springsecurity.html#form-config Hi Sarath,
As far as I remember the configuration of 1.0+ is mostly different than previous versions so you can look at upgrade guides and
http://www.acegisecurity.org/guide/springsecurity.html#form-config

]]> By: Sarath Babu Polavarapu http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-916 Sarath Babu Polavarapu Sun, 26 Apr 2009 15:53:46 +0000 http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-916 Hi Mert, Thanks for your response. As you addressed, the problem was version specific problem. When I have replaced acegi-security-1.0.7 (latest version, downloaded from spring website), problem got resolved. And I am able to run your TestCase. However, in my legacy code, we are uisng acegi framework constant, "AbstractProcessingFilter.ACEGI_SECURITY_TARGET_URL_KEY", which is available in previous jar file (acegi-security-1.0.0-RC1.jar). But when I have changed this jar file reference from acegi-security-1.0.0-RC1.jar to acegi-security-1.0.7.jar, it is displaying the compile time error: "AbstractProcessingFilter.ACEGI_SECURITY_TARGET_URL_KEY cannot be resolved" Do you have any idea how to resolve this issue ? Thanks, Sarath. Hi Mert,

Thanks for your response. As you addressed, the problem was version specific problem. When I have replaced acegi-security-1.0.7 (latest version, downloaded from spring website), problem got resolved. And I am able to run your TestCase.

However, in my legacy code, we are uisng acegi framework constant, “AbstractProcessingFilter.ACEGI_SECURITY_TARGET_URL_KEY”, which is available in previous jar file (acegi-security-1.0.0-RC1.jar). But when I have changed this jar file reference from acegi-security-1.0.0-RC1.jar to acegi-security-1.0.7.jar, it is displaying the compile time error: “AbstractProcessingFilter.ACEGI_SECURITY_TARGET_URL_KEY cannot be resolved”

Do you have any idea how to resolve this issue ?
Thanks, Sarath.

]]> By: altuure http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-915 altuure Thu, 23 Apr 2009 07:46:43 +0000 http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-915 Hi Sarath, I am not sure about these versions since it a very old post and project.. but you can download the jar files from http://mirrors.ibiblio.org/pub/mirrors/maven2/org/acegisecurity/acegi-security/1.0.3/ Regards Mert Can Akkan Hi Sarath,
I am not sure about these versions since it a very old post and project..
but you can download the jar files from
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/acegisecurity/acegi-security/1.0.3/

Regards
Mert Can Akkan

]]> By: Sarath Babu Polavarapu http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-914 Sarath Babu Polavarapu Tue, 21 Apr 2009 12:55:31 +0000 http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-914 Hi Altuure, I am using spring 1.2.6.jar and acegi-security-1.0.0-RC1.jar. Please let me know if I need to changes acegi security version. In your dependency list, it is being mentioned to use acegi 1.0.3. Can I have to reference URL to dowload this version Jar file. Thanks, Sarath. Hi Altuure,

I am using spring 1.2.6.jar and acegi-security-1.0.0-RC1.jar. Please let me know if I need to changes acegi security version. In your dependency list, it is being mentioned to use acegi 1.0.3. Can I have to reference URL to dowload this version Jar file.
Thanks,
Sarath.

]]> By: Dan http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-566 Dan Mon, 23 Feb 2009 18:06:09 +0000 http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-566 After further research, this is a common problem with web servers. It seems that the session destroyed event is called for the sessions in the current node and is not global to the cluster. There is an easy solution in the JBoss link below. You can load a properties file to determine if a shutdown is occurring. The only issue with this is that one would have to remember to update the properties file before the instance was shut down and then again prior to the app server restart. ;) If you can come up with a better solution I would like to hear about it. https://jira.jboss.org/jira/browse/JBSEAM-3172 http://www.mail-archive.com/users@tomcat.apache.org/msg42968.html After further research, this is a common problem with web servers. It seems that the session destroyed event is called for the sessions in the current node and is not global to the cluster. There is an easy solution in the JBoss link below. You can load a properties file to determine if a shutdown is occurring. The only issue with this is that one would have to remember to update the properties file before the instance was shut down and then again prior to the app server restart. ;) If you can come up with a better solution I would like to hear about it.

https://jira.jboss.org/jira/browse/JBSEAM-3172
http://www.mail-archive.com/users@tomcat.apache.org/msg42968.html

]]> By: Dan http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-565 Dan Mon, 23 Feb 2009 16:38:24 +0000 http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-565 I added log statements to your source code otherwise I wouldn't have even noticed it if I wasn't checking log files. The Authentication object gets replicated even if I shutdown one instance of OAS. It does not get destroyed, therefore the user can continue to use the application with no DistributedSessionInformation in the DistributedSessionRegistryImpl (getSessionInformation returns null). However since there is no DistributedSessionInformation , the last refresh date will never get updated and the account will eventually expire. I'm going to double check my server configuration and then look into the Spring event flow to see why this event is being published when I shutdown an instance. Thanks! I added log statements to your source code otherwise I wouldn’t have even noticed it if I wasn’t checking log files. The Authentication object gets replicated even if I shutdown one instance of OAS. It does not get destroyed, therefore the user can continue to use the application with no DistributedSessionInformation in the DistributedSessionRegistryImpl (getSessionInformation returns null). However since there is no DistributedSessionInformation , the last refresh date will never get updated and the account will eventually expire. I’m going to double check my server configuration and then look into the Spring event flow to see why this event is being published when I shutdown an instance. Thanks!

]]> By: altuure http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-564 altuure Mon, 23 Feb 2009 16:11:30 +0000 http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-564 session replication should be enabled, but since I haven't run this on oracle, I am not sure what the problem might be :( session replication should be enabled, but since I haven’t run this on oracle, I am not sure what the problem might be :(

]]> By: Dan http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-563 Dan Mon, 23 Feb 2009 16:07:17 +0000 http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-563 I do have session replication enabled on the OC4J instances. Are you saying that I have to have this disabled? If I disable this, will this stop the HttpSessionDestroyedEvent from being fired off when I shut down a single instance of OC4J? Thanks! I do have session replication enabled on the OC4J instances. Are you saying that I have to have this disabled? If I disable this, will this stop the HttpSessionDestroyedEvent from being fired off when I shut down a single instance of OC4J? Thanks!

]]> By: altuure http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-562 altuure Mon, 23 Feb 2009 15:24:04 +0000 http://www.altuure.com/2007/12/23/clustering-acegi-via-jgroups-distributedhashtable/#comment-562 hi Sarath, I think this is a version specific problem , in other words my code and you project are possibly not using the same version can you specify your spring-security version please ? regards hi Sarath,
I think this is a version specific problem , in other words my code and you project are possibly not using the same version
can you specify your spring-security version please ?

regards

]]>