Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

Has anyone managed to get multiple instances of tomcat to use terracotta sessions when the tomcat instances are started with a security manager?

We can run them just fine when they are run without security but as soon as we start them with it enabled we get issues.

We found that if we attempt to access the session on both tomcat instances, through a proxy, that the tomcat instances hang and stop responding.

The security policy we use basiclly allows anything.

Has anyone had this experience?

I've never tried it, but it doesn't surprise me that the terraotta client has issues with a security manager enabled. It might be helpful to collect the various security exceptions you're seeing in a JIRA ticket.

I don't totally understand the bit about accessing sessions through a proxy. Are you talking about java proxies to the sessions objects, or about http proxy in front of tomcat? Either way, if you're experiencing a hang, a thread dump is what we'd want to see.