If you get an out-of-memory error (or would like to increase the amount of memory that the server can use), add the "-mx128m" argument when running java/jre. In fact, we recommend increasing the amount of memory available to Java to allow Java and the server to use up to 128 megabytes of virtual memory, if necessary. Alternatively, the config.dct file can be edited to cut down on the amount of memory used by changing the number of threads allocated for each listener.

The client and server software need Java 1.4.2 (or higher). The servlets require the Java Servlet library which is available from Java.com in the Java Enterprise Edition (J2EE), or via downloading a servlet engine such as Apache Tomcat. See similar questions...

If you get an out of memory error, you may be trying to read in a larger file than Datasqueeze can hold in memory.In the File window, check the box marked "File Swap." This will slow things down a bit but allow much larger files to be manipulated. See similar questions...

If you are running Windows XP; 2000 or 98 you will need to be sure to have the following JAVA Runtime installed; The new JAVA Release 6 (sometimes called 1.6) will work with our current Blackboard WebCT CE system when running Windows XP; 2000 or 98! If you are using the new Windows Vista operating system, you MUST use version 1.6 with Blackboard WebCT as earlier editions will not work with this new operating system. See similar questions...

You probably have run out of virtual memory on your system, or your kernel has a low limit for certain resources. Try this before starting postmaster: ulimit -d 262144 limit datasize 256m Depending on your shell, only one of these may succeed, but it will set your process data segment limit much higher and perhaps allow the query to complete. This command applies to the current process, and all subprocesses created after the command is run. See similar questions...

Wusage contains no arbitrary limitations on the maximum size of a log file to be processed. However, If your log is especially large, and especially when the Summary Reports (summary), Quarterly Reports and Annual Reports options are active, you may receive the following message: This occurs when your computer does not have, or will not allocate, enough memory for Wusage to successfully analyze your log. See similar questions...

This usually happens when a transaction is attempted before the Java applet is completely loaded into your PC. To reload the applet, click on the toolbar, re-select the transaction and wait for the loading to be completed before you proceed. If this does not help, please try clearing the browser's cache before you log in again. See similar questions...

Incorrect browser version. Check and if the browser is 3.0 level, you will have to upgrade. Browser version is identified by clicking on "Help" and "About Communicator" or "About Internet Explorer" from the drop down menu which appears. See similar questions...

One of the most common memory problem faced in older PC system during boot-up is "incorrect memory sizing" or the error number 164. Sometimes failures could be caused by incorrect software setting, sometimes it could be caused by hardware ? which could be easily fixed if you know where the faults lies. See similar questions...

You don't have DivX 3.11alpha but some VKI patch or a newer (never use them!) version. Reinstall Divx 3.11alpha and answer yes when asked to overwrite some files. Then reboot and try again. SBC isn't a wonder solution for good rips. It's a tool for advanced rippers which allows you to push the codec to its limits when using the right parameters. My profiles are but a starting point.. you'll end up encoding the same movie many times to get the ideal rip. See similar questions...

Try increasing the -Xmx value to give the JVM more memory. Performance will rapidly disintegrate if you allocate more memory than physical memory on your machine. At this point, the solution is to buy more RAM or go and have a long coffee break. I've got 512 MB and this is OK for good performance with all but the largest dumps from servers that I've seen. Saving the state once parsed is the best thing to do. Also see the section on memory usage in the documentation. See similar questions...

My program ran fine on the orignal PIC, but it behaves erratically or doesn't run when I put it on a different PIC. See similar questions...

If you can access your security features, verify that you have them set the way you want them. If you cannot access the security features, go into Unibase\misc and delete etpasswd file. You will then have to recreate your security features. See similar questions...

According to posts in webtv.users from Steve Perlman, ex-president of WebTV, WebTV has been working to provide a form of Personal Java for the WebTV Plus terminal (and possibly the new Classics and Dishplayer, but nothing was said specifically about them as they were not announced products at the time of the posts)?there is no guarantee this will happen. For the full text of Steve's posts, click here. See similar questions...

There are two ways to control this. If you get an OutOfMemoryError when Cocoon is generating pages, see the first paragraph. If you get an OutOfMemoryError when outside of Cocoon (e.g., copying raw files), see the second paragraph. The maxmemory property in the forrest.properties file controls how much memory Cocoon uses. Like many other properties you can copy them from the default configuration at src/core/fresh-site/forrest. See similar questions...