Limiting the Number of Components Per Request 

Use

Because of looping applications, missing endRequest() calls, or endRequest() calls with a wrong request name, too many components can be added to a request. To avoid an overflow, use this procedure to limit the number of components for each request.

Procedure

...

       1.      Start the J2EE Engine Visual Administrator.

       2.      Choose Server → Services → Performance Tracing → Properties tab.

       3.      Select the jarm/maxreqcomplow and modify its value.

If the specified number is exceeded, the next endRequest() call will finish the request even if the name does not match. A subsequent getRequestMonitor() call then gets a new monitor object. Calls using the old object are skipped.

Using this property has one weakness – if no endRequest() is done, the number of components will still increase. Therefore, also complete the next step to entirely limit the number of components.

       4.      Select the jarm/maxreqcomphigh property and modify its value.

If the specified number is exceeded, the next startComponent() or endRequest() call will end the request. Subsequent calls to the closed monitor object are skipped.