Knowledgebase : Advisories

Overview

When deploying Workflow 5.0.x on Tomcat 9.0 an "HTTP Status 500 - Internal Server Error" is displayed after every restart of the Tomcat web server. The following exception is displayed in the browser:

Tomcat9 HTTP 500

Searchable Stack Trace:


Type Exception Report

Message AuthConfigFactory error: java.lang.reflect.InvocationTargetException

Description The server encountered an unexpected condition that prevented it from fulfilling the request.

java.lang.SecurityException: AuthConfigFactory error: java.lang.reflect.InvocationTargetException
     javax.security.auth.message.config.AuthConfigFactory.getFactory(AuthConfigFactory.java:85)
     org.apache.catalina.authenticator.AuthenticatorBase.findJaspicProvider(AuthenticatorBase.java:1239)


java.lang.SecurityException: org.xml.sax.SAXNotRecognizedException: Feature: http://apache.org/xml/features/allow-java-encodings
     org.apache.catalina.authenticator.jaspic.PersistentProviderRegistrations.loadProviders(PersistentProviderRegistrations.java:65)
     org.apache.catalina.authenticator.jaspic.AuthConfigFactoryImpl.loadPersistentRegistrations(AuthConfigFactoryImpl.java:345)

Environment

FileCatalyst Workflow v5.x
Tomcat 9.0

Resolution

The error displayed above can be resolved by modifying the catalina.properties file which is located inside the installation directory of the Tomcat 9.0 web server. Use the following steps to apply the solution:

  1. Shutdown the Tomcat 9.0 web server.
  2. Using a text editor open the catalina.properties file. It is usually located in /install-path-to-tomcat/conf/. Make a copy of this file before you continue further.
  3. At the very top of the file add the following properties:

    • javax.xml.parsers.DocumentBuilderFactory = com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
    • javax.xml.transform.TransformerFactory = com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
    • javax.xml.parsers.SAXParserFactory = com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
    • javax.xml.datatype.DatatypeFactory = com.sun.org.apache.xerces.internal.jaxp.datatype.DatatypeFactoryImpl

  4. Please note that the properties above are case sensitive. Once these properties have been added to the top of the file you can save and close this file.
  5. Start the Tomcat web server.
Overview

For any of our clients who have upgraded their Mac OS to v10.15 (Catalina) in October 2019, you may encounter the following issue when trying to install our software:



We can confirm that users on older versions of the MacOSX  (v10.10.X to v10.14) will not see this error message and it is only present in the latest release.

This signing issue has been escalated to our Engineering Team and we will post a new release with the fix as soon as possible. 

Please check back here for future updates on the issue. 

Environment

MacOSX Catalina v10.15
FileCatalyst Direct Suite v3.7.3 and older.

Overview

The FileCatalyst Server supports writing to external file systems. Our application can read and write directly to these cloud-based storage vendors by adding them to the User account on the FileCatalyst Server. The following is a list of storage vendors we currently support:

  • Amazon S3
  • Azure Blob
  • OpenStack Swift
  • Google Cloud Storage
  • Backblaze B2
  • Wasabi
  • Dropbox (Labs)

We recognize that there are many vendors who support specific feature sets, however, we would like to advise our clients using any Cloud Storage to configure your tasks without using the following features:

  • Basic and Advanced Progressive Transfers (HotFolder)
  • Transfer File Delta (HotFolder)
  • Transfer Files using Incremental Modes (HotFolder and TransferAgent Express)
  • Auto-Resumes or Overwrites (All Clients)
  • Zipping (All Clients)
All the features mentioned above use the FTP command APPE (append) which means that there will be a file fragment that will have more blocks written to it. Using the features listed above could also leave orphaned files in your storage bucket which is not always visible or accessible by our software. These files are visible using the Native Storage Browser from the vendors and will need to be removed manually to prevent you from being charged with extra fees.

All of the limitations that are placed on External File Systems transfers using FileCatalyst Products are available Section 13: External File Systems page of our Server Documentation:

http://filecatalyst.software/download/filesFCDirect/current/documentation/server/Help.html#efs

Please note the link above requires a download password. You can obtain this by logging into the Support Portal and clicking on Get Download Credentials button in your profile. Alternatively, you can access the documentation from the Help menu from your Server Remote Administration application.


Resolution

Where possible please avoid the features listed above when configuring your transfer options and tasks. 

Overview

For the last decade, we have embedded an SFTP module inside our FileCatalst Server which was sourced using the Apache MINA libraries. Security has been a foremost concern for our clients and in our last few releases, we have tried to harden our security, for example making all our software TLSv1.2 complaint out of the box.  This is possible since we can control the source code.

SFTP is highly secure and requires consistent updates to maintain the security level. The update schedule for Apache does not always match our delivery schedule. This is one of the most important factors of why we will be sun-setting this feature on November 30, 2020.

There are many other vendors who specialize in SFTP delivery and we encourage you to use them, our focus will be towards making accelerated file transfer secure, more reliable and easier to use. If you have any questions regarding how this change will affect your deployment, please reach out to your FileCatalyst Account Executive 


Environment

FileCatalyst Server v3.8.2 and newer.
All Windows, macOS and Linux versions.

Overview

For FileCatalyst Workflow and Webmail (discontinued), we have been producing a Windows-based installer that contained an embedded Tomcat. In the last five years, we have seen many vulnerabilities with Tomcat which have been exposed such as POODLE, Logjam and other man-in-the-middle attack variants. In some cases, Tomcat has been very responsive to patching CATALINA and in other instances, there has been the need to engineer a solution. 

For the Windows platform, we currently have two ways you can install the Workflow product (Standalone Tomcat and Embedded Tomcat) and when it comes to hardening Tomcat or patching or even migration there are variations in the instruction sets. This leads to confusion, loss of productivity and ultimately impacts production. In many cases, we have found that our clients who have used the Windows installer need to migrate away from it at some point to the standalone Tomcat installation.

One of our goals at FileCatalyst is to make our products easier to use. As of November 30th, 2020, we will be removing the Windows Installer and standardizing our installs across Linux and Windows.

We will have migration documentation available on our KnowledgeBase and if you require assistance in migrating your instance you can always reach out to your FileCatalyst Account Executive to discuss your options.

Environment

FileCatlayst Workflow v5.1.2 and older
Windows OS only.

Overview

The FileCatalyst Server traditionally offered an installer on Windows, Linux and macOS. Alongside these packages, we built tools to administer these Servers which are called the Server Remote Admins.

Our commitment to the macOS platform remains strong and we are currently in the process to update all our development and testing infrastructure to support Apple Silicone.

Over the last few years, there has been a significant decline in the number of downloads for the FileCatalyst Server macOS installer as more administrators are opting to use a Linux distribution such as Ubuntu and CentOS to run their server infrastructure. Given a very low number of existing customers running FileCatalyst Server on macOS, we decided to stop producing and supporting the FileCatalyst Server .pkg installer file as of November 30th, 2020.

As of November 30, 2020, the only products that will be supported on macOS are:

  • FileCatalyst Server Remote Admin
  • FileCatalyst Hotfolder and FileCatalyst Hotfolder Remote Admin
  • FileCatalayst Express and TransferAgent
  • FileCatalyst APIs and Command-line tool


We will still be supporting the macOS Server for clients who have a valid support contract and have deployed the Server to their production environments until November 30, 2021, for the FileCatalyst Server v3.8.1 build 99 only.

If you are looking to migrate your current macOS Server to another platform please submit a ticket to using our Support Portal. Alternatively, you can also reach out to your FileCatalyst Account Executives to assist you with migration planning as well.

The FileCatalyst Server and the Remote Admin applications will continue to be produced for Windows and Linux platforms and only FileCatalyst Server Remote admin application will be produced for macOS.

Environment

FileCatalyst Server v3.8.2 and newer.
macOS platform only.
Overview

Internet Explorer has been the stock web browser that has been packaged in every Windows OS. As of November 30, 2020, Microsoft plans to end extended support for this browser. Following in the same footsteps we will also be terminating support for Internet Explorer browsers at this time as well.





You can read the full details of this update here: https://techcommunity.microsoft.com/t5/microsoft-365-blog/microsoft-365-apps-say-farewell-to-internet-explorer-11-and/ba-p/1591666

For our clients who are on Internet Explorer, we would highly recommend migrating your workflows to use Chrome, Firefox or Edge browsers.



Environment

Windows OS - Internet Explorer (all version)


FileCatalyst Workflow
FileCatalyst TransferAgent
FileCatalyst Server - Link/Upload/Download

Overview

Attempts to add an External File System (EFS) fails on a FileCatalyst Server installed within a Linux environment with an unable to connect error.  

When you click the Test button from the File Systems tab, a dialog box pops up with the message that file system test failed: Please check that your hostname/endpoint is correct.

If you click Save, a dialog pops up to indicate changes committed to FileCatalyst Server and the External File System appears in the File System list. After a few seconds, it turns red and message appears to indicate that it is not available.

Environment

Filecatalyst Server v3.5 and v3.6.

Java v8.0 build 60.

Linux Environment.

Amazon S3 Storage or Azure Blob Storage.

Resolution

To resolve this issue an update to a more recent version of Java is required. The Java upgrade documentation can be found here:

http://docs.oracle.com/javase/8/docs/technotes/guides/install/install_overview.html

 

 

Overview

Behaviour:

Trying to open the FileCatalyst Central Administration page results in Central encountering a 500 error in the web browser. This occurs after installation of Java Version 8 Update 91 or higher on Linux or Windows Environments. MAC OSX users are unaffected by this update of Java 8.

 

Exception:

org.apache.jasper.JasperException: Unable to compile class for JSP: 

An error occurred at line: 1 in the generated java file
The type java.io.ObjectInputStream cannot be resolved. It is indirectly referenced from required .class files

Stacktrace:
        org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:97)
        org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330)
        org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:457)
        org.apache.jasper.compiler.Compiler.compile(Compiler.java:374)
        org.apache.jasper.compiler.Compiler.compile(Compiler.java:352)
        org.apache.jasper.compiler.Compiler.compile(Compiler.java:339)
        org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:601)
        org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:344)
        org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:389)
        org.apache.jasper.servlet.JspServlet.service(JspServlet.java:333)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:722)

 


Environment

Windows and Linux OS.

FileCatalyst Central all versions.

Java Version 8 Update 91 or higher. (JRE or JDK) 

 

Resolution

  1. Turn off the FileCatalyst Central Service.
  2. Install an older version of Java, older than version mentioned in the Environment.
  3. Point the FileCatalyst Central folder Java Path in the mawrapper.conf to the correct Java path. 
  4. Search for wrapper.java.command=
  5. Replace this path after the = to point to the older <path to Java Install>\Java\bin\ version. For example:
    # Java Application
    wrapper.java.command=C:\Program Files\Java\jdk1.8.0_73\jre\bin\java
  6. Start the FileCatalyst Central service.

Note: 

Most machines will probably be using the JRE.  Confirm your environment and choose the appropriate version.

See http://www.oracle.com/technetwork/java/archive-139210.html for older versions of Java.

Overview

There are two transfer features in the FileCatalyst HotFolder which have shown some issues when used simultaneously. The Progressive feature allows the HotFolder to transfer the file as it grows. The Incremental feature will limit file transfers to files that are new or have been modified. The Delta of a file is defined as portions of the original file that have been modified or changed. Depending on the Incremental setting selected, either the whole file or File Deltas will be sent to the receiver. More information on the Incremental and Advanced Progressive features are available in the HotFolder documentation.

By default, the Basic Progressive feature is enabled in HotFolder tasks. When Incremental and Progressive options are enabled, the transfer will generate an index of what chunks of the file have been modified. As the size of the original and changed file increases the process of calculating the File Delta takes longer to complete. Factors that can increase the time it takes to process the file include low read speeds from the source drive and low write speeds to the destination drive and insufficient system resources such as CPU and memory allocation.

The problem that we have identified occurs when there are large sized Delta files that need to be transferred and the amount of time that is required to move them and reconstruct the file on the receivers end is not sufficient. In most of these cases, only a portion of the file gets sent and the Delta file is not created fast enough on senders side.

This guide provides a solution for Progressive file transfers without the use of Incremental (Deltas) and Progressive Transfers with the use of Basic Progressive. There are signals sent from the receiver to trigger the next batch of files and by that time this request is processed the read timeout kicks in and terminates the transfer.

Environment

FileCatalyst HotFolder v3.5 to v3.7

Resolution

  1. Dynamic Files Options

    This solution has to be deployed by using the MultiClient option in the HotFolder Task Settings. The Advanced Progressive feature will wait for 5-seconds and this value can be raised in 5-second intervals by modifying step f outlined below. This value can not be predetermined and will be different from one network to another. Use the following steps to deploy a 5-second delay in the transfer:


    1. Open FileCatalyst HotFolder.
    2. Click on the Scheduler Tab on the left and side and select your task. Hit the Edit button above it to access the task settings.
    3. From the Transfer Tab at the top make sure Enable Multi-Client and select the number of MultiClient Connections you would like to use.
    4. Hit the Apply button and then navigate to the Dynamic Files tab.
    5. Select the Advanced Progressive radial.
    6. Check the option that will Wait for file growth to cease. Enter 5 (seconds) for the Wait value.
    7. Hit Ok to save your changes.

  2. HotFolder System Property

    The System Property forces the transfer to delay to 5-seconds after each incremental transfer of the Growing Delta File, the receiver immediately checks if the file has grown while the transfer was taking place. Without the System Property, the transfer would stop and fail if the Delta File hadn't grown (would fail because the Delta File wasn't actually done yet). With the System Property, instead of terminating the transfer, the receiver will wait for 5-seconds and check again. The 5-second delay will automatically add at least 5 seconds to every progressive transfer, and more if the incremental transfers lead to mid transfer delays. So choosing the delay time can have impacts on performance, but choosing a delay that is too short will cause the delta transfers to fail.

    A very important note to mention if you choose to deploy this solution: this feature impacts all progress transfers by delaying their completion by the defined number of seconds. When using this System Property the HotFolder application will accept two types of input, one is an integer which will reflect the Wait Time in Seconds or a boolean value of True which will default the Wait Time to 5-seconds. You can only use one of these two inputs for the System Property. 

    Follow these steps to properly deploy the System Property in the FileCatalyst HotFolder:

    1. Open the HotFolder Control Panel.
    2. Click on Settings on the left side and navigate to the System Properties tab at the top.
    3. Select the Add Property button.
    4. Here are some examples of delay values you can use:

      1. Default 5-Second Delay:

        Property Name: unlimited.fc.progressiveDelayBeforeAppending
        Value: True

      2. 10-Second Delay:

        Property Name: unlimited.fc.progressiveDelayBeforeAppending
        Value: 10

      3. 15-Second Delay:

        Property Name: unlimited.fc.progressiveDelayBeforeAppending
        Value: 15 

      4. After you have entered your delay value click on OK to close the dialog and hit the Apply button to save these changes to your configuration file.

Overview

When hosting the FileCatalyst Server on Amazon Web Services (AWS) - EC2 instances, S3 buckets can be added to the FileCatalyst Server as an external storage device. Amazon provides libraries that we have used to integrate this storage device into the Server where we can read and write to this endpoint.

In FileCatalyst Server v3.6 beta 27, when the Security Group on the EC2 instance is set to allow all IPs the transfer experiences some packet loss and when our congestion control algorithm tries to recover from the packet loss it causes a reduction in the bandwidth in some cases the transfer comes to a halt. The symptoms of the increase in Packet Loss and decrease in Bandwidth happen simultaneously and are visual indicators of issues transferring files into the EC2 deployment.

Our Engineers are currently working with the latest AWS drivers to resolve this issue and improve the performance to reading and writing to S3 buckets.

Environment

FileCatalyst Server v3.6 and newer.
Amazon Web Services - Elastic Compute Cloud Servers.

Resolution

This issue has been reported to AWS Support and it has been confirmed that it is a limitation that is found in their environment. A workaround has been posted on the AWS Support site. Please visit
https://forums.aws.amazon.com/thread.jspa?messageID=428003#428003 to get details on the workaround and deploy the solution.

If you are experiencing this issue and would like assistance please submit a ticket through our Support Portal. In your ticket please reference Bug 5937.

Overview

Google has made changes in the default settings of Chrome version 42, released April 14th, 2015, that block Java applets from running in that browser.

This is part of Google’s announced strategy (http://blog.chromium.org/2014/11/the-final-countdown-for-npapi.html) of eliminating all NPAPI (or NP-API) applet support by September 2015.

For FileCatalyst users, this means that right now you are going to be unable to run our Java applets, as well as everyone else, in your Chrome browsers. 

 

Environment

Google Chrome v42 and later for all Operating Systems.

 

Resolution

As of January 2016, the only web browsers that support Java Applets are:

  • Firefox
  • Internet Explorer v10 and later

FileCatalyst TransferAgent was released in March 2015 as an alternative solution to Java Applets running in Chrome and Firefox. We strongly recommend our users migrate to this application and if you would like more information on deployment and usage of TransferAgent please contact your FileCatalyst Sales Representative or submit a ticket in our FileCatalyst Support Portal.

As of February 2017, the only web browsers that support Java Applets are:

  • Safari
  • Internet Explorer v10 and later.

 

Overview
FileCatalyst Workflow v4.9.9 introduced a new feature called Strict Security. This feature requires the use of the Administration account on the FileCatalyst Server to create and authenticate Virtual Users on the FileCatalyst Server. On Workflow deployments which have a large volume of activity the Server Remote Admin connections can multiply and remain open for long periods of time. These open connections hang and do not close properly. If you use Strict Security as part of your deployment the solution outlined in this article will be useful for you.

This article contains modifications that can be made to the Tomcat Web Server service. Please follow the steps in the resolution section to deploy the fix.

Environment
FileCatalyst Workflow v4.9.9 only.
FileCatalyst Server v3.7 only.
Apache Tomcat v7.0 and v8.0.

Resolution
The modification to the Tomcat Web service will require an addition of Java properties to the Java Additional properties section of the startup script. There are several ways to implement this change, we will cover our recommended method in this section.


  1. Shut down the Tomcat Web Server.
  2. Modifying the Java Additional properties:
    1. For Windows using our embedded Tomcat Installation. You can verify this in Services.msc, the service name will be listed as FileCatalyst Web Workflow or FileCatalyst Workflow.
      1. Using explorer navigate to the installation directory of FileCatalyst Workflow. Drill down into the bin directory inside the apache-tomcat folder. A sample path would be C:\FileCatalyst Web Workflow\apache-tomcat\bin
      2. Run the tomcat7fcwebw.exe application.
      3. Under the General tab make sure the Service Status is Stopped. If it is not hit the Stop button.
      4. Navigate to the Java tab.
      5. In the Java Options tab add the following on a new line:

        -Dunlimited.fc.server.api.globalFCAdminExpiry=1440

      6. Hit Apply to save your changes.

    2. In Windows using the standalone Tomcat Installation. You can verify this in Services.msc, the service name will be listed as Apache Tomcat 7.0 or Apache Tomcat 8.0.
      1. Using explorer navigate to the installation directory of Apache Tomcat. Drill down into the bin directory. A sample path would be C:\Tomcat 8.0\bin
        1. Run the tomcat7w.exe or tomcat8w.exe application.
        2. Under the General tab make sure the Service Status is Stopped. If it is not hit the Stop button.
        3. Navigate to the Java tab.
        4. In the Java Options tab add the following on a new line:

          -Dunlimited.fc.server.api.globalFCAdminExpiry=1440

        5. Hit Apply to save your changes.

    3. For all Linux based deployments, the Java Additional property needs to be added to the catalina.sh file.
      1. In a Terminal window, navigate to the Tomcat directory. Drill into the bin folder.
      2. Using vi or nano open the catalina.sh file.
      3. Locate the export JAVA_OPTS line and add the following property, if this line does not exist then you will need to add the full line:

        Property: 
        -Dunlimited.fc.server.api.globalFCAdminExpiry=1440
        Example:
        export JAVA_OPTS="-server -XX:MaxPermSize=256m -Xmx1200m -Xms1200m -Dfile.encoding=utf-8 -Dunlimited.fc.server.api.globalFCAdminExpiry=1440"

      4. Save your changes and close the file.

  3. Once the property is added, the Tomcat Web Server can be started.
  4. Log into Workflow using the Super Admin Account.
  5. Click on About FileCatalyst button on the top menu bar.
  6. Scroll down the page to Additional Java Info and in this subsection, you should be able to locate the parameter unlimited.fc.server.api.globalFCAdminExpiry if the modifications in step 2 were successful. You should see the following:


    FileCatalyst Workflow Settings

Overview
When you use Java 7 to run the FileCatalyst HotFolder, it can not delete a task from the HotFolder Web Admin UI. This issue was observed when using the FileCatalyst HotFolder Web Admin through FileCatalyst Central or connecting directly to the FileCatalyst HotFolder deployment. 

This issue is only present in Java 7 RE and Java 7 DK.

Environment
Oracle Java 7

FileCatalyst HotFolder v3.7.1 and newer.

Resolution

The best solution would be to upgrade the Java deployment on the Operating System.  The following guide will help you install the latest version of Java:
http://docs.oracle.com/javase/8/docs/technotes/guides/install/install_overview.html


Illustration of the issue:


Error Deleting Task
Overview

Currently, there is a known issue with transferring files that contain some Asian characters in the file name when using the OpenStack EFS driver on the FileCatalyst Server.

This is currently impacting our 3.7.1 build 7 and newer releases. This issue is client independent as the Server contains the driver in question.

We are actively working to resolve this and will update this notification when we have news.

Environment

FileCatalyst Server v3.7.1 and newer.
OpenStack Object Storage.

Resolution

If you encounter this behaviour you will need to rename the problematic file name to transfer and again rename the file at the destination.

A code fix is expected when v3.7.3 is released.

Overview

In Tomcat 9, the core engine starts up faster than previous Tomcat versions and the web front end is active. This means that the HTTP Connector is open and listening to requests from your web browser.

Our application which is a container in the application is still starting and as a result, the end user is presented with a HTTP 500 error.

Sample Stack Trace:

org.apache.catalina.core.StandardHostValve.invoke Exception Processing /workflow/
java.lang.SecurityException: AuthConfigFactory error: java.lang.reflect.InvocationTargetException
     at javax.security.auth.message.config.AuthConfigFactory.getFactory(AuthConfigFactory.java:85)
     at org.apache.catalina.authenticator.AuthenticatorBase.findJaspicProvider(AuthenticatorBase.java:1239)
     at org.apache.catalina.authenticator.AuthenticatorBase.getJaspicProvider(AuthenticatorBase.java:1232)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
     at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:668)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
     at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:408)
     at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
     at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:791)
     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1417)
     at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
     at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
     at java.lang.Thread.run(Unknown Source)


Error observed in the browser:



Environment
FileCatalyst Workflow v5.0.3

Tomcat v9.0

Resolution
This bug resides deeper in the Tomcat code which can not be fixed by FileCatalyst. We have escalated this up to the development team of Apache.

The resolution to this issue is to wait 1-2 minutes and Workflow will start up and synchronize with Tomcat 9.0.

Overview

A recent update to the Firefox framework introduced behaviour where the sessionStorage information no longer persists across new tabs created by our web applications. For example, new tabs are created with the activity views and Server log pages. Because of the new lack of persistence, our web applications experience issues when attempting to authenticate WebSocket connections with the underlying WebServers. These issues cause the customer's pages to properly load, which then leads to unusable pages.


Environment

Firefox v80
FileCatalyst Central 
FileCatalyst Server 
FileCatalyst HotFolder 
FileCatalyst TransferAgent 

Note: For the FileCatalyst Application listed above you could encounter this issue while running v3.7.2 to v3.8.

Resolution

A downgrade of Firefox to a lower version (tested with 77.0) or you can use alternative browsers that we support (Chrome and Edge). Doing so will allow you to successfully view pages that are created in tabs that are produced by our applications.

Our aim is to have this issue resolved in a future build of the products listed above as soon as possible.

Overview

In October of 2015, Mozilla had issued an advisory where Firefox Development intends to remove support for most NPAPI plugins by the end of 2016. (NPAPI Plugins in Firefox)

A post on Slashdot confirmed this news earlier this week: 

"Starting March 7, when Mozilla is scheduled to release Firefox 52, all plugins built on the old NPAPI technology will stop working in Firefox, except for Flash, which Mozilla plans to support for a few more versions. This means technologies such as Java, Silverlight, and various audio and video codecs won't work on Firefox."

For a short period of time, enterprise customers of Firefox have the ability to subscribe to Firefox Extended Support Release which will allow them to continue in browser FileCatalyst Applet usage. Please visit the Firefox ESR Webpage for more details.


For FileCatalyst users, this means that right now you are going to be unable to run our Java applets, as well as everyone else, in your Firefox browsers. 

Environment

Mozilla Firefox v52 and later for all Operating Systems.

Resolution

FileCatalyst TransferAgent was released in March 2015 as an alternative solution to Java Applets running in Chrome and Firefox. We strongly recommend our users migrate to this application and if you would like more information on deployment and usage of TransferAgent please contact your FileCatalyst Sales Representative or submit a ticket in our FileCatalyst Support Portal.

As of February 2017, the only web browsers that support Java Applets are:

  • Safari
  • Internet Explorer v10 and later.

 

Overview
With Oracle releasing Java 9, clients may encounter issues running older versions FileCatalyst applications. This issue will only impact clients using Windows and Linux Environments.

The resolution section will outline how to configure the various FileCatalyst Direct Applications for use with Oracle Java 9.

The parameter that needs to be added is located in the Java Additional Properties section in the FileCatalyst configuration file.

As of v3.7.1, the default Java Additional Properties Section contains the following:

# Java Additional Parameters
wrapper.java.additional.1=-XX:MaxDirectMemorySize=1G
wrapper.java.additional.2=-XX:+UseConcMarkSweepGC
wrapper.java.additional.3=-Dsun.java2d.noddraw=true
wrapper.java.additional.4=-Dcom.sun.management.jmxremote.authenticate=false
wrapper.java.additional.5=-Djava.rmi.server.hostname=localhost
wrapper.java.additional.6=-Dcom.sun.management.jmxremote
wrapper.java.additional.7=-Dcom.sun.management.jmxremote.port=11392
wrapper.java.additional.8=-Dcom.sun.management.jmxremote.ssl=false
wrapper.java.additional.9=-Dcom.sun.management.jmxremote.authenticate=false

Please note that if you modify the configuration file as instructed in the resolutions below, older versions of Java (JRE or JDK 6/7/8) will be unusable.

Environment
Oracle Java JRE/JDK v9.0 only.
FileCatalyst Direct Suite v3.7.1 and older.

Resolution

  1. FileCatalyst Server
    • Shutdown the FileCatalyst Server and the FileCatalyst Server Remote Admin.

      • Windows
        • Open the fcconf.conf file in a text editor.
        • Locate the # Java Additional Parameters section.
        • Add the following property and increment the parameter integer. Using the defaults above your entry will look like:

          wrapper.java.additional.10=-XX:+IgnoreUnrecognizedVMOptions --add-modules=java.xml.bind

        • Save and close the fcconf.conf file and start the FileCatalyst Server service.

      • Linux
        • Open the wrapper.conf file using vi or nano. This file can be found in the conf directory of your installation folder.
        • Locate the # Java Additional Parameters section.
        • Add the following property and increment the parameter integer. Using the defaults above your entry will look like:

          wrapper.java.additional.10=-XX:+IgnoreUnrecognizedVMOptions --add-modules=java.xml.bind

        • Save and close the wrapper.conf file and start the FileCatalyst Server service.

        • If your FileCatalyst Server is running standalone you will need to add the following parameter to the fc_server.sh file before the -jar:

          java -Djava.library.path=. -Dsun.java2d.d3d=false -Xms64M -Xmx1024M -XX:MaxDirectMemorySize=512M -XX:+IgnoreUnrecognizedVMOptions --add-modules=java.xml.bind -jar

  2. FileCatalyst HotFolder
    • Shutdown the FileCatalyst HotFolder and the FileCatalyst HotFolder Remote Admin.

      • Windows
        • Open the fchf.conf file in a text editor.
        • Locate the # Java Additional Parameters section.
        • Add the following property and increment the parameter integer. Using the defaults above your entry will look like:

          wrapper.java.additional.10=-XX:+IgnoreUnrecognizedVMOptions --add-modules=java.xml.bind

        • Save and close the fchf.conf file and start the FileCatalyst Server service.

      • Linux
        • Open the wrapper.conf file using vi or nano. This file can be found in the conf directory of your installation folder.
        • Locate the # Java Additional Parameters section.
        • Add the following property and increment the parameter integer. Using the defaults above your entry will look like:

          wrapper.java.additional.10=-XX:+IgnoreUnrecognizedVMOptions --add-modules=java.xml.bind

        • Save and close the wrapper.conf file and start the FileCatalyst Server service.

        • If your FileCatalyst HotFolder is running standalone you will need to add the following parameter to the fc_hotfolder.sh file -jar:

          java -Djava.library.path=. -Dsun.java2d.d3d=false -Xms64M -Xmx1024M -XX:MaxDirectMemorySize=512M -XX:+IgnoreUnrecognizedVMOptions --add-modules=java.xml.bind -jar

  3. FileCatalyst Central
    • Shutdown the FileCatalyst Central service.

      • Windows
        • Open the mawrapper.conf file in a text editor.
        • Locate the # Java Additional Parameters section.
        • Add the following property and increment the parameter integer. Using the defaults above your entry will look like:

          wrapper.java.additional.10=-XX:+IgnoreUnrecognizedVMOptions --add-modules=java.xml.bind

        • Save and close the mawrapper.conf file and start the FileCatalyst Central service.

      • Linux
        • Open the wrapper.conf file using vi or nano. This file can be found in the conf directory of your installation folder.
        • Locate the # Java Additional Parameters section.
        • Add the following property and increment the parameter integer. Using the defaults above your entry will look like:

          wrapper.java.additional.10=-XX:+IgnoreUnrecognizedVMOptions --add-modules=java.xml.bind

        • Save and close the wrapper.conf file and start the FileCatalyst Central service.

  4. FileCatalyst TransferAgent
    • Shutdown the FileCatalyst TransferAgent service or standalone application.

      • Windows
        • Open the tawrapper.conf file in a text editor.
        • Locate the # Java Additional Parameters section.
        • Add the following property and increment the parameter integer. Using the defaults above your entry will look like:

          wrapper.java.additional.10=-XX:+IgnoreUnrecognizedVMOptions --add-modules=java.xml.bind

        • Save and close the tawrapper.conf file and start the FileCatalyst TransferAgent service or standalone application.

      • Linux
        • Open the wrapper.conf file using vi or nano. This file can be found in the conf directory of your installation folder.
        • Locate the # Java Additional Parameters section.
        • Add the following property and increment the parameter integer. Using the defaults above your entry will look like:

          wrapper.java.additional.10=-XX:+IgnoreUnrecognizedVMOptions --add-modules=java.xml.bind

        • Save and close the wrapper.conf file and start the FileCatalyst Central service.

        • If your FileCatalyst TransferAgent is running standalone you will need to add the following parameter to the fc_transferagent.sh file before the -jar:

          java -Djava.library.path=. -Dsun.java2d.d3d=false -Xms64M -Xmx1024M -XX:MaxDirectMemorySize=512M -XX:+IgnoreUnrecognizedVMOptions --add-modules=java.xml.bind -jar

  5. FileCatalyst CLI/API/SDK

    • When constructing your call add the -XX:+IgnoreUnrecognizedVMOptions --add-modules=java.xml.bind parameter before you call the -jar file.
Overview

The TransferAgent Client contains an SSL Certificate to secure the domain localhost.filecatalyst.net. This domain is used to access the configuration pages and the Express application that is hosted inside the TransferAgent client.

Older builds of TransferAgent (older than v3.7.1) that have not been upgraded at customer's site will start having a warning dialog when they try to browse to the TransferAgent.  The warning looks something like this:



Environment

TransferAgent Client v3.7.1 and older

Resolution

Customers who have access to the Download Archive can access the latest builds of TransferAgent Client and upgrade. Any v3.7.2 build will contain a certificate which does not expire until 2021.

For a complete solutions guide please click here.
Overview

With the release of Tomcat v9.0.19 (April 12, 2019) we have had clients report that our Workflow WAR file deployment has not been successful.


This issue has been escalated to our Development team. In the meanwhile, we recommend that our clients use Tomcat v9.0.16 which can be downloaded from the Tomcat repository available here:

https://archive.apache.org/dist/tomcat/tomcat-9/v9.0.16/bin/

Please note this does not apply to any clients who have used the Windows self-executable installer.

Environment

Workflow 5.0 to 5.0.4

Workflow (legacy builds) 4.9.7 to 4.9.9.