|Table of Contents|
10.1 Error Messages
Server Side Error Messages
- This usually happens during installation in UNIX at the command line.
- Resolution: When you're running the install, don't type ".class" at the end of the class file name.
Exception in thread "main" java.lang.ClassFormatError: vchat2_6_1 (Illegal constant pool type)
- This message might occur on a UNIX installation when the class file has been improperly uploaded or downloaded as an ASCII file rather than binary.
- Resolution: Make sure that you download or upload the VolanoChat class file as a binary file with your browser or FTP program.
With server side errors you need to sort through all the startup status messages for something that looks like an error. The following is a list of known startup errors you could get.
java.net.BindException: Address in use
- In this case, the chat server can't start because the address/port it is trying to start on is already taken by something else. This could be an instance of the chat server already running, or some other program on your server.
- Resolution: Check to see what else is running. Use an unused port or a different IP on the machine. Also make sure to check port 8080 (default) if you haven't disabled the servlet runner.
java.net.BindException: Cannot assign requested address
- The Java VM can't match the IP address it is looking for to one on the machine.
- Resolution: The IP address doesn't exist on the machine. Add it or use a different IP or don't specify
server.host. This error is most common with people using NAT. The address specified in your license must be the actual IP address on the machine, and NOT the IP address that your NAT router is forwarding.
java.security.SignatureException: invalid license
- The license is not a valid license for this version of VolanoChat.
Please download a trial key from www.volano.com.
java.io.FileNotFoundException: ./conf/key.txt (No such file or directory)
- The license file
key.txtwas not found in the
confdirectory of your VolanoChat installation.
- Resolution: Make sure that you have created and installed the
key.txtand placed it in your
confdirectory of your VolanoChat installation.
Unable to start server (COM.volano.j)
- This error occurs when the license string in your
key.txtcontains either a line break or is word wrapped.
- Resolution: Make sure that the
key.txtfile is in plain text format and that the license string contains no line breaks or word wrapping.
Errors you might see in your
java.net.SocketException: Connection reset by peer
- This is a common message reported by the VolanoChat server when trying to send a message to the client applet, but the connection has already been closed by the applet. If the VolanoChat server sends something to the client before receiving notification that the connection has already been closed, the TCP/IP stack of the client sends a reset.
- This is common and normal - nothing of concern. The only reason it is logged is because all SocketExceptions are logged, and the VolanoChat server has no way of knowing the difference between these harmless SocketExceptions from the ones resulting from true errors.
java.net.SocketException: Too many open files in system
- If the VolanoChat server hits the OS's file descriptor limit, you may receive this message. The VolanoChat server requires one file descriptor for each person chatting through a VolanoChat applet. You can modify the default starting file descriptor limit in the
startup.shfile. For more information, please see [4.0] Installation.
Client Side Error Messages
When diagnosing problems on the client side, there are 3 sources of information: any error message webpages, the status information in the Java applet, and your Java console. You can enable the Java console by....
- Unable to Connect
This error is caused by one of two conditions: a down server or a communication problem between client and server. First, make sure the chat server is actually running. If it is, then either the client applet properties file doesn't have the correct port settings or there is something like a proxy server or firewall preventing direct communication. To test this, open up a telnet session and try to connect to the port and IP address of the server. This can be done on a windows machine by typing this at the command prompt:
telnet 192.168.1.1 8000
Notice that there is no colon after the IP address. Also, make sure to replace the IP and port listed here with the IP and port of your own server.
Finally, make sure that the VolanoChat software is running on the same machine that is serving up your chat page. A security restriction in Java only allows an applet to connect back to the machine from which it was called.
- exception: java.lang.NullPointerException
Internet Explorer displays this message in the browser status area if any of the VolanoChat applet true or false properties are left undefined in its properties file. To work around the problem, make sure all of the following properties are included in the properties file you have defined for the applet:
override.myvolanochat=true history.enable=false member.editable.name=true member.editable.profile=true alert.entrance.default=false alert.audio.default=false alert.count.default=false webtouring.default=false image.button.border=true page.newwindow=false page.use.document.base=false
You can define the values differently than their defaults shown above, but each property must be found in the file. This problem was fixed in VolanoChat Version 2.1.7.
- Applet COM.volano.VolanoChat can't start: ERROR
- Netscape Communicator displays this message in the browser status area for the same problem documented above.
|XHTML 1.0||Table of Contents|