Exception while client is doing a lookup for Entity beans

[Shivakanth Thyagarajan]

Dear Ranchers,
I am running a simple Entitybean on J2EE 1.3, when my client is doing a lookup i am encoutering the following exception. I have set the classpath with the jar generated for the bean. I was trying to search in google i could find similar problems posted in various forums, but there was no specific answers. I am using the default cloudscape database, i have set every thing to default, i have generated default query.




javax.naming.CommunicationException: java.rmi.MarshalException: CORBA MARSHAL 13
98079699 Maybe; nested exception is:
org.omg.CORBA.MARSHAL: Unable to read value from underlying bridge : m
inor code: 1398079699 completed: Maybe
org.omg.CORBA.MARSHAL: Unable to read value from underlying bridge : minor cod
e: 1398079699 completed: Maybe
at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_value(CDRInput
Stream_1_0.java:1083)
at com.sun.corba.ee.internal.iiop.CDRInputStream.read_value(CDRInputStre
am.java:296)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.lo
okup(Unknown Source)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:120
)
at javax.naming.InitialContext.lookup(Unknown Source)
at BonusClient.go(BonusClient.java:17)
at BonusClient.main(BonusClient.java:10)

at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:138
)
at javax.naming.InitialContext.lookup(Unknown Source)
at BonusClient.go(BonusClient.java:17)
at BonusClient.main(BonusClient.java:10)

Thanks
Shivakanth.T

[Rahul Mishra]

Dump your namespace and check..if the place where you are looking up the EJB is the place where it is actually bound

You can dump the namespace by calling dumpnamespace.bat.

[Shivakanth Thyagarajan]

Hi Rahul
Thanks for your response, but i am running with j2sdkee1.3.1 server, i presume the dumpnamespace.bat is used for websphere.

Thanks
Shivakanth

[Frederic Esnault]

The exception says Marshall exception.

Marshalling is the process that occurs when data is being "serialized" before being sent over the network. This happens, for example, when you call a business method on a component interface and give some parameters, or when you receive the returned value.

A marshalling exception means that the container was unable to perform this serialization process. I recommand that you check that all the types you use in your home/component interfaces (espacially in the home interface because this happens when you do a lookup, so when it tries to send you the home stub) are shippable (ie complies with the RMI/IIOP restrictions).

Shippable types :

primitives;

serializable objects;

arrays/collections of primitives or serializable objects;

remote objects.

Hope this helps.

[Shivakanth Thyagarajan]

Hi Fred
I have only primitive and a String as my arguments both in home and no argument in component interface. String is Serializable, hence there should be any problem. I am assuming that the problem might be with the server. If any of you encountered this problem. Please write to me.

Thanks
Shivakanth.T

[Shivakanth Thyagarajan]

Please respond

Thanks
Shivakanth.T

[Frederic Esnault]

Try to ensure that your String is neither null nor zero length (empty).

Does it help?

[Shivakanth Thyagarajan]

Hi Fred
I am sending a string value populated. Should it be a problem of the server. Why i am stressing is that i am continously searching for a similar topic in google. I could found many topic within Javaranch but no answer has been provided to those question. It does make be believe this problem has been reproduced many a time but only the guys who were able to solve could answer to this.

Thanks

Shivakanth.T

[Frederic Esnault]

Could you send me your source code (everything, ejb-jar.xml included) and also your ear file so that I can try to see if it works here and if i can find an answer?

My mail is: esnault (dot) frederic (at) gmail (dot) com