[
https://issues.jboss.org/browse/WELD-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614777#comment-12614777
]
Ales Justin commented on WELD-863:
----------------------------------
Did we try this .ear with latest AS7 (its cluster setup)?
> Replication of EJB Session Beans does not work in cluster
> ---------------------------------------------------------
>
> Key: WELD-863
> URL: https://issues.jboss.org/browse/WELD-863
> Project: Weld
> Issue Type: Bug
> Affects Versions: 1.1.0.Final, 1.1.1.Final
> Environment: JBossAS 6 SNAPSHOT (from 2011-03-02) - built in hudson
> Reporter: Martin Gencur
> Assignee: Ales Justin
> Fix For: TBC
>
> Attachments: weld-translator.ear
>
>
> I tested this feature with JSF/Translator example and I needed to do a few
> changes to test this feature. My fork of weld-core with the changes can be
> found at: https://github.com/mgencur/core/tree/cluster-test. I'll also attach
> a packaged ear of the app which I used.
> Steps to reproduce the bug:
> 1) deploy the attached weld-translator.ear file or checkout my changes from
> github and build the application
> 2) start first and second instance of the JBossAS to create a cluster (can be
> found at https://github.com/weld/core/blob/master/examples/README.md)
> 3) deploy the app
> 4) go to your web browser and disable cookies
> 5) go to http://localhost:8080/weld-translator, enter some text and click
> "Translate"
> 6) now change the port number in the address to 8180 and refresh (note that
> there should be also jsessionid included in the URL)
> 7) now the text you entered into the text area should be still there (since
> the value is stored in a field of SFSB which is clustered, but instead, you
> get the following exception at the slave JBossAS instance:
> 12:00:16,662 WARN
> [org.jboss.web.tomcat.service.session.distributedcache.ispn.DistributedCacheManager]
> Problem accessing session [hz****59+A__]:
> org.jboss.weld.exceptions.WeldException: WELD-001500 Failed to deserialize
> proxy object
> Note that if you then go to the first address (with port 8080) and then again
> to 8180 - from now the replication works fine. But IMHO this is not desired
> behaviour, the second (backup) JBoss instance should be ready immediately
> The question is if the changes of the application are the right ones. There
> is nobody here who could confirm this. Please pay attention to it and comment
> this issue if it's not correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
