It's all about the answers!

Ask a question

issues working RTC 4.0.1- performance issues

vinay kumar bondugula (7312560) | asked May 29 '13, 4:33 a.m.
This is on behalf of our client.
They are having both Clearcase 7.0 and RTC 4.0.1. one a single server(windows 2008 & 16GB RAM) clearcase is already installed and we installed RTC  4.0.1(tomcat server and Derby database). While configuring RTC, we are experiencing errors in tomcat and while accessing clients. 

When we click on a user in user management, A pop up is showing with the following message:
Type error: "local storage is undefined"

The following error is in the tomcat server:
-CRJCA0042W Host https://locathost:9443 has indicated a problem with an LPA request

For 3-4 weeks the server worked fine. Because of the errors we could not access anything on server so we uninstalled and re-installed RTC, now the errors are right after the installation.

Can any one figure out the issue and guide me further to clear the above issues.

Thank You.

One answer

permanent link
Stephanie Bagot (2.1k1513) | answered Jun 04 '13, 12:03 p.m.
The first type error can be investigated in the following ways:
  1. checking the ccm.log around the timestamp for a more clear error
  2. Using firebug to debug the rror

The second error with regards to the LPA means that the server is trying to create an LPA, or send a request between applications and incurred a problem. There are two red flags here:

  1. the host is LOCATHOST (typo from localhost?)
    Was your first public URI configured as localhost, and after re-install you typed locathost by accident? The change in URI is unsupported, and may cause the problem if this is the case.
  2. there is no context root information (for example /jts or /ccm)
    So we cannot determine which application is incurring the problem to begin investigation

I would recommend opening up a PMR with IBM Support to review your log files and help to determine whats going on. The relevant log files are in server/logs and server/tomcat/logs directories.

On a side note, for production deployments, your public URI should be named after the server, and you should not use 'localhost' since it is not individual to that machine. You may run into DNS routing issues down the line if you use localhost as the public URI. If you have set your public URI as the machine name, try to access the server using that public URI at all times. Lastly, we do not support Derby database for production environments, so I would suggest migrating to a different database vendor.

Your answer

Register or to post your answer.