• Welcome, guest

  • Login

  •  

Type:
Bug
Priority:
Show-stopper Show-stopper  
State:
Fixed
Subsystem:
Agent
Reporter:
Gibson (rxgibson) Send Email
Assignee:
Anna Kozlova (anet) Send Email
Affects:
Build 1615 (RC1)
Fixed in:
1.2 EAP (1748), TeamCity 1.2
Created:
24 months ago (26 Sep 2006 19:53)
Updated:
20 months ago (15 Jan 2007 16:01)
Votes:
0
Resolved:
JIRA source:
TW-858
teamcity.log (21 kb)
Issue has no links

I ssh into a remote machine and start an agent.
At this point everything runs OK because ssh is set up to do X forwarding, so any process that needs an X server can use my local machine.
I then put the agent process into the background and log out of my remote session. The agent can no longer connect to my X server on my local machine.


Now I get an error whenever I try to run an Inspections build. I attach the log.
Looks the same as TW-773


Environment: RH Linux on headless machine


Issue wasresolved

  • Anna Kozlova (anet) Send Email
    24 months ago (27 Sep 2006 15:52)

This is a bug in jdk. It creates toolkit and after that checks if it is headless environment. We need to instantiate our event queue thus we need default toolkit. We will do our best to provide a workaround but not in IDEA 6.0 unfortunately.
Sorry for inconvenience.
Thank you.

  • Tim McNerney (mumbly) Send Email
    23 months ago (10 Oct 2006 18:01)

Can you start up the agent with the argument:


-Djava.awt.headless=true


to fix this?


Other possibility, you can run Xvfb, which is a virtual frame buffer. We run it with:


/usr/X11R6/bin/Xvfb :0 -screen 0 1600x1024x16


and have a display to point to at :0.

  • Gibson (rxgibson) Send Email
    23 months ago (10 Oct 2006 19:13)

The -Djava.awt.headless=true doesn't work because the agent is looking for a display (unfortunately).
I'll try and find Xvfb and give it a go.

  • Gibson (rxgibson) Send Email
    23 months ago (10 Oct 2006 19:55)

It seems that running the inspection "needs" to have a proper display, since I am prompted to give a value for my path variables (output directory is defined as a path variable in my module definitions).


Inspections should be able to run completely headlessly - if it needs path variables and they haven't been defined in the build configuration it should just crash giving the name of the variable to define. In my case it's doubly annoying because the output directory is specified as part of the build.

  • Anna Kozlova (anet) Send Email
    23 months ago (10 Oct 2006 20:02)

I am fixing this step by step. Sorry for inconvenience. Thank you

  • Gibson (rxgibson) Send Email
    23 months ago (11 Oct 2006 11:11)

See also TW-946

Old New
Gibson (rxgibson) - 20 months ago (15 Jan 2007 16:01)

JetBrains Tracker revision #1363 [02-Oct-2008 13:30] (version #47) Copyright 2007-2008 JetBrains s.r.o.