search

Norconex / jef-monitor

Web-based application for monitoring jobs progress (created with JEF).
4 stars 3 forks source link

Norconex http Collector won't start with jef monitor running #5

Closed murdock71 closed 7 years ago

murdock71 commented 7 years ago

Whenever I leave jef monitor running my collector won't start.

The error I receive says that the file is locked by another process. As soon as I stop jef monitor everything works as expected and I can restart the monitor once the collection has begun.

Is this expected behavior? Is there a way to allow the monitor to keep running while still allowing indexing to take place? Or do I have to start and stop the monitoring app each time?

Thank You

essiembre commented 7 years ago

Which version of both are you using? File locking was purposely introduced in the snapshot versions to solve other issues, but JEF monitor should be able to read the files without causing issues (else we'll fix).

murdock71 commented 7 years ago

The collector is 2.6.0 which I know was the stable version when I downloaded it. JEF monitor is 4.0.4, although looking at the release date of that becoming stable I wonder if I didn't get a snapshot version.

How can I tell for certain?

If I do indeed have the snapshot version I assume I can download the new one and overwrite everything but the config folder and it should just work?

Thank You

essiembre commented 7 years ago

Usually when you run the collector, the first few lines should list the versions in use. You can upgrade a release, but I would not just overwrite the files since you will have duplicates (e.g., same Jars, but different versions). So maybe backup the lib folder and and replace it. For the collector, make sure to reinstall your committer libraries.

You can also install in a different location and just copy your configs over.

essiembre commented 7 years ago

I think I was able to reproduce and fix the locking issue you experienced. The latest snapshot version of both HTTP Collector and Filesystem Collector as well as the latest JEF Monitor snapshot release contain the fix. You will need to update both your collector and JEF Monitor.

Please confirm.

essiembre commented 7 years ago

The fix is in the stable 4.0.5 release.