JacORB Error in JBOSS 4.0.1.RC2 when run in Clustering Mode
JBOSS Server 4.0.1 RC2
*********************
The application deploys succesfully. The application requires to connect to the weblogic server and then to the oracle server for auithentication. Authentocation fails and the Log FIle says
INFO [ 2005-04-01 09:44:51,656] - [INFO]-[http-0.0.0.0-8080-Processor23] [ jacorb.home unset! Will use '.' ]
INFO [ 2005-04-01 09:44:51,656] - [INFO]-[http-0.0.0.0-8080-Processor23] [ File .\jacorb.properties for configuration jacorb not found ]
INFO [ 2005-04-01 09:44:51,656] - [INFO]-[http-0.0.0.0-8080-Processor23]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JacORB V 2.2 (JBoss patch 3), www.jacorb.org
(C) Gerald Brose, XTRADYNE Technologies/FU Berlin, 06-Oct-2004
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
INFO [ 2005-04-01 09:44:51,656] - [INFO]-[http-0.0.0.0-8080-Processor23] Property "jacorb.hashtable_class" not present. Will use default hashtable implementation
INFO [ 2005-04-01 09:44:51,703] - [INFO]-[http-0.0.0.0-8080-Processor23] javax.naming.InvalidNameException: Couldn't resolve initial reference: NameService. Root exception is
INFO [ 2005-04-01 09:44:51,703] - [INFO]-[http-0.0.0.0-8080-Processor23] org.omg.CORBA.ORBPackage.InvalidName
INFO [ 2005-04-01 09:44:51,703] - [INFO]-[http-0.0.0.0-8080-Processor23] at org.jacorb.orb.ORB.resolve_initial_references(Unknown Source)
INFO [ 2005-04-01 09:44:51,703] - [INFO]-[http-0.0.0.0-8080-Processor23] at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
INFO [ 2005-04-01 09:44:51,703] - [INFO]-[http-0.0.0.0-8080-Processor23] at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
INFO [ 2005-04-01 09:44:51,703] - [INFO]-[http-0.0.0.0-8080-Processor23] at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
INFO [ 2005-04-01 09:44:51,703] - [INFO]-[http-0.0.0.0-8080-Processor23] at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
INFO [ 2005-04-01 09:44:51,703] - [INFO]-[http-0.0.0.0-8080-Processor23] at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
INFO [ 2005-04-01 09:44:51,703] - [INFO]-[http-0.0.0.0-8080-Processor23] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
INFO [ 2005-04-01 09:44:51,703] - [INFO]-[http-0.0.0.0-8080-Processor23] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
INFO [ 2005-04-01 09:44:51,703] - [INFO]-[http-0.0.0.0-8080-Processor23] at javax.naming.InitialContext.init(InitialContext.java:219)
INFO [ 2005-04-01 09:44:51,703] - [INFO]-[http-0.0.0.0-8080-Processor23] at javax.naming.InitialContext.(InitialContext.java:195)
INFO [ 2005-04-01 09:44:51,703] - [INFO]-[http-0.0.0.0-8080-Processor23] at com.wyndham.foundation.helper.JNDILookups.getInitialContext(JNDILookups.java:79)
INFO [ 2005-04-01 09:44:51,703] - [INFO]-[http-0.0.0.0-8080-Processor23] at com.wyndham.foundation.helper.AbstractServiceLocator.getRemoteHome(AbstractServiceLocator.java:195)
...
...
.and a lot more
The same application works fine when run in default mode.
Any suggestions, can i turn off CORBA NAming Service, dont think i need it as when run on default mode the app works fine, How do i turn off Corba Naming Service