Is there some limitation for the numbers of CORBA objects under Java IDL

Question

Operation System : Windows 98 Second Edition(4.10.2222)
Java 2 SDK version :
java version "1.4.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-b21)
Java HotSpot(TM) Client VM (build 1.4.1-b21, mixed mode)
I have programmed a distributed application with java IDL.
there are a lot of CORBA objects in my application and all of those objects must registered with the same orb.
At the beginning,I launched 4 CORBA objects,which is the least number of CORBA objects needed to run my application,and the application runs well.Then I increased the number of CORBA objects gradually.But when the number of CORBA objects has been changed to 6,the application runs instably,that is, the application sometimes runs well,and sometimes it generates an error when I launched my client-side program,the error is as follow:
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
at com.sun.corba.se.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:161)
at com.sun.corba.se.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:65)
at com.sun.corba.se.internal.iiop.GIOPImpl.getConnection(GIOPImpl.java:67)
at com.sun.corba.se.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:644)
at com.sun.corba.se.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:586)
at com.sun.corba.se.internal.corba.ClientDelegate.is_a(ClientDelegate.java:838)
at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
at org.omg.CosNaming.NamingContextExtHelper.narrow(NamingContextExtHelper.java:73)
at Client.main(Client.java:19)
the NO.19 line in Client.java is :
NamingContextExt ncref = NamingContextExtHelper.narrow(comobj);
The COMM_FAILURE/SUN-201 means CONNECT_FAILURE.
This will happen if a client gets a reference to an object reference whose server is not yet started,or perhaps not yet initialized.
But I think I have waited for enough long time before launched Client.java?Can anybody help me?Thanks very much....

Answer 1

We are trying to connect to corba naming services using Apache/Tomcat5.0 .We are using servlets to call the Corba services.
We are initializing the ORB as follows:
Properties p= new Properties();
p.setProperty("org.omg.CORBA.ORBInitialHost","ramesh");
p.setProperty("org.omg.CORBA.ORBInitialPort","1234");
p.setProperty("org.omg.CORBA.ORBClass","com.sun.corba.se.internal.iiop.ORB");
ORB orb = ORB.init((String[])null,p);
nmref = NamingContextHelper.narrow(orb.resolve_initial_references("NameService"));
NameComponent[] dmNamingComps ={new NameComponent("DATAMgt","")};
DataManagement.DatamanagementFactory data_factory_ref= DataManagement.DatamanagementHelper.narrow(nmref.resolve(dmNamingComps ));
masterDataref = data_factory_ref.createMasterData();
=====================
when we run the program:
we are getting the error message:
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
at com.sun.corba.se.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:161)
at com.sun.corba.se.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:65)
at com.sun.corba.se.internal.iiop.GIOPImpl.getConnection(GIOPImpl.java:67)
at com.sun.corba.se.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:644)
at com.sun.corba.se.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:586)
at com.sun.corba.se.internal.corba.ClientDelegate.is_a(ClientDelegate.java:838)
at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
at org.omg.CosNaming.NamingContextExtHelper.narrow(NamingContextExtHelper.java:73)
at Client.main(Client.java:19)
Can anybody help ?Do we need any other configuration setup apart from the code in Apache/Tomcat?