lucee.runtime.spooler.SpoolerEngineImpl EOFException

dev support
1

I think it’s been a couple years since the forum hosted an issue like this one.

After upgrading to 6.1.0.243 we’re getting these in our application logs:

"ERROR","Thread-100468","11/07/2024","11:04:13","lucee.runtime.spooler.SpoolerEngineImpl","java.io.EOFException;java.io.EOFException

FWIW, The app sends a handful of messages to AWS every few minutes, and these seem to coincide with that event. It would be nice to know what [F]ile it considers to be [EO] :wink:.

I’ve seen some chatter about file or folder permissions possibly being the cause of this, but I don’t know what or where the spooler requires access. Anyone know more?

I’ve also seen comments that this is not an important message, which makes me wonder why Lucee considers it worthy of “ERROR” status.

Ideas welcome, and thanks,
AL

Linux (5.4.0-200-generic) 64bit
11.0.24 (Ubuntu) 64bit
Apache Tomcat/9.0.95
Lucee 6.1.0.243

2

Full Stack:

"ERROR","Thread-101961","11/07/2024","11:18:04","lucee.runtime.spooler.SpoolerEngineImpl","java.io.EOFException;java.io.EOFException
	at java.base/java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2911)
	at java.base/java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3406)
	at java.base/java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:932)
	at java.base/java.io.ObjectInputStream.<init>(ObjectInputStream.java:375)
	at lucee.runtime.converter.JavaConverter$ObjectInputStreamImpl.<init>(JavaConverter.java:127)
	at lucee.runtime.spooler.SpoolerEngineImpl.getTask(SpoolerEngineImpl.java:205)
	at lucee.runtime.spooler.SpoolerEngineImpl.getTaskByName(SpoolerEngineImpl.java:195)
	at lucee.runtime.spooler.SpoolerEngineImpl$SpoolerThread.run(SpoolerEngineImpl.java:466)
"