-
1. Re: Replicated Session State problem
integ Oct 4, 2002 4:14 PM (in response to brall)Is jbossha-client.jar in your classpath? If not try putting it in the classpath.
-
2. Re: Replicated Session State problem
brall Oct 5, 2002 12:11 PM (in response to brall)Adding jbossha-client.jar to my classpath didn't seem to help. Maybe I need to elaborate on the problem; I am seeing the problem when I access the web interface for my application. It looks like the server is having problems when it tries to replicate the HttpSession state between the clustered servers. The class that it is complaining about is stored in the session.
-
3. Re: Replicated Session State problem
slaboure Oct 7, 2002 6:02 AM (in response to brall)it seems that the class is not available on the other node. Try to put the JAR containing your shared classes under /lib or /deploy and check if it works.
-
4. Re: Replicated Session State problem
jlouis Mar 3, 2003 10:47 AM (in response to brall)Was anyone able to figure this out? I have my war file in the deploy directory but it still can't find the class. I even tried putting it in the lib directory but that didn't work either. I do want to keep it in the deploy or farm directory so that I can use hot deployment.
-
5. Re: Replicated Session State problem
jlouis Mar 3, 2003 12:08 PM (in response to brall)Nevermind, I figured it out. Thanks.
-
6. Re: Replicated Session State problem
olivert Mar 12, 2003 3:03 PM (in response to brall)We run into the same problem.
How did you fix it? -
7. Re: Replicated Session State problem
slaboure Mar 17, 2003 2:35 PM (in response to brall)Can you please try from a fresch CVS checkout from Branch_3_0: this should have been fixed by now (thanks to Scott). It is a classloader problem between servlet engine(s) and JBoss kernel.
Cheers,
sacha