Filter
Top Products
Restrictions on the CORBA Service
2-19
Restrictions on the CORBA Service
Table 2-12 Restrictions on the CORBA Service
No. Restriction Alternative
Method
Date of
Removal
1
The system may not release the CORBA Service port
number (eg, 8002) when the isstop command is run.
When the OD_start service was started (including
execution of the isstart command) in this status, it is
possible that a communication error occurs in the
application.
Use the netstat
-a command to
check that the
CORBA Service
port number
has been
released then
start the
service.
Not
determined
2
If the OD_start service is terminated before a CORBA
application is terminated, the system may stop
responding or "hang" while the CORBA application is
terminated.
Terminate all
CORBA
applications
before
terminating the
OD_start
service.
Not
determined
3 When the server per method is used for starting a
CORBA application, starting the CORBA application may
fail.
None Not
determined
4
In Windows NT® Server with Service Pack 5, when
simultaneous requests are issued by a client that has
generated multiple threads and a communication error
(COMM_FAILURE exception) occurs, the system
resources used by the CORBA Service may not be
released.
This will show up as repeated communication errors,
followed by all requests from client applications causing
communication errors.
It is necessary
to stop and
restart the
CORBA
Service.
Not
determined
5 When the dynamic skeleton interface of C++ language is
used with the server application, memory leak occurs.
(Approximately 150 bytes for a request)
None Not
determined
6 The odlistproc process may output the message od10727
while quitting the CORBA service (ObjectDirector).
None
No operation
problems other
than output
messages
Not
determined