Here it is, I am not crazy!!!
It seems that some sort of AWT timer has been used in GF.
[#|2007-09-17T17:02:24.891+0100|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Application
server startup complete.|#]
[#|2007-09-17T17:03:30.696+0100|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=13;_ThreadName=TimerQueue;_RequestID=71b7ea44-9c3a-4830-868c-70943b46e62d;|Exception
in thread "TimerQueue" |#]
[#|2007-09-17T17:03:30.702+0100|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=13;_ThreadName=TimerQueue;_RequestID=71b7ea44-9c3a-4830-868c-70943b46e62d;|java.lang.InternalError:
Can't connect to X11 window server using 'localhost:11.0' as the value
of the DISPLAY variable.
at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
at
sun.awt.X11GraphicsEnvironment.access$100(X11GraphicsEnvironment.java:52)
at
sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:155)
at java.security.AccessController.doPrivileged(Native Method)
at
sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:131)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at
java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:68)
at sun.awt.X11.XToolkit.<clinit>(XToolkit.java:89)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at java.awt.Toolkit$2.run(Toolkit.java:836)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:828)
at java.awt.Toolkit.getEventQueue(Toolkit.java:1678)
at java.awt.EventQueue.invokeLater(EventQueue.java:954)
at javax.swing.SwingUtilities.invokeLater(SwingUtilities.java:1264)
at javax.swing.Timer.post(Timer.java:562)
at javax.swing.TimerQueue.postExpiredTimers(TimerQueue.java:198)
at javax.swing.TimerQueue.run(TimerQueue.java:234)
at java.lang.Thread.run(Thread.java:619)
|#]
Piero Filippin wrote:
> Hi,
> I am having a weird problem in Glassfish (58b) on Linux.
>
> Basically, I have noticed Glassfish dying without any apparent reason
> (nothing on the log) after a random time (usually in 5 minutes), so I
> started running it in debug mode, and I found:
>
>
> [#|2007-09-07T08:56:45.226+0100|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Application
> server startup complete.|#]
>
> ... after a while ...
>
> _*X connection to localhost:10.0 broken (explicit kill or server
> shutdown).*_
> Domain domain1 is ready to receive client requests. Additional
> services are being started in background.
> Domain [domain1] is running [Sun Java System Application Server 9.1
> (build b58b-rc3)] with its configuration and logs at:
> [/usr/share/glassfish/domains].
> Admin Console is available at [http://localhost:4848].
> Use the same port [4848] for "asadmin" commands.
> User web applications are available at these URLs:
> [http://localhost:8080 https://localhost:8181 ].
> Following web-contexts are available:
> [/web1 /__wstx-services /WebApp ].
> Standard JMX Clients (like JConsole) can connect to JMXServiceURL:
> [service:jmx:rmi:///jndi/rmi://RFIDLab:8686/jmxrmi] for domain
> management purposes.
> Domain listens on at least following ports for connections:
> [8080 8181 4848 3700 3820 3920 8686 ].
> Domain does not support application server clusters and other
> standalone instances.
>
> at this point GF dies.
>
> I usually connect to Glassfish from my Windows machine using SSH, and
> I have X-Forwarding enabled (hence the localhost:10.0) but I do not
> keep the X server (cygwin) running on windows.
>
> If I start the X server in windows, Glassfish runs for hours without
> problems - but no window is open on the windows machine (I was
> expecting some sort of log window to appear to justify the X connection).
>
> Any clue?
>
> Piero
>