Hi,
I am trying to cluster 2 jboss 4.2.2.GA instances with apache 2.0.x load
balancer.
I have enabled sticky session by worker.loadbalancer.sticky_session=1.
I ve the default values for Isolation level and CacheMode
REPEATABLE_READ
!-- Valid modes are LOCAL, REPL_ASYNC and
Hi,
I'm seeing similar issue.
[EMAIL PROTECTED] wrote :
| Everyone else -- is anyone seeing this problem with sticky sessions enabled
and working properly? You have to use sticky sessions.
Why does sticky session need to enabled? We have sticky session false and want
to replicate the
Hi all!
my setup is a little bit different... instead of using Apache WS, my client is
using windows network load-balancer to achieve HA on the application (they felt
apache will be the single point of failure). so i used default settings with no
jk_mod. the session got replicated properly but
Re: mod_proxy_ajp, your ProxyPass looks fine. There's the
ProxyPassReverseCookieDomain directive to look into (see
http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxy) but if there was a
problem with the cookie domain I'd expect it would be a non-stickyness problem
but rather a loss of
Last night I reverted back to mod_jk 1.2.21. I have stickysession working
correctly and load balancing working correctly. I no longer have any error
messages regarding the session replication in the jboss log.
This leads me to believe the issue we are all having is with mod_proxy and not
[EMAIL PROTECTED]
Ok, could you comment next. I've written servlet with session supporting. I did
stress test with 100 queries in sticky_mode = false. Aproximatelly 5%
replications failed with concurrency problem in any synchronization modes and
levels of isolation. Other test I did with
Open another thread please, as your replication failing question is a different
topic.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4044318#4044318
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4044318
We are experiencing EXACTLY the same problem with Apache 2.0 proxying requests
to JBoss 4.0.5 using mod_proxy_ajp. I'd like to participate further in the
discussion/resolution as this is a critical issue for us.
Should this topic be opened under a different forum group? Or is
Folks, no offense intended, but can someone on this thread please post saying
We're using sticky sessions, we understand how to configure them and as far as
I know they are working correctly, but we are still seeing the Possible
concurrency problem message.
Once I see that I'll look into it.
Mr Stansberry,
We're using sticky sessions, we understand how to configure them and as far as
I know they are working correctly, but we are still seeing the Possible
concurrency problem message.
To elaborate a little on our configuration, we use jBoss4.0.5GA with Apache
2.2.4 on the front end
Thanks. Please clarify a bit:
1) You mention that sticky sessions are working correctly, but your #2
indicates they aren't. Are you finding your #1 problem even when you know
sticky sessions are working?
2) In either case, when you see issues with requests failing over and the
expected
1) I am moving from mod_proxy_ajp back to mod_jk tonight so after than I can be
more sure of sticky sessions working because I know they work for sure in
mod_jk. I know they are not working correctly now, although I have it setup
just like the Wiki explains
Even with REPL_SYNC you need sticky sessions to work. It's possible to get two
concurrent requests for the same session.
1) Think IFRAMEs or similar stuff. Nothing prevents browsers making
simultaneous requests.
2) Similarly, the webapp can flush or even close the HttpResponse's
Has anyone followed up on this issue?
I am also seeing this (behind a cisco loadbalancer), my session timeout is 40
mins and I don't think that I am hitting this limit...
|
| 2007-05-08 16:14:38,538 INFO
| [org.jboss.ha.framework.server.ClusterFileTransfer
| ] Start push of file
I am seeing the same on 4.2.0CR2 with REPL_SYNC and REPEATABLE_READ. WE are
using Cicso load balancer, no stickiness fior now as we are trying to figure
out how to stick based on jsessionid on the Cisco side.
Looks like we all have in common REPL_SYNC | no sticky LB, don't we?
View the
sparrow: Don't use SERIALIZABLE; use REPEATABLE_READ. REPL_SYNC + SERIALIZABLE
will almost for sure lead to lock timeout exceptions.
Everyone else -- is anyone seeing this problem with sticky sessions enabled and
working properly? You have to use sticky sessions.
View the original post :
Hi !
I've discavered same problem too. Mode REPL_SYNC with SERIALIZABLE with
SyncCommitPhase=true and SyncRollbackPhase=true doesn't always allow to
replicate session succsessfully. I would glad for any advices. Thanks.
View the original post :
Hi
I'm having same problem.
The sticky_session property is disabled (siticky_session=0) in mod_jk config.
The Sessions are replicated, I can see they when I invoke the printDetails
method in the jboss.cache:service=TomcatClusteringCache MBean,
but fail over doesn't work properly and I see the
Are sticky sessions working properly?
Other than that, the following comment from the code explains the only
situation I know of where the code block that logs that gets executed.
// This could be an issue but can happen legitimately in unusual
| // circumstances, so just log something at
19 matches
Mail list logo
