Problems with JDK 1.4.2_04 implementation

Thread view:

Antti Oikarinen - 13 Jun 2004 22:50 GMT

Hi,

i have an odd problem with JDK 1.4.2_04: a normal call from client to
server reports an error (see end of post for longer stack trace):

org.omg.CORBA.BAD_OPERATION: vmcid: 0x0 minor code: 0 completed: Maybe

I have no idea what could cause this. IDLs, implementation, everything has
been checked, double checked and checked again. All similar, older, method
calls work just fine, only the new one reports an error. I tried both
renaming the method and moving it to another server class but it didn't
help. Could this be a JDK 1.4.2_04/Windows 2000-related issue? All help is
greatly appreciated!

Thanks,

- Andy -

Stack trace:

org.omg.CORBA.BAD_OPERATION: vmcid: 0x0 minor code: 0 completed: Maybe
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
    at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
    at java.lang.Class.newInstance0(Class.java:308)
    at java.lang.Class.newInstance(Class.java:261)
    at
com.sun.corba.se.internal.iiop.messages.ReplyMessage_1_2.getSystemException(ReplyMessage_1_2.java:90)
    at
com.sun.corba.se.internal.iiop.ClientResponseImpl.getSystemException(ClientResponseImpl.java:105)
    at
com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:314)
    at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)

Reply to this Message

lqqchen - 16 Jun 2004 10:24 GMT

Hi,

You may try to run your program against other java ORBs (such as Jdk1.3,
Jacorb and etc) to see if your program is correct.

lqqchen

> Hi,
>
[quoted text clipped - 20 lines]
> Method)
> at

sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAcces
sorImpl.java:39)

> at

sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstruc
torAccessorImpl.java:27)

> at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
> at java.lang.Class.newInstance0(Class.java:308)
> at java.lang.Class.newInstance(Class.java:261)
> at

com.sun.corba.se.internal.iiop.messages.ReplyMessage_1_2.getSystemException(
ReplyMessage_1_2.java:90)

> at

com.sun.corba.se.internal.iiop.ClientResponseImpl.getSystemException(ClientR
esponseImpl.java:105)

> at

com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:31
4)

> at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)

Reply to this Message

John Black - 15 Jul 2004 17:55 GMT

[stuff deleted]

> > Hi,
> >
[quoted text clipped - 13 lines]
> >
> > - Andy -

Is it possible that your heap is not big enough? I have seen similar stack
traces in JacORB when I have deliberately tried to send huge octet sequences
without making the maximum heap size big enough. Perhaps the JVM's
-Xmx<size> option would help.

-John

Reply to this Message

Matthias Ernst - 16 Jul 2004 18:20 GMT

> All similar, older, method
> calls work just fine, only the new one reports an error.

Sorry, but that sounds a lot like you didn't update your server
implementation. BAD_OPERATION is the equivalent of a NoSuchMethodError.

Matthias

Signature

Matthias Ernst
CoreMedia - The Content Technology Experts

"Toll takes its time."

Reply to this Message

Problems with JDK 1.4.2_04 implementation

Free Magazines