----- Original Message -----
From: "Kathleen Milsted" <[EMAIL PROTECTED]>
To: "Nikolaus Rumm" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, August 31, 2000 10:59 AM
Subject: Re: Deploying application on server and RMI problems
> Nikolaus Rumm wrote:
> >
> > Hello,
> >
> > I have some troubles deploying my application concerning RMI. Both the
> > client and the server are running on the same machine. Everything is
> > ok as long as I include everything in everybody's CLASSPATH, but
> > that's not a clean way for using RMI.
> > 1) I start the RMI registry with a classpath that only includes ...
> > rmiregistry.jar
> > RMI_jonas.jar
> > 2) I start the Server with a classpath that includes ...
> > jta-spec1_0_1.jar
> > jdbc2_0-stdext.jar
> > ejb11.jar
> > classes12_01.zip (Oracle thin JDBC driver)
> > ... and of course the application classes including the Stubs and
> > Skeletons
> > When launching the ejbserver the property
> > -Djava.rmi.server.codebase=file:///H:/Dolores/ is set.
> >
> > The problem is that the server can't find the Stub-classes. Do I have
> > to seperate the Stub-classes from the rest of the application classes
> > and exclude them from the server classpath (only having them in the
> > codebase) ?
> >
> >
> > Best regards
> >
> > Nikolaus Rumm
>
>
> Dear Nikolaus,
>
> What you're doing looks correct. Is it really the server that can't
> find the stub classes, or is it the registry (which reports its errors
> back through the server as a java.rmi.RemoteException)?
>
> If it's the registry, could it be that there are some classes that
> you haven't put in the codebase directory? In particular, you
> need to put in the codebase all interfaces and exceptions that
> the stub class needs for the registry to be able to reconstruct a
> stub.
>
> If it's the server, then it could be just a simple classpath
> problem: pure server code uses the classpath to find stub classes
> (and dependents) but does not use the codebase property.
>
> However, if part of your server code operates as a client of another
> server, then a reason for such a server to complain about not finding
> stub classes is that it needs to have been run with an adequate
> security policy (just like any old client) to load the stub classes.
>
> Regards,
> Kathleen Milsted
>
>
> France Telecom R&D
> Distributed Systems Architecture department (DTL/ASR)
> 28 chemin du Vieux Chene
> BP 98, 38243 Meylan Cedex
> FRANCE
> E-mail: [EMAIL PROTECTED]
> Tel: +33 4 76 76 45 94
> Fax: +33 4 76 76 45 57
>
Hello Kathleen,
thank you for your response, but my problem is still not solved.
What I get on starting the EJBServer is...
JOnAS Server, version 2.0, running on rmi.
Mapping datasource jdbc:oracle:thin:@192.168.0.1:1521:ORCL on devdb1
Cannot register bean SequenceKeyFactoryHome
javax.naming.CommunicationException [Root exception is
java.rmi.ServerException: Server RemoteException; nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments; nested
exception is:
java.lang.ClassNotFoundException:
com.dolores.ejb.utility.sequence.JOnASSequenceKeyFactoryBeanSequenceKeyFacto
ryHome_Stub]
This looks like a simple CLASSPATH problem on the server, but I am
absolutely sure that my classes are inside the CLASSPATH (I can access the
stub with java
com.dolores.ejb.utility.sequence.JOnASSequenceKeyFactoryBeanSequenceKeyFacto
ryHome_Stub).
Any suggestions ?
Best regards
Nikolaus Rumm
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
