[
https://issues.apache.org/jira/browse/OFBIZ-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18059551#comment-18059551
]
Daniel Watford edited comment on OFBIZ-13363 at 2/19/26 7:53 AM:
-----------------------------------------------------------------
We do apply some resource limits to our containers:
* db: 300MB memory limit
* ofbiz: 2400MB memory limit
So I wondered if the database could be running out of ram.
This does not appear to be the case. Here is the output of the `docker stats`
command:
{noformat}
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM %
NET I/O BLOCK I/O PIDS
669b1e8a9135 demo-next-db-1 0.01% 22.51MiB / 300MiB 7.50%
15.4kB / 126B 4.1kB / 86.8MB 7
6025ace227f2 demo-next-ofbiz-1 0.00% 0B / 0B 0.00% 0B
/ 0B 0B / 0B 0
c99c91344848 demo-trunk-ofbiz-1 0.00% 0B / 0B 0.00% 0B
/ 0B 0B / 0B 0
2c9885768657 demo-trunk-db-1 0.00% 22.52MiB / 300MiB 7.51%
15.6kB / 126B 4.1kB / 86.3MB 7
41a514852370 demo-stable-ofbiz-1 0.00% 0B / 0B 0.00% 0B
/ 0B 0B / 0B 0
c273acc5fc79 demo-stable-db-1 0.00% 34.07MiB / 300MiB 11.36%
15.7kB / 126B 13.9MB / 84.7MB 7{noformat}
The database containers' resource usage seems well within limits. What was
interesting was the low resource usage of the ofbiz containers.
I then found the ofbiz containers keep restarting.
Running ` docker compose logs -f` in the /home/ofbizdocker/docker-stable
directory:
{noformat}
ofbiz-1 | + sed '--expression=s/@HOST@/db/;'
'--expression=s/@OFBIZ_DB@/ofbizmaindb/;'
'--expression=s/@OFBIZ_USERNAME@/ofbiz/;'
'--expression=s/@OFBIZ_PASSWORD@/CHANGEME/;'
'--expression=s/@OLAP_DB@/ofbizolapdb/;'
'--expression=s/@OLAP_USERNAME@/ofbizolap/;'
'--expression=s/@OLAP_PASSWORD@/CHANGEME/;'
'--expression=s/@TENANT_DB@/ofbiztenantdb/;'
'--expression=s/@TENANT_USERNAME@/ofbiztenant/;'
'--expression=s/@TENANT_PASSWORD@/CHANGEME/;'
templates/postgres-entityengine.xml
ofbiz-1 | sed: can't read templates/postgres-entityengine.xml: Permission
denied
ofbiz-1 exited with code 2 (restarting){noformat}
There is a problem reading the templates/postgres-entityengine.xml file when
the object container starts.
was (Author: danwatford):
We do apply some resource limits to our containers:
* db: 300MB memory limit
* ofbiz: 2400MB memory limit
So I wondered if the database could be running out of ram.
This does not appear to be the case. Here is the output of the `docker stats`
command:
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM %
NET I/O BLOCK I/O PIDS
669b1e8a9135 demo-next-db-1 0.01% 22.51MiB / 300MiB 7.50%
15.4kB / 126B 4.1kB / 86.8MB 7
6025ace227f2 demo-next-ofbiz-1 0.00% 0B / 0B 0.00% 0B
/ 0B 0B / 0B 0
c99c91344848 demo-trunk-ofbiz-1 0.00% 0B / 0B 0.00% 0B
/ 0B 0B / 0B 0
2c9885768657 demo-trunk-db-1 0.00% 22.52MiB / 300MiB 7.51%
15.6kB / 126B 4.1kB / 86.3MB 7
41a514852370 demo-stable-ofbiz-1 0.00% 0B / 0B 0.00% 0B
/ 0B 0B / 0B 0
c273acc5fc79 demo-stable-db-1 0.00% 34.07MiB / 300MiB 11.36%
15.7kB / 126B 13.9MB / 84.7MB 7
The database containers' resource usage seems well within limits. What was
interesting was the low resource usage of the ofbiz containers.
I then found the ofbiz containers keep restarting.
Running ` docker compose logs -f` in the /home/ofbizdocker/docker-stable
directory:
ofbiz-1 | + sed '--expression=s/@HOST@/db/;'
'--expression=s/@OFBIZ_DB@/ofbizmaindb/;'
'--expression=s/@OFBIZ_USERNAME@/ofbiz/;'
'--expression=s/@OFBIZ_PASSWORD@/CHANGEME/;'
'--expression=s/@OLAP_DB@/ofbizolapdb/;'
'--expression=s/@OLAP_USERNAME@/ofbizolap/;'
'--expression=s/@OLAP_PASSWORD@/CHANGEME/;'
'--expression=s/@TENANT_DB@/ofbiztenantdb/;'
'--expression=s/@TENANT_USERNAME@/ofbiztenant/;'
'--expression=s/@TENANT_PASSWORD@/CHANGEME/;'
templates/postgres-entityengine.xml
ofbiz-1 | sed: can't read templates/postgres-entityengine.xml: Permission
denied
ofbiz-1 exited with code 2 (restarting)
There is a problem reading the templates/postgres-entityengine.xml file when
the object container starts.
> ERR_TOO_MANY_REDIRECTS on trunk and next demos, stable not concerned.
> ---------------------------------------------------------------------
>
> Key: OFBIZ-13363
> URL: https://issues.apache.org/jira/browse/OFBIZ-13363
> Project: OFBiz
> Issue Type: Bug
> Components: Demo
> Affects Versions: Upcoming Branch
> Reporter: Jacques Le Roux
> Priority: Major
> Attachments: OFBIZ-13363-end-of-log.txt
>
>
> For now, trunk an next are actually the same, both are trunk. I investigated
> only on trunk side.
> I initially thought that it could be a DDOS attack because I saw a lot of "An
> active login is required for view with name [main]" error in the error.log
> file. It's not.
> The issue is "Unable to acquire a new connection from the pool" unrelated to
> "An active login is required for view with name [main]". Exactly 10 seconds
> after the last "An active login is required for view with name [main]"
> {noformat}
> 2026-02-17 02:35:26,793 |-0.0.0.0-8009-exec-5 |ControlServlet
> |E| Error in request handler:
> org.apache.ofbiz.webapp.control.RequestHandlerException: An active login is
> required for view with name [main]
> [...]
> 2026-02-17 02:35:26,793 |-0.0.0.0-8009-exec-5 |ControlServlet
> |E| An error occurred, going to the errorPage:
> file:/ofbiz/framework/common/webcommon/error/Error.ftl
> 2026-02-17 02:35:36,696 |Thread-0 |GenericDelegator
> |E| Failure in findByCondition operation for entity [Visit]:
> org.apache.ofbiz.entity.GenericDataSourceException: Unable to establish a
> connection with the database. (Unable to acquire a new connection from the
> pool). Rolling back transaction.
> {noformat}
> As stable is not concerned I thought it could be due to a yesterday commit.
> But I see is no reason for that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
