[
https://jira.jboss.org/jira/browse/MODCLUSTER-123?page=com.atlassian.jira...
]
Jean-Frederic Clere edited comment on MODCLUSTER-123 at 1/8/10 10:31 AM:
-------------------------------------------------------------------------
I can't reproduce this one.
Are you sure you are testing that correctly?
DISABLE means it won't accept requests without sessionid, could it be that you send a
sessionid somehow?
was (Author: jfrederic.clere(a)jboss.com):
I can't reproduce this one.
Are you sure you are test that correctly?
DISABLE means it won't accept requests without sessionid, could it be that you send a
sessionid somehow?
Disabling contexts does not work
--------------------------------
Key: MODCLUSTER-123
URL:
https://jira.jboss.org/jira/browse/MODCLUSTER-123
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.2.GA
Environment: RHEL 5.4
Reporter: Radoslav Husar
Assignee: Jean-Frederic Clere
Disabling contexts does not work and it keeps connecting on disabled contexts on the
specified node (neither does 'disable all contexts' option).
Note that in mod_cluster-manager it displays correctly that its disabled.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira