…. and what would be the reason for any Java Client calling Weblogic, not to use oracle recommended way, faster Client "t3 thin client“ with include Cluster Support and developed for 3-td part JEE App servers :-)
According to oracle interoperability list Java SE IIOP Client is without web logic cluster support.
https://docs.oracle.com/middleware/1221/wls/SACLT/basics.htm#SACLT121 ( -> look for  Foreign Server Applications )


Of cours the best would be to move Application to Wildfly and just call Wildfly :-)

Cheers Radek

Am 14.02.2016 um 23:40 schrieb Michael Musgrove <mmusgrov@redhat.com>:

I am attempting to lookup a remote EJB from WildFly to WLS.

If I use COSNaming as required by [1] (by setting INITIAL_CONTEXT_FACTORY to "com.sun.jndi.cosnaming.CNCtxFactory") I get the following error on the WildFly end:
  "ClassNotFoundException: com.sun.jndi.cosnaming.CNCtxFactory"

If I use the default wildfly name service (new InitialContext().lookup("corbaname:iiop:localhost:7001/NameService#SessionBean")) I get the following error on the WLS end (presumably because I am not using CNCtxFactory):
  "A RuntimeException was generated by the RMI server: weblogic.corba.cos.naming.RootNamingContextImpl.resolve([Lorg.omg.CosNaming.NameComponent"

I did try adding the CosNaming dependency (<path name="com/sun/jndi/cosnaming"/>) to modules/system/layers/base/sun/jdk/main/module.xml or to jboss-deployment-structure.xml in my deployment but that approach did not work.

[1] row 3 of Table 2-1 in https://docs.oracle.com/cd/E13222_01/wls/docs81/rmi_iiop/rmiiiop2.html

Michael Musgrove
Transactions Team
t: +44 191 243 0870

Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham (US), Paul Hickey (Ireland), Matt Parson
(US), Charles Peters (US)

Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Michael O'Neill(Ireland)
wildfly-dev mailing list