Activity

From 01/16/2023 to 02/14/2023

02/14/2023

12:29 PM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration: The problem with the new interface was missing directory.xml configs. Fixed. Galya B

02/13/2023

10:48 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration: I need assistance with FWD RPC. I'm trying to use a new interface for clients to send data to the server, but the cal... Galya B
08:13 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration: I'm currently working on a new logger class that encapsulates the previously used Java Logger and handles a lot of th... Galya B

02/07/2023

08:31 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration: > Client and server are different processes
This is only because of how we implement in FWD. The equivalent syste... Greg Shah
06:11 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration: Back to question 1: clients are separate processes started with different process ids and user ids - do we want their... Galya B
03:02 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration: Greg Shah wrote:
> 2. In regard to "File names are not configurable to make file identification and sorting easier, ... Galya B
02:49 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration: Greg Shah wrote:
> 1. I don't think we want a separate client and server logging infrastructure. The fact that we h... Galya B

02/06/2023

04:46 PM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration: Galya Bogdanova wrote:
> Please review my proposal for standardization of the logging: [[internal-documentation:Logs... Greg Shah
07:37 AM Bug #5703: rationalize, standardize and simplify the client-side log file name configuration: Please review my proposal for standardization of the logging: [[internal-documentation:Logs#Future-Improvements|Logs#... Galya B

02/03/2023

08:35 AM Bug #5703 (WIP): rationalize, standardize and simplify the client-side log file name configuration: I'm trying to figure out what is part of our OpenEdge replica implementation and what is our invention.
* @outputT... Galya B

02/02/2023

12:05 PM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: At this point, we need to pause because of the freeze on trunk. We will rebase and merge when the "thaw" occurs. Greg Shah
12:05 PM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Code Review Task Branch 5701a Revisions 14485 and 14486
The changes are good. Greg Shah
04:18 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Thank you for the explanation. Actually I was able to figure out the first part by reading the documentation for the ... Galya B

02/01/2023

11:40 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Lets consider this code from @spawn.c@:... Greg Shah
10:17 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Galya Bogdanova wrote:
> Eugenie Lyzenko wrote:
> > Yes, I did. @src/native/spawn.c@ has neither history nor year u... Eugenie Lyzenko
09:43 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Eugenie Lyzenko wrote:
> Yes, I did. @src/native/spawn.c@ has neither history nor year update. @src/native/winspawn.... Galya B
09:25 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Galya Bogdanova wrote:
> Eugenie Lyzenko wrote:
> > When you add new history entry with date (@2023MMDD@), and you ... Eugenie Lyzenko
06:04 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Eugenie Lyzenko wrote:
> When you add new history entry with date (@2023MMDD@), and you should mark your change the ... Galya B
06:01 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Galya Bogdanova wrote:
> Eugenie Lyzenko wrote:
> > I have no objections, in addition to history entries it is requ... Eugenie Lyzenko
03:02 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Eugenie Lyzenko wrote:
> I have no objections, in addition to history entries it is required to change Year to @2023... Galya B
02:43 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Greg Shah wrote:
> Code Review Task Branch 5701a Revisions 14484 and 14485
>
> 1. In @spawn.c:launchP2JClient@, t... Galya B

01/31/2023

04:46 PM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Greg Shah wrote:
> Eugenie: Please review branch 5701a.
I have no objections, in addition to history entries it i... Eugenie Lyzenko
03:54 PM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Eugenie: Please review branch 5701a. Greg Shah
03:53 PM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Code Review Task Branch 5701a Revisions 14484 and 14485
1. In @spawn.c:launchP2JClient@, the @memset(arguments[len... Greg Shah
04:47 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: I've tested both Linux and Windows spawner. Here are the final changes in the .diff file, also committed to @5701a@.
... Galya B
03:56 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Constantin Asofiei wrote:
> Galya, please describe how you are running a program on the appserver. A batch program ... Galya B

01/30/2023

08:50 AM Feature #6377: provide tooling (and UI in the admin interface) to manage appserver agents (start/...: I would prefer to implement this using a REST API. We will provide a CLI (command line interface) and would probably... Greg Shah
07:24 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Galya, please describe how you are running a program on the appserver. A batch program executes its 4GL program imme... Constantin Asofiei
06:40 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: So configuration-wise @appserver@ turns into batch if I remove @<node-attribute name="appserver" value="app_server"/>... Galya B
05:05 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Galya Bogdanova wrote:
> Greg, Constantin, I'll need some clarifications here:
> 1. What do you refer to as agent l... Constantin Asofiei
03:25 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Greg, Constantin, I'll need some clarifications here:
1. What do you refer to as agent logs in FWD? @outputToFile@ i... Galya B

01/27/2023

10:44 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: I meant both cases. It sounds like we are OK there, if I understand your points.
Do we have the same control over... Greg Shah
10:38 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Greg Shah wrote:
> > Galya, I've tested in OpenEdge and only @MESSAGE@ statement (with or without @VIEW-AS ALERT-BOX... Constantin Asofiei
09:59 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: > Galya, I've tested in OpenEdge and only @MESSAGE@ statement (with or without @VIEW-AS ALERT-BOX@) end up in the age... Greg Shah
09:53 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Galya, I've tested in OpenEdge and only @MESSAGE@ statement (with or without @VIEW-AS ALERT-BOX@) end up in the agent... Constantin Asofiei
09:09 AM Bug #5701 (Test): logfile names for -O outputToFile use the spawner pid instead of the Java (FWD ...: I'm uploading the latest diff that includes the win changes. They are committed to 5701a as well. I'll be testing tho... Galya B
05:47 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Starting appserver as scheduled batch initializes @ThinClient@, @BatchDriver@, @OutputManager@, @ErrorWriterBatch@, c... Galya B
03:02 AM Feature #7080: expose all admin APIs via REST: A small clarification. The Admin remoting isn't based on @RemoteObject@ since the GWT rewrite.
There are three (GW... Hynek Cihlar

01/26/2023

06:36 PM Feature #7080: expose all admin APIs via REST: Moving to a REST API will provide several benefits.
* It will be a simpler and cleaner model than the current sync... Greg Shah
06:20 PM Feature #7080 (Test): expose all admin APIs via REST: Greg Shah
10:35 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Greg Shah wrote:
> Eugenie: Please review.
The change looks good for me. Eugenie Lyzenko
08:15 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Eugenie: Please review. Greg Shah
08:05 AM Bug #5701 (Review): logfile names for -O outputToFile use the spawner pid instead of the Java (FW...: Galya B
08:01 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...: Find attached a good solution to the wrong pid in @outputToFile@ name. It simplifies the spawner logic by removing a ... Galya B

01/16/2023

05:23 PM Bug #6671: Build configurations need "fine tuning": I found that @src/4gl/embedded/**@ was missing from the *archive* task for the @"${dist.home}/fwd_deploy-convert_${ma... Roger Borrello

« Previous

Also available in: Atom

Project

General

Profile

FWD » Core Development » Runtime Infrastructure

Activity

Activity

02/14/2023

02/13/2023

02/07/2023

02/06/2023

02/03/2023

02/02/2023

02/01/2023

01/31/2023

01/30/2023

01/27/2023

01/26/2023

01/16/2023