I am not an expert, but, in my experience (with EAP 6.1), the clients were seeing "Server-side Exception: unknown oid" error when doing JNDI lookup on EAP 6.x server over IIOP and if the "orb" name and the initial string of the "root-context" don't match. For example, here, I have shown the snippet from standalone-full.xml file, look for the STRING_MUST_MATCH string. The strings there must match. If they don't match, I consistently see the "Server-side Exception: unknown oid" error with no further help.
I don't know why they should match though..... I only figured it by accident. HTH
Anonymous (Guest):
I am not an expert, but, in my experience (with EAP 6.1), the clients were seeing "Server-side Exception: unknown oid" error when doing JNDI lookup on EAP 6.x server over IIOP and if the "orb" name and the initial string of the "root-context" don't match. For example, here, I have shown the snippet from standalone-full.xml file, look for the STRING_MUST_MATCH string. The strings there must match. If they don't match, I consistently see the "Server-side Exception: unknown oid" error with no further help.
I don't know why they should match though..... I only figured it by accident. HTH
<subsystem xmlns="urn:jboss:domain:jacorb:1.3">
<orb name="STRING_MUST_MATCH" socket-binding="jacorb" ssl-socket-binding="jacorb-ssl">
<initializers security="identity" transactions="on">
</initializers></orb>
<naming root-context="STRING_MUST_MATCH/Naming/root">
</naming></subsystem>
3:20 a.m., Tuesday Aug. 27
Moderate this comment by email
Email address: anonymous@anonymous.com | IP address: 71.204.140.213
Reply to this email with “Delete”, “Approve”, or “Spam”, or moderate from the Disqus moderation panel.