Yes, the error can indeed be mystifying.
Briefly, GlassFish detected that a stream to an application file was opened
but never explicitly closed. The stack trace shows where the stream was
opened as a hint about what part of the code might need to close it too.
This message is a warning, but for some reason the load operation failed.
(It looks as if a previously-deployed app is being reloaded during server
start-up. Is that right?) The two messages are very close in time (.007 s
apart) so it looks as if the warning caused load to fail, which it should
not.
Does this happen on every restart with this app deployed? Were there other
errors in the log file just before or just after this one? (I know you
mentioned the URI length problem which you resolved.)
- Tim
--
[Message sent by forum member 'tjquinn']
View Post: http://forums.java.net/node/789009