Hi Gautam,
The problem was with the classpath, I did not have jta-spec1_0_1.jar in my
classpath. So why did that result in the "local class incompatible" error?
My guess is that the server threw
javax.transaction.InvalidTransactionException which clashed with the
javax.transaction.InvalidTransactionException.class that is part of Java
(v1.3.1).
My current classpath includes:
client.jar
ejb.jar
jta-spec1_0_1.jar
rmiregistry.jar
providerutil.jar
jndi.jar
jaas.jar
> -----Original Message-----
> From: Gautam Borah [SMTP:[EMAIL PROTECTED]]
> Sent: Saturday, June 16, 2001 3:19 AM
> To: Baker, Richard
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Pure Java Client ---> Deployed EJB
>
> Hi Richard,
>
> I think the "sync" problem is due to the clash of JDK versions that are
> running the server and client. For RMI to work, both the versions of the
> JDK
> should be the same. I tried the following,
>
> 1. Ran the SERVER in JDK version 1.3.
>
> java version "1.3.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C)
> Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)
>
> 2. Ran the client in JDK version 1.4(beta)
>
> java version "1.4.0-beta"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta-b65)
> Java HotSpot(TM) Client VM (build 1.4.0-beta-b65, mixed mode)
>
>
> 3. I got the following error,
>
> javax.naming.ServiceUnavailableException: Unable to get RemoteNameServer :
> java.io.InvalidClassException: sun.rmi.server.Unic
> astRef; local class incompatible: stream classdesc serialVersionUID
> = -6675064658493207194, local class serialVersionUID = -9
> 213327104222131866
>
> This is because of the different JDK versions.
>
> Could you kindly check the JDK versions you are running at both SERVER and
> CLIENT and make them the same if they are not.
> Please get back to me if it does not solve your problem.
> Thanks & Regards,
> Gautam
> Server Team
> www.pramati.com
>
>
>
> ----- Original Message -----
> From: "Baker, Richard" <[EMAIL PROTECTED]>
> To: "'Gautam Borah'" <[EMAIL PROTECTED]>
> Sent: Friday, June 15, 2001 11:32 PM
> Subject: RE: Pure Java Client ---> Deployed EJB
>
>
> > Hi ,
> >
> > Per your advise, I tried both /PS30/server/lib/server/client.jar and
> > /PS30/server/lib/server/client.jar
> >
> > But, I am experiencing the same "sync" problem. I Don't know what to do.
> >
> > > -----Original Message-----
> > > From: Gautam Borah [SMTP:[EMAIL PROTECTED]]
> > > Sent: Friday, June 15, 2001 9:21 AM
> > > To: [EMAIL PROTECTED]
> > > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > > Subject: Pure Java Client ---> Deployed EJB
> > >
> > > Hi Richard,
> > >
> > > The client.jar seems to be out of sync with server.jar. Could you
> kindly
> > > check that client.jar you are setting in the classpath is from
> > > INSTALL_DIR\server30\lib\server. If this is the case then a work
> around
> > > can be achived by putting
> > > INSTALL_DIR\server30\lib\server\server.jar(Instead of client.jar) in
> the
> > > classpath of the client.
> > >
> > > In your java client please set the System.SecurityManager as,
> > > public static void main(String args[]){
> > > System.setSecurityManager(new
> > > com.pramati.security.client.RMIClientSecurityManager());
> > > ......
> > > ......
> > > }
> > >
> > > This is to enable dynamic downloading of IMPL_stubs(Home and Remote
> > > stubs).
> > >
> > > If you are putting MyApp.jar and MyAppClient.jar from
> > >
> INSTALL_DIR\server30\nodes\StandAlone\default\archives\MyApp.ear\classes
> > > in the client's classpath, then you need not set the security manager.
> > >
> > > This weekend we are planning one more upload to support jar
> deployment,
> > > deferred primary key support and minor bug fixes. Please let us know
> if
> > > the same problem recurs. It would be a great help to us to resolve all
> the
> > > problems before the coming upload.
> > >
> > > Thanks & Regards,
> > >
> > > Gautam
> > > Server Team
> > > www.pramati.com <http://www.pramati.com>
> > >
> > >
> > >
> > > > Can you provide an example of calling a deployed EJB from a pure
> > > > java client app?
> > > >
> > > > Here's what I tried...
> > > >
> > > >
> > > > naming environment:
> > > >
> > > >
> > > >
> > >
> java.naming.factory.initial=com.pramati.naming.client.PramatiClientContext
> > > Fa
> > > > ctory
> > > > java.naming.provider.url=rmi://127.0.0.1:9191/
> > > >
> > > >
> > > > -classpath client.jar;jaas.jar;MyAppClient.jar
> > > >
> > > >
> > > > result:
> > > >
> > > > "javax.naming.ServiceUnavailableException: Unable to get
> > > > RemoteNameServer : java.
> > > > io.InvalidClassException: com.pramati.util.ProtonUnicastRef; Local
> > > > class not com
> > > > patible: stream classdesc serialVersionUID=-2937931484566183960
> > > > local class seri
> > > > alVersionUID=-5703586549380452216"
> > >
> >
