[jboss-user] [JBoss Portal] - Re: Portal-Cluster: REPL_ASYNC vs. REPL_SYNC

2008-06-23 Thread [EMAIL PROTECTED]
IronMan77/Stepahan, Which portllet did you use to replicate problem with preferences? If you could let me know the exact way to reproduce it, that would be great. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4160033#4160033 Reply to the post :

[jboss-user] [JBoss Portal] - Re: Portal-Cluster: REPL_ASYNC vs. REPL_SYNC

2008-06-23 Thread [EMAIL PROTECTED]
I tested with IdentityUserPortletInstance in a 2-node cluster as admin user. I enabled captcha support and change was reflected when I brought down the node that was active. Please let me know how I can reproduce otherwise I will mark the jira as unreproducible. View the original post :

[jboss-user] [JBoss Portal] - Re: Portal-Cluster: REPL_ASYNC vs. REPL_SYNC

2008-06-16 Thread [EMAIL PROTECTED]
Your problem seems to be tied to your use case and it will be very hard (resource issues) for me to dig into it. I suggest that you use our support services and they will be able to replicate and fix your issues more quickly. View the original post :

[jboss-user] [JBoss Portal] - Re: Portal-Cluster: REPL_ASYNC vs. REPL_SYNC

2008-06-13 Thread [EMAIL PROTECTED]
Yes, I am aware of some problems when using REPL_SYNC and we are still investigating it. Your logout issue I believe is fixed in the latest portal release which is 2.6.5.SP1. Can you verify that at your side? I have created a jira issue http://jira.jboss.com/jira/browse/JBPORTAL-2044 for your

[jboss-user] [JBoss Portal] - Re: Portal-Cluster: REPL_ASYNC vs. REPL_SYNC

2008-06-13 Thread [EMAIL PROTECTED]
Are you hitting two servers directly or through a load balancer? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4158000#4158000 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4158000

[jboss-user] [JBoss Portal] - Re: Portal-Cluster: REPL_ASYNC vs. REPL_SYNC

2008-06-13 Thread IronMan77
Although the logout has been fixed in 2.6.5-sp1 (i can confirm that!) it's no viable option for us. As we were already in a production environment there are to many changes in my opinion (many services have been renamed for example) to use it. As a follow up to the portlet preferences