Activity

From 05/24/2026 to 06/22/2026

06/22/2026

04:51 PM Feature #11526: Implement in-memory uniquness validation using Bloom filters: +Review of 11526a, r16609+
I think you are on the right track. The issues previously reported look fixed. I see ot... Ovidiu Maxiniuc
09:18 AM Feature #11526 (Review): Implement in-memory uniquness validation using Bloom filters: I made the changes, now the filters are initialized async on the first validation, until it is fully initialized, it ... Artur Școlnic
06:14 AM Bug #10962 (Internal Test): Optimized multi-table compound components are not invalidated: > Hmm, I think that query.getTableCount() == 1 && limitation can be lifted, in order to avoid setting the reference r... Alexandru Lungu

06/18/2026

03:59 PM Bug #11552: Stale data with write trigger.: Ovidiu Maxiniuc wrote:
> The @doBlock@ itself will not mark the record as @STALE@, just @CHANGED@. Clearly, a secon... Eduard Soltan
03:35 PM Bug #11552: Stale data with write trigger.: I tried to track it back, but something is missing. A link.
The @doBlock@ itself will not mark the record as @STAL... Ovidiu Maxiniuc
02:33 PM Bug #11552: Stale data with write trigger.: Constantin Asofiei wrote:
> Eduard, do you have a standalone test for this? Or these are just observations from deb... Eduard Soltan
02:03 PM Bug #11552: Stale data with write trigger.: Eduard, do you have a standalone test for this? Or these are just observations from debugging? Constantin Asofiei
11:46 AM Bug #11552: Stale data with write trigger.: Lets suppose we will have a buffer scoped to transactional block. As finalizables of this block the will be register... Eduard Soltan
11:18 AM Bug #11552 (New): Stale data with write trigger.: Eduard Soltan

06/17/2026

08:56 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Artur, rebuild the index at FWD server must be done concurrently (the runtime will work without the filter, and the f... Constantin Asofiei
08:53 AM Feature #11526 (WIP): Implement in-memory uniquness validation using Bloom filters: Artur Școlnic
08:52 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Ok, I was reluctant to go with this approach since it would cripple the server on startup for an undetermined amount ... Artur Școlnic
07:44 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Artur Școlnic wrote:
> > * consistency - always rebuilt on server startup, while feeding records from the database t... Constantin Asofiei
07:38 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Constantin Asofiei wrote:
> * degradation - there are cases where a physical table is used as a temp-table - data is... Artur Școlnic
07:16 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: If you have an early implementation, we need some serious stress-testing, for 100s of millions of records, where mult... Constantin Asofiei
07:13 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Artur, these are some notes after having a discussion with Ovidiu:
* degradation - there are cases where a physical ... Constantin Asofiei
04:37 AM Feature #6720: lazy hydration: Committed with the fix for #6720-179 in +6720b/r16636+. Teodor Gorghe

06/16/2026

05:30 PM Feature #11526: Implement in-memory uniquness validation using Bloom filters: +Review of 11526a, r16607+
*I.* I see you have radically changed the way the hash is computed. I see it is closer ... Ovidiu Maxiniuc
09:21 AM Feature #11526 (Review): Implement in-memory uniquness validation using Bloom filters: Ovidiu Maxiniuc wrote:
> ** lines 311, 342: not having default values will make configuration difficult. What shou... Artur Școlnic
08:37 PM Feature #11526 (WIP): Implement in-memory uniquness validation using Bloom filters: +Review of 11526a, r16500..16606+
* @Validation.java@
** lines 151-153: the imports should use the .* syntax (pac... Ovidiu Maxiniuc
10:21 AM Feature #10436: Detect Sequential Data Access and Prefetch Records from the Database: We could detect at runtime and record hints based on this. Those hints could then change how we convert. Greg Shah
09:25 AM Feature #10436: Detect Sequential Data Access and Prefetch Records from the Database: I finished a prototype implementation, it detects when a find unique query is being iterated, meaning that the same s... Artur Școlnic
05:35 AM Bug #11502: Recycle dirty share H2 session: Generally speaking I would expect the dirty db to be less strained than the primary one due to the limited scope of t... Artur Școlnic
05:28 AM Bug #11502: Recycle dirty share H2 session: I don't think cloning *shared primary db* / *tenant primary db* config because of #11502-12.
Dirty DB connections ... Teodor Gorghe
04:50 AM Bug #11502: Recycle dirty share H2 session: Teodor, the shared db has a directory config, it can be used for the dirty shared db. The tenant private databases ha... Artur Școlnic
04:47 AM Bug #11502: Recycle dirty share H2 session: A quick reminder about the question from #11502-12.
#11502 is not a critical issue, but the performance is a bit w... Teodor Gorghe
04:00 AM Feature #6720: lazy hydration: Committed revision *16635* on task branch *6720b*:
* Implemented runtime feedback field usage feature which decides ... Teodor Gorghe
02:36 AM Feature #6720: lazy hydration: Rebased *6720b* to trunk rev *16603*. Latest revision is *16632*.
A copy of old *6720b* is in @devsrv01:/tmp/tg.2026... Teodor Gorghe

06/15/2026

07:11 AM Feature #6720: lazy hydration: Ok, I am starting to rebase this branch.
I have tried to reproduce what you told in previous discussions, two @FOR... Teodor Gorghe
06:36 AM Feature #6720: lazy hydration: > Alexandru/Greg, should I rebase 6720b to latest trunk revision or should I port these to a new branch?
Please r... Alexandru Lungu
04:14 AM Feature #6720: lazy hydration: *Alexandru/Greg*, should I rebase *6720b* to latest trunk revision or should I port these to a new branch?
I have ... Teodor Gorghe
03:59 AM Feature #6720: lazy hydration: I think #10554 fix relevant here because there are more @Session.associate@ calls.
There is a bug with this testca... Teodor Gorghe
01:50 AM Feature #11526 (Review): Implement in-memory uniquness validation using Bloom filters: 11526a can be reviewed. The implemented features are:
1. Filter population and persistence as a separate ant task
2... Artur Școlnic

06/12/2026

09:03 AM Feature #6720: lazy hydration: Alexandru Lungu wrote:
> Well, if you have a result-set and do 3 next operations, the first two rows are lost. If yo... Teodor Gorghe
08:31 AM Feature #6720: lazy hydration: Again, let's back up here and understand what is the case for 4GL code to access to a specific row's results after it... Greg Shah
08:07 AM Feature #6720: lazy hydration: > This would be outside of the PRESELECT. If the buffers used for a PRESELECT query can't be accessed outside of thei... Alexandru Lungu
07:50 AM Feature #6720: lazy hydration: > If a FIND is executed and the FFC is used, then the id provided. The id is checked against the session cache. The s... Greg Shah
07:43 AM Feature #6720: lazy hydration: Alexandru Lungu wrote:
> The fundamental difference between trunk and #6720 is that the session cached DMOs may get ... Teodor Gorghe
07:30 AM Feature #6720: lazy hydration: > I'm not sure I agree on the PRESELECT. I'd like to know what the real cases are where we have to load the DMO after... Alexandru Lungu
06:24 AM Feature #6720: lazy hydration: Greg Shah wrote:
> Is the current implementation handling things like @OPEN QUERY@/@GET@, all scenarios that use thi... Teodor Gorghe
06:21 AM Feature #6720: lazy hydration: I'm not sure I agree on the @PRESELECT@. I'd like to know what the real cases are where we have to load the DMO afte... Greg Shah
05:45 AM Feature #6720: lazy hydration: > We should expand this much further as a first step. After that, we can look at optimizations to minimize cases wher... Alexandru Lungu
04:07 AM Feature #6720: lazy hydration: Greg Shah wrote:
> > Until now, the lazy hydration is done just for three things:
>
> We should expand this much ... Teodor Gorghe
08:40 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I changed the config to be read from directory, each database will have it's config under @database/db_name/orm/bloom... Artur Școlnic
06:41 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: When a record is added, we hash its indexed fields and set the corresponding bits to 1. Those bits may already be sha... Artur Școlnic
06:22 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I'm surprised that the solution doesn't just clear the bits associated with the deleted record. Greg Shah
06:16 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Greg Shah wrote:
> So there will be a "buildup" of invalid (out of date) bits for deleted records?
Yes, but a spa... Artur Școlnic
06:13 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: So there will be a "buildup" of invalid (out of date) bits for deleted records? That is even more of a reason to re-... Greg Shah
02:10 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: A bloom filter is not meant to register a deleted record, there is a separate structure called counting bloom filter ... Artur Școlnic

06/11/2026

03:43 PM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Artur, a more technical question:
The Bloom data structure is inherently additive, you set/add bits as the hashes ar... Ovidiu Maxiniuc
10:37 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: The implementation is at a point where a customer project could be tested fully, I will get on with that and deffer f... Artur Școlnic
09:24 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Constantin Asofiei wrote:
> Artur, some questions:
> * for a running FWD server, when does this gets persisted on d... Artur Școlnic
09:09 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Greg Shah wrote:
> I like the non-persisted nature of the design in #11526-27.
I like it too, unless the population... Artur Școlnic
08:40 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I like the non-persisted nature of the design in #11526-27.
I don't think we can apply changes to the filter befor... Greg Shah
08:37 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Artur, some questions:
* for a running FWD server, when does this gets persisted on disk? Can it recover in case th... Constantin Asofiei
08:32 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: > This is a level of speed that means we don't need to persist things in between server restarts. We could just build... Alexandru Lungu
08:10 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: For now, make the location of the cache configurable. Production deployments must carefully place and secure all fil... Greg Shah
08:10 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: As far as memory consumption for the same 10 tables with 7mil rows goes, these are the values
if all where in the sm... Artur Școlnic
07:56 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Greg Shah wrote:
> This is a level of speed that means we don't need to persist things in between server restarts. ... Artur Școlnic
07:53 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: This is a level of speed that means we don't need to persist things in between server restarts. We could just build ... Greg Shah
07:48 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I tested the filter population on a customer db, I used 10 tables with 7.2 mil rows in total, the filters took only 1... Artur Școlnic
07:34 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: When it comes to security, the filters have no readable data, it is hashed and highly compressed. The more concerning... Artur Școlnic
07:29 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: The easiest and most performant way is to store the artifacts (serialized filters) on the server filesystem, for dist... Artur Școlnic
07:23 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: My point is that this should be a general solution not something hard coded to multi-tenant.
Yes, you can read the... Greg Shah
07:03 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Greg Shah wrote:
> I don't understand why this would be associated with tenant data. This is a general solution for... Artur Școlnic
06:45 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I don't understand why this would be associated with tenant data. This is a general solution for persistence, right?... Greg Shah
06:36 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I actually intended to use an external file. Adding tenant API for filter management is the better and more elegant s... Artur Școlnic
06:28 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Artur Școlnic wrote:
> I just realized that tenant API needs a running server, I think as a first option, manually w... Greg Shah
05:49 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I just realized that tenant API needs a running server, I think as a first option, manually writing all the database ... Artur Școlnic
05:34 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I need a way to specify what tables need to use the filters and what config to apply to them, since filter population... Artur Școlnic
07:48 AM Bug #11502: Recycle dirty share H2 session: There is a list of @c3p0@ parameters which should not be copied from primary database, like @minPoolSize@, @initialPo... Teodor Gorghe

06/10/2026

06:31 PM Bug #11529: Incorrect Data Structure for TenantManager: This is an issue I am thinking for some time now. It is not critical, but only because the single client using a MT-e... Ovidiu Maxiniuc
06:02 PM Bug #11529 (New): Incorrect Data Structure for TenantManager: Ovidiu Maxiniuc
10:03 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Added artifact persistence, initialization from db, support for an Ant task. The code needs proper formatting and jav... Artur Școlnic
08:18 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I am planning to execute the filters initialization as Ant task, it would need to be executed after the import, stric... Artur Școlnic
03:16 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: The structure is a bit array, a very large one, 5 million for example. On write the indexed fields are hashed a few t... Artur Școlnic
08:33 AM Feature #6720: lazy hydration: Greg Shah wrote:
> > Until now, the lazy hydration is done just for three things:
>
> We should expand this much ... Teodor Gorghe
06:44 AM Feature #6720: lazy hydration: > Until now, the lazy hydration is done just for three things:
We should expand this much further as a first step.... Greg Shah
05:40 AM Feature #6720: lazy hydration: I have started to partially implement *Runtime feedback per call-site*, with the key set to @(database, fql)@.
{{C... Teodor Gorghe
03:04 AM Feature #6720: lazy hydration: Greg Shah wrote:
> I wonder if we have minimized the hydration needed? My understanding is that previous attempts a... Teodor Gorghe
01:58 AM Feature #6720: lazy hydration: Greg Shah wrote:
> > I have made these measurements because I need to know if fixing the performance findings, but I... Teodor Gorghe
01:12 AM Feature #6720: lazy hydration: Ovidiu Maxiniuc wrote:
> Teodor,
> I had a quick look at the patch you posted in #6720-159. What I immediately not... Teodor Gorghe
07:14 AM Bug #11288: Check if c3p0 is required for in-memory databases: 11288d was ported to 10614_main rev 16417. Artur Școlnic
06:53 AM Bug #11288: Check if c3p0 is required for in-memory databases: Artur, please patch 10614_main with 11288a now. Constantin Asofiei

06/09/2026

06:47 PM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Sorry to play the devil's advocate.
I understand that the data structure is some kind of SQL index, mapping from ... Ovidiu Maxiniuc
10:09 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Alexandru Lungu wrote:
> This is a red flag for me. We are talking about tens of millions of record. This may requir... Artur Școlnic
09:56 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: > on initialization all records are read from the db,
This is a red flag for me. We are talking about tens of mill... Alexandru Lungu
09:36 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Ovidiu, the new approach is much simpler than that. The initialized filters hold only bits, some of them are set base... Artur Școlnic
09:29 AM Feature #11526 (WIP): Implement in-memory uniquness validation using Bloom filters: This is definitely a new approach.
Some notes in this regard:
* at 'in-memory' level, we already have @UniqueTrac... Ovidiu Maxiniuc
09:19 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Committed the initial version, so far it supports only in memory insertion/filter population and lookup, the filters ... Artur Școlnic
04:15 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: A Bloom filter is a space-efficient probabilistic data structure used to quickly test whether an item has been seen b... Artur Școlnic
04:05 AM Feature #11526 (Review): Implement in-memory uniquness validation using Bloom filters: Artur Școlnic
10:49 AM Feature #6720: lazy hydration: > I have made these measurements because I need to know if fixing the performance findings, but I think I shall find ... Greg Shah
10:43 AM Feature #6720: lazy hydration: Teodor,
I had a quick look at the patch you posted in #6720-159. What I immediately noticed is that it rolls back R... Ovidiu Maxiniuc
08:41 AM Feature #6720: lazy hydration: I have done some tests *6720b* vs *trunk* and these are the measurements:
|_. scenario |_. rows |_. fields |_. 4GL (... Teodor Gorghe
03:20 AM Feature #6720: lazy hydration: This is the list of findings for a patch which I am using (based on *6720b*):
{{Collapse(Findings)
h1. Code Review ... Teodor Gorghe
03:34 AM Bug #11502: Recycle dirty share H2 session: It is good, but the used config for the data sources is the default one, it needs to use the tenant specific one to a... Artur Școlnic
03:30 AM Bug #11502: Recycle dirty share H2 session: Can you take into the patch? Is a reasonable change? Teodor Gorghe
03:29 AM Bug #11502: Recycle dirty share H2 session: If it helps a customer application, I am ok with adding it back, just make sure to inherit the configuration of the d... Artur Școlnic
03:25 AM Bug #11502: Recycle dirty share H2 session: Artur Școlnic wrote:
> Connection pooling was removed for the Meta and Dirty databases to simplify configuration and... Teodor Gorghe
03:07 AM Bug #11502: Recycle dirty share H2 session: Connection pooling was removed for the Meta and Dirty databases to simplify configuration and improve maintainability... Artur Școlnic

06/08/2026

06:06 AM Bug #11502: Recycle dirty share H2 session: Artur, can you explain your changes for #11288 regarding dirty database?
I think the easiest way to fix the perfor... Teodor Gorghe

06/03/2026

04:29 AM Bug #9194 (WIP): FWD selects the wrong index when using CONTAINS?: False alarm, it seems that the selected index is wrong even with the recent trunk. The discussion happened in #11448. Radu Apetrii
04:03 AM Bug #9194 (Test): FWD selects the wrong index when using CONTAINS?: Radu Apetrii

05/29/2026

08:11 AM Bug #11502: Recycle dirty share H2 session: Teodor, mind the effort in #8388 of dropping dirty-share being stored in H2, but in persistence database. Alexandru Lungu
08:00 AM Bug #11502: Recycle dirty share H2 session: Currently, on @DefaultDirtyShareManager@, when we need the dirty-share session, we use @new Session(dirtyDatabase)@ a... Teodor Gorghe
07:43 AM Bug #11502 (Internal Test): Recycle dirty share H2 session: Teodor Gorghe
06:15 AM Feature #9545: confirm/add table parameter support: Rebased to trunk rev. 16588. Eduard Soltan
06:06 AM Bug #11501: Investigate useSnapshot usage in multi-table indexed-reposition queries: This task is dedicated for investigating how the @useSnapshot@ array shall be used in the context of an invalidate mu... Alexandru Lungu
06:00 AM Bug #11501 (New): Investigate useSnapshot usage in multi-table indexed-reposition queries: Alexandru Lungu
05:52 AM Bug #10962 (WIP): Optimized multi-table compound components are not invalidated: > [MAJOR] functional CompoundQuery.stateChanged: Replaces cursor.peekLastLoadedResult() with cursor.peekLastLoadedRes... Alexandru Lungu
03:22 AM Bug #11499: Debug and fix query logging issues: Great, thanks Alexandru.
Radu,
I am hoping you could help me with a few things, my first question is why the report... Artur Școlnic
03:19 AM Bug #11499: Debug and fix query logging issues: I added Radu to this task; he is the dinosaur that built this a long time ago already :) Alexandru Lungu
02:23 AM Feature #4369 (Test): implement stateless FWD server clustering: 4369a was merged to trunk rev. 16588 and archived. Eduard Soltan
01:58 AM Feature #4369 (Merge Pending): implement stateless FWD server clustering: Eduard: please merge 4369a now. Constantin Asofiei
01:57 AM Feature #4369: implement stateless FWD server clustering: Ovidiu Maxiniuc wrote:
> Greg Shah wrote:
> > [...] we are waiting on Ovidiu's thoughts on the metadata configurati... Constantin Asofiei

05/28/2026

02:11 PM Feature #4369: implement stateless FWD server clustering: Constantin Asofiei wrote:
> Is the wiki complete? Ovidiu, can you take a look, too? [[p2j:Stateless_Server_Clusteri... Ovidiu Maxiniuc
02:03 PM Feature #4369: implement stateless FWD server clustering: Ovidiu Maxiniuc wrote:
> * then there is the @useMeta@ in @DatabaseManager@. Even if the meta tables are availab... Eduard Soltan
12:50 PM Feature #4369: implement stateless FWD server clustering: Greg Shah wrote:
> [...] we are waiting on Ovidiu's thoughts on the metadata configuration.
Yes, I am a bit concern... Ovidiu Maxiniuc
12:16 PM Feature #4369: implement stateless FWD server clustering: Is the wiki complete? Ovidiu, can you take a look, too? [[p2j:Stateless_Server_Clustering]] Constantin Asofiei
11:58 AM Feature #4369: implement stateless FWD server clustering: Eduard Soltan wrote:
> Waiting for large gui application smoke tests, and I will retest chui just in case.
Large ... Eduard Soltan
08:40 AM Feature #4369: implement stateless FWD server clustering: Greg Shah wrote:
> Did you change the default setting for metadata (at least in non-clustered mode)?
>
Yes, now i... Eduard Soltan
08:38 AM Feature #4369: implement stateless FWD server clustering: Did you change the default setting for metadata (at least in non-clustered mode)?
We need clear documentation on h... Greg Shah
08:32 AM Feature #4369: implement stateless FWD server clustering: Constantin Asofiei wrote:
> OK, anything else left to test or work?
Waiting for large gui application smoke tes... Eduard Soltan
08:09 AM Feature #4369: implement stateless FWD server clustering: Eduard Soltan wrote:
> Constantin Asofiei wrote:
> > Did you do a security scanning of the other jars brought by ge... Constantin Asofiei
07:15 AM Feature #4369: implement stateless FWD server clustering: Constantin Asofiei wrote:
> Did you do a security scanning of the other jars brought by geode in 4369a?
Yes, ther... Eduard Soltan
05:03 AM Feature #4369: implement stateless FWD server clustering: Did you do a security scanning of the other jars brought by geode in 4369a? Constantin Asofiei
04:32 AM Feature #4369: implement stateless FWD server clustering: Constantin Asofiei wrote:
> Eduard, is this gradle change in the branch? What about the other jars?
I upgraded th... Eduard Soltan
04:27 AM Feature #4369: implement stateless FWD server clustering: Constantin Asofiei wrote:
> Eduard, is this gradle change in the branch? What about the other jars?
I committed o... Eduard Soltan
04:21 AM Feature #4369: implement stateless FWD server clustering: Eduard, is this gradle change in the branch? What about the other jars?
Can we finish testing today for the other ... Constantin Asofiei
11:48 AM Bug #11499: Debug and fix query logging issues: Artur Școlnic wrote:
> Another issues is meta table logging that is logged at the persistent table level, it must me... Ovidiu Maxiniuc
07:01 AM Bug #11499: Debug and fix query logging issues: A few explanations for the unexpected logs:
1. Some of the queries were not logged because the reported time was bel... Artur Școlnic
06:21 AM Bug #11499: Debug and fix query logging issues: Another feature I want to add is a base latency log, I think executing a simple @Select 1@ and logging the time is a ... Artur Școlnic
06:12 AM Bug #11499 (WIP): Debug and fix query logging issues: Artur Școlnic
06:11 AM Bug #11499: Debug and fix query logging issues: Query logging seems to have a few unexpected issues, this is one example... Artur Școlnic
06:03 AM Bug #11499 (WIP): Debug and fix query logging issues: Artur Școlnic

05/27/2026

11:08 AM Feature #4369: implement stateless FWD server clustering: ... Eduard Soltan
09:41 AM Feature #4369: implement stateless FWD server clustering: Constantin Asofiei wrote:
>
> We need to move to 6.2.18 version in build.gradle - is this possible?
>
I looke... Eduard Soltan
05:58 AM Feature #4369: implement stateless FWD server clustering: Constantin Asofiei wrote:
> Additional testing: in multi-tenant mode and with i.e. 150 or 200 classic agents started... Eduard Soltan
05:51 AM Feature #4369: implement stateless FWD server clustering: Eduard Soltan wrote:
> I have tested ETF and chui on my side, they both pass.
Great, then I won't bother with ETF.
... Constantin Asofiei
05:50 AM Feature #4369: implement stateless FWD server clustering: Constantin Asofiei wrote:
> 4369a is OK. ChUI passed, I'll let you know about ETF.
>
I have tested ETF and ch... Eduard Soltan
05:49 AM Feature #4369: implement stateless FWD server clustering: 4369a is OK. ChUI passed, I'll let you know about ETF.
Eduard: we need to figure out the spring library version we... Constantin Asofiei
08:39 AM Bug #7667 (Test): Support OUTER-JOIN with PRESELECT at conversion: #11470 was fixed and support is now in trunk. Alexandru Lungu

05/26/2026

03:53 PM Feature #4369: implement stateless FWD server clustering: Constantin Asofiei wrote:
> * @GuiWebSocket.java@ needs to be reverted to trunk revision
Meant to solve some ja... Eduard Soltan
02:38 PM Feature #4369: implement stateless FWD server clustering: Also: please rebase when convenient so other projects can be tested. Constantin Asofiei
02:36 PM Feature #4369: implement stateless FWD server clustering: Eduard, good work, there are only a few more issues; I'll run ETF and ChUI with this. Please also rebase. Bellow is ... Constantin Asofiei
01:16 PM Feature #4369: implement stateless FWD server clustering: Constantin Asofiei wrote:
> Eduard Soltan wrote:
> > Committed on 4369a, rev. 16616.
> >
> > I think this handle... Eduard Soltan
12:31 PM Feature #4369: implement stateless FWD server clustering: Eduard Soltan wrote:
> Committed on 4369a, rev. 16616.
>
> I think this handles everything.
Did you address the ... Constantin Asofiei
11:32 AM Feature #4369: implement stateless FWD server clustering: Committed on 4369a, rev. 16616.
I think this handles everything.
About the spring-dependecy:... Eduard Soltan
03:30 AM Feature #4369: implement stateless FWD server clustering: Eduard, this is review for 4369a rev 16611:
* for the management of temp group and users
** there should be a singl... Constantin Asofiei
02:37 AM Feature #4369: implement stateless FWD server clustering: Eduard, how's the testing going for other apps?
> Fix is to exclude spring-jcl dependency.
I don't see this in b... Constantin Asofiei
08:11 PM Feature #4369: implement stateless FWD server clustering: +Review of 4369a / r16611 (with focus on persistence)+
This is a huge changeset. I focused on persistence mainly, ... Ovidiu Maxiniuc

05/25/2026

04:43 AM Bug #7667 (Pending): Support OUTER-JOIN with PRESELECT at conversion: This is being implemented in #11470. Alexandru Lungu
02:16 AM Feature #4369: implement stateless FWD server clustering: Constantin Asofiei wrote:
> > -chui regression testing (had to eliminate spring-beans-5.3.20.jar, spring-core-5.3.20... Eduard Soltan
01:51 AM Bug #11288: Check if c3p0 is required for in-memory databases: Eric,
I don't expect performance in a customer application to be affected in a measurable way, this change was more ... Artur Școlnic

« Previous

Also available in: Atom

Project

General

Profile

FWD » Core Development » Database

Activity

Activity

06/22/2026

06/18/2026

06/17/2026

06/16/2026

06/15/2026

06/12/2026

06/11/2026

06/10/2026

06/09/2026

06/08/2026

06/03/2026

05/29/2026

05/28/2026

05/27/2026

05/26/2026

05/25/2026