[Babeldoc-devel] Some JMX stuff...

[Michael A. <mic...@ze...>]

Hi, all,

I've noticed a small anomoly under a particular condition.  When I start
JBoss, the babeldoc.home variable isn't set.  Before I start running
docs through the JMX scanner, I normally set the babeldoc.home, restart
the scanner, and all is well.  Sometimes, however, I forget to set
babeldoc.home.  When I run the first document through, it gets picked
up, queued, deleted from the source directory (I'm using a directory
scanner), and then babeldoc errors, because it presumably can't find the
babeldoc.home, so it doesn't know where the processing libraries are. 
This is all fine.  So, I stop the scanner using jmx-console, set the
babeldoc.home, and start the scanner again.  Now, I get a persistent
error:

23:31:27,958 ERROR [DiskQueue] [DiskQueue.removeNoWait]
java.io.FileNotFoundException: ./scanner22096.tmp (No such file or
directory)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.<init>(FileInputStream.java:106)
        at
com.babeldoc.core.pipeline.feeder.DiskQueue.deserializeDocument(Unknown
Source)
        at
com.babeldoc.core.pipeline.feeder.DiskQueue.removeNoWait(Unknown Source)
        at com.babeldoc.core.pipeline.feeder.DiskQueue.remove(Unknown
Source)
        at
com.babeldoc.core.pipeline.feeder.AsynchronousFeeder$1.run(Unknown
Source)
        at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:727)
        at java.lang.Thread.run(Thread.java:534)

And it just goes on and on until I stop the scanner.  I'm not sure
what's going on here, but it looks like a reference is being left in a
queue somewhere, but the file underneath the reference is being
deleted.  I'm not sure what I should do here?  Does the feeder need some
debugging?  Or is this acceptable behaviour?  If so, what escape
mechanism can I use that will allow the user to stop this, without
restarting the whole application server?

Cheers...


MikeA

PS: I have since made it so that the scanner sets the correct
babeldoc.home automatically on startup, but I still need to resolve the
base problem.