This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hello, 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 com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.mapSystemExceptio n(ShutdownUtilDelegate.java:137) at javax.rmi.CORBA.Util.mapSystemException(Unknown Source) at headfirst._Advice_Stub.getAdvice(Unknown Source) at AdviceClient.go(AdviceClient.java:35) at AdviceClient.main(AdviceClient.java:13) Caused by: org.omg.CORBA.BAD_OPERATION: vmcid: 0x0 minor code: 0 completed: No at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Sou rce) at java.lang.reflect.Constructor.newInstance(Unknown Source) at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at com.sun.corba.ee.internal.iiop.messages.ReplyMessage_1_2.getSystemExc eption(ReplyMessage_1_2.java:93) at com.sun.corba.ee.internal.iiop.ClientResponseImpl.getSystemException( ClientResponseImpl.java:108) at com.sun.corba.ee.internal.POA.GenericPOAClientSC.invoke(GenericPOACli entSC.java:132) at org.omg.CORBA.portable.ObjectImpl._invoke(Unknown Source) at headfirst._Advice_Stub.getAdvice(Unknown Source) ... 2 more
Joined: Dec 15, 2003
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
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 /Magnus