Questions about input/output buffSize.

Problem:

• Product Version: VBC 4.5 Full
• Platform Version: ALL
• JDK Version: NA
• Compiler Version: NA
• Product Component: ORB

Questions about input/output buffSize:

1. What is the actual size of each buffer listed below?
   vbroker.orb.input.buffSize
   vbroker.orb.ouput.buffSize
2. Can each buffer hold multiple IDL calls?
3. When all buffer are full, we have seen situations where the ORB appears to "dispatch" all queue up requests in a very short period of time. Could you confirm this behavior?
4. Does ORB dispatch all inbound TCP requests immediately to these ORB buffers? That means ere is no delay in TCP level.

Resolution:

1. What is the actual size of each buffer listed below?
   vbroker.orb.input.buffSize
   vbroker.orb.ouput.buffSize
Answer: Both of these buffers are initialized to a size of 255 bytes. If the data to be read in is larger than this size, it is re-sized to fit the payload.

2. Can each buffer hold multiple IDL calls?
Answer: No, these buffers are for single invocation. Once the use of these buffers is over, they are put back into a pool. By default the buffer pool can hold 16 such buffers. This can be configured by the properties vbroker.orb.input.maxBuffers and vbroker.orb.output.maxBuffers.

3. When all buffers are full, there have been situations where the ORB appears to "dispatch" all queue up requests in a very short period of time. Please confirm this behavior?
Answer: When the buffer pool is not empty, an incoming request is read into a buffer picked up from the buffer pool. If however, the buffer pool is empty, a new buffer is created dynamically. Once the request has been read in, it is dispatched to the dispatcher. There is no relationship between buffer pool being full and requests being dispatched earlier.

4. Does ORB dispatch all inbound TCP requests immediately to these ORB buffers? That means ere is no delay in TCP level.
Answer: When a request is expected on a GIOP connection, it is said to be "hot". A "hot" GIOP connection is then read for the incoming message into a buffer from the buffer pool. After the message is completely read, it is then dispatched on to the dispatcher.