Live Chat Software by Kayako |
Knowledgebase : Advisories
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
[https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/])
A post on Slashdot
[https://tech.slashdot.org/story/17/02/04/2323204/mozilla-to-drop-support-for-all-npapi-plugins-in-firefox-52-except-flash]
confirmed this news earlier this week:
"Starting March 7, when Mozilla is scheduled to relea...
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 Proper...
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...
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:
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:
...
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 ...
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 res...
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 t...
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 algor...
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
[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...
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
deploy...
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...
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 Storag...
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: AuthConfigFac...