"bbalaji" wrote : | java.rmi.RemoteException: Service unavailable. | at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxyHA.invoke(JRMPInvokerProxyHA.java:301) | |
It's not easy to tell exactly what's breaking, since JBoss is so "kind" to discard the original exception before throwing the RemoteException with a useless message text. This is done after the proxy has failed to invoke the method on any of the cluster nodes (it tries all nodes if allowed), but there can be lots of reasons for this. Network problems, marshalling exceptions, server overload and so on. We've developed a modified version of the JRMPInvokerProxyHA class to wrap the last causing exception in the RemoteException and you may have a look at it. Note that only the last causing exception is wrapped (there may be different exceptions from different cluster nodes) and treat it as a dirty hack and restrict the use to development or testing systems. You can download the classes from: http://jarnbjo.de/o2-lacosa-jbossextension.jar and place the jar file in $JBOSS_HOME/server/all/lib and somewhere accessible for your client/web-application. Then change the cluster configuration (cluster-service.xml) to use com.o2.lacosa.jboss.proxy.JRMPInvokerHA instead of org.jboss.invocation.jrmp.server.JRMPInvokerHA. Tor View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3849836#3849836 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3849836 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
