users@glassfish.java.net

Glassfish sending invalid corbaloc:iiop message to client

From: <glassfish_at_javadesktop.org>
Date: Thu, 13 Dec 2007 11:13:20 PST

I am seeing problem with glassfish sending invalid corbaloc.iiop message to client. The correct formate should be "corbaloc:iiop:1.2_at_localhost:8080/OurLittleClient", but sends "corbaloc:iiop:1.2_at_localhost:8080/OurLittleClient/". Is anyone know how to modify this on glassfish side? I am seeing this message on Client side trace, Is anyway I can get a ORB trace on glassfish side? I have tried the method provided in Sun Java System Application Server document, but none of them works.

Following is the stack trace i am seeing

The server side registers an intial reference corbaloc:iiop:1.2_at_localhost:8080/OurLittleClient.
On the client side, using the same INS URL and calling
orb.string_to_object('corbaloc:iiop:1.2_at_localhost:8080/OurLittleClient') passes the testcase.

But if the INS URL is 'corbaloc:iiop:1.2_at_localhost:8080/OurLittleClient/' and using the Sun JDK version
java version '1.6.0_03'
Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode)

the exception thrown is
Caused by: org.omg.CORBA.OBJ_ADAPTER: ----------BEGIN server-side stack trace---
-------

>> SERVER (id=270d2533, host=9.122.20.37) TRACE START:
>> org.omg.CORBA.OBJ_ADAPTER: vmcid: IBM minor code: B81 complete
d: No
>> at com.ibm.rmi.iiop.ORB.process(ORB.java:496)
>> at com.ibm.CORBA.iiop.ORB.process(ORB.java:1553)
>> at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2680)
>> at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2554)
>> at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:62)
>> at com.ibm.rmi.iiop.WorkerThread.run(ThreadPoolImpl.java:202)
>> at java.lang.Thread.run(Thread.java:803)
>> SERVER (id=270d2533, host=9.122.20.37) TRACE END.

----------END server-side stack trace---------- vmcid: 0x4942f000 minor code:
2945 completed: No
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at com.sun.corba.se.impl.protocol.giopmsgheaders.MessageBase.getSystemEx
ception(MessageBase.java:902)
        at com.sun.corba.se.impl.protocol.giopmsgheaders.ReplyMessage_1_2.getSys
temException(ReplyMessage_1_2.java:99)
        at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.getSystemExce
ptionReply(CorbaMessageMediatorImpl.java:572)
        at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.proce
ssResponse(CorbaClientRequestDispatcherImpl.java:430)
        at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.marsh
alingComplete(CorbaClientRequestDispatcherImpl.java:326)
        at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaCl
ientDelegateImpl.java:129)
        at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClie
ntDelegateImpl.java:213)
        at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
        at com.sun.corba.se.impl.javax.rmi.PortableRemoteObject.narrow(PortableR
emoteObject.java:218)

This exception stack trace is the same as reported in this defect it originates from a string_to_object call, which results in an _is_a request and fails due to
 an invalid OBJ_ADAPTER id.
[Message sent by forum member 'firstcong' (firstcong)]

http://forums.java.net/jive/thread.jspa?messageID=249988