Startup fails because of dependency on MySQL about docker-liferay-portal HOT 4 CLOSED

hey @SaurabhVatsa that's the expected behaviour, as Liferay Portal GA4 does not have a retry strategy for the datasource.

This feature has been added to the next release here: https://issues.liferay.com/browse/LPS-73667

In future releases, you'll be able to configure a retry strategy adding two properties:

##
## Retry JDBC connection on portal startup.
##

    #
    # Set the number of seconds to retry getting a JDBC connection on portal
    # startup.
    #
    retry.jdbc.on.startup.delay=0

    #
    # Set the max number of times to retry getting a JDBC connection on portal
    # startup.
    #
    retry.jdbc.on.startup.max.retries=0

On the other hand, as we added support for configuring Liferay Portal with environment variables, you'll be able to add env_vars representing any portal prop. Please read this JIRA ticket carefully: https://issues.liferay.com/browse/LPS-72541

from docker-liferay-portal.

Hey @mdelapenya , thanks for the response.
Docker documentation mentions that it is possible to delay the startup of one service until another service that it depends on, fires up. I was wondering if we can use/create something on that line and delay the startup of Liferay untill MySQL starts.

For ex.
version: "2"
services:
web:
build: .
ports:
- "80:8000"
depends_on:
- "db"
command: ["./wait-for-it.sh", "db:5432", "--", "python", "app.py"]
db:
image: postgres
Documentation for wait-for-it
Though it is good to have this feature in the next release, is there a way to manually configure this in the current Version ?

from docker-liferay-portal.

Yes, Docker documentation says that, but it waits for the main process, not for the custom logic expected by portal: so whenever the mysql container is up, portal will start, but it does not mean that the mysql database is already created.

from docker-liferay-portal.

Hey @SaurabhVatsa, is this issue solved? If so, could you please close it. Thanks!

from docker-liferay-portal.