Posted by Jim Barbaruolo on July 06, 2007 at 09:35:25:
We ran into a problem this morning where a customer of ours lost access to a configured Comet directory. Everyday they manually add and delete text files to and from this directory, sometimes leaving no files (except the 2 QDIR files). In order to update the dir QDIRs they run a QDIR rebuild prgm. This morning they received an error when their application prgm attempted to open a text file on this directory. After investigating I found the directory was not accessed and I could not access it not matter what I did. The directory existed with one text file and the 2 QDIR files.
The Comet Startup log reported it was finding the directory without any problem, yet it was not accessible from Comet not matter what I did. I deleted the entire directory (from Windows) and re-ran Comet but still, no start up warning that it could not find the QDIRs for the directory?? Very strange, never seen this before!
I then recreated the directory/folder in Windows, ran Comet and created the Comet directory in Q/45. Comet created the QDIRs in the folder but was still not allowing access to the directory even after starting Comet!
To test further, I renamed another currently accessed Comet directory to another name (in windows). When I re-started Comet there was no startup warning that it could not find this directory either.
We had to re-boot the Comet Server in order to correct the problem.
Seems to be some sort of a caching problem.
The customer has been running Comet 2007/.380 with CometServerProducts 7.01 since mid May without any problems. Has anyone seen this before?
Thanks in advance,
Jim Barbaruolo