
UNSOLVED
Relationship between threads and FP_OPTION_MAXCONNECTIONS
Hi,
I've inherited an application that calls out to Centera. The application is clustered across 4 weblogic nodes. As far as I can work out from the (Java) code a single FPPool object is created within each node - so 4 FPPool objects are used across the clustered app. There are only 2 threads within the app that use the pool (basically driven by single instance MDBs each consuming messages from a separate JMS queue). So in total I think there are 8 threads across the cluster that are trying to access the pool.
I've also discovered that the FP_OPTION_MAXCONNECTIONS is set (globally) to 500. Apart from the value being set in the code there is no indication of why this figure was chosen. Can anybody tell me what this actually means?
Secondly - from what I've read about Centera so far - I think we are using too few threads to call into the SDK. We need to store several thousand smallish files every day. I think we have 2 Access Nodes, so I'm guessing we could go up to about 40 threads in total across the cluster (presuming no other App is also accessing the AN) would provide more efficient use of the resources?
And finally - I understand the reason the number of threads accessing the SDK has been throttled is because historically the application logs are filled with exceptions thrown when trying to call the SDK's writeBlob method. This was attributed to the 'flaky' product and the SDK's management of the connections to the physical cluster. I'm not sure this is the case - so any indication of how I can start to investigate these errors would be greatly received.
thanks in advance.
Responses (0)
Solutions (0)
