xvfb font error

[Brent Moore_1]

I'm running hp-ux on an A500 machine. When trying to access xvfb from java I get the following error -
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0xC4FBCFB8
Function=XGetFontPath
Library=/usr/lib/X11R6/libX11.3
( see attached file for full detail). We are running JRun 4.0 and trying to generate a graph. We have an identically configured A500 that works with this configuration just fine.

I have installed the latest patches and tried everything I can find on this site. No luck so far in getting it to work.

Any ideas would be greatly appreciated.


Thanks,

Brent

[James A. Donovan]

Signal 11 is generally indicative of a memory shortage issue. Either real, or more likely, virtual. Double check your swap utilization/settings on the "broken" A500 against those on the "working" A500.

[Steven E. Protter]

compare swapinfo -tam output

You should see a difference, utilization and or configuration.

SEP

[Brent Moore_1]

The only number that differs is the reserve. It is twice the size on the good server - 1400 versus 700 on the bad. Could reserve be causing the problem (I'm a little fuzzy on the type of swap space available).

[Steven E. Protter]

It would be best if you posted the swapinfo -tam from both machines.

Maybe its priority, reserve is set automatically or based on kernel, can't remember.

I didn't explicitly set mine.

SEP

[Tim Adamson_1]

Hi Brent,

Are you using the headless java option, java.awt.headless=true? If so then you may need to upgrade the version of Java to 1.4.1.02 or higher.


Cheers!!

[Alex Glennie · Accepted solution]

That error is an old friend of mine if you are using the headless=true option : defect id JAGae6791 was raised back in April by myself to address it .... basically libmawt.sl libs are being loaded in the wrong order ie motif version is being loaded before the headless one.

fix is due out in 1.4.1.02 released circa end of may

nasty workaround : remove the libmawt.sl link in the /opt/java1.4/jre/lib/PA_RISC2.0/ directory then set SHLIB_PATH to point the headless version before starting java. ie

$ cd /opt/java1.4/jre/lib/PA_RISC2.0/
$ mv libmawt.sl libmawt.sl.org
$ cd
$ export SHLIB_PATH=/opt/java1.4/jre/lib/PA_RISC2.0/headless
$ java -Djava.awt.headless=true TestHeadless sun.java2d.HeadlessGraphicsEnvironment@19ee1ac"

If you are not using the headless=true option there should be no problems ..... xvfb can be configured to work with the above .... I have details if this is the case so let us know ....

[Brent Moore_1]

Thanks Alex - that fix worked like a charm. I'll work on getting the 1.4.1.02 jdk asap, but in the mean time I can get my app up.

Brent