-
Enhancement
-
Resolution: Won't Fix
-
P4
-
None
-
1.4.1
-
sparc
-
solaris_1
*******************************************************************************
###@###.### 2002-04-17
The current implementation does not have a upper limit on the poa queue size when poamanager is in hold state. Even though this allows any numbers of requests to be put in hold state, due to resource constraints in platforms like Windows and Linux, OutOfMemoryError is raised.
The spec suggests POA may raise CORBA_TRANSIENT exception if the queue size is reached to indicate that the client reissue the request.
But since this is implementation and platform dependent, a default finite queue size with an option to cofigure might be a better approach.
********************************************************************************
###@###.### 2002-04-17
The current implementation does not have a upper limit on the poa queue size when poamanager is in hold state. Even though this allows any numbers of requests to be put in hold state, due to resource constraints in platforms like Windows and Linux, OutOfMemoryError is raised.
The spec suggests POA may raise CORBA_TRANSIENT exception if the queue size is reached to indicate that the client reissue the request.
But since this is implementation and platform dependent, a default finite queue size with an option to cofigure might be a better approach.
********************************************************************************