1 of 1 people found this helpful
What problem is it causing ?
You can disable the x11 forwarding in the secure file on the agent, I think that will take care of it. I forget if that can apply to the nsh client as well.
"By default, X11 forwarding is turned on. You can use the
x11_fwdoption in the
rscdentry in the RSCD Agent's secure file to turn off X11 forwarding or to turn it back on. For more information, see Secure file overview and Options for the secure file.
Note: If you change the value of the
x11_fwdoption in the secure file while the RSCD Agent is running, restart the agent for your changes to take effect."
is helpful but I take it there is no global setting...?
BTW, the issue was Tomcat process dying after being started using NSH:
5/28/13 08:12:31 PM EDT [INFO] [IntroscopeAgent] Statement Normalizer: No sql normalizer extension was configured in the properties, falling back to the preconfigured normalization scheme [Risk has diagnostic equipment such as MRIs, CT Scan, Risk has printers with more than 3 color capability, Risk has products in refrigerated storage] X connection to 127.0.0.1:12.0 broken (explicit kill or server shutdown).^M
Afaik no. pretty easy to create a job to do it though. that should disable the display setting in the nexec’d session.
What does that have to do w/ the display setting ?
When they get this:
X connection to 127.0.0.1:12.0 broken (explicit kill or server shutdown)
The tomcat process stops. If they don't use NSH there is no x connection. This is not a cause but a well tested correlation.
Why is tomcat trying to use x ? that’s odd. I have x forwarding setup w/ putty and start and stop tomcat and have my display set and never have an issue.
I believe its Introscope call embedded in the java args that is having the issue. CA has looked into this and the DISPLAY is the only thing they could find. Again, testing without DISPLAY set hasn't failed while with DISPLAY set consistently fails. Not 100% sure the cause. Thanks Bill.