issues working RTC 4.0.1- performance issues
One answer
- checking the ccm.log around the timestamp for a more clear error
- 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:
-
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.
-
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.