Menu

#24 CURE crashes if it can't connect to an X Server

open
nobody
None
5
2008-02-08
2008-02-08
Uwe Sinha
No

Under certain circumstances, CURE crashes leaving the following message in catalina.out:

X connection to localhost:10.0 host broken (explicit kill or server shutdown)

To reproduce do the following:

* remotely log in to your server
* start up Tomcat
* open a browser and configure CURE
* close the browser
* log out again

As it seems, the connection to the X server is closed at logout time. The questions are (IMO):

* Does any component of CURE (or ACTIVEMQ) require a running X server (and if so, why)?

* Why does that component depend on the X connection associated with the remote login (which is what "localhost:10.0" stands for)?

The environment is as follows:

* OS: SuSE Linux Enterprise Server 10 SP1
* JDK 1.5.0_11
* Tomcat 5.5.25
* CURE 1.0.0

Discussion


Log in to post a comment.