7 Replies Latest reply: Apr 16, 2006 7:57 AM by 843844 RSS

    Sun One - Weblogic interoperability

    843844
      I have a web app on Sun One. I am trying to use an EJB on a weblogic server. I get the following error.

      Unexpected exception in LoginManagerHome:org.omg.CORBA.INITIALIZE: can't instantiate custom socket factory: weblogic.corba.client.cluster.ORBSocketFactory vmcid: 0x0 minor code: 0 completed: No

      I have added the weblogic jar and the wlclient.jar to the path. Can anyone point me in the right direction???
        • 1. Re: Sun One - Weblogic interoperability
          843844
          I have same issue. What was the resolution?
          • 2. Re: Sun One - Weblogic interoperability
            843844
            I have same issue. What was the resolution?
            Post some details - the lookup code, for example.
            • 3. Re: Sun One - Weblogic interoperability
              843844
              We are using spring to do lookup.

              <bean id="registrationService"
              class="org.springframework.ejb.access.SimpleRemoteStatelessSessionProxyFactoryBean2" lazy-init="true">
              <property name="jndiEnvironment">
                   <props>
                   <prop key="java.naming.factory.initial">
                   weblogic.jndi.WLInitialContextFactory
                   </prop>
                   <prop key="java.naming.provider.url">${regEJBURL}</prop>
                   </props>
              </property>
              <property name="jndiName">
              <value>ejb.PortalInterface</value>
              </property>
              <property name="businessInterface">
              <value>com.bcbsma.providerreg.ejb.portalinterface.ProviderPortalInterface</value>
              </property>
              </bean>
              • 4. Re: Sun One - Weblogic interoperability
                843844
                SimpleRemoteStatelessSessionProxyFactoryBean can be substituted for SimpleRemoteStatelessSessionProxyFactoryBean2.

                It's just overridden to correct a bug in spring m3 that's fixed in m4:

                package org.springframework.ejb.access;

                import java.util.Iterator;
                import java.util.Map;
                import java.util.Properties;

                import javax.naming.NamingException;

                public class SimpleRemoteStatelessSessionProxyFactoryBean2 extends
                          SimpleRemoteStatelessSessionProxyFactoryBean {

                     public void afterPropertiesSet() throws NamingException {
                          Properties properties = new Properties();

                          for (Iterator iter = getJndiEnvironment().entrySet().iterator(); iter.hasNext();) {
                          Map.Entry property = (Map.Entry) iter.next();

                          properties.setProperty((String) property.getKey(),(String) property.getValue());
                          }
                          setJndiEnvironment(properties);
                          super.afterPropertiesSet();

                     }

                }
                • 5. Re: Sun One - Weblogic interoperability
                  843844
                  What can I do if We do not use the Spring framework?
                  • 6. Re: Sun One - Weblogic interoperability
                    843844
                    Spring framework is going to do all the normal stuff. The problem is with the config I think.
                    • 7. Re: Sun One - Weblogic interoperability
                      843844
                      I will look into the config part and will post my results