Activity
From 01/28/2026 to 02/26/2026
02/26/2026
- 05:39 PM Bug #11235: Deprovisioning tenants does not clear data sources
- Well, that's a philosophical question :).
When a tenant is deleted, beside the effect on the database we discussed a... - 01:46 PM Bug #11235: Deprovisioning tenants does not clear data sources
- Ovidiu, I meant on tenant delete, do we need to disconnect the private database?
- 12:28 PM Bug #11235: Deprovisioning tenants does not clear data sources
- This method is the implementation of @DISCONNECT@ statement. Unfortunately, this is not documented in javadoc. Theref...
- 05:29 AM Bug #11235: Deprovisioning tenants does not clear data sources
- @ConnectionManager.disconnect@ expects the logical db name, which can/should be the same for all the tenant databases...
- 04:55 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Ovidiu Maxiniuc wrote:
> +Review of 11235a / r16440+
>
> Nicely done! I think the code will work as expected.
... - 10:22 AM Bug #7841 (WIP): Invalid conversion of temp table DMO when using clob/blob fields
- I took a quick look here and found this in @rules/include/common-progress.rules@ -> @<function name="create_temp_tabl...
- 09:57 AM Feature #9545: confirm/add table parameter support
- Constantin Asofiei wrote:
> Eduard, the root cause is that the dynamic temp-table created for an argument does not i... - 08:28 AM Feature #9545: confirm/add table parameter support
- Eduard, the root cause is that the dynamic temp-table created for an argument does not inherit the undoable from the ...
- 04:47 AM Feature #9545: confirm/add table parameter support
- We can divide this in 2 cases temp-table *with* @no-undo@ and *without* @no-undo@ option....
- 02:52 AM Feature #9545: confirm/add table parameter support
- Eduard, so please check why FWD doesn't clear the record from the buffer,or otherwise doesn't mark it as 'deleted'. ...
- 02:33 AM Feature #9545: confirm/add table parameter support
- Constantin Asofiei wrote:
> After @doBlock1@ I would expect that in 4GL the buffer has no record (as the tx was roll... - 09:54 AM Bug #11231: FastFindCache clear operations may leak memory
- Review of 11231a:
* @implements Map<K, V>@ clause should be on a new line
* @MINIMAL_LOAD_FACTOR@ should be @minima...
02/25/2026
- 03:34 PM Bug #11235 (Internal Test): Deprovisioning tenants does not clear data sources
- +Review of 11235a / r16440+
Nicely done! I think the code will work as expected.
Please start the regression tests. - 11:29 AM Feature #9545: confirm/add table parameter support
- After @doBlock1@ I would expect that in 4GL the buffer has no record (as the tx was rolledback). Please check this.
- 11:25 AM Feature #9545: confirm/add table parameter support
- Constantin Asofiei wrote:
> Is the buffer @httTest:default-buffer@ still holding the record when @OutputTableHandleC... - 10:53 AM Feature #9545: confirm/add table parameter support
- Is the buffer @httTest:default-buffer@ still holding the record when @OutputTableHandleCopier@ is copied?
- 10:51 AM Feature #9545: confirm/add table parameter support
- Constantin Asofiei wrote:
> Eduard Soltan wrote:
> > I think we need to make this method @finalizable@ aware that a... - 10:50 AM Feature #9545: confirm/add table parameter support
- Eduard Soltan wrote:
> I think we need to make this method @finalizable@ aware that a *rollback happened previously*... - 10:43 AM Feature #9545: confirm/add table parameter support
- start.p...
- 10:05 AM Bug #11161: fail gracefully when the database connection can not be established
- Greg Shah wrote:
> The @CONNECT@ must be in a *separate* @.p@. Call the @<connect_program>.p@ from *within* the 4GL... - 10:01 AM Bug #11161: fail gracefully when the database connection can not be established
- The @CONNECT@ must be in a *separate* @.p@. Call the @<connect_program>.p@ from *within* the 4GL code block that tri...
- 09:51 AM Bug #11161: fail gracefully when the database connection can not be established
- Do nested blocks like this:...
- 09:04 AM Bug #11161: fail gracefully when the database connection can not be established
- Maybe my tests are wrong, I can't seem to register the STOP
connect.p... - 08:50 AM Bug #11161: fail gracefully when the database connection can not be established
- In our past testing, the @STOP@ condition in disconnect cases can be caught, but only by a block that is outside of a...
- 08:40 AM Bug #11161: fail gracefully when the database connection can not be established
- When it comes to database shutdown during an open session:
1. program executed on the server - is terminated, error ... - 08:05 AM Bug #11161: fail gracefully when the database connection can not be established
- Artur Școlnic wrote:
> In OE, failure happens early.
> At the beginning of an unbound session:
> * A database conn... - 06:37 AM Bug #11161: fail gracefully when the database connection can not be established
- I was talking strictly about insufficient database connections, if the connection is interrupted during a session, I ...
- 06:33 AM Bug #11161: fail gracefully when the database connection can not be established
- > In OE, failure happens early.
What about a communications/network failure that happens later? - 04:24 AM Bug #11161: fail gracefully when the database connection can not be established
- *With the current infrastructure, handling database connection starvation remains challenging*
Key Challenges:
...
02/24/2026
- 12:17 PM Bug #11235 (Review): Deprovisioning tenants does not clear data sources
- I added cleanup for the dirty database sources and extended the source clearing to include the tenant update scenario...
- 09:48 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Artur Școlnic wrote:
> Understood, thank you.
> I got another question, using the tenant api, we can update a tenan... - 09:39 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Artur Școlnic wrote:
> Understood, thank you.
> I got another question, using the tenant api, we can update a tenan... - 09:35 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Understood, thank you.
I got another question, using the tenant api, we can update a tenant, including the urls. On ... - 09:17 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Artur Școlnic wrote:
> Ovidiu, please comment on #11235-19.
As documented in javadoc of that method, the returned d... - 09:05 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Constantin Asofiei wrote:
> Do we have a dirty database instance in H2 for each tenant?
Yes. This is the architectu... - 08:57 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Ovidiu, please comment on #11235-19.
- 08:51 AM Bug #11235: Deprovisioning tenants does not clear data sources
- The @sources@ map should contain for a tenant-enabled database:
* @N + 1@ sources for each (postgresql) permanent da... - 08:10 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Artur Școlnic wrote:
> I would expect so. I am using just one tenant, so there are 2 dirty db, the default tenant an... - 08:10 AM Bug #11235: Deprovisioning tenants does not clear data sources
- I would expect so. I am using just one tenant, so there are 2 dirty db, the default tenant and the explicit one.
- 08:08 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Artur Școlnic wrote:
> Ok, it makes sense, so we do need to clear only the data source for the dirty databases.
Do ... - 08:06 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Ok, it makes sense, so we do need to clear only the data source for the dirty databases.
On tenant delete, this is n... - 07:52 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Artur Școlnic wrote:
> Also, what about the _temp database, where the temp tables reside? Shouldn't it also be tenan... - 07:52 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Artur Școlnic wrote:
> Ovidiu,
> I have a few questions:
> 1. Not all h2 databases are marked as @temp@, is this ... - 07:46 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Also, what about the _temp database, where the temp tables reside? Shouldn't it also be tenant specific and cleared o...
- 06:21 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Ovidiu,
I have a few questions:
1. Not all h2 databases are marked as @temp@, is this expected?
2. The dirty data... - 02:33 AM Bug #11235 (WIP): Deprovisioning tenants does not clear data sources
02/23/2026
- 05:43 PM Bug #11235: Deprovisioning tenants does not clear data sources
- I realized that the datasource for dirty database (in-memory, h2 dialect) should also be processed (removed from @sou...
- 09:40 AM Bug #11235 (Internal Test): Deprovisioning tenants does not clear data sources
- +Review of 11235a/r16438+
Good job!
Please start the regression tests. Make sure there are no regressions with th... - 08:18 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Ovidiu,
Constantin raised the question of data source resources retention, mainly the helper threads, just to be on... - 04:06 AM Bug #11235 (Review): Deprovisioning tenants does not clear data sources
- It looks like I was wrong, the values are not overwritten, just a different context local instance of the connection ...
- 03:32 AM Bug #11235 (WIP): Deprovisioning tenants does not clear data sources
- Ovidiu,
I encountered an issues while working with @tenantsByDatabase@, adding a tenant with the same logical datab... - 02:18 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Not sure if it is relevant in these cases, but in certain broker modes, the contexts can be reused across appserver s...
02/20/2026
- 05:57 PM Bug #11235: Deprovisioning tenants does not clear data sources
- +Review of 11235a/r16436+
My bet is the changes will work as expected. Related to this revision I have only some l... - 09:29 AM Bug #11235 (Review): Deprovisioning tenants does not clear data sources
- I added the data source removal on tenant db removal.
Ovidiu, please review 11235a.
Collections affected by ten... - 04:58 AM Bug #11235 (WIP): Deprovisioning tenants does not clear data sources
- 05:43 AM Bug #11231: FastFindCache clear operations may leak memory
- Alexandru, I added a new implementation for the Map that shrinks if the load factor is low enough and used it for ff ...
02/19/2026
- 05:54 PM Bug #11235: Deprovisioning tenants does not clear data sources
- Indeed, at the moment when support for tenants was implemented, the operation of removing them did not take this aspe...
- 09:00 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Artur Școlnic wrote:
> Just to be sure, deprovisioning a tenant means simply deleting it via tenant API?
In FWD ter... - 08:58 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Just to be sure, deprovisioning a tenant means simply deleting it via tenant API?
- 08:27 AM Bug #11235: Deprovisioning tenants does not clear data sources
- FWD creates a data source (connection pool) for each tenant, if one is deprovisioned, the data source is not cleared,...
- 08:25 AM Bug #11235 (Test): Deprovisioning tenants does not clear data sources
- 10:37 AM Feature #4369: implement stateless FWD server clustering
- Alexandru Lungu wrote:
> FYI: I created https://proj.goldencode.com/projects/p2j/wiki/Stateless_Server_Clustering fo... - 09:06 AM Feature #4369: implement stateless FWD server clustering
- FYI: I created https://proj.goldencode.com/projects/p2j/wiki/Stateless_Server_Clustering for documentation on this fe...
- 08:34 AM Bug #11236 (New): Buffers whose scope is restricted to an iterative block shoud be released durin...
- 08:09 AM Bug #11231: FastFindCache clear operations may leak memory
- Please note this change which moved from 'new instance' to 'clear':...
- 07:41 AM Bug #11231: FastFindCache clear operations may leak memory
- Alexandru Lungu wrote:
> I am concerned that the size represents the number of active elements, not the actual cap... - 07:38 AM Bug #11231: FastFindCache clear operations may leak memory
- > When clearing an L3 map, check its current size against a defined threshold:
I am concerned that the size repres... - 07:01 AM Bug #11231 (Review): FastFindCache clear operations may leak memory
- I used the following heuristics to alleviate the issue:
* On L3 clear –
When clearing an L3 map, check its current ... - 05:14 AM Bug #11231 (WIP): FastFindCache clear operations may leak memory
- 05:01 AM Bug #11231: FastFindCache clear operations may leak memory
- After refactoring FFCache to be driven by the @ReverseLookup@, so that there is only one unified LRU cache that contr...
- 04:43 AM Bug #11231 (Test): FastFindCache clear operations may leak memory
- 01:49 AM Bug #10390: FIND FIRST buffer field change does not propagate into the next FIRST FIRST statements.
- ChUI regression testing has passed.
02/18/2026
- 11:44 AM Feature #9545: confirm/add table parameter support
- I can confirm, I have personally tested it.
And I must apologise again. In my note #9545-18 I have actually looked... - 08:33 AM Feature #9545: confirm/add table parameter support
- Greg Shah wrote:
> Have these programs been tested on OE? Sometimes the OE documentation is incorrect, misleading o... - 08:24 AM Feature #9545: confirm/add table parameter support
- Have these programs been tested on OE? Sometimes the OE documentation is incorrect, misleading or incomplete.
- 06:18 AM Feature #9545: confirm/add table parameter support
- Ovidiu Maxiniuc wrote:
> Yet, I think the error is correct. Only the @test22.p@ is persistent. @test21.p@ is not. Th... - 06:10 AM Feature #9545: confirm/add table parameter support
- OK, sorry I was mislead by the persistent initialisation of @test22.p@.
Yet, I think the error is correct. Only th... - 05:42 AM Feature #9545: confirm/add table parameter support
- Ovidiu Maxiniuc wrote:
> The problem in #9545-12 testcase is that @start.p@ declares the temp-table @ttTest@ as @r... - 05:32 AM Feature #9545: confirm/add table parameter support
- Eduard Soltan wrote:
> I understand this, and already handled majority of this error cases in 9545a. What I am tryin... - 03:11 AM Feature #9545: confirm/add table parameter support
- Ovidiu Maxiniuc wrote:
> Eduard,
>
> You can only @BIND@ a temp-table to a @REFERENCE-ONLY@ temp-table. There are...
02/17/2026
- 06:16 PM Feature #9545: confirm/add table parameter support
- Eduard,
You can only @BIND@ a temp-table to a @REFERENCE-ONLY@ temp-table. There are two cases here (these are my ... - 08:48 AM Feature #9545: confirm/add table parameter support
- I could not find this anywhere in the documentation. My best guess is that for calling procedures that passes an actu...
- 07:08 AM Feature #9545: confirm/add table parameter support
- However in a slightly more complicated case, extracted from the testcases:
start.p... - 06:54 AM Feature #9545: confirm/add table parameter support
- start.p...
- 09:35 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Lorian Sandu wrote:
> I've started the @...@ script a few times and unfortunately it gets stuck (or works very slow)... - 09:30 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I've started the @conv-launch@ script a few times and unfortunately it gets stuck (or works very slow) at a step that...
- 01:43 AM Bug #10390: FIND FIRST buffer field change does not propagate into the next FIRST FIRST statements.
- About the testcases cross-session tests, they have passed.
I have run the ChUI regression testing and I see two un...
02/16/2026
- 04:43 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I have made some tests on 9383c for the scenario what *Alexandru* pointed out on #9383-100 (DMO stale records).
Th... - 03:44 AM Feature #8834 (Closed): add bootstrap configuration support for -db OE command line parameter (an...
- 03:28 AM Feature #8834 (Test): add bootstrap configuration support for -db OE command line parameter (and ...
- Merge notification for task branch 8834a.
- 03:18 AM Feature #8834 (Merge Pending): add bootstrap configuration support for -db OE command line parame...
- Please merge 8834a now.
02/13/2026
- 04:50 PM Bug #11015: allow cleanup the DMO types, caches, etc for dynamic temp-tables
- +Review of 11015b, r16411+
First, to note that all affected files lack the H entries and possible (c) year update.... - 10:32 AM Bug #11015: allow cleanup the DMO types, caches, etc for dynamic temp-tables
* @AsmClassLoader@ - seems ok
* @CacheManager@ - is ok
* @DynamicConversionHelper@ - seems ok
* @DynamicTablesHe...- 09:57 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I have started doing some tests, but so far, I have didn't encountered issues with stale records. I will make more te...
- 09:55 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Committed revision *16421* on task branch *9383c*:
- Use @persistence.list@ instead of @persistence.scroll@ to store... - 08:26 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Ok.
In @BatchResults@, I am thinking to change @persistence.scroll@ to @persistence.list@.
One difference is that @... - 04:38 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- > I removed that because the batched records are not currently in the session cache.
But they end up in the sessio... - 03:33 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Ovidiu Maxiniuc wrote:
> I assume the array you mention is the @BaseRecord.data@. Or you mean the cursor data array?... - 03:24 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Teodor Gorghe wrote:
> I don't currently know what @normalized@ means on the extent fields, but what I know is that ... - 02:25 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Alexandru Lungu wrote:
> What we have discussed in a daily today, to keep track of:
>
> * the batch size should b... - 04:21 AM Feature #4369: implement stateless FWD server clustering
- I have continued working on changes needed for clustering in FWD. Even though we initially agreed that caches(includi...
02/12/2026
- 08:35 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- What we have discussed in a daily today, to keep track of:
* the batch size should be calculated based on the data... - 04:05 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Committed revision *16420* on task branch *9383c*:
- @BatchResults@ invalidates the query when PK is different.
- F... - 01:04 AM Bug #10937 (Internal Test): fwd-h2 'killedMultiplexesCleanup' must not abend if the batch is not ...
- Committed revision *16320* on task branch *10937a*:
- Replaced @nonEmptyTableFlags@ with H2 @fastHasRecords@.
02/11/2026
- 02:13 PM Bug #10937: fwd-h2 'killedMultiplexesCleanup' must not abend if the batch is not empty
- Teodor Gorghe wrote:
> I have done some performance tests with and without @nonEmptyTableFlags@ and I can confirm th... - 01:37 PM Bug #10937: fwd-h2 'killedMultiplexesCleanup' must not abend if the batch is not empty
- I have done some performance tests with and without @nonEmptyTableFlags@ and I can confirm that the performance is be...
- 05:39 AM Bug #10937: fwd-h2 'killedMultiplexesCleanup' must not abend if the batch is not empty
- Ovidiu Maxiniuc wrote:
> Teodor,
> Although 10937b was already merged into trunk, there are some changes in 10937a ... - 02:11 PM Bug #11015 (Review): allow cleanup the DMO types, caches, etc for dynamic temp-tables
- Branch 11015b was created from trunk rev 16410.
In rev 16411, I've added the cache for the DMOMeta instances for d... - 11:54 AM Bug #9950: Upgrade the metadata schema to a newer version
- I just wanted to post a method by which an application can be backward compatible for building. Some projects have mu...
- 09:36 AM Bug #10390 (Internal Test): FIND FIRST buffer field change does not propagate into the next FIRST...
- I am OK with the changes - they are on spot with UNIQUE handling in dirty-share.
Please run ChUI regression testin... - 03:03 AM Bug #10390: FIND FIRST buffer field change does not propagate into the next FIRST FIRST statements.
- Alex: please review this.
- 08:29 AM Bug #11037: Record not being evicted from FFCache
- I have committed @11037a/rev. 16327@. I removed the part where I was deleting the stale nodes at @put@ operation. I h...
- 06:46 AM Bug #10776: FFC.touch standing out in profiling
- Actually, the root cause for the problem exposed in #10776-10 is not because of the changes per-se on this branch. It...
- 02:20 AM Bug #9383 (Review): Cache only the current delegate on transaction commit if a ProgressiveResults...
- Committed revision *16419* on task branch *9383c*:
- Cache the batch after fetching from database.
- Added @batchRe...
02/10/2026
- 10:40 AM Bug #10776: FFC.touch standing out in profiling
- Alex, while working on finishing #11037, I discovered a problem in the solution from #10776 for this testcase:...
- 10:31 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Committed revision *16418* on task branch *9383c*:
- When ResultSet is invalided, fetch the full record using batche... - 06:39 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- > Is this a JDBC problem because the query needs to be re-executed after the connection commit?
Yes. See #10172-31... - 06:29 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Alexandru Lungu wrote:
> * if you commit a transaction, the progressive results most probably get redundant, as each... - 06:19 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- A question about Alexandru's note from #9972-167:
> if you commit a transaction, the progressive results most probab... - 06:17 AM Bug #9383 (WIP): Cache only the current delegate on transaction commit if a ProgressiveResults is...
- Created task branch *9383c*.
- 06:57 AM Bug #9950: Upgrade the metadata schema to a newer version
- Not explicitly.
But this should not be a problem. When the DMO is initialised, the mandatory fields are automaticall... - 02:48 AM Bug #9950: Upgrade the metadata schema to a newer version
- Ovidiu, I did another review of the new standard.df and the @_trans@ meta table has new *mandatory* fields - did you ...
- 07:07 PM Bug #9950 (Test): Upgrade the metadata schema to a newer version
- Roger Borrello wrote:
> [...] If we upgrade the runtime of FWD to *trunk_16415*, but have _not_ reconverted (both wi... - 06:39 AM Bug #11037: Record not being evicted from FFCache
- I have ported the changes from @10776a@ into @11037a/rev. 16326@.
- 06:23 AM Bug #11037: Record not being evicted from FFCache
- Alexandru Lungu wrote:
> Andrei, please embed the changes from 10776 into 11037a and let me review and test it as a ... - 05:56 AM Bug #11037 (Review): Record not being evicted from FFCache
- Andrei, please embed the changes from 10776 into 11037a and let me review and test it as a whole (according to #10776-9)
02/09/2026
- 06:52 PM Bug #9950: Upgrade the metadata schema to a newer version
- Ovidiu Maxiniuc wrote:
> Roger,
> The application's behaviour shouldn't be affected. The upgrade should consist of... - 05:57 PM Bug #9950: Upgrade the metadata schema to a newer version
- Roger,
The application's behaviour shouldn't be affected. The upgrade should consist of:
* upgrade FWD to r16415
... - 04:58 PM Bug #9950: Upgrade the metadata schema to a newer version
- Are there any immediate changes to customer applications post merge?
- 02:46 PM Bug #9950 (Merge Pending): Upgrade the metadata schema to a newer version
- Please merge after 10894a.
- 02:26 PM Bug #9950: Upgrade the metadata schema to a newer version
- Constantin Asofiei wrote:
> [...] are there meta tables stored in the physical DB which are affected? This is requi... - 02:13 PM Bug #9950: Upgrade the metadata schema to a newer version
- Ovidiu, please remind me - are there meta tables stored in the physical DB which are affected? This is required to k...
- 02:08 PM Bug #9950: Upgrade the metadata schema to a newer version
- Constantin Asofiei wrote:
> Ovidiu: please prepare tasks in each customer project to upgrade to the new standard.df ... - 07:20 AM Bug #9950: Upgrade the metadata schema to a newer version
- Ovidiu: please prepare tasks in each customer project to upgrade to the new standard.df file. We will do this depend...
- 05:03 AM Bug #10937: fwd-h2 'killedMultiplexesCleanup' must not abend if the batch is not empty
- Teodor,
Although 10937b was already merged into trunk, there are some changes in 10937a which might be useful. What ... - 04:00 AM Feature #8834: add bootstrap configuration support for -db OE command line parameter (and related...
- Harness, reports and navigation passed!
- 03:50 AM Feature #8834 (Internal Test): add bootstrap configuration support for -db OE command line parame...
- 03:59 AM Bug #10772: NUM-RESULTS on a FOR EACH query fails
- Harness, reports and navigation passed!
02/06/2026
- 09:08 AM Feature #9545: confirm/add table parameter support
- Some things that I noticed:...
- 04:00 AM Feature #9545: confirm/add table parameter support
- Eduard Soltan wrote:
> From the above example shows that NUM-REFERENCES is updated at the end of the called procedur... - 03:40 AM Feature #9545: confirm/add table parameter support
- There is something in @TemporarBuffer.associateImpl@....
02/05/2026
- 03:50 PM Bug #6767: Possible name clashes in DMO classes
- Greg Shah wrote:
> Greg Shah wrote:
> > Hynek/Constantin/Eric: What testing is needed here?
> >
> > Should this ... - 08:55 AM Bug #11161: fail gracefully when the database connection can not be established
- Eric,
to answer your questions from the meeting.
* what happens when c3p0 runs out of connections?
The request... - 04:18 AM Bug #11161: fail gracefully when the database connection can not be established
- I checked the OE database logs, on agent startup there is no activity in the database, in the agent logs there are no...
- 03:57 AM Feature #9545: confirm/add table parameter support
- I have been looking at DataSet implementation of @num-reference@, I think it is not quite right.
*start.p*...
02/04/2026
- 10:42 AM Bug #11161: fail gracefully when the database connection can not be established
- I want to document the testing env I am using:
* 1 PASOE agent with 300 executor threads
* the session manager conf... - 06:47 AM Bug #11161: fail gracefully when the database connection can not be established
- As far as I can understand, in OE, the db connection is reserved when starting a MSA session, whereas in FWD, the con...
- 05:57 AM Bug #11161: fail gracefully when the database connection can not be established
- It is a bit tricky with the @connect@ statement and appservers, the client cannot connect to a db and use the connect...
- 09:54 AM Feature #9545: confirm/add table parameter support
- *start.p*...
- 08:47 AM Bug #6767: Possible name clashes in DMO classes
- Greg Shah wrote:
> Hynek/Constantin/Eric: What testing is needed here?
>
> Should this be in Internal Test status... - 08:11 AM Bug #10385: Incorrect reset of the cursor cache in Reposition
- Alexandru Lungu wrote:
> Also mind that in #11021, I removed the reposition in child components when doing @loadByVa...
02/03/2026
- 09:24 AM Bug #11161: fail gracefully when the database connection can not be established
- Connecting with...
- 07:32 AM Bug #11161: fail gracefully when the database connection can not be established
- Constantin Asofiei wrote:
> Did you configure the database to be automatically connected in the PASOE config, and se... - 07:30 AM Bug #11161: fail gracefully when the database connection can not be established
- Did you configure the database to be automatically connected in the PASOE config, and set the @-n@ argument at @prose...
- 07:26 AM Bug #11161: fail gracefully when the database connection can not be established
- I connected a PASOE agent to a database that has maximum 5 users. ...
- 04:42 AM Bug #11161 (WIP): fail gracefully when the database connection can not be established
- 08:49 AM Feature #8834: add bootstrap configuration support for -db OE command line parameter (and related...
- Constantin Asofiei wrote:
> You are correct. If this is happening also when the @cfgOverrides@ is being processed f... - 08:46 AM Feature #8834: add bootstrap configuration support for -db OE command line parameter (and related...
- Teodor Gorghe wrote:
> Constantin Asofiei wrote:
> > * in @ParameterFileStartupParameter.readParameterFile@ - the f... - 08:40 AM Feature #8834: add bootstrap configuration support for -db OE command line parameter (and related...
- Constantin Asofiei wrote:
> * in @ParameterFileStartupParameter.readParameterFile@ - the file needs to be read from ... - 08:33 AM Feature #8834: add bootstrap configuration support for -db OE command line parameter (and related...
- Constantin Asofiei wrote:
> * does existing directory configurations still work, or will they need to be adjusted?
... - 08:28 AM Feature #8834: add bootstrap configuration support for -db OE command line parameter (and related...
- Teodor, from 8834a rev 16351:
* in @ParameterFileStartupParameter.readParameterFile@ - the file needs to be read fro... - 08:04 AM Bug #10455 (Closed): Persistent table CAN-FIND FIRST issue
- 08:03 AM Bug #10956 (Closed): Wrong primary index selection on FOR EACH table
- 08:03 AM Bug #10689 (Closed): Wrong temp-table FOR EACH sorting criteria
- 08:02 AM Bug #10560 (Closed): Wrong buffer picking for ReadXml when seralization name of a buffer correspo...
- 08:02 AM Feature #6457 (Closed): finish COPY-LOB support
- 08:02 AM Bug #10526 (Closed): Progressive results don't get invalidated when buffer-copy is performed
02/02/2026
- 10:01 AM Bug #11015 (WIP): allow cleanup the DMO types, caches, etc for dynamic temp-tables
- Branch 11015a was merged to trunk rev 16397 and archived.
- 09:58 AM Bug #10937: fwd-h2 'killedMultiplexesCleanup' must not abend if the batch is not empty
- Branch 10937b was merged to trunk rev 16396 and archived.
What remains is to decide how to improve the @nonEmptyFl... - 09:50 AM Bug #10901 (Closed): BEGINS trims the rvalue if the lvalue field is first in an index
- Branch 10901a was merged to trunk rev 16395 and archived.
- 09:38 AM Bug #10455 (Test): Persistent table CAN-FIND FIRST issue
- Branch 10455b was merged to trunk rev. 16392 and archived.
- 05:31 AM Bug #10455: Persistent table CAN-FIND FIRST issue
- Merge to trunk after 10203a
- 09:16 AM Bug #10956 (Test): Wrong primary index selection on FOR EACH table
- Branch *10956a* was merged to trunk rev. *16389* and archived.
- 05:31 AM Bug #10956 (Merge Pending): Wrong primary index selection on FOR EACH table
- Merge to trunk after 10925a
- 08:54 AM Bug #10689 (Test): Wrong temp-table FOR EACH sorting criteria
- Branch 10689a was merged to trunk rev. 16386 and archived.
- 05:30 AM Bug #10689 (Merge Pending): Wrong temp-table FOR EACH sorting criteria
- Merge to trunk after 10636a
- 08:46 AM Bug #11027 (Test): Unflushed record causes infinite loop
- 07:44 AM Bug #11027: Unflushed record causes infinite loop
- Greg, at this moment, all the testing done for this task passed and also, didn't found any testcases related to this ...
- 08:44 AM Bug #10560 (Test): Wrong buffer picking for ReadXml when seralization name of a buffer correspond...
- Branch 10560a was merged to trunk rev. 16384 and archived.
- 05:29 AM Bug #10560 (Merge Pending): Wrong buffer picking for ReadXml when seralization name of a buffer c...
- Merge to trunk after 6457a
- 08:28 AM Feature #6457 (Test): finish COPY-LOB support
- Constantin Asofiei wrote:
> Merge to trunk after 10716a
6457a was merged into trunk rev. 16383 and archived. - 05:29 AM Feature #6457 (Merge Pending): finish COPY-LOB support
- Merge to trunk after 10716a
- 01:57 AM Feature #6457: finish COPY-LOB support
- 6457a rev 16365 fixes a XML header problem.
- 07:49 AM Bug #10526 (Test): Progressive results don't get invalidated when buffer-copy is performed
- 10526a was merged into trunk rev. 16380 and archived.
- 05:28 AM Bug #10526 (Merge Pending): Progressive results don't get invalidated when buffer-copy is performed
- Merge to trunk after 10935a
- 07:42 AM Bug #10385: Incorrect reset of the cursor cache in Reposition
- Alexandru Lungu wrote:
>
> Also mind that in #11021, I removed the reposition in child components when doing @load... - 06:45 AM Bug #10385: Incorrect reset of the cursor cache in Reposition
- Eduard, please mind the @peek@ option. In peek mode, you do not load buffers, but rather gather the actual data that ...
- 02:56 AM Bug #10390: FIND FIRST buffer field change does not propagate into the next FIRST FIRST statements.
- Rebased task branch *10390a* to trunk rev *16377*. This includes changes from #11027.
*Alexandru*, when you have t...
01/30/2026
- 09:22 AM Bug #11027 (WIP): Unflushed record causes infinite loop
- 08:00 AM Bug #11027: Unflushed record causes infinite loop
- Branch 11027a was merged into trunk as rev. 16374.
- 07:51 AM Bug #11027: Unflushed record causes infinite loop
- Before merging I realized the changed file didn't have history entries. I added that, and also changed the copyright ...
- 07:22 AM Bug #11027 (Merge Pending): Unflushed record causes infinite loop
- 11027a passed ETF and POC testing without any observable performance degradation. Please merge 11027a to trunk now.
- 07:24 AM Bug #11161: fail gracefully when the database connection can not be established
- I could not capture the raised condition via @ON ERROR/QUIT/STOP/END-KEY@ - at least for @mpro@, it seems to just ter...
- 07:21 AM Bug #11161: fail gracefully when the database connection can not be established
- In OpenEdge, @proserve@ command has the @-n@ argument which tells it the number of concurrent users it can serve. Se...
- 07:17 AM Bug #11161 (Review): fail gracefully when the database connection can not be established
- 07:09 AM Bug #10611: Incorrect abbreviation name resolved at conversion time
- ...
01/29/2026
- 09:41 AM Bug #9383 (New): Cache only the current delegate on transaction commit if a ProgressiveResults is...
- 09:41 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- @9383b@ was merged into @trunk / 16369@
- 09:35 AM Bug #9383 (Merge Pending): Cache only the current delegate on transaction commit if a Progressive...
- Go ahead and merge now.
- 09:34 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Constantin Asofiei wrote:
> Please double-check in the docker container for the #10614 app, the heap set for the Cli... - 09:31 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Lorian Sandu wrote:
> I don't think there is anything left. The branch can be added to merge queue.
Please double-c... - 09:29 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Constantin Asofiei wrote:
> Lorian, what else is left?
I don't think there is anything left. The branch can be ad... - 09:29 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Lorian, what else is left?
- 09:27 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- * CHui tests passed
* Large GUI app unit-tests passed - 06:20 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- The smoke test passed on the app I'm managing.
- 05:15 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Lorian Sandu wrote:
> Constantin, do you think we should test other apps besides ETF and #10614?
Yes. Both large G... - 05:15 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Constantin, do you think we should test other apps besides ETF and #10614?
- 08:11 AM Feature #9545 (WIP): confirm/add table parameter support
- I have run the @tests/table/parameter@ tests. And this are some problems spotted so far.
1) Right know I am focusi...
01/28/2026
- 05:13 PM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Lorian Sandu wrote:
> I've created @9383b / rev 16369@ which reverts the changes that were introduced in @trunk / 16... - 08:09 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I've created @9383b / rev 16369@ which reverts the changes that were introduced in @trunk / 16217@.
- 03:36 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- From my POV, this is a customer specific pattern that breaks #9383 idea. I don't think we would be able to generate a...
- 03:35 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I documented the issue in #11154.
- 03:22 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I am working on a scenario to test and check what can be done.
- 10:20 AM Feature #4369: implement stateless FWD server clustering
- Roger Borrello wrote:
> Is this backward compatible with non-Docker configuration? If so, I think it should be added... - 08:45 AM Feature #4369: implement stateless FWD server clustering
- Andrei Plugaru wrote:
> Roger Borrello wrote:
>
> > Very clever... and your testing confirms?
>
> Yes, it work... - 06:39 AM Feature #4369: implement stateless FWD server clustering
- As the discussion regarding the synchronization of metadata tables was not officially closed, I have done some analys...
- 04:33 AM Bug #11027: Unflushed record causes infinite loop
- I think a simple null check there will solve the issue.
I will redo some of the testing I am handling as I don't ... - 04:15 AM Bug #11027: Unflushed record causes infinite loop
- There is a regression on a large customer application caused by the latest revision.
I am attaching the stack trace ...
Also available in: Atom