Terracotta Discussion Forums

Sort of like an earlier issue:

http://forums.terracotta.org/forums/posts/list/686.page

I am keeping the same session id, but the serverid/jvmRoute bounces around randomly. At this point, I haven't figured out how to TC JCaptcha so sometime when an image is generated on one server, the user ends up trying to verify on another server and the auth fails.

Anyone have any ideas how to TC JCaptcha or a better way to implment character verification in a TC/Spring envrionment?

Note: Unlike the other question, I am staying on the same domain (not a subdomain which the mod_jk patch will fix). I am using a custom sessionid.name (MYSESSIONID) to work around the duplicate JSESSIONID issue for now.

Thanks,

Darin

[list]
Terracotta 2.5.2, as of 20080218-120204 (Revision 7031 by cruise@rh4mo0 from 2.5)
Tomcat 5.5.25
JDK 1.5.0_10
Spring 2.0.4
JCaptcha 1.0RC4
[/list]

Darin, how exactly Terracotta for Spring is used in this application?

A simple test app would make it much easier to investigate this issue. Some more details about duplicate JSESSIONID issue and custom sessionid.name would also help to understand the problem.

I haven't used JCaptcha before, and was under impression that it generates captcha image/text (which don't need to be clustered) and stores corresponding answer into http session, so in theory it should be completely transparent as long as session is clustered properly.

Out of curiosity, why do you bounce user to a different server on each request? If you bring him to the same server every time it would reduce amount of data for replication.

regards,
Eugene Kuleshov

I don't bounce the user to a different server on purpose. Sometimes the session goes back to the originating server, sometimes it goes to another server in the cluster. There's no rhyme or reason to why it happens. I have confirmed that:

Terracotta server.id == Tomcat jvmRoute == Apache entry in workers.properties

Its really got me pretty confused. If I remove Terracotta from the solution, I do not get bounced around. The only thing that is different with and without Terracotta is the session cookie reverts back to JSESSIONID. It's probably a container thing.

AFA JCaptcha goes, it doesn't put anything into session. We are evaluating other options.

Darin

I don't have any real wisdom here but as a previous poster mentioned. If you can jar up a sample that shows the problem we can help try and track it down.

Cheers,
Steve