If you are experiencing issues, review the listed common problems and workarounds for Tcat Server.

1. MULE TCAT SERVER
Fixing Common Problems
Shanky Gupta

2. PROBLEM 1: UNABLE TO COMMUNICATE
WITH TCAT SERVER
• When servers are registered, they are registered with a specific IP
address. If you are testing on a laptop with a wireless connection and
you move from one location to another, your IP address might change,
and the servers no longer are able to communicate with Tcat Server.

3. WORKAROUND:
• In this case, you must un-register and re-register the servers with the
current IP address.

4. PROBLEM 2: MAIN SCREEN DOES NOT
APPEAR
• If you are running Internet Explorer 7 on Windows 2008, you can log
in to Tcat Server but the main screen does not appear.

5. WORKAROUND:
• To work around this, choose File > Add this site to… > Trusted Sites.

6. PROBLEM 3: DEPLOYMENT IS
INTERRUPTED
• If you navigate to another tab while a package is being deployed, the
deployment is interrupted.

7. WORKAROUND:
• To work around this issue, wait for a package to be deployed before
navigating elsewhere.

8. PROBLEM 4: MONITORING AND
DIAGNOSTIC SCREENS DISAPPEAR
• If you increase the font size on Mozilla Firefox, the monitoring and
diagnostic screens disappear.

9. WORKAROUND:
• Leave the font size set to the default.

10. PROBLEM 5: FILENAME PARENTHESES IN
FIREFOX
• If you download the installer more than once, Firefox appends
parentheses to the file name, which causes problems when you try to
run the installer.

11. WORKAROUND:
• If you must download the installer again, delete the original file first
so that Firefox leaves the original name intact.

12. PROBLEM 6: SSL/TLS HANDSHAKE
EXCEPTION
• APR Connector Failure using Tomcat 5.5 with Tcat
Errors such as "javax.net.ssl.SSLHandshakeException: Remote
host closed connection during handshake" may result from limitations
within the Tcat Server Administration Console, which cannot
currently pair with SSL/TLS connectors under certain conditions.

13. WORKAROUNDS:
• Configure the Tomcat servers with an HTTP (non-SSL) connector on a
port that the firewall blocks from the public internet, but not from the
console.
• Configure the Tomcat servers with an AJP (non-SSL) connector on a
port that the firewall blocks from the public internet, but not from the
console.

14. PROBLEM 7: TCAT FAILS TO START ON
WINDOWS
• Tcat Server service on Windows fails to start

15. WORKAROUND:
• Open a terminal window and navigate to the Tcat Server
installation/bin directory. Type tcatserver6w and examine the contents
under Java tab. Make sure both JAVA_HOME and JRE_HOME are
pointing to the right path