Ive been asked by our developers about the possible impact of increasing  FP_OPTION_MAXCONNECTIONS to 200 in relation to a recurring problem (im not a developer..i only support the hardware).

Apparently applications reading >100pages at a a time have regularly returned 10-15% of the pages as corrupt gibberish.

This has not been a problem in the past with very few records being written this large..but is now becoming a problem.

Previously for one offs the developers have a script to pull large records one page at a time.

Its been suggested that the FP_OPTIONS_MAXCONNECTIONS setting (currently left to the 100 default) be increased to 200.

Any comments on the problem , if this is right direction to go on ...or if this parameter will bring other peformance improvement or degredation??

The original notes from th developers attached below.

Thanks

Marc

We are planning to set the MaxConnections per FPPool object used to 200. Currently we use 1 FPPool object per Weblogic cluster node.

Currently we have 4 weblogic clusters in production so totally WorkSmart can have 800 connections(at max) with Centera.The SDK will initially allocate a smaller number of connections and allocate more (up to the limit) when required.

We are using the FPLibrary(Centera SDK) to open connections

The existing code snippet

com.filepool.fplibrary.FPPool;

centeraConnectionPool

= new FPPool(poolAddress + "?" + peaFileLocation);

For production we use the following 2 entries in the config file

%CENTERA_PEA_FILE_LOCATION%=/opt/Centera_SDK/wms_prod-rw.pea

%CENTERA_POOL_ADDRESS%=centera02.production.local

we looked into the API document of FPPool.After API analysis found

1. we set only one global option

"openstrategy" to 0

2. we are not setting

FP_OPTION_MAXCONNECTIONS Global option on the FPpool object.

FP_OPTION_MAXCONNECTIONS

("maxconnections") - The maximum number of connections in the connection pool maintained by the FPPool object. If your application uses multiple threads, each thread will use a separate connection up to the limit specified here. The default value is 100; the maximum value is 999. To take advantage of this feature, the application must use multiple threads against a single FPPool object.

Daeja viewer uses ImageRetrievalServlet to retrieve individual pages from Centera using Document Retrieval Service (multithreaded access to FPPool)

Newly added code snippet

Currently we have added the following code to set the Max Connections global option to 200.

FPPool.setGlobalOption(FPLibraryConstants.

FP_OPTION_MAXCONNECTIONS, 200);

Please let us know if this change is fine with Centera.