FWD » Core Development » Runtime Infrastructure

10/26/2021

11:56 AM Feature #5776: reduce memory requirements for the FWD client

Yes, memptr/file to memptr/file (m to m, m to f, f to m, f to f) should be an all client operation in a single downcall. Greg Shah

11:33 AM Feature #5776: reduce memory requirements for the FWD client

Another idea: for COPY-LOB when both the source and the target are on the client (like file to memptr), we should do ... Constantin Asofiei

11:25 AM Feature #5776: reduce memory requirements for the FWD client

> In my view, the goal of this task is to identify all APIs which work with byte[] in FWD to transfer data over the n... Greg Shah

10:54 AM Feature #5776: reduce memory requirements for the FWD client

Greg Shah wrote:
> The memptr data only persists on the client. This is required to properly work with native APIs,... Constantin Asofiei

10:45 AM Feature #5776: reduce memory requirements for the FWD client

The BLOB and CLOB support was added in #3500. That task has no useful details about the actual implementation, just ... Greg Shah

10:34 AM Feature #5776: reduce memory requirements for the FWD client

> with every memptr and I think for COPY-LOB, too, we transfer the entire LOB to the client
The memptr data only p... Greg Shah

10:23 AM Feature #5776: reduce memory requirements for the FWD client

The GUI client uses a huge amount of memory. We have had to set it around 1GB for some installations, which is a rid... Greg Shah

10:22 AM Feature #5776 (Test): reduce memory requirements for the FWD client

Greg Shah

10/15/2021

06:00 AM Bug #5734: datetimetz.toStringMessage() incorrect output: the time zone spec is duplicated

The result of converting a @datetimetz@ value to a string with @toStringMessage@ has two time zone specs instead of o... Vladimir Tsichevski

05:48 AM Bug #5734 (Closed): datetimetz.toStringMessage() incorrect output: the time zone spec is duplicated

Vladimir Tsichevski

10/02/2021

08:55 PM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

I think we need to implement the following:
* standard redirections
* log file names and locations
* log helper ... Greg Shah

08:41 PM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

Our "internal" FWD-specific logging is written to @STDERR@. This happens when we write to any @Logger@ instance obta... Greg Shah

10/01/2021

09:37 PM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

This task is intended to implement a unified and simple approach for configuring logging. We need to also consider w... Greg Shah

09:33 PM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration

+4GL Logging Facilities+
* @LOG-MANAGER@ system handle
** assign the @LOGFILE-NAME@ attribute to associate a log ... Greg Shah

09/30/2021

01:17 PM Bug #5703 (Closed): rationalize, standardize and simplify the client-side log file name configura...

Greg Shah

12:35 PM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...

When @clientConfig/outputToFile@ is specified in the directory for an appserver process, the value is treated as a sp... Greg Shah

12:22 PM Bug #5701 (Closed): logfile names for -O outputToFile use the spawner pid instead of the Java (FW...

Greg Shah

11:50 AM Bug #5699: broken logfile name on Windows appserver clients (and probably other cases on Windows)

Spawned appserver clients (and batch processes?) can be configured in the server's directory with a log filename for ... Greg Shah

11:23 AM Bug #5699 (Closed): broken logfile name on Windows appserver clients (and probably other cases on...

Greg Shah