MQSeries.net :: View topic - Thin Client Monitor

jmac · Posted: Wed Feb 20, 2002 12:44 pm Post subject:

When attempting to use the Thin Client monitor on an AIX platform I receive
the following:

com.ibm.workflow.servlet.client.ClientException
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:61)
at java.lang.Class.forName1(Native Method)
at java.lang.Class.forName(Class.java:134)
at
java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment
.java:65)
at java.awt.Font.initializeFont(Font.java:270)
at java.awt.Font.(Font.java:300)
at com.ibm.workflow.servlet.client.ProcessMonitor.(ProcessMonitor.java:55)
at
com.ibm.workflow.servlet.client.MonitorHandler.showMonitor(MonitorHandler.ja
va:100)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.workflow.servlet.client.Util.invoke(Util.java:124)
at
com.ibm.workflow.servlet.client.GenericCommandHandler.execute(GenericCommand
Handler.java:108)
at
com.ibm.workflow.servlet.client.BuiltinHandler.execute(BuiltinHandler.java:1
43)
at
com.ibm.workflow.servlet.client.ApplicationContextImpl.dispatch(ApplicationC
ontextImpl.java:263)
at com.ibm.workflow.servlet.client.Main.doGet(Main.java:217)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager
.java:626)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycl
eServlet.java:160)
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java:287)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycle
Servlet.java:105)
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:36
0)
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java:775)
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManag
er.java:701)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebAppRequestDispatcher.java:478)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequest
Dispatcher.java:234)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestD
ispatcher.java:138)
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.
java:77)
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedIn
vocation.java:67)
at
com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(Cacheabl
eInvocationContext.java:106)
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java:160)
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener
.java:300)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp$ServiceRunnable.run(SQ
EventListenerImp.java:230)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp.notifySQEvent(SQEventL
istenerImp.java:104)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQEventSource.notifyEvent(SQE
ventSource.java:212)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.notifyService(SQWrapperEventSource.java:353)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.run(SQWrapperEventSource.java:220)
at
com.ibm.servlet.engine.oselistener.outofproc.OutOfProcThread$CtlRunnable.run
(OutOfProcThread.java:248)
at java.lang.Thread.run(Thread.java:481)

Can anyone tell me how to get around this?

THANKS

_________________
John McDonald
RETIRED