This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
After spending countless hours searching for a solution I've given up and decided I'll need some help.
I deployed my EJB .jar file in the /farm folder (for clustering) and the clustering works fine for the multiple nodes.
However I run into some problems when testing a node using a standalone test client.
The EJB is located in a remote server (server A) and the client jar file is located in another machine. I execute the client jar file via the command line using java -jar client.jar. However it throws me the following exception.
I've added jbossall-client.jar to my classpath (I've added this in the MANIFEST.MF file of the client.jar file). I haven't been using a legacy version of JBoss, consistently using JBoss 6.
My guess is I haven't packaged my client jar correctly. Currently I have the following in there:
> package1: client + beanRemoteInterface
The contents of the Client is as follows:
My EJB jar looks like this: (one package)
Am I suppose to include the remote bean interface with the client jar? I did some research and some people claim it's a class loader issue loading two instances of the same BeanRemote interface. Anyone got any suggestions? I'm really looking to just get a very simple standalone client to test clustering functions.