ovsyslogcfg can fail when using Hummingbird Exceed or Reflection X emulators#

  • KM324287
  • 10-Jan-2008
  • 10-Jan-2008


The launch of the 'syslog Trap Mapping' configuration GUI (ovsyslogcfg) can fail when launched from a third party X emulation package such as Hummingbird Exceed or Reflection X. Either an error message is reported, or the command just hangs (depending on the emulator in use).


Hummingbird Exceed - tested versions 8,9,10,11
Xlib: unexpected async reply (sequence 0x79)!
Additionally, when executing the commands within /opt/OV/bin/ovsyslogcfg from the command line,
the following messages can be output:
      To run:

# export JRE_DIR=${OV_JRE:-/opt/OV/jre/jre1.4}
# export JAVA=$JRE_DIR/bin/java
# export APP_NAME=com.hp.ov.nnm.syslog.AppFrame

# $JAVA -cp $OV_MAIN_PATH/classes/syslogGui.jar:$OV_MAIN_PATH/classes/syslogGuiNls
gGuiNls_ko.jar $APP_NAME $OV_CONF/syslogtrap.xml


syslogGuiNls_zh_CN.jar:/opt/OV/classes/syslogGuiNls_ko.jar com.hp.ov.nnm.syslog.AppFrame

Exception in thread "main" java.lang.NoClassDefFoundError

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Unknown Source)

at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(Unknown Source)

at java.awt.Window.init(Unknown Source)

at java.awt.Window.<init>(Unknown Source)

at java.awt.Frame.<init>(Unknown Source)

at javax.swing.JFrame.<init>(Unknown Source)

at com.hp.ov.nnm.syslog.AppFrame.<init>(AppFrame.java:35)

at com.hp.ov.nnm.syslog.AppFrame.main(AppFrame.java:53)

Reflection X

On the tested version 14.0.1, ovsyslogcfg simply returns no output at all (appears to hang) when using NNM 7.51.
When using NNM 7.50, the message "Xlib: unexpected async reply..." can be observed.


This problem is caused by a defect in the skin used to display the GUI window.
The associated defect report is QXCR1000301036. 


A hotfix is available for this issue.  Currently this fix is only available by contacting HP support.

The fix applies to NNM 7.51 and should apply to all later intermediate patch releases.
The fix should also work for 7.50 releases, but update to 7.51 is recommended.

For updates on this issue, please check the associated defect QXCR1000301036.