Forgot to tell about image.server.path in catalog.properties. I guess you are 
already setting it?

Le 05/06/2024 à 07:58, Jacques Le Roux a écrit :
Hi Ingo,

After reading https://lists.apache.org/thread/ymbjbf4r6tlcj5r8grh9dsrdhnfkj2tp

Are you putting your images on a dedicated server as suggested here 
https://lists.apache.org/thread/k2zj0hkf4sr2rdb90s6s8x2jfzb256lb ?

HTH

Jacques

Le 04/06/2024 à 16:22, Ingo Wolfmayr a écrit :
Hi Johan,

I have already excluded these tasks. In my case, Ofbiz is ready to take requests. I can see the requests in the log, but nothing seems to happen after showing the information mentioned below. If I remove the images and restart the instance, everything works as expected. I can make the images available afterwards, and it will work just fine.

I thought it could be something with loading images into the cache or indexing?

Best regards,
Ingo
-----Ursprüngliche Nachricht-----
Von: Johan Cronje <johanhpcro...@gmail.com>
Gesendet: Dienstag, 4. Juni 2024 15:41
An: user@ofbiz.apache.org
Betreff: Re: Ofbiz starting slow

Hi Ingo,

Not sure if this would be of help.
Since we did not need it on our local instance we made zip and tar gradle tasks 
optional based on arguments.

Added the below within the build.gradle:

tasks.named('distTar').configure {
     onlyIf {
         project.hasProperty('includeDistTar')
     }
}
tasks.named('distZip').configure {
     onlyIf {
         project.hasProperty('includeDistZip')
     }
}

This made our startup significantly faster.

Kind Regards,
Johan

On Tue, 4 Jun 2024 at 14:32, Ingo Wolfmayr <ingo.wolfm...@wolfix.at> wrote:
Hi everybody,

I have an OFBiz installation (multiple tenants, trunk) with many products and therefore many images. When I start OFBiz, it takes forever until it can be accessed via the interface. The log stops with the following entry: "This is the first request in this visit. Hidden sessionId by default."

If I remove the images (unmount the path) and restart, OFBiz is quickly 
available as usual.

What could be the problem here? During the waiting time, hardly any resources 
are used - neither CPU, memory, nor HDD read.

Best regards,
Ingo

Reply via email to