JMS, the Java Messaging Service, is a elaborated queueing system. Clients add messages to the queues and servers remove the messages. Resin-EJB's EJB message-bean implementation can use any JMS implementation which conforms to the specifications. Resin-EJB also includes a basic memory-based JMS implementation.
How about clustering for Resin EE? Does it support In Memory Session Replication for both HttpSession and Stateful Session Beans? I have used load balancing with Resin for a stateless Application using the IIS plugin and it worked very well. What about clustering for JNDI, EJB, and JMS? Anything at all? [ September 26, 2002: Message edited by: Chris Mathews ]
Resin has supported HTTP session clustering for years. EJB session clustering will probably be in 3.0, but I'm not all that sure how much of a benefit it really is. JNDI won't be clustered (what's the point?), but there might be a JNDI <resource> which is a clustered object.
posted 17 years ago
To enable good EJB clustering, JNDI must be clustered. Each node in the cluster needs to know what services the other nodes offer. Otherwise the stubs you get will be pinned to the node that they came from and there goes your fail-over. Most App Servers now use a distributed shared JNDI tree (including WebLogic, JBoss, and WebSphere) as well as a local JNDI tree.