mule tcat server - common problems and solutions
TRANSCRIPT
MULE TCAT SERVERFixing Common Problems
Shanky Gupta
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.
WORKAROUND:
• In this case, you must un-register and re-register the servers with the current IP address.
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.
WORKAROUND:
• To work around this, choose File > Add this site to… > Trusted Sites.
PROBLEM 3: DEPLOYMENT IS INTERRUPTED
• If you navigate to another tab while a package is being deployed, the deployment is interrupted.
WORKAROUND:
• To work around this issue, wait for a package to be deployed before navigating elsewhere.
PROBLEM 4: MONITORING AND DIAGNOSTIC SCREENS DISAPPEAR
• If you increase the font size on Mozilla Firefox, the monitoring and diagnostic screens disappear.
WORKAROUND:
• Leave the font size set to the default.
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.
WORKAROUND:
• If you must download the installer again, delete the original file first so that Firefox leaves the original name intact.
PROBLEM 6: SSL/TLS HANDSHAKE EXCEPTION
• APR Connector Failure using Tomcat 5.5 with TcatErrors 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.
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.
PROBLEM 7: TCAT FAILS TO START ON WINDOWS
• Tcat Server service on Windows fails to start
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