Views:

 Behavior:
After updating DocuWare to Version 6.5 or newer, it can happen that many .input and .sorted files are stored in the Fulltext Server temp path and are not deleted automatically.

Solution:
These files are needed during the fulltext catalog creation process. If they are not deleted, you have to allocate more memory to the Fulltext Server, so that these files can be deleted properly. Additionally, a resource wasting feature should be disabled. Please follow the steps below to solve this issue.

1. Deactivate an unused and resource wasting feature:

With the changes to the solrconfig.xml file described here, you can deactivate a feature, which is activated by default, but not yet used by DocuWare. This wastes resources and it may be a factor in causing the behavior described above.
You can typically find the file at "C:\Program Files (x86)\DocuWare\Full-Text Server\webapps\solrt\solr\conf". Please adapt the file as shown (highlighted) in the screenshot below.

2. Assign more memory to the Fulltext Server:

Navigate to the “Fulltext Server” path and run the program “configdwtomcat.cmd“. Then click on the “JAVA” tab and change the “Initial memory pool“ and “maximum memory pool“ to 1225 MB (see screenshot down below):
*Note: If you assign more memory the Fulltext Server will not start!

 

3. Delete .input and .sorted files / Verify:

Stop the Fulltext Server and manually delete all .input and .sorted files from Fulltext Server temp directory. After that start the Fulltext Server, so that the new settings can take effect. According to our experience the files .input and .sorted files are deleted after creation. Occasionally check this folder for .input and .sorted files, it should only remain there temporary and delete afterwards. If the files are not deleted automatically contact us for further steps.

4. Process after manually deleted .input and .sorted files:

The manually deleted .input and .sorted files have to be processed again. Therefore reset the Fulltext status for the file cabinet with the option “Reindex not processed or failed documents” in the DocuWare Administration under specific file cabinet (see screenshot down below).

Comments (1)
  • The settings are too high for some systems. I have not tested it on all but for 64bit VM I have set them this high and they have issues.  I have tried Pool at 1000 and Max at 1000 with good results on smaller cabinets (<1 million pages) and I have used Pool of 100 and a Max of 1000 with very good results on larger cabinets. Both of these are connected to the same enterprise system and work very well. I have found balancing the load the most difficult thing to do.