[jira] [Commented] (MYFACES-3772) SessionScoped beans are not synchronizing between tomcat 6 cluster
[ https://issues.apache.org/jira/browse/MYFACES-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772859#comment-13772859 ] Prasenjit Purohit commented on MYFACES-3772: Hi, I am getting the similar effect with OWB too i followed procedure described at [http://tandraschko.blogspot.de/2013/09/enable-failover-with-openwebbeans-120.html]. Now i am getting a sense that i am making something wrong. SessionScoped beans are not synchronizing between tomcat 6 cluster -- Key: MYFACES-3772 URL: https://issues.apache.org/jira/browse/MYFACES-3772 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.1.12 Environment: Tomcat6 + JDK7 + Win7 + Apache httpd load balancer (without sticky session) Reporter: Prasenjit Purohit Assignee: Leonardo Uribe I am using myfaces in our project. We use some session scoped beans. Let me explain the error reproduction steps with two Tomcat6 nodes and Apache httpd load balancer (without sticky session). web.xml has distributable/ element. Other session variables are synchronizing well. 1. Start node 1 2. Set some value in the property of a session bean 3. Value is available for get on node 1 4. Start node 2 same value is available on node 2 5. Set new value on the property of node 1 6. New value is available on node 1 7. Node 2 still contains the old value 8. Restart node 2 9. Node 2 now contains new value 10. Set new value on node 2 11. New value available on node 2 but not on node 1 12. Restart node 2 13. Node 2 has the old value taken from Node 1 No exception is raised during the process. Session bean implements Serializable interface. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3772) SessionScoped beans are not synchronizing between tomcat 6 cluster
[ https://issues.apache.org/jira/browse/MYFACES-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770651#comment-13770651 ] Thomas Andraschko commented on MYFACES-3772: I think we should do it the same as we did in OWB. Creating a bag/container with all sessionScoped beans and always store this container in the session after each request. (this should be the same for viewscoped beans, too) In this container we should also store a server identifier / jvm_id (in OWB it's just a static UID). So we can restore the beans from the container if the jvm_id is another as from the last request. [~prasenjitpurohit] As workaround, you can use ObenWebBeans and CDI instead of JSF Beans or using another failover manager for tomcat - http://code.google.com/p/memcached-session-manager/ SessionScoped beans are not synchronizing between tomcat 6 cluster -- Key: MYFACES-3772 URL: https://issues.apache.org/jira/browse/MYFACES-3772 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.1.12 Environment: Tomcat6 + JDK7 + Win7 + Apache httpd load balancer (without sticky session) Reporter: Prasenjit Purohit Assignee: Leonardo Uribe I am using myfaces in our project. We use some session scoped beans. Let me explain the error reproduction steps with two Tomcat6 nodes and Apache httpd load balancer (without sticky session). web.xml has distributable/ element. Other session variables are synchronizing well. 1. Start node 1 2. Set some value in the property of a session bean 3. Value is available for get on node 1 4. Start node 2 same value is available on node 2 5. Set new value on the property of node 1 6. New value is available on node 1 7. Node 2 still contains the old value 8. Restart node 2 9. Node 2 now contains new value 10. Set new value on node 2 11. New value available on node 2 but not on node 1 12. Restart node 2 13. Node 2 has the old value taken from Node 1 No exception is raised during the process. Session bean implements Serializable interface. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3772) SessionScoped beans are not synchronizing between tomcat 6 cluster
[ https://issues.apache.org/jira/browse/MYFACES-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770658#comment-13770658 ] Karl Kildén commented on MYFACES-3772: -- A little out of scope I realize but how do you enable session failover in OWB? Any other steps required? SessionScoped beans are not synchronizing between tomcat 6 cluster -- Key: MYFACES-3772 URL: https://issues.apache.org/jira/browse/MYFACES-3772 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.1.12 Environment: Tomcat6 + JDK7 + Win7 + Apache httpd load balancer (without sticky session) Reporter: Prasenjit Purohit Assignee: Leonardo Uribe I am using myfaces in our project. We use some session scoped beans. Let me explain the error reproduction steps with two Tomcat6 nodes and Apache httpd load balancer (without sticky session). web.xml has distributable/ element. Other session variables are synchronizing well. 1. Start node 1 2. Set some value in the property of a session bean 3. Value is available for get on node 1 4. Start node 2 same value is available on node 2 5. Set new value on the property of node 1 6. New value is available on node 1 7. Node 2 still contains the old value 8. Restart node 2 9. Node 2 now contains new value 10. Set new value on node 2 11. New value available on node 2 but not on node 1 12. Restart node 2 13. Node 2 has the old value taken from Node 1 No exception is raised during the process. Session bean implements Serializable interface. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3772) SessionScoped beans are not synchronizing between tomcat 6 cluster
[ https://issues.apache.org/jira/browse/MYFACES-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770659#comment-13770659 ] Thomas Andraschko commented on MYFACES-3772: - http://tandraschko.blogspot.de/2012/08/test.html SessionScoped beans are not synchronizing between tomcat 6 cluster -- Key: MYFACES-3772 URL: https://issues.apache.org/jira/browse/MYFACES-3772 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.1.12 Environment: Tomcat6 + JDK7 + Win7 + Apache httpd load balancer (without sticky session) Reporter: Prasenjit Purohit Assignee: Leonardo Uribe I am using myfaces in our project. We use some session scoped beans. Let me explain the error reproduction steps with two Tomcat6 nodes and Apache httpd load balancer (without sticky session). web.xml has distributable/ element. Other session variables are synchronizing well. 1. Start node 1 2. Set some value in the property of a session bean 3. Value is available for get on node 1 4. Start node 2 same value is available on node 2 5. Set new value on the property of node 1 6. New value is available on node 1 7. Node 2 still contains the old value 8. Restart node 2 9. Node 2 now contains new value 10. Set new value on node 2 11. New value available on node 2 but not on node 1 12. Restart node 2 13. Node 2 has the old value taken from Node 1 No exception is raised during the process. Session bean implements Serializable interface. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3772) SessionScoped beans are not synchronizing between tomcat 6 cluster
[ https://issues.apache.org/jira/browse/MYFACES-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770691#comment-13770691 ] Prasenjit Purohit commented on MYFACES-3772: Thanks [~tandraschko] for your workaround. I am going to try that. Anyway CDI will replaye these beans. But then also we should have this feature in faces session/view beans. SessionScoped beans are not synchronizing between tomcat 6 cluster -- Key: MYFACES-3772 URL: https://issues.apache.org/jira/browse/MYFACES-3772 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.1.12 Environment: Tomcat6 + JDK7 + Win7 + Apache httpd load balancer (without sticky session) Reporter: Prasenjit Purohit Assignee: Leonardo Uribe I am using myfaces in our project. We use some session scoped beans. Let me explain the error reproduction steps with two Tomcat6 nodes and Apache httpd load balancer (without sticky session). web.xml has distributable/ element. Other session variables are synchronizing well. 1. Start node 1 2. Set some value in the property of a session bean 3. Value is available for get on node 1 4. Start node 2 same value is available on node 2 5. Set new value on the property of node 1 6. New value is available on node 1 7. Node 2 still contains the old value 8. Restart node 2 9. Node 2 now contains new value 10. Set new value on node 2 11. New value available on node 2 but not on node 1 12. Restart node 2 13. Node 2 has the old value taken from Node 1 No exception is raised during the process. Session bean implements Serializable interface. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3772) SessionScoped beans are not synchronizing between tomcat 6 cluster
[ https://issues.apache.org/jira/browse/MYFACES-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770155#comment-13770155 ] Leonardo Uribe commented on MYFACES-3772: - The spec doesn't mention anything about call session#putAttribute(mySessionBean) for session scoped beans. I can see the point. If that so, the only possible solution is create some code that iterate over session scope beans and call the method, but it will be implementation specific. Thanks Thomas for explain what's going on. I think it has sense to add this feature, even if faces beans will become obsolete someday with the rise of CDI. SessionScoped beans are not synchronizing between tomcat 6 cluster -- Key: MYFACES-3772 URL: https://issues.apache.org/jira/browse/MYFACES-3772 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.1.12 Environment: Tomcat6 + JDK7 + Win7 + Apache httpd load balancer (without sticky session) Reporter: Prasenjit Purohit Assignee: Leonardo Uribe I am using myfaces in our project. We use some session scoped beans. Let me explain the error reproduction steps with two Tomcat6 nodes and Apache httpd load balancer (without sticky session). web.xml has distributable/ element. Other session variables are synchronizing well. 1. Start node 1 2. Set some value in the property of a session bean 3. Value is available for get on node 1 4. Start node 2 same value is available on node 2 5. Set new value on the property of node 1 6. New value is available on node 1 7. Node 2 still contains the old value 8. Restart node 2 9. Node 2 now contains new value 10. Set new value on node 2 11. New value available on node 2 but not on node 1 12. Restart node 2 13. Node 2 has the old value taken from Node 1 No exception is raised during the process. Session bean implements Serializable interface. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3772) SessionScoped beans are not synchronizing between tomcat 6 cluster
[ https://issues.apache.org/jira/browse/MYFACES-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13767597#comment-13767597 ] Leonardo Uribe commented on MYFACES-3772: - This issue is not related to MyFaces. If you use JSF beans, I'm sure they are stored inside session properly. Note with OpenWebbeans you need to enable session failover, otherwise you'll experience something similar. The mechanism used to replicate the state in a cluster rely on servlet spec. JSF is built on top of servlet spec, so in this case I don't see what can we do to fix this. If there is a fix, it should be done inside tomcat, I suppose. I'll close this issue as invalid, because there is no hard evidence that this behavior could be caused by MyFaces. SessionScoped beans are not synchronizing between tomcat 6 cluster -- Key: MYFACES-3772 URL: https://issues.apache.org/jira/browse/MYFACES-3772 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.1.12 Environment: Tomcat6 + JDK7 + Win7 + Apache httpd load balancer (without sticky session) Reporter: Prasenjit Purohit I am using myfaces in our project. We use some session scoped beans. Let me explain the error reproduction steps with two Tomcat6 nodes and Apache httpd load balancer (without sticky session). web.xml has distributable/ element. Other session variables are synchronizing well. 1. Start node 1 2. Set some value in the property of a session bean 3. Value is available for get on node 1 4. Start node 2 same value is available on node 2 5. Set new value on the property of node 1 6. New value is available on node 1 7. Node 2 still contains the old value 8. Restart node 2 9. Node 2 now contains new value 10. Set new value on node 2 11. New value available on node 2 but not on node 1 12. Restart node 2 13. Node 2 has the old value taken from Node 1 No exception is raised during the process. Session bean implements Serializable interface. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3772) SessionScoped beans are not synchronizing between tomcat 6 cluster
[ https://issues.apache.org/jira/browse/MYFACES-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13767632#comment-13767632 ] Thomas Andraschko commented on MYFACES-3772: Leo, are you sure that MyFaces handles this 100% correctly? I had the same problem before switching to OpenWebBeans some years ago. Do we always call session#putAttribute(mySessionBean) after each request? Otherwise, the change of a property won't be replicated. SessionScoped beans are not synchronizing between tomcat 6 cluster -- Key: MYFACES-3772 URL: https://issues.apache.org/jira/browse/MYFACES-3772 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.1.12 Environment: Tomcat6 + JDK7 + Win7 + Apache httpd load balancer (without sticky session) Reporter: Prasenjit Purohit Assignee: Leonardo Uribe I am using myfaces in our project. We use some session scoped beans. Let me explain the error reproduction steps with two Tomcat6 nodes and Apache httpd load balancer (without sticky session). web.xml has distributable/ element. Other session variables are synchronizing well. 1. Start node 1 2. Set some value in the property of a session bean 3. Value is available for get on node 1 4. Start node 2 same value is available on node 2 5. Set new value on the property of node 1 6. New value is available on node 1 7. Node 2 still contains the old value 8. Restart node 2 9. Node 2 now contains new value 10. Set new value on node 2 11. New value available on node 2 but not on node 1 12. Restart node 2 13. Node 2 has the old value taken from Node 1 No exception is raised during the process. Session bean implements Serializable interface. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
