You get an error message while installing the Sun Java Studio Mobility IDE:
Error writing file = There may not be enough temporary disk space. Try using -is:tempdir to use a temporary directory on a partition with more disk space

Start the installer using -is:tempdir command-line option to specify a directory with more space.

For example, in a Linux operating environment, type the following at the command prompt:

$ jstudio_M04q3-linux-en.bin -is:tempdir temporary-directory

You get the following error message while installing the Sun Java Studio Mobility IDE:
Error: Could not find JVM

Start the installer with the -is:javahome command-line option, to specify where the J2SE platform is installed.

For example, in a Linux OS, type the following at the command prompt:

jstudio_M04q3-linux-en.bin -is:javahome java-home-directory

During installation, the installer could stop running with the following message:

The installer is unable to run in graphical mode. Try running the installer with the -console or
-silent flag.

• If your DISPLAY environment variable is not correctly set, type the following command in a C shell:
  setenv DISPLAY your-local-host:0.0
• If you are running the installer remotely and the host name is not allowed access to the local server, follow these steps:
• Run the following command on the local server where display is used:
  xhost +remote-host-name
• Run the installer.
• Immediately after the installer finishes, run the following command on the local server:
  xhost -remote-host-name

This last step is particularly important since the xhost + command disables security and makes systems vulnerable to a variety of attacks.

If you install the cobundle with the zh.UTF-8 locale, the console displays some distorted text when the installer is starting. This bug does not affect the installation. Ignore the text and continue following the installer instructions.

(Solaris OS only)

ERROR: could not initialize interface awt - exception: java.lang.NoClassDefFoundError java.lang.NoClassDefFoundError at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:130

...

Wizard.getExitCode(): called after WizardServices is shutdown.

Wizard.getExitCode(): called after WizardServices is shutdown.

This error indicates that your DISPLAY environment variable is not set correctly. In some cases, you need to make sure that it includes the domain as well as the host name. For example:

setenv DISPLAY your-machine-name.your-domain:0.0

The IDE installer exits without installing the product. No messages are displayed.

• Your installation directory might not have enough space. check the system requirements to determine the space you need, then check to ensure your directory has enough space.
• The file you downloaded from the Sun Java Studio product download page is not complete. Download the file again and check that the size of the downloaded file is the same as the file size specified on the product download page. Run the IDE installer again.
• You have specified an invalid command-line parameter in the installer-name.sp file. Check the file and correct the command-line options. Run the IDE installer again. See Appendix B.
• Run the installer launcher (installer-name.exe file or installer-name.bin file) with the option -is:log log.txt, where installer-name is the specific installer file name for your platform. Check log.txt for possible errors. See Appendix B.

The -is:tempdir command-line option is not working.

Ensure that you are using the correct syntax for the command-line option. For example, in a Linux environment, the syntax is as follows:

jstudio_M04q3-linux-en.bin -is:tempdir temporary-directory.

You get an error message that says that the product is not supported for the Solaris 7 OS after you inserted the product CD on a computer running in the Solaris 7 operating environment.

The Sun Java Studio Mobility IDE is only supported for the Solaris 9 OS.

(Solaris OS only) You get the following error message:

ERROR: cannot find product/product.xml on your computer.

Stop and restart the volume management process (vold) on your system, and run the installer again.

1. Ensure that CD-ROMs or floppy disks are not being used. If you are not sure whether you have found all users of the media, run the fuser command.
2. Become superuser.
3. Stop volume management.
   # /etc/init.d/volmgt stop
4. Restart volume management.
   # /etc/init.d/volmgt start

When setting the installation directory, you get the following error message:

Uninstall the following installed software from the specified install directory or specify another empty directory. To uninstall successfully, you have to exit this installer first!

This message indicates that you already have an installation of Java Studio Mobility in the selected directory. You must exit the installer before you uninstall the existing version of the software. After you have fully uninstalled the previous version, restart the installer to install the latest version of the IDE.

(Microsoft Windows) After exiting the installer or uninstaller wizard, you see the WindowsNativeToolkit process consuming a large percentage of your CPU resources.

The WindowsNativeToolkit process is started during installation and uninstallation. Sometimes it does not stop properly. Use the Windows Task Manager to find any instances of the process WindowsNativeToolkit and end the process.

When starting the IDE, you get an error message similar to the following:

ERROR: The J2SE[tm] 1.2.1 found at /usr/java1.2/bin/java cannot be used by the IDE. J2SE[tm] 1.4.1_02 is recommended.
NOTE: You can download and install the J2SE[tm] and related Solaris[tm] patches from http://access1.sun.com/forte/.

Warning: Current runtime environment does not satisfy minimum requirements.

The values of the $JAVA_PATH and $JDK_HOME environment variables override the value of the J2SE platform path you specified during the IDE installation. You need to unset these environment variables or use the -jdkhome command-line option when starting the IDE. See Chapter 10.

You experience performance problems running the IDE.

Increase your virtual memory or swap space to 1.5 to 2 times the amount of your machines's installed RAM.

Error message appears when you select one of the IDE Start Menu items that take you to a web page. For example:

Error: Cannot find the file C:\Sun\SUNWjstudio\Mobile04q3\docs\documentation.html. Make sure the path and filename are correct and that all required libraries are available.

This error is a Microsoft Windows error that occurs when using a Netscape browser. If you have Netscape set as the program to open HTML pages, but you don't set Netscape as your default browser, you may see this error.

Click OK to dismiss the error.

To solve this problem, set Netscape as your default browser, or set Internet Explorer as the program to open HTML pages.

A subsequent error message appears after dismissing the one described above.

Error: Unable to run this command.

Click OK to dismiss this error.

Set Netscape as your default browser.

[java.rmi.RemoteException: HTTP transport error: java.net.ConnectException: Connection refused; nested exception is: HTTP transport error: java.net.ConnectException: Connection refused

• Changes were made to the web service, and you did not refresh the web service client that was making the call to the web service. To refresh the web service client: Right-click the web service client node and select Refresh From Web Service. from the contextual menu. This regenerates the client proxy to reflect the changes made to the web service.
• After you developed and deployed your web service, you changed the target deployment server and you did not change the web service SOAP RPC URL. To fix this:
• Change the SOAP RPC URL property found on the web service property sheet.
• Right-click the web service node and choose Generate Web Service Files.
• If you have a default client, right-click it and select Refresh From Web Service.
• Redeploy the web service.

[java.rmi.RemoteException:cannot connect to server:Not found;

nested exception is: cannot connect to server: Not found

The Web Context property of the web module in the J2EE application does not match the context root specified in the SOAP RPC URL property of the web service. To view the Web Context property of the web module:

1. Expand the J2EE application to which the web service was added.
2. Right-click the web module of the web service (the file whose name ends in _War) and choose Properties.
3. The Web Context property is one of the properties displayed in the Properties window.

To view the context of the SOAP RPC URL property of the web service:

1. Right-click the web service node and choose Properties.
2. The SOAP RPC URL property displays a value that is similar to the following:
   http://localhost:8000/MyService/MyService

The first instance of MyService in this URL is the context root or web context. You can change it to any value of your choice, but it must match the value of the Web Context property of the web module in the J2EE application.

You get an empty web page when viewing .wsdl files.

Many versions of the Netscape web browser do not display the .wsdl file. View the page's source file to see the actual .wsdl file.

You get the following exception when searching for anything in a UDDI registry using the New Client wizard:
IllegalArgumentException

If you intend to use a public UDDI registry, set the User Proxy Server name and port information in the IDE.

• Choose Tools Setup Wizard from the main window of the IDE and provide the User Proxy Server name and port.

You must restart the IDE for the values to take effect.

The internal UDDI registry server fails to start and displays the following exception:

jjava.lang.RuntimeException: RegistryServerSevlet.initializeDB(...):

com.sun.xnode.XNodeException: aborting connection attempt.,

RegistryServerServlet.init(...): connection: 1, Database failed to connect

A possible cause is that a previous Xindice server instance was not terminated properly. (On a Microsoft Windows system, you might have to restart the operating system to get rid of these server instances.)

1. Terminate the corresponding Java processes associated with that Xindice server instance.
2. Restart the IDE.

Always terminate the internal UDDI registry server using the following steps:

1. Select the Runtime tab of the Explorer.
2. Expand the UDDI Server Registry node.
3. Right-click the Internal UDDI Registry and choose Stop Server from the contextual menu.