[
https://issues.apache.org/jira/browse/TOMEE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553649#comment-13553649
]
Dmitry Volkov commented on TOMEE-731:
-------------------------------------
I have updated pom.xml according to your recommendations (and commited changes
in github, please refresh the project).
Also, there is "no submit" link now.
I can still reproduce the issue.
There is an alternative way to reproduce:
1. Turn off session stickiness (delete jvmRoute in both server.xml).
2. Start tomee's and httpd.
3. Open /tomee_replication-1.0/index.xhtml and submit some data one time.
4. Click "no submit" link multiple times.
Contents of input fields vary every time the node changes.
> CDI beans replication does not work
> -----------------------------------
>
> Key: TOMEE-731
> URL: https://issues.apache.org/jira/browse/TOMEE-731
> Project: TomEE
> Issue Type: Bug
> Affects Versions: 1.5.2
> Environment: Windows 7, apache + mod_jk
> Reporter: Dmitry Volkov
>
> CDI Beans are not replicated between cluster nodes. Properties of migrated
> beans are null after session migration.
> mod_jk configuration:
> worker.list=lb
> worker.lb.type=lb
> worker.lb.balance_workers=showcase_node1,showcase_node2
> worker.lb.mount//tomee_replication-1.0/*
> worker.showcase_node1.host=localhost
> worker.showcase_node1.port=10030
> worker.showcase_node2.host=localhost
> worker.showcase_node2.port=10040
> The issue can be reproducer with test application:
> https://github.com/eiskonzept/tomee
> Steps to reproduce:
> 1.Configure and start Apache
> 2. Start two tomee instances:
> mvn clean package tomee:start -P node1
> mvn clean package tomee:start -P node2
> 3. Open /tomee_replication-1.0/index.xhtml and remember current node
> 4. Submit some values. Values are saved in WindowScoped bean.
> 5. Stop current node
> 6. Reload page(without form submission)
> After session migration values of WindowScoped bean are null.
--
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
