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]]
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.
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...
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
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.