Tcat Server Release Notes

Tcat Server reached its End of Life in 2017. Contact your Customer Success Manager to determine options for managing, monitoring, or deploying your application.

August 2015

This guide provides release Notes for:

Tcat Server 7.1.0 Release Notes - August 2015

Tcat Server 7.1.0 includes a large number of high priority bug fixes, and new improvements and updates.

7.1.0 Performance and Scalability

We spun up hundreds of virtual machines containing managed Tcat instances and registered them with the Console. The Console was really fast, we saw a maximum of 35% CPU usage (with some occasional spikes as the caches were loading) and a top memory usage of 35% of the system. Mostly the CPU consumption was less than 20%. The Tcat console was installed on a quad-core machine with 4GB of memory on a 64-bit Linux server.

7.1.0 Faster UI

User interface is much more snappier and listing of servers and deployments is significantly faster. The Dashboard also now lists all the deployments instead of just 10 per page.

7.1.0 LDAP Integration and Multiple Databases

Configuring LDAP is now possible through the installer if you are doing a fresh install of Tcat Server. Similarly, you also have the ability to configure a different backend database for Jackrabbit persistence, although we do recommend the one we ship with by default.

7.1.0 Upgraded Backend Persistence Schema

The backend persistence schema was given a nice little overhaul. A brand new persistence manager bundled with optimized caching and lucene indexing, significantly speeds up queries which in turn positively impacts the UI as well as REST API calls.

7.1.0 Optimized GC Configuration and Logging

On non-windows systems, Tcat Server now comes with an optimized configuration for the JVM. We have enabled GC logging, set the initial heap size to 1GB and partitioned the memory sections appropriately. We are expecting reduction in long GC pauses. This also helps us get better insight when providing support to our customers.

7.1.0 Upgraded Bundled Tomcat Version and JRE

The bundled Tomcat version is now upgraded to 7.0.51 and JRE is upgraded to 7.0.51.

7.1.0 Bug Fixes

  • [TCAT-1141] - Fix to Tcat-1140 breaks Deployment Purge scripts

  • [TCAT-1160] - Redeployment does not work properly when multiple artifact are part of the deployment

  • [TCAT-1163] - Continuous Deployment Purge Script execution failure: null

  • [TCAT-1176] - Log regex alert causing classnotfoundexception

  • [TCAT-1177] - Introduce validation for jcr nodes, to void the database corruption

  • [TCAT-1182] - If a server group has servers in it, then deleting the group does not remove the group from the server.groups property of the server node in JCR

  • [TCAT-1189] - Profiles are currently broken

  • [TCAT-1199] - Change copyright information to 2014. Its 2013 right now

  • [TCAT-1203] - Jasper API has changed for Tomcat 7, this breaks the JSP files display for server

  • [TCAT-1212] - Deployment Status portlet shows the status column twice in the Dashboard

  • [TCAT-1217] - If an undeploy fails then the deployment stays "In Progress"

7.1.0 Improvements

  • [TCAT-1088] - Server→Settings→Edit Server Info not working properly

  • [TCAT-1144] - Jackrabbit DAO overhaul

  • [TCAT-1151] - Replace the custom caching mechanism with spring cache and Ehcache

  • [TCAT-1185] - Groovy plugin should get compiled and tested to avoid that changes in the API break them

  • [TCAT-1198] - Database and LDAP configuration screen need not be shown during agent+tomcat custom installation option

  • [TCAT-1207] - Console treats catalina.out as a binary file, prompting user to agree to open binary file, should just treat it as text file instead

  • [TCAT-1214] - Show all servers in the Dashboard instead of the default 50 servers.

  • [TCAT-1215] - Remove Paging for Deployment status in the Dashboard thus allowing all deployments to be shown instead of just 10

  • [TCAT-1216] - ServerName column should autoexpand to occupy remaining columnar space in table in order to show maximum characters of server name

  • [TCAT-1220] - Make CMS Garbage Collector the default, enable GC logging and set 1GB the default heap memory

  • [TCAT-1224] - Optimize default settings for backend Jackrabbit persistence

7.1.0 New Features

  • [TCAT-1148] - Introducing the possibility to upgrade the agent directly from the console

  • [TCAT-1161] - The installer should allow you to configure/test ldap connectivity

  • [TCAT-1200] - Deployment name should be able to contain colons

  • [TCAT-1221] - Migration tool to migrate existing repository to newer configuration using bundle pool persistence managers

7.1.0 Tasks

  • [TCAT-1110] - Upgrade GWT to version 2.5

  • [TCAT-1123] - Upgrade bundled JRE to 1.7.51 and create the missing installers

  • [TCAT-1128] - Upgrade Spring libraries to version 3.1.4

  • [TCAT-1150] - Upgrade maven plugins to their last version

  • [TCAT-1180] - Migrate distributionManagement to the new corporate nexus

  • [TCAT-1187] - Create upgrader for changes in deployment and server schema in jackrabbit

  • [TCAT-1225] - Upgrade bundled Tomcats to 7.0.53 and 6.0.39 respectively. Upgrade other dependent libraries as well

  • [TCAT-1170] - Create a LdapPlugin to update the ldap group configuration

  • [TCAT-1172] - Create a repository copier to allow migration from a jcr PersistenceManager to another

  • [TCAT-1173] - Introduce the possibility to cluster JCR and quartz

  • [TCAT-1197] - Enable closure compiler

Tcat Server 7.0.2 Release Notes

7.0.2 Sub-Tasks

  • [TCAT-1138] - Upgrade bundled version of tomcat to version 7.0.37

  • [TCAT-1147] - Upgrade bundled version of tomcat to version 7.0.39

7.0.2 Bug Fixes

  • [TCAT-916] - Webapps can be deployed to empty Server group.

  • [TCAT-987] - Slow console/timeouts and continuous exceptions

  • [TCAT-1027] - On Deployments, you cannot change the name of deployable application from the repo.

  • [TCAT-1048] - On Dashboard, Webapp status, checkboxes of deployed webapps are cleared each 10 seconds.

  • [TCAT-1145] - ErrorPanel shows link to "Error message details". On clicking it just displays "null"

7.0.2 Improvements

  • [TCAT-45] - Support concurrent deployment of applications within a package

  • [TCAT-1140] - Console very slow when listing deployments both on the dashboard as well as on the deployments tab

  • [TCAT-1143] - Deleting a deployment is not immediately reflected on the deployments list page

  • [TCAT-1149] - Allow JmDns disabling via system properties

Tcat Server 7.0.1 Release Notes

Tcat Server 7.0.1 includes a large number of high priority bug fixes, and new improvements and updates.

7.0.1 Parallel Deployments

Tcat now allows you to perform true parallel deployments. Earlier, most of your deployments were added to a queue and if a deployment took too long, then all subsequent deployments were kept waiting. Now you can setup a thread pool and configure the number of threads you need to spawn, whereby each thread is allocated to one deployment. You can create a in WEB-INF/classes directory and update the property named deployments.corePoolSize.

7.0.1 Slowness in Listing Deployments

You should now see improvements in this area. Deployments are now listed slightly faster than before.

7.0.1 Upgraded Bundled Tomcat Version

The bundled Tomcat version is now upgraded to 7.0.30.

7.0.1 Less Noisy Logs

We’ve tweaked the loggers so as to suppress the noisy Lucene index messages. Your log files now are smaller and quieter.

7.0.1 Bug Fixes

  • [TCAT-610] - Restarts of Tcat Server Agent from causes ItemNotFoundException

  • [TCAT-658] - Files → New File → Upload is causing Write access denied error

  • [TCAT-1025] - About dialog box should point at 2012 instead of 2011.

  • [TCAT-1026] - On Deployments, when creating a new deployment, context path of the webapp disappears after clicking on the field.

  • [TCAT-1037] - On Deployments, when creating a deployment, any file can be uploaded as webapp.

  • [TCAT-1042] - On Deployments, when creating a new deployment, you can undeploy and redeploy even if no server and/or app is specified.

  • [TCAT-1044] - On Administration, Users Group, you can delete a user group even if it has 1 or more users associated to it.

  • [TCAT-1049] - On Dashboard, Webapp status, there is only one entry per webapp, no matter if there are different webapp with different status, deployments, etc.

  • [TCAT-1051] - On Alerts, destinations, on edit mode, delete button has incorrect label.

  • [TCAT-1054] - On Dashboard, Server Metrics, system does not allow to add "Avg Response Time" and/or "Error Count" portlets.

  • [TCAT-1057] - Tcat 7.x build on RED because issues with installer module.

  • [TCAT-1058] - System does not allow to re pair a server.

  • [TCAT-1060] - Server autodiscovering does not work.

  • [TCAT-1063] - On Repository, error message when deleting apps used on deploys is incorrect.

  • [TCAT-1064] - On Rest API, system does not create server group.

  • [TCAT-1069] - On Servers, unable to register a server successfully using IBM JDK.

  • [TCAT-1090] - tcat-env.conf not loaded correctly on OSX

  • [TCAT-1102] - Connector’s stats not showing up

  • [TCAT-1109] - Ldap login fails silently

  • [TCAT-1115] - MMC exception: This node already exists: /ldapUserMetadata/_x0031_45206

  • [TCAT-1118] - Registering a host with domain name replaces the domain name with an IP address

  • [TCAT-1122] - Slowness while listing deployments

  • [TCAT-1126] - showDashboard property not getting persisted while using ldap

  • [TCAT-1132] - Deployments can’t be performed while a failed deployments is still in progress

  • [TCAT-1133] - Artifact with the same name existing in 2 different repository, only versions of one are prompted.

7.0.1 Improvements

  • [TCAT-1097] - AccessControlManagerImpl.doCreateInitialNodes should not use hardcoded values

  • [TCAT-1099] - Upgrade bundled version tomcat to version 7.0.30

  • [TCAT-1108] - Increment the request we receive from prospect downloading Tcat

  • [TCAT-1125] - Improve redirect after login

Tcat Server 6.4.5 Release Notes

Tcat Server 6.4.5 includes a large number of high priority bug fixes, and several new improvements and updates.

6.4.5 CATALINA_BASE Installation Creation Script

For Tcat on Non-Windows Operating Systems

Tcat now includes a script that allows you to install any number of independently operable Tcat Server installations as CATALINA_BASE directories that all run using the same CATALINA_HOME Tcat installation. This script allows Tcat users to take full advantage of the CATALINA_HOME / CATALINA_BASE split feature of Apache Tomcat, combined with the Tcat Server reliable restarts and single command upgrades. The script is named 'tcat-base' (look in the CATALINA_HOME/bin directory).

6.4.5 REST API Improvements

  • The Tcat console REST API now supports 'Set Profile' REST API calls for individual servers and server groups.

  • Deleting files and directories via the REST API now functions as it should.

  • Deleting deployments via the REST API now functions as it should.

  • Some other misc REST API bugs are now fixed (listed below).

6.4.5 Continuous Deployment from Maven to Tcat via Ant Tasks and Logic

While implementing Tcat 6.4.5 we also developed some Maven POM format XML that allows you to have full programmatic control over your continuous deployments to and through the Tcat console. This Maven POM format content lets you store and deploy your webapps into the Tcat Server console when your webapps are built via Maven.

6.4.5 Continuous Deployment Purge Script

When you are continuously deploying your webapp(s), many versions of them accumulates in your Tcat console content repository. You typically only be deploying these webapps for a period of time, and then older versions of your webapps are no longer used. These older versions tend to be large binaries that are not deployed anywhere anymore, and it is better to purge them from your repository instead of allowing them to accumulate and use disk space. Tcat 6.4.5 adds a new continuous deployment purge script that you can configure to run periodically to purge the older copies of your webapps from Tcat’s repository. This script only purges webapps that are not currently deployed – you may configure how long the script keeps webapps when they are no longer in use. Find the script in Administration > Admin Shell.

Due to one or more security fixes and enhancements, along with several bug fixes, it is important to upgrade your Tcat agent webapp to the 6.4.5 version of the agent. The Tcat 6.4.5 console can still register and control older versions of the Tcat agent, and recent older Tcat console versions can still register and control the new 6.4.5 agent, but it is important to upgrade your agents with the fixes contained in version 6.4.5.

6.4.5 Fixed and Implemented Issues

Issue Type Key Summary Fix Version

New Feature



Include a CATALINA_BASE installation creation script for Tcat on non-Windows Oss

New Feature


Management Server, REST API, Tools

Continuous deployment from Maven to Tcat via Ant Tasks/Logic

New Feature



Solaris support in the tcat-base script

New Feature



Add 'Set Profile' REST APIs for individual servers and server groups

New Feature



Continuous deployment purge script: purge old repository artifacts




Upgrade to a newer version of the Derby database



Generic (other) UI

License text changes



Repository, REST API

REST repository workspace delete fails if path doesn’t begin with /Applications




Lack of Manage Server Profiles permission truncates server list




Windows service doesn’t support CATALINA_BASE with spaces in install paths




JCR data inconsistency causes NPE on Deployments tab




REST API does not delete deployments




Tailing of logs of any size freezes console




Failed (re)deployments leave copies of WAR files in temp




Rapid deploys / undeploys fail due to random agent command ordering



Agent, Deployment

When autoDeploy=true Tcat deployments can be autodiscovered / deployed




Context files and work files aren’t deleted for multi-level context root deployments



Generic (other) UI

Server profiles artifact version combo box doesn’t show all choices




Agent allows requests from any HTTPS client when HTTPS is in use




Log screen doesn’t dynamically resize vertically




Server health status never updates in the ServerListPanel




Deployment wrongly shows success status even when it did not deploy



Console Permissions, Repository

Profile repository artifact permission denials cause server list exceptions



Deployment, Repository

Console web UI slows due to accumulation of objects in the database




Agent should open secure agent socket on original connector’s address



Agent, Deployment

Tomcat manager mistakenly allows concurrent (un)deployment of a URI




REST API NPE when creating deployment without webapps causes console UI render problem




Activity log records system user in some cases instead of the logged in user




Init script shell erroneously propagates its process signals to Tomcat JVM




Alert Description is missing when displaying raised alert



Repository, REST API

Atom artifact creation response href broken when version contains colon



Agent, Management Server

Console GWT UI disappears when trying to display tcat-agent-sys log



Generic (other) UI

In console: Can’t expand width of dropdown to select artifact revision




REST API file and dir delete does not work




Tcat is unable to deploy two of the same webapps with different URIs



Generic (other) UI

On IE: vertical scrollbar is missing on the Server tree panel

Tcat Server 6.4.4 Release Notes

Tcat Server 6.4.4 includes several new improvements, updates, and bug fixes.

6.4.4 Tcat Server Console Security Improved

  • Fine grained user activity logging was added in this release. Here are the activities that are captured in the activity log, when a user is using the console either from their favorite web browser, or via the console REST API:

    • User Login Failed

    • User Login Successful

    • User Creation

    • User Deletion

    • User Password Change

    • User Permission Change

    • Server Register

    • Server Unregister

    • Server Save

    • Server Restart

    • Server File Read

    • Server File Metadata Read

    • Server File Write

    • Server Directory Listing

    • Deployment Save

    • Deployment Deploy

    • Deployment Undeploy

    • Deployment Redeploy

    • Deployment Rollback

    • Deployment Delete

  • The console now hides sensitive / password attribute values in the JMX browser. The hidden attribute names are configurable, but the default hidden attribute names are:

    • password **keystorePass

    • keypass

    • trustStorePass

    • connectionPassword

    • userPassword

    • SSLPassword (Tomcat 5.5)

    • secret

    • passphrase

  • The console now times out and invalidates its server session after a configurable duration of inactivity. In previous versions, the GWT heartbeat was preventing inactivity session timeouts.

  • A bug was preventing an administrator from changing another user’s group membership successfully. That is now fixed.

  • By default, the agent is configured to disallow a console user to read/write any files in the tcat-data directory.

6.4.4 Deployment Status Panel Improvements

  • The Deployment panel now updates more frequently to reflect a more up to date and accurate deployment status.

  • There were some edge conditions where the deployment status said Success, but the deployment had failed asynchronously in the background. This is now fixed.

  • The console now shows both the last deployment action as well as the current deployment status – two separate / distinct fields of information.

6.4.4 REST API Improvements

  • The Tcat console REST API now supports creating new directories on the managed Tomcat servers. In previous releases it was possible to create new files on the managed servers via the REST API, but there was no way to create directories.

6.4.4 Updated to the latest Tomcat 6.0.32

Tcat Server 6.4.3 Release Notes

Tcat Server 6 R4 P3 includes several new improvements and bug fixes.

6.4.3 Server Metrics on Global Dashboard

In addition to viewing server metrics on the server dashboard, portlets can be created on the main dashboard which monitor critical statistics for servers or server groups. This allows you to track statistics like requests/second for a group of servers or put a critical application specific JMX metric front and center on the main dashboard.

6.4.3 Alerting improvements

In addition to being able to alert at a per server level, many alerts can now be applied to server groups as well, allowing you to more easily monitor your servers. These include server up/down alerts, log regex alerts, JMX alerts, and web application statistic alerts.

6.4.3 Full Support for the Latest Tomcat 7

Tcat now includes full support for the latest version of Tomcat, version 7.0.5 beta. You may mix and match Tomcat versions that are registered with a Tcat Server console, from Tomcat version 5.5.x all the way up to and including the latest Tomcat 7.

6.4.3 Solaris Tcat Installer

R4P3 introduces a new automated installer for the Solaris operating system, including supporting multiple Tcat Server installations per Solaris OS installation. The installer offers both GUI installations and "headless" text-only installations, supporting all of the same installation options on Solaris 10 and Solaris 11 as were already available on the Linux and Windows operating systems.

6.4.3 Solaris SMF Service Integration and Reliable Tcat Server JVM Restarts

Tcat Server now deeply integrates with the Solaris 10 Service Management Framework (SMF), supporting standard service querying, stops, starts, and restarts. Tcat now supports fully reliable, scriptable, and remote server JVM restarts on Solaris 10 and Solaris 11. The new Tcat Server installer for Solaris also allows installing multiple Tcat Server installations in the same Solaris OS installation, so that you can start, stop, and restart each Tcat instance independently, and have a different service name for each. You may now also create mixed groups of Tcat servers that run on a set of different operating systems including Solaris, Linux, and Windows, and automate remote server restarts across them without dealing with operating system specific details.

6.4.3 Server Profiles Improvements

Tcat allows adding to an environment variable by referencing the server’s current value. For example if you set JAVA_OPTS in a server profile to "${JAVA_OPTS} -DmyProp=true", then when you apply the server profile to a server, the server’s existing value for JAVA_OPTS is saved, with "-DmyProp=true" added to the end. This makes it easy to add JVM startup arguments, and generally add to the beginning or the end of environment variables.

Tcat allows referencing system properties in server profile environment variable values. For example, if you set the OS_NAME environment variable to "$\{}" in a server profile, when you apply the server profile to a server, Tcat inserts the agent JVM’s "" system property value into the value of the OS_NAME environment variable.

Conditional environment variable value references: You may now use server profiles to conditionally add strings to the server’s environment variable settings. For example: if you set the JAVA_OPTS environment variable to "${JAVA_OPTS} $\{ -sw Windows|-Xmx512m}" in a server profile, when you apply the server profile to a server, Tcat conditionally adds "-Xmx512m" to the value of the server’s JAVA_OPTS environment variable only when the agent JVM is running on Windows.

Tcat allows writing a server profile whose environment variable settings are multiplatform, such that the settings are translated to the agent’s server operating system native shell syntax. For example, if you set MY_ENV_VAR in a server profile to "$\{shell:ANOTHER_VAR}/foo/bar", then that setting stores in tcat-env.conf as MY_ENV_VAR=%ANOTHER_VAR%\foo\bar on Windows OSs, and ${ANOTHER_VAR}/foo/bar on non-Windows OSs such as Linux, MacOS, and Solaris.

6.4.3 Support for the IBM J9 and Oracle JRockit Java VMs

Tcat R4P3 introduced support for the IBM J9 1.5.0 and 1.6.0 JVMs, as well as the Oracle JRockit 1.6.0 JVM. The IBM J9 1.5.0 JVM can only be used with Tomcat vesions 6.0 and newer (due to a problem with the 1.5.0 J9 JVM not accepting self-signed X.509 certificates), while the IVM 1.6.0 JVM can be used with any version of Tomcat 5.5.x and newer. The JRockit 1.6.0 JVM can be used with any version of Tomcat 5.5.x and newer.

6.4.3 Known Issues

  • When exporting a server profile, the browser loads a blank page whose URL says "/serverProfileExport.form?serverProfileId=the-id" when it should instead say "/console/serverProfileExport.form?serverProfileId=the-id". After clicking the Export button, add "/console" to the URL after the host and port, and the export proceeds.

  • Memory usage can be reported incorrectly if you are running a 32 bit JVM on a 64 bit OS.

  • CPU utilization is the utilization reported by the JVM, which is not guaranteed to be correct.

  • Upon the very first start of Tcat, this harmless exception may appear in the catalina.out log file:

    [12-22 14:21:33] WARN  DelegatingMultiEventListener [async-event-thread-1]: Failed to execute <public void com.mulesoft.tcat.server.ServerDataCacheImpl.onServerRegisteredEvent(com.mulesoft.common.server.ServerRegisteredEvent) throws java.lang.Exception> on <com.mulesoft.common.server.ServerRegisteredEvent@1fe1135>java.lang.RuntimeException: org.mule.galaxy.NotFoundException: The item local$b61a5afb-8d9a-4ad8-94d0-9dd18697349b was not found.        at org.mule.galaxy.impl.event.AbstractDelegatingGalaxyEventListener$MethodInvoker.runInTransaction(

Tcat Server 6.4.1 Release Notes

This release includes minor bug fixes only:

  • Memory usage was displayed incorrectly for servers on the main dashboard.

  • Stock Tomcat Windows services are now detected and restarts are now disabled in the console for them since they are not supported.

6.4.1 Known Issues

  • Memory usage can be reported incorrectly if you are running a 32 bit JVM on a 64 bit OS.

  • CPU utilization is the utilization reported by the JVM, which is not guaranteed to be correct.

Tcat Server 6 R4P0 Release Notes

Tcat Server 6 R4 includes many major new features for users, including dashboarding, alerting, permissions and more.

6 R4P0 Dashboards

Tcat now includes global and per server dashboards. The global dashboard allows you to see your overall server health, the status of your deployments, raised alerts (see below) and the status of your web applications. There is also a per server dashboard, where you can view critical information about your server - including deployment information and system metrics. You can also attach different JMX metrics as charts to this dashboard, giving you critical insight into how your servers are performing.

6 R4P0 Permissions

  • Administrators can now lock down Tcat for the different roles in their organization. Permissions are controlled by server group to limit who can view what servers, what information users can view for each server, and what types of actions they can take. Now operations can give read access of their environment to developers or allow certain people to restart servers but not modify anything else.

  • Included are a number of predefined user groups including, Administrators, Server Administrators, Deployers and Monitors.

6 R4P0 Alerting

  • Administrators can now define alerts. There are many different alert types supported, including:

    • Log regular expression: listen for a regular expression in your log files and be alerted when it matches, allowing you to bubble up things like "SEVERE" log errors to your console easily.

    • Web app statistics: Alert based on statistics relating to your webapps like request count, error count, or average response time.

    • JMX: you can now create an alert based on any JMX attribute, such as file descriptor usage or cache statistics, allowing you to monitor nearly anything within your application.

    • Servers going up or down

    • The health of URLs, allowing you to be notified if a public URL becomes unavailable

  • Alerts can also be sent to various destinations via SNMP traps or emails

6 R4P0 JMX Improvements

We now expose our own webapp statistics (request count, average response time, error count) as JMX attributes for customers who already have a monitoring solution and would like to monitor the Tomcat agents directly.

6 R4P0 Known Issues

  • Memory usage can be reported incorrectly if you are running a 32 bit JVM on a 64 bit OS.

  • CPU utilization is the utilization reported by the JVM, which is not guaranteed to be correct.

6 R4P0 Fixed Issues

Key Component Summary



Agent can’t detect a stock Tomcat Windows service



Agent on Tomcat 7.0.5 unable to re-register on console



Cannot remove a user group that was created before ldap integration was setup.



Console throws JCR ItemNotFoundExceptions just after startup



Create Tcat installer for Solaris



Create an Alert type that applies to servers and/or groups



Disable "server is taking longer to respond than normal" message when doing uploads



Enabled APR breaks agent registration



Env var and JVM arg changes not used upon Windows service restart



First space in server profile name field truncates export filename



IBM J9 JDK doesn’t work with Tcat: registration fails on SSL handshake


Generic (other) UI

JMX browser tab for server



Logs tab shows zero logs when running on Oracle JRockit


Generic (other) UI

Low memory alerts don’t fire


Generic (other) UI

Memory utilization reported incorrectly under System Info



Notification fields saved whether or not you click save



On Webapp status portlet on Dashboard section, if you click on the name field of the row, then the checkbox on the left is checked, but regardless of how many clicks on name field, checkbox is not unchecked



Save button disabled when saving a script


Generic (other) UI

Server Dashboard Overview panel is not refreshing properly


Generic (other) UI

Server profile export button doesn’t work in IE



Server uptime in dashboard needs to compute days correctly



Solaris Tcat server restarts and SMF service integration



Support deployment pre-processing for Liferay portlets



Support multiplatform server profiles



Tomcat 7.0.5 NoSuchMethodError when viewing Servlets


Generic (other) UI

Tomcat version on dashboard doesn’t update dynamically



Update documentation for server diagnostics



Update documentation with latest screenshots



View permission (only) not correctly handled on Dashboard: Portlet creation allowed but not persisted.



Webapp status portlet on Dashboard section does not show Deployment information.



When creating a User, there is no validation on email field.



Windows service installer does not always correctly detect JVM binary bitness


Console, Agent

Setting JAVA_OPTS in a server profile caused Tcat restart failures

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub