Hi,

Because i just got to know about it from you now :) we were planning to go
for plain Tomcat but then switched to TomEE but kept most of the previous
setup.

I will check TomEE's clustering now.

Many thanks,
Jalal
On Jan 27, 2016 5:08 PM, "Romain Manni-Bucau" <rmannibu...@gmail.com> wrote:

> Hi
>
> TomEE has a built in cluster support, why didnt you use that?
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com>
>
> 2016-01-27 15:04 GMT+01:00 Jalal Almutawa <jalal.almut...@gmail.com>:
>
> > Hello,
> >
> > I have a TomEE 1.7.1 cluster setup using DeltaManager with a
> > ForceReplicationValve that forces all JSF bean attributes to be
> replicated
> > between nodes. I also have a session-test JSF application with a Session
> > Scoped Managed Bean with a simple Integer "counter" to serve as a
> > replication test. A facelet with an <h:commandButton /> is used to
> > increment the counter just to see if the replication works.
> >
> > Now replication works fine, I can see the incremented value of the
> counter
> > each type a hit the commandButton. The issue is that when we failover
> > between nodes, MyFaces throws a No saved view state could be found error.
> > It then works when we refresh the page, but it will not maintain the POST
> > request to increment the counter (e.g. counter=4, we click the increment
> > button, we get the error, we refresh the page, counter still = 4)
> >
> > Code for the session-test webapp:
> https://github.com/jmutawa/session-test
> > Code for the ForceReplicationValve:
> > https://github.com/jmutawa/ForceReplicationValve
> >
> > We tried various configuration options in the web.xml (setting state
> saving
> > in the client, setting serialize state in session to false, ..) but still
> > same error.
> >
> > Appreciate if someone could tell us what are doing wrong.
> >
> > Thanks,
> > Jalal
> >
>

Reply via email to