Just for the record I am trying to find a solution for this problem at
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=74446 since
setting the flag to false makes the session cookie to be ignore in
those contextualized applications if the request does not include the
whole context path as it is indeed the case for an Apache + modjk +
jboss clustered infrastructure.
On Jan 30, 2008 4:15 PM, Nestor Urquiza <nestor.urquiza(a)gmail.com> wrote:
Just to update this thread in case someone else is having this
problem. Take a look at
http://jira.jboss.com/jira/browse/JBAS-2568?page=all&decorator=printable
Bottom line attribute emptySessionPath must be set to "false" for the
specific connector.
As stated there though this might come with problems for portlets and
other web apps that rely on session sharing between them.
On Jan 28, 2008 6:49 PM, Nestor Urquiza <nestor.urquiza(a)gmail.com> wrote:
> Hello guys,
> Can anyone please provide some guidance as to where I can make JBoss
> ignore any incomming JSESSIONID not generated by JBoss itself?
>
> Currently I use ModJk and to tag a given server I use an initial
> request using JSESSIONID=.nodeName. The request goes to the right node
> but the session id keeps on being .nodeName for the rest of the
> session which is unnaceptable.
>
> Thanks in advance for your help,
> -Nestor
>