I've done some testing and here are the results I'm seeing. I am looking up an entity bean from a remote host which uses hajndi to get the bean from a cluster of 2 machines.
Using the jnp.partitionName produces undesireable results. When both nodes are down and then one comes back up, the client lookups will fail with "Service Unavailable" exceptions. The client must be restarted to fix the problem, creating a new InitialContext will not help. Using the java.naming.provider.url produces better, but not optimal results. When both nodes are down an exception will be thrown on the client, but creating a new InitialContext will give you a context on the localhost which has recent lookups cached. Any lookups on immutable data will succeed, but volatile data cannot be found and lookups will return null. This means the client doesn't have to restart, which is good, but the behavior can give you headaches. You can never know if your lookup is legitimately returning null, or if your cluster is down. Does anyone have suggestions for clients surviving when an entire cluster goes down? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863135#3863135 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863135 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
