> Installation and Upgrade Guide > Troubleshooting

Installation and Upgrade Guide

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Troubleshooting

This chapter provides troubleshooting tips for installing and deploying Studio. It includes the following sections:

 

Reviewing Log Files

If the installer fails and you are unable to complete the installation, follow the installer error messages to correct problems with software dependencies. You can also review the installation log file, AquaLogic_Interaction_Studio_InstallLog.log, that is saved in the directory from which you run the installer.

If you encounter problems after installation, review the log files to help you diagnose and correct the problem:

 

Reconfiguring Studio

If the installation verification tool reports configuration errors, review the configuration decisions you recorded in the Installation Worksheet for AquaLogic Interaction Studio 2.2 MP1 and re-run the installer.

Advanced users can review and modify settings in PTStudioConfig.xml:

 

Diagnosing Unexpected Results

This following table provides symptom-solution interpretations for unexpected results you might encounter when you install and deploy Studio.

Table 6-1 Troubleshooting
Symptom
Solution
When you start Studio, the portlets time out.
If you are running Studio for the first time, you might need to refresh the page a couple of times, because the .jsp pages are compiled when Studio is first accessed.
When you start up Studio, the Studio portlets do not start or fail to preload on startup.
Review the log files:
  • For Windows the log files are located in C:\bea\alui\ptstudio\2.2\settings\logs
  • For UNIX or Linux the log files are located in /opt/bea/alui/ptstudio/2.2/settings/logs
If the logs contain Java errors for connection requests:
  • Ensure that your Studio service is running in a healthy state; if it is not, restart it.
  • Ensure the portal configuration for the Studio service base URL and port are correct.
If the logs contain database connection errors:
  • Verify that the database is up and running in a healthy state; if it is not, restart the database.

Verify connection information configured for the Studio host database server matches the running configuration in PTStudioConfig.xml:

  • For Windows: C:\bea\alui\ptstudio\2.2\settings\config\PTStudioConfig.xml
  • For UNIX or Linux: /opt/bea/alui/ptstudio/2.2/settings/config/PTStudioConfig.xml
If the Studio service and database are configured correctly, verify the <PortalServerHost>\bea\alui\pthome.xml (Windows) or /opt/bea/alui/pthome.xml (UNIX and Linux) files include the following configuration for Studio: 
<product name=”studio”>
    <install version=”2.2“>
       <path>C:\bea\alui\ptstudio\2.2</path>
       <configpath>/settings/config</configpath>
    </install>
</product>
Port conflict, port in use, BindException
Port numbers for HTTP and HTTPS are configured in <PT_HOME>/ptstudio/2.2/settings/config/application.xml. Edit the http and https settings in application.xml to set the value to an available port. The service must be restarted to pick up changes made in the configuration file. Note that changes to a service port number require corresponding changes to any web service or remote server settings which may reference that port number.
Memory consumption, Out of Memory Errors
The maximum amount of memory, in megabytes, that the service JVM will be allowed to use is controlled by the wrapper.java.maxmemory property, configured in the file <PT_HOME>/ptstudio/2.2/settings/config/wrapper.conf. For example, the following line shows a maximum memory setting of 1 GB: 
wrapper.java.maxmemory=1024
The setting corresponds directly to the -Xmx parameter used by the java executable. The default value of this setting in the config file will be adequate for most configurations. For large production configurations, especially those in which the service is installed on a dedicated host machine, this value should be set as high as possible (e.g. 1024 or 1536) but should always remain below the amount of physical RAM on the host machine.


  Back to Top       Previous  Next