Win a copy of Think Java: How to Think Like a Computer Scientist this week in the Java in General forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Ejb J2EE

 
gajanan deshpande
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi...
This the exeception i get when i run client lookup in the jar file .Why such exception occours.
Please Suggest.
Thanks Gajanan.
java.rmi.RemoteException: ; nested exception is:
weblogic.rmi.ServerException: A remote exception occurred while executing the method on the remote object
- with nested exception:
[weblogic.rmi.UnmarshalException: error unmarshalling arguments
- with nested exception:
[java.io.InvalidClassException: ATIDev.Entity.Lender.pk_Lender; Local class not compatible: stream classdesc serialVersi
onUID=3742474523416509179 local class serialVersionUID=2597316673039095556]]
 
Sean
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
Were the classes compiled using the same JDK?
Serialization is not always compatible across different
compliers.
 
gajanan deshpande
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I have used the same Jdk to compile the code,and the problem is not in jdk but in lookup when we lookup the JNDI name it gives such type of exception.
Waiting for your reply.
thanks
Gajanan.
 
Kiran Karupalli
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It means... your server side class is not same as your local copy. Copy that class to the client machine again and put that in the classpath
 
gajanan deshpande
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I am putting all class files in a jar file hence the jar file contains all the class files required,still then it is giving the same exception.
please suggest as we have checked all these small points such as classpath,etc...
 
sandy gupta
Ranch Hand
Posts: 228
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Please make 100% sure that the error is coming in the lookup statement and then
Try This
It seems to me that the Unmarshall Exception is being generated coz the Stub and Skeleton do not match and that means that there was a problem in ejbc.........
OR
WHAT MOST PROBABLY IS THE REASON IS THAT ONE OF THE CLASSES THAT U ARE BOUNCING AROUND IS NOT IMPLEMENTING THE 'SERIALIZABLE' INTERFACE AND HENCE IS NOT IN A WIRE TRANSFERABLE FORM AND HENCE IT IS THROWING THE REMOTE EXCEPTION,AT THE TIME OF UNMARSHALLING
TRY THESE AND LET US KNOW
SAHIL
 
sandy gupta
Ranch Hand
Posts: 228
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
DOES U'R PK CLASS IMPLEMENT SERIALIZABLE
 
gajanan deshpande
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
The problem is solved and we have written a new bean code for it as the suggestions you have mentioned were tried by us before,but could not get a solution to it.After writing a new bean for it we could solve the problem.
Thanks for all your help.
Gajanan.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic