Previous Next Up FAQ Table of Contents

3.4 Known Problems

You can report any problems you're having with VolanoChat by sending a complete description along with your VolanoChat server support.log file to Volano Support <support@volano.com>. Below are some of the problems of which we are already aware.

VolanoChat applet hangs while window is resized.

The Microsoft Virtual Machine in Internet Explorer for Windows can hang when the VolanoChat applet chat room window is resized while a message is being received in the chat room. The problem can be solved by upgrading to the Sun Java 2 Plug-in.

VolanoChat applets work poorly on the Mac.

Most Java applet display problems with the mouse, windows, and scroll bars on the Mac can be solved by upgrading to Mac OS X Panther v10.3 and using its much-improved Java version 1.4.1 support available in the Safari Web browser.

VolanoChat applets fail to load.

The applets in VolanoChat will fail to load when an applet property which expects a numeric value is assigned an empty or non-numeric value. For example, either of the following property definitions would cause the applets to fail loading:

banner.width=null
banner.width=

This problem occurs most often when trying to remove the BannerPlayer applet from the banner and logo areas of VolanoChat. To remove the embedded applets, simply set the banner.code and logo.code properties to the empty string as shown below, leaving the numeric properties with their proper values:

banner.code=
logo.code=
Web touring does not work in the WebVolanoChat applet.

The WebVolanoChat applet does not recognize the applet property webtouring.default=true.

VolanoChat server crashes with a segmentation violation.

A bug in the name service lookup on Linux could cause the VolanoChat server to crash with a segmentation violation, printing a message like this:

./startup.sh: line 93: 21554 Segmentation fault (core dumped)

or this:

SIGSEGV   11*  segmentation violation
    si_signo [11]: SIGSEGV   11*  segmentation violation
    si_errno [0]: Success
    si_code [0]: SI_USER [pid: 0, uid: 0]
    stackpointer=0x526dccc4

The problem can be corrected by installing the latest updates for the Glibc library on your Linux system. For details, see the Red Hat Errata, "Updated glibc packages fix vulnerabilities in resolver."

Previous Next Up FAQ XHTML 1.0 Table of Contents