cancel
Showing results for 
Search instead for 
Did you mean: 

EJB shows "UnsatisfiedReferenceImpl" in VA JNDI Registry

darcy_curtin
Explorer
0 Kudos

I have a ejb that I am using in J2EE and non-J2EE (portal application). The EJB seems to work fine in both cases [local and remote].

When I use VA's JNDI browser (Visual Administrator->JNDI Registry) and drill down to Bean there are two entries "Class Name" and "Object Value".

Values are

"Class Name" ==> "com.sap.engine.services.jndi.persistent.UnsatisfiedReferenceImpl"

"Object Value" ==> "com.sap.engine.services.jndi.persistent.UnsatisfiedReferenceImpl@19beb53 Returned because an Exception occured in deserialization process:[java.lang.ClassCaseException]

Is this a problem in bean implementation?

How to fix this problem?

why is bean working (or is not)?.

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

SvetoManolov
Employee
Employee
0 Kudos

Hello,

there is no problem with the bean - it does work. The problem you found is the unability of the Visual Administrator to load bean classes for the remote interfaces and thus to show meaningful Class names and to deserialize object values.

The exception you see is no longer there. In the last version of the Engine (I checked SP12) the information in the JNDI tree is the following:

local beans (can be found below localejbs JNDI context):

"Class Name" ==> <the real class name>

"Object Value" ==> "NON Serializabble Object"

remote beans:

"Class Name" ==> "com.sap.engine.interfaces.cross.ObjectReferenceImpl"

"Object Value" ==> <the remote object ID>

Anyway the information about the bean references in the JNDI is not very helpful, unless the fact that the object exists in the JNDI and is bound to the corresponding name.

Regards,

Svetoslav

darcy_curtin
Explorer
0 Kudos

Svetoslav, Thanks for clarification.

Answers (0)