Fujitsu V6.0 manual Restrictions on the Corba Service

Restrictions on the CORBA Service

Restrictions on the CORBA Service

Table 2-12 Restrictions on the CORBA Service

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

2-19