Dear Ravi
Please let me know the loading test result, cause I built identity provider
with this cluster mode, and I have to check whether it exists the same problems.
Thanks
> On 8 Mar 2018, at 20:15, Ravi wrote:
>
> Hi Shengche,
>
> sorry for the late reply. The replication as such is worki
Hi Shengche,
sorry for the late reply. The replication as such is working. We do run into
what seems to be a timing factor.
On a very small scale it works now with the pagestore on a shared
filesystem. We'll do some loadtesting within the next days.
-Ravi
--
Sent from: http://apache-wicket.1842
Ravi
Another question, does your apache https using mod_cluster package from jboss ?
Or have you check the replication packets working status via port ?
> On 5 Mar 2018, at 19:09, Ravi wrote:
>
> Hi,
>
> wildfly runs in domain mode with default settings for the distributed cache.
>
>
Hi,
wildfly runs in domain mode with default settings for the distributed cache.
It seems that the problem is not the jboss settings but somehow the
pagestore is either not written fast enough or concurrently.
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
Hello
Dose your wildfly runs at standalone mode ? or domain mode ? any adjustment of
session replicating?
I add boss-web.xml as flowing
http://www.jboss.com/xml/ns/javaee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
http://www.jboss.com
We also tried to put the pagestore on a shared filesystem, with a similar
result.
The session itself is only a few kb.
Thanks for taking the time!
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
--
Hi Ravi,
Sorry - I have no experience with "real-time" session replication.
Personally I would never attempt it, as wicket sessions can grow relatively
large and thus replication may not be instantaneous (as you are
experiencing)…
Met vriendelijke groet,
Kind regards,
Bas Gooren
Op 2 maart 201
Hi Bas,
we have an apache that balances by using a round robin (byrequest).
The application runs in an infrastructure that does not support
sticky-sessions.
So far from what we've seen both servers getting pinged withing
milliseconds. One server responds correctly. The other one throws a
Componen
Hi Ravi,
You don’t mention what’s in front of your application servers.
Are you doing non-sticky load balancing?
Or are you having issues when the user hits the same application server?
(Which would be a different issue)
Met vriendelijke groet,
Kind regards,
Bas Gooren
Op 2 maart 2018 bij 13: