I cannot see anything obviously wrong, especially since the code works in a standalone client. In fetchRemoteObject, after the lookup, cast the object to javax.naming.Reference (should work because the exception said that the object is of that type), and then use a for loop to examine the results from calling Reference.getAll(), and also log the value of Reference.getClassName(). Maybe that will give a clue as to what is going on. Another thing to try is add -vebose:class to the JAVA_OPTS in the run script. This will print out each class loaded and its JAR file. It would be interesting so see from where the FlightReservationAccessorRemote interface gets loaded. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231488#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...