Wildfly issue - unexpected shutdown

[brightpeoples]

I used WildFly 9.0.0.

Sometime all 'Subsystem' of 'Subsystems' disappeared. (I don't know why)

And WildFly did not work correctly.

I had to reinstall wildfly.

Today I installed 9.0.1.

If someone knows why it happens, can you let me know the reason?

There was no specific log.

Message was edited by: jaikiran pai - Edited subject of the thread to match what's being discussed

[mayerw01]

One reason might be that you'd changed the configuration file (eg standalone-full.xml) while the AS was running).

But you should not need to re install the AS when the configuration file is corrupted. Wildfly usually backs up the configurations (eg in standalone_xml_history)

[brightpeoples]

Thank you.

I use standalone.xml.

However I did not edit the file.

Sometimes, the AS server is stopped automatically.

I am using 'mysql-connector-java-5.1.36.jar' to connect to mysql database

[jaikiran]

Please post the original standalone.xml that you are/were using and the one that is missing the subsystems. What kind of operations do you do when the server is up?

[mayerw01]

Which operation System are you using and how is your AS started/stopped?

Do you see any messages in the logs when the AS is unintentionally going down?

[brightpeoples]

Here is the list what I have used for a project.

1. OS

     Linux medusa 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u2 x86_64 GNU/Linux

2. Spring 4.1.7

3. MyBatis 3.2.8

4. JDBC driver : mysql-connector-java-5.1.36

5. standalone.xml : I changed only this part, IP address, when I installed the WildFly9.0.1.

    <interfaces>

        <interface name="management">

            <inet-address value="${jboss.bind.address.management:0.0.0.0}"/>

        </interface>

        <interface name="public">

            <inet-address value="${jboss.bind.address:0.0.0.0}"/>

        </interface>

        <interface name="unsecure">

            <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>

        </interface>

    </interfaces>

6. log : I am not sure if this log is about the shutdown automatically.

2015-08-12 10:16:04,112 DEBUG [org.jboss.as.ee] (MSC service thread 1-8) Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0048: Could not find default constructor for class org.springframework.http.server.ServletServerHttpAsyncRequestControl

        at org.jboss.as.ee.component.DefaultInterceptorConfigurator.configure(DefaultInterceptorConfigurator.java:92)

        at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81)

        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

        at java.lang.Thread.run(Thread.java:745)

2015-08-12 10:16:04,112 DEBUG [org.jboss.as.ee] (MSC service thread 1-8) Configuring component class: org.springframework.web.context.request.async.StandardServletAsyncWebRequest named org.springframework.web.context.request.async.StandardServletAsyncWebRequest

2015-08-12 10:16:04,113 WARN  [org.jboss.as.ee] (MSC service thread 1-8) WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)

2015-08-12 10:16:04,114 INFO  [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.

2015-08-12 10:16:04,121 DEBUG [org.jboss.as.ejb3.deployment.processors.EjbClientContextSetupProcessor] (MSC service thread 1-2) unRegistering EJB client context for classloader ModuleClassLoader for Module "deployment.abc-1.0.0.war:main" from Service Module Loader

2015-08-12 10:16:04,121 DEBUG [org.wildfly.jberet] (MSC service thread 1-7) Removing batch environment; ModuleClassLoader for Module "deployment.abc-1.0.0.war:main" from Service Module Loader

2015-08-12 10:16:04,121 ERROR [org.jboss.as.server] (XNIO-1 task-5) WFLYSRV0021: Deploy of deployment "abc-1.0.0.war" was rolled back with the following failure message: "WFLYCTL0344: Operation timed out awaiting service container stability"

2015-08-12 10:16:04,125 DEBUG [org.jboss.as.security] (MSC service thread 1-5) Stopping security domain service jboss-ejb-policy

2015-08-12 10:16:04,128 DEBUG [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0003: Removed mail session [java:jboss/mail/Default]

2015-08-12 10:16:04,129 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Stopped Driver service with driver-name = mysql-connector-java-5.1.36.jar_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1

2015-08-12 10:16:04,129 DEBUG [org.jboss.as.ee] (MSC service thread 1-8) Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0048: Could not find default constructor for class org.springframework.web.context.request.async.StandardServletAsyncWebRequest

        at org.jboss.as.ee.component.DefaultInterceptorConfigurator.configure(DefaultInterceptorConfigurator.java:92)

        at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81)

        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

        at java.lang.Thread.run(Thread.java:745)

Thank you.

[mayerw01]

I understand the warning regarding Spring may be ignored JBAS011054: Could not find default constructor for class org.springframework.web.context.request.async.StandardServletAsyncWebRequest

It looks like the server was shutdown intentionally. What is your process of shutting down the server? Is there any automated shutdown process in place (eg via cron)?

[brightpeoples]

I shutdown the server only manually.

I would like to know which Spring version is supported by Wildfly 9.0.1. (Actually not only Spring)

[mayerw01]

I am not sure where exactly your issue is now.

If you look for information regarding support of 3rd party products I don't think checking the WildFly documentation will be the best approach.

When looking into the Getting started guide you may realized that the only product which is mentioned under 'Requirements' is the Java version.

You may also find a chart there that lists the supported JEE technologies indeed.

But I don't think you will find much more about the products there that are supporting these technologies.

This information should rather come from the product provider itself.

So eg when checking the Spring page Hibernate, Jackson, Jetty etc support in Spring 4.2 you may find some information regarding WildFly support as well.

[brightpeoples]

Thank you, Wolfgang.

That is what I am concerned about.

I could not find the information.

I have installed JBoss EAP 6.4.0.

I will check if there is same issues on JBoss.

[jaikiran]

Kyumin Lee wrote:

I have installed JBoss EAP 6.4.0.

I will check if there is same issues on JBoss.

From the logs that you have shown we haven't seen any real issue (after from the DEBUG logs that can be ignored). So which exact issue are you trying to track down?

[brightpeoples]

Like I said, I am not sure if it is related to shutdown.

The main issue is server shutdown even though I didn't do it.

[jaikiran]

Kyumin Lee wrote:

Like I said, I am not sure if it is related to shutdown.

The main issue is server shutdown even though I didn't do it.

That log message is not related to shutdown.

How are you starting the server? What exact command? Are you starting it on your local machine or some other system? How long does it stay up before going down? Here's one thread which explains how to debug a similar issue Re: Wildfly 8.2 process go down without any logs NEW MESSAGES

[brightpeoples]

1. I use this command to start and stop.

Start : /usr/share/wildfly/bin/standalone.sh &

Stop : /usr/share/wildfly/bin/jboss-cli.sh --connect command=:shutdown

2. Not local machine.

   Like I mentioned upper, on Linux system.

3. about 1 time per day

[jaikiran]

Kyumin Lee wrote:

1. I use this command to start and stop.

Start : /usr/share/wildfly/bin/standalone.sh &

Stop : /usr/share/wildfly/bin/jboss-cli.sh --connect command=:shutdown

2. Not local machine.

   Like I mentioned upper, on Linux system.

I suspect after you start the server on the remote system, you are logging out of the remote session and that's what's causing the server shutdown. Use "nohup" to start the server, as below:

nohup /usr/share/wildfly/bin/standalone.sh &