Tcat Server Release Notes

[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"

[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

[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

[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-1138] - Upgrade bundled version of tomcat to version 7.0.37

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

[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"

[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-610] - Restarts of Tcat Server Agent from startup.sh 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.

[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

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).

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:

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:

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.

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.

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.

Tcat Server now bundles Apache Tomcat 6.0.32, which has security fixes (see http://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.32), and other bug fixes (see http://tomcat.apache.org/tomcat-6.0-doc/changelog.html).

Many other minor bugs are now fixed.

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(AbstractDelegatingGalaxyEventListener.java:206)...

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.

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.

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

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

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.