Problems serving LineSeparatorImage on SuSE 9.0 without X in

[brooksl]

Do you really need X11 to generate these images?

java.lang.InternalError: Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.
at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
at sun.awt.X11GraphicsEnvironment.(X11GraphicsEnvironment.java:134)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:62)
at java.awt.image.BufferedImage.createGraphics(BufferedImage.java:1041)
at org.ajax4jsf.framework.resource.Java2Dresource.getImage(Java2Dresource.java:114)
at org.ajax4jsf.framework.resource.Java2Dresource.send(Java2Dresource.java:88)
at org.ajax4jsf.framework.resource.ResourceLifecycle.send(ResourceLifecycle.java:86)
at org.ajax4jsf.framework.resource.InternetResourceService.sendResource(InternetResourceService.java:213)
at org.ajax4jsf.framework.resource.InternetResourceService.serviceResource(InternetResourceService.java:183)
at org.ajax4jsf.framework.resource.InternetResourceService.serviceResource(InternetResourceService.java:118)
at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:207)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
at espial.engage.integration3A.ui.util.phase.EngageSessionFilter.doFilter(EngageSessionFilter.java:35)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:927)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:983)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

[ishabalov]

This is well known issue in Java2D, that required some kind of graphical engine to work. Normally it solved by adding environment parameter -Djava.awt.headless=true to server startup