> ->there is an error message in my catalin.out like this:
> Xlib: connection to "212.186.159.80:0.0" refused by server
> Xlib: No protocol specified
> 
> ->the cocoon page puts out the following
> org.apache.cocoon.ProcessingException: Error compiling sitemap:
> java.lang.InternalError: Can't connect to X11 window server using ':0.0'
> as the value of the DISPLAY variable.
I think batik uses the display (which explains why you can't use cocoon
on a headless station).

The user root is not allowed to access your display through the network.

XFree 86 allows display of programs to be exported on distant hosts. It
might be misconfigured in your case
Try the command : 

xhost +

(dangerous on a network) or 

xhost +127.0.0.1
or either

xhost +<your IP address 212.186.159.80>

point to 
http://marc.theaimsgroup.com/?l=xml-cocoon-users&w=2&r=1&s=headless+linux&q=b
for more explanations.

Doc taken form http://xml.apache.org/cocoon/installing/index.html :

UNIX with X server

Cocoon is bundled with the Batik (SVG rasterization toolkit) to deliver
SVG imaging capabilities. Batik uses Java java.awt library, which (at
least in Sun JDK before 1.4) requires graphics display. This means that
X server must be running and Cocoon should have permission to connect to
it.

Easiest way to avoid X server connection problem (and to have mentioned
permission) is to install and run Cocoon and entire servlet engine of
your choice under regular user account.

For security, and many other reasons, X server can be replaced by Xfvb
or PJA (alternative awt implementation).

[Note] Sun JDK 1.4 does not require graphics display anymore, but Java
has to be started with the argument -Djava.awt.headless=true

Regards

Benoît Clouet




---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Reply via email to