Pblm wildfy Starting taking too long time

[Adrien B.]

Hello,

We have a problem on some of our servers.

Sometimes, yet we don't know the cause, the server takes too much time to start.

I'm looking some ways to determine which part takes longest time.

In this case, i don't know where to start.

Which logger could help me measure these times ?

Or any idea to know what's going on a startup ?

In the files attached, you will find a some logs from normal startup (server.log ), and another (server.log.2026-08-16*)  from a failed Startup.

Thanks in advance and keep up the good work.

Adrien

[Jose Socola]

HI,

Do need to review wars in deployments specifically coswin.war, u can remove all war and attach one by one so you can see your problems withs setup and configuration.

Regards,

JS

--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/wildfly/571a43a9-90e8-4145-b407-2b1625107959n%40googlegroups.com.

[Adrien B.]

Hello, 

Thanks for your answer, but this is happening only one instance of our wildfy, and this instance is the production and only happening after an hardware reboot.

So the idea to remove all war and attach one by one is appears to me as not pratical.

I'm looking for some ways to monitor the startup process when doing an hardware reboot and where does startup time goes.

Thanks in advance,

Adrien B.

[Jose Socola]

Hi Adrien, 

From this timeline, coswin.war is the last application to complete deployment and appears to consume most of the overall startup time and several warnings are reported while deploying coswin.war in normal startup. 

Please Enable DEBUG logging for the following WildFly components:

<logger category="org.jboss.weld">
    <level name="DEBUG"/>
</logger>

<logger category="org.jboss.as.controller">
    <level name="DEBUG"/>
</logger>

<logger category="org.jboss.as.server.deployment">
    <level name="DEBUG"/>
</logger>

<logger category="org.jboss.msc">
    <level name="DEBUG"/>
</logger>

Collect and compare:
A startup log after a full server reboot.

if you can collect the thread dump may reveal whether a thread is blocked waiting for.

The thread dump may reveal whether a thread is blocked waiting for:

jcmd <PID> Thread.print > threads.txt
jstack -l <PID> > threads.txt

Regards,

JS

To view this discussion visit https://groups.google.com/d/msgid/wildfly/9f5cc0ea-27e2-4a0b-bcd5-7bb852ed3ab2n%40googlegroups.com.

[Adrien B.]

Thanks for your answer, I'll put this in place and keep you posted.

Regards,

Adrien B.