On 12/12/2013 17:38, Laurent Bourgès wrote:
Alan,
Thanks for creating the bug 9005822 !
The logging bug we created is JDK-8029834
:
I think this bug should be converted into a more general shutdown hook
issue:
- execute first application hooks (not JVM ones)
- fix priorities / order
Alan,
Thanks for creating the bug 9005822 !
As I spotted in my initial email, both shutdown hook problems (JavaWS and
JUL) are due to the concurrent execution of shutdown hooks :
com.sun.imageio.stream.StreamCloser.java
101: Runtime.getRuntime().addShutdownHook(streamCloser);
Anybody wants to look at this logging issue I reported several months ago?
Le 27 juin 2013 11:57, Laurent Bourgès bourges.laur...@gmail.com a
écrit :
Dear members,
I have a problem within an external library using one JVM Shutdown hook
to perform resource cleanup (socket, lock file deletion
Given that this issue has existed (and been known) since 1.4, I doubt
anyone is particularly inclined to fix it. The most common workaround I
know of is to simply use or create a LogManager that implements reset()
as a no-op. Just subclassing the built-in LogManager is sufficient to
do this.
On 09/12/2013 17:59, Laurent Bourgès wrote:
Anybody wants to look at this logging issue I reported several months ago?
Your previous mail mentioned 9005822, this seems to be an incident
submitted to Java Web Start rather than java.util.logging.
I couldn't a specific bug on the topic so I've
