This week's book giveaway is in the Jobs Discussion forum.
We're giving away four copies of Customer Requirements for Developers and have Marcho Behler on-line!
See this thread for details.
The moose likes EJB Certification (SCBCD/OCPJBCD) and the fly likes Error in client Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Customer Requirements for Developers this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Certification » EJB Certification (SCBCD/OCPJBCD)
Bookmark "Error in client" Watch "Error in client" New topic

Error in client

Thomas Dev

Joined: Dec 15, 2003
Posts: 4
I was trying the Advice example from Kathy's HFE book.
When I am running the client I am getting following error.
If I comment the remote call then program executes perfectly.
That means I am getting the Remot and Home object properly without error.
However when I make a call to the remote method then I get this error.
I am using J2EE SDK 1.3.1 and J2SDK 1.4.2_02

Exception in thread "main" java.rmi.RemoteException: CORBA BAD_OPERATION 0 No; n
ested exception is:
org.omg.CORBA.BAD_OPERATION: vmcid: 0x0 minor code: 0 completed: No
at javax.rmi.CORBA.Util.mapSystemException(Unknown Source)
at headfirst._Advice_Stub.getAdvice(Unknown Source)
at AdviceClient.go(
at AdviceClient.main(
Caused by: org.omg.CORBA.BAD_OPERATION: vmcid: 0x0 minor code: 0 completed:
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Sou
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at org.omg.CORBA.portable.ObjectImpl._invoke(Unknown Source)
at headfirst._Advice_Stub.getAdvice(Unknown Source)
... 2 more
Thomas Dev

Joined: Dec 15, 2003
Posts: 4
Thanx in advance...
I found out the solution from other threads...
Changed the name of the method to something else and it seems to work
Magnus Stattin
Ranch Hand

Joined: Jun 05, 2003
Posts: 65
Please see this thread.
The problem has to do with a bug in RI that makes it fail when the methodname resembles the name of the bean. (getAdvice(), advice).
Try to rename the advice() method to something like getMessage().
Best Regards
wood burning stoves
subject: Error in client
It's not a secret anymore!