Re: can intermittent 'illegal relative path' be cause by something besides broken session affinity?

On Sat, Mar 20, 2010 at 7:19 PM, Nikita Tovstoles wrote: > I may have found something - but first another question: under which > conditions would an ajax wicket:interface request omit a 'version'? (I see > request processor then assumes that the version is 0). correct, the first version of the p

Re: can intermittent 'illegal relative path' be cause by something besides broken session affinity?

I may have found something - but first another question: under which conditions would an ajax wicket:interface request omit a 'version'? (I see request processor then assumes that the version is 0). I may have found a race condition: - check out this

Re: can intermittent 'illegal relative path' be cause by something besides broken session affinity?

OK, here's what I can surmise thus far: - Only 'wicket:interface' JS requests - from 'onchange' Ajax validator or from a SubmitLink-initiated form submission trigger the exception - the form being submitted or validated is in a couple of pages but *never *in *StateProgramDetailsPage*

Re: can intermittent 'illegal relative path' be cause by something besides broken session affinity?

i doubt its the diskstore since you are the only one seeing this problem. is this happening on multiple pages or just a particular one? -igor On Sat, Mar 20, 2010 at 10:34 AM, Nikita Tovstoles wrote: > I wonder if this is a serialization problem: > > the following request: > > 10.242.46.21 - -

Re: can intermittent 'illegal relative path' be cause by something besides broken session affinity?

I wonder if this is a serialization problem: the following request: 10.242.46.21 - - [20/Mar/2010:13:04:19 -0400] "POST /?wicket:interface=:0:EmbeddedCategoryCriteriaPanel:inputPanel:categorySearchForm:zipCodeComponent:zipCode::IBehaviorListener:1:10&random=0.014624584217842351 HTTP/1.1" 200 161

can intermittent 'illegal relative path' be cause by something besides broken session affinity?

We're suddenly seeing a fair number of exceptions like one below. Thought the root cause is failing session affinity in our clusters, but the exceptions persist even after we shut down all but one host behind HAProxy. I realize the question is somewhat ambiguous, but what - besides lack of session