-
1. Re: CommunicationException / ClassNotFoundException on looku
meiners Dec 1, 2008 5:30 AM (in response to meiners)The Swing Client runs without errors on any Windows machines (only jre 1.6.0 and network contact installs to the JBoss of the Vista machine).
An exception is thrown with the Swing Client on the Debian machine, here:
initial.lookup("project_projectQ");
The exception reads:
javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: project.query.projectQHome]
The project.query.projectQHome is an interface in a file project.ear, which is on the JBoss (the Vista machine) deployed.package project.query; public interface projectQHome extends javax.ejb.EJBHome { public projectQ create() throws java.rmi.RemoteException, javax.ejb.CreateException; }
If this interface in the .jar file of the Swing Client is merged, the functions run also on the Debian machine!!
Why doesn't run the interface project.query.projectQHome from project.ear the JBoss on Debian machine? Are there Threads, which miss communication and/or the download of the interface run? -
2. Re: CommunicationException / ClassNotFoundException on looku
meiners Dec 3, 2008 9:34 AM (in response to meiners)If the interface project.query.ProjectQHome is merged in the.jar file of the Swing Client,
those of port 2001,2000 and 4444 are used.
If this interface is not merged, those of port 2001,2000,4444 and 8083 are used.
When starting of the JBoss the following is logged:
08:47:05,244 INFO [WebService] Using RMI server codebase: http://MAINSERV:8083
08:47:05,986 INFO [NamingService] Started jndi bootstrap jnpPort=2001, rmiPort=2000, backlog=50, bindAddress=/192.168.1.2, Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
The WebService Using RMI server code base 8083 has here the attitude on MAINSERV.
MAINSERV is the computer name of the Vista machine.
In my opinion that could be the cause for the CommunicationException,
there all Windows machines in the local network the computer 'MAINSERV' to reach (e.g. http://MAINSERV:8080/ for the starting side of the JBoss),
the Debian distribution can so not, but only over the IP address http://192.168.1.2:8080/ for the starting side of the JBoss and http://192.168.1.2:8083/ for the WebService.
I tried to change the codebase properties for run.bat of JBoss.
The changes were also accepted according to JBoss for the WebService, e.g.:
-Djava.rmi.server.codebase=http://192.168.1.2/
-Djava.rmi.server.codebase=http://192.168.1.2:8083/
Perhaps a possibility seems to be,
but that does not function in such a way, because I probably set the wrong data over here.
The local Windows machines throw then an exception, as before with the Debian machine:
javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: project.query.ProjectQHome]