• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Bear Bibeault
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • salvin francis
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Frits Walraven
Bartenders:
  • Jj Roberts
  • Carey Brown
  • Scott Selikoff

java.rmi.UnmarshalException: Could not unmarshal method ID; nested exception

 
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
HI,
I have successfully deployed my EJB stateless bean application on weblogic 8.1 server.
iam getting following error that my class unable to access data from EJB bean.
any bodu can give me what is cause behind this error
plz help me.
the error is here:::
Caught an unexpected exception!
java.rmi.UnmarshalException: Could not unmarshal method ID; nested exception is:
java.rmi.UnmarshalException: Method not found: 'dollarToYen(D)'
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
at ConverterBean2_5dab3i_EOImpl_812_WLStub.dollarToYen(Unknown Source)
at ConverterClient.main(ConverterClient.java:120)
Caused by: java.rmi.UnmarshalException: Method not found: 'dollarToYen(D)'
at weblogic.rmi.internal.MethodDescriptor.init(MethodDescriptor.java:155)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:265)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:923)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:844)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:222)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:794)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:570)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:105)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 
Ranch Hand
Posts: 209
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Ajoy,
Have you compiled a client using one ejb interface and then deployed ejb app with the modified interface.
Eg, originally you had a component interface ( the one that extends EJBObject ) that declares getDollarToYen(...). This method was referenced by the client app at the time of client compilation.
After the client had been compiled the component interface has been modified (method getDollarToYen(...) removed or parameter list changed). Then an ejb app had been deployed to the app server.
When you ran a client app it found the bean's home, got bean's remote interface (i.e. stub) and then tried to invoke a method that did not exist.
Hope it helps.
 
reply
    Bookmark Topic Watch Topic
  • New Topic