To be sure it was not related to the recent VM migration, I had a look at
https://s.apache.org/2daaj
The migration was complete before the log issue have seems to appear
(2026-02-17)
But I just found that and it's very weird (look at the dates).
2026-02-17 12:24:11,789 |-0.0.0.0-8009-exec-8 |ControlServlet
|T| [[[projectmgr::main
(Domain:https://demo-stable.ofbiz.apache.org)] Request Done-
total:1.405,since last([projectmgr::main...):1.405]]
2026-02-17 12:24:20,953 |Thread-0 |ContainerLoader |I|
Shutting down containers
2026-02-17 12:24:20,955 |Thread-0 |ContainerLoader |I|
Stopping container catalina-container
2026-02-17 12:24:20,967 |Thread-0 |ServiceContainer |I|
Removing from cache dispatcher: ebay
2026-02-17 12:24:20,967 |Thread-0 |ServiceDispatcher |I|
De-Registering dispatcher: ebay
2026-03-27 15:35:16,833 |Thread-0 |ServiceContainer |I|
Removing from cache dispatcher: ebay
2026-03-27 15:35:16,833 |Thread-0 |ServiceDispatcher |I|
De-Registering dispatcher: ebay
2026-03-27 15:35:16,860 |Thread-0 |ServiceContainer |I|
Removing from cache dispatcher: marketing
2026-03-27 15:35:16,860 |Thread-0 |ServiceDispatcher |I|
De-Registering dispatcher: marketing
2026-03-27 15:35:16,862 |Thread-0 |ServiceContainer |I|
Removing from cache dispatcher: exampleext
This in stable ofbiz.log (now renamed ofbiz-2026-4-8.log on server) I have a
copy of it locally (396+ MB)
Jacques
Le 08/04/2026 à 17:02, Jacques Le Roux via dev a écrit :
Hi Jacopo,
Most of the information is in
https://github.com/apache/ofbiz-tools/tree/master/demo-backup/ofbizdocker
I have just updated it because of the recent VM change. The rest should still
be OK.
Also you need to ask Infra an access to the VM
Later if you have questions I may help, but not on Docker. And maybe this issue
is related to it.
Thanks to care
Jacques
Le 08/04/2026 à 15:55, Jacopo Cappellato a écrit :
Hi Jacques, all,
I’d be happy to help. Before I look into this, I need to understand how to
work with our demo instances. If you or anyone else could provide some
guidance or point me to relevant documentation, I’ll review it.
Jacopo
On Wed, Apr 8, 2026 at 10:34 AM Jacques Le Roux via dev <
[email protected]> wrote:
Le 08/04/2026 à 09:55, Jacques Le Roux via dev a écrit :
Le 07/04/2026 à 17:59, Jacques Le Roux via dev a écrit :
Le 07/04/2026 à 15:26, Jacques Le Roux via user a écrit :
Hi,
I don't know why and I have no time to look at it right now (I could
restart)
Trunk demo is OK
Jacques
I downloaded the ofbiz. log file (393 MB) but did not find any
reasonable explanation, but a lot of session destroyed (~100) in the last
hour.
After that, only the sending emails job continued to work for almost an
hour and a half.
Also ~100 session destroyed in the last hour does not mean much,.
Since the start there are 31000+ such cases.
But what is weird is the start was 2026-02-17. So something is wrong
with logs rotation since this date and it continues. It's OK before.
Maybe the reason of the crash?
I restarted the demos.
Jacques
I had a look at log4j2.xml (not changed for 2 years) and
docker-compose.yml that has not related changes.
I also had a look at the Git log of tools\demo-backup\ofbizdocker,
nothing. But I'm not quite sure that changes on repo are exactly the same
than on
VM (hard to compare).
Finally the same thing happen for all demo instances for all logs.
As I don't understand what's happening, I'll stop demos, rename the logs
affected (to keep them) and restart demos to see tmrw if it has an impact.
Jacques
The demos were restarted but no new logs were created (ie no error.log and
ofbiz.log).
I created error.log and ofbiz.log files in trunk to no avail, they remain
empty.
We clearly have an issue with logs.
I don't know docker, so it seems I'm missing something... Help
appreciated...
Jacques
