Troubleshooting Tips

In this section:

Review the following tips when troubleshooting Developer Studio.

Top of page

Tomcat Configuration Options

Since Tomcat runs as a service, Tomcat Java settings and other parameters are written into the registry. They can be configured through the Apache Tomcat Properties window. You can launch this from the Start menu by selecting Programs, Information Builders, Tomcat, and Tomcat Configuration Utility.

If you need to adjust the Java release, click the Java tab to change where Tomcat looks for Java components.

Top of page

Java Memory Issues

If the Developer Studio installation configured Tomcat for you, the Tomcat Java VM memory settings are automatically increased. This is done because default application server Java VM memory options may not be sufficient for some WebFOCUS features. If you need to troubleshoot further or if you manually install Tomcat or another application server, you may need to manually increase the Java VM memory options.

The most common Java VM options you need to set involve the size of the Java heap and stack, which determine memory availability for Java programs and the Java VM. Errors can occur if not enough memory is available, and the heap size impacts performance, since it determines how often garbage collection occurs.

The following are the most common Java VM options related to memory settings. Replace the ### with the size you wish to set:


Sets the maximum Java heap size. It is common to make this 1/4 of the system RAM.


Sets the initial Java heap size. It is common to make this 1/8 of the system RAM.


Sets the Java thread stack size. You do not need to set this unless you are fine tuning your environment.

The size is normally set in megabytes, for example:


Optimum sizes vary depending on your total memory, the needs of your application, how many other processes require memory, the type of Java VM, and other considerations. To start, you can set the minimum MaxPermSize to 1/8 of the total RAM, and set the maximum to 1/4 of total RAM.

Note: As of Release 8.0 Version 02M, the application server minimum MaxPermSize setting has been increased to 256M.

When Developer Studio installs or configures the Tomcat application server, it will configure Tomcat with the MaxPermSize set to 256. In prior WebFOCUS 8 releases, the WebFOCUS Client and Developer Studio Full Install options set the Tomcat application server MaxPermSize to 128M.

Where to set these and other Java VM options, depend on your application server.

Top of page

Starting Developer Studio

If you close Developer Studio and then cannot restart it, you may need to manually stop the underlying focshell.exe process. To do this:

  1. Press Ctrl + Alt + Delete and choose Task Manager.
  2. Click the Processes tab.
  3. Find and select a focshell.exe Image Name if it appears.

    Note: You can click the Image Name column to sort by name.

  4. Click End Process.

You should be able to restart Developer Studio if no focshell.exe processes appear.

Top of page

Multiple Developer Studio Installations

There is normally no reason to install more than one instance or release of Developer Studio on a single machine. When you install Developer Studio, it partially disables any other instances of Developer Studio. If you must switch between instances, be aware that you may need to reconfigure your web and/or application servers. In addition, you must reregister the correct DLL files with the operating system. Developer Studio provides a batch file to register DLL files. It appears in the bin directory for the Developer Studio release. For example: