[
https://issues.apache.org/jira/browse/OFBIZ-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18059053#comment-18059053
]
Jacques Le Roux commented on OFBIZ-13363:
-----------------------------------------
Here is the end of log: [^OFBIZ-13363-end-of-log.txt]
> 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
> Assignee: 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)
