Solved: What are the causes for JVM down without error

jeesshnasree · ‎01-20-2019

Hi All,

could you please help me on JBOSS JVM Down, but logs deoes not contain any error.

1.could you please let me , what are causes for JVM down,

2. How to troubleshoot the issue,

3. How to fix the issue

its a rare situation and and don’t have logs . Kindly suggest for solution. I hope might be receive the solution .

Scott · ‎01-31-2019

Realize that the JBoss app server is a java process. If the process is killed (in a non-sigterm way), it may very well not log in the app server log as the appserver itself was killed. I would look in system logs, or if this is something that's somewhat predictable, stick an strace on it so you can see, from a system level, what the jvm is doing when it is terminated. That might give you an idea.

-STM

View solution in original post

RuGI · ‎02-06-2019

In the folder of your installation (we will call it JBOSS_HOME), this path must exist:
JBOSS_HOME / standalone / configuration

In that folder there is a file called:
standalone.xml

This file has all the configuration of your server.
You are going to locate the subsystem of logs, it is this:

        <subsystem xmlns="urn:jboss:domain:logging:1.5">
            <console-handler name="CONSOLE">
                <level name="INFO"/>
                <formatter>
                    <named-formatter name="COLOR-PATTERN"/>
                </formatter>
            </console-handler>
            <periodic-rotating-file-handler name="FILE" autoflush="true">
                <formatter>
                    <named-formatter name="PATTERN"/>
                </formatter>
                <file relative-to="jboss.server.log.dir" path="server.log"/>
                <suffix value=".yyyy-MM-dd"/>
                <append value="true"/>
            </periodic-rotating-file-handler>
            <logger category="com.arjuna">
                <level name="WARN"/>
            </logger>
            <logger category="org.apache.tomcat.util.modeler">
                <level name="WARN"/>
            </logger>
            <logger category="org.jboss.as.config">
                <level name="DEBUG"/>
            </logger>
            <logger category="sun.rmi">
                <level name="WARN"/>
            </logger>
            <logger category="jacorb">
                <level name="WARN"/>
            </logger>
            <logger category="jacorb.config">
                <level name="ERROR"/>
            </logger>
            <root-logger>
                <level name="INFO"/>
                <handlers>
                    <handler name="CONSOLE"/>
                    <handler name="FILE"/>
                </handlers>
            </root-logger>
            <formatter name="PATTERN">
                <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
            </formatter>
            <formatter name="COLOR-PATTERN">
                <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
            </formatter>
        </subsystem>


Assign all your logs to DEBUG level:

<subsystem xmlns="urn:jboss:domain:logging:1.5">
            <console-handler name="CONSOLE">
                <level name="DEBUG"/>
                <formatter>
                    <named-formatter name="COLOR-PATTERN"/>
                </formatter>
            </console-handler>
            <periodic-rotating-file-handler name="FILE" autoflush="true">
                <formatter>
                    <named-formatter name="PATTERN"/>
                </formatter>
                <file relative-to="jboss.server.log.dir" path="server.log"/>
                <suffix value=".yyyy-MM-dd"/>
                <append value="true"/>
            </periodic-rotating-file-handler>
            <logger category="com.arjuna">
                <level name="DEBUG"/>
            </logger>
            <logger category="org.apache.tomcat.util.modeler">
                <level name="DEBUG"/>
            </logger>
            <logger category="org.jboss.as.config">
                <level name="DEBUG"/>
            </logger>
            <logger category="sun.rmi">
                <level name="DEBUG"/>
            </logger>
            <logger category="jacorb">
                <level name="DEBUG"/>
            </logger>
            <logger category="jacorb.config">
                <level name="DEBUG"/>
            </logger>
            <root-logger>
                <level name="DEBUG"/>
                <handlers>
                    <handler name="CONSOLE"/>
                    <handler name="FILE"/>
                </handlers>
            </root-logger>
            <formatter name="PATTERN">
                <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
            </formatter>
            <formatter name="COLOR-PATTERN">
                <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
            </formatter>
        </subsystem>


Restart your server.

All the logs are in the folder:
JBOSS_HOME/standalone/log

Whatever happens, it must be reflected in the logs.

----

"Aurum nostrom non est aurum vulgo"

View solution in original post

Scott · ‎02-08-2019

I was refererencing the strace command. Take a look at the man page, specifically, how to attach it to a running process, then try it out. If you have further questions after actually working with it, I'd be happy to additionally respond/assist.

"Putty Mode" I don't think this is a thing. Putty is an ssh client tool. strace is a command you run on Linux system's shell. How you get access to that shell is immeterial.

"JVM restart required or not". I would not know because I don't know what it is you're trying to capture. I think if you read the Description section in the strace man page, you could probably get a better idea on whether you wanted to restart the JVM or not. My initial suggestion was to keep it running.

"could you please share if possible example." There are generally an Examples section in man pages. I would turn this back on you though. If you're unable to figure it out, give me the example command you're using, along with any error messages, and ask for assistance. Simply typing in commands people give you does not advance your own proficiency in system administration. However, learning how to run a new tool. Interpreting error messages. Figuring out how to read the output from the tool. These are all skills that a systems administrator should have, so building and practicing them is more valuable to you than me just providing a command for you to exectute.

-STM

View solution in original post

RuGI · ‎01-30-2019

Hi!

Have you tried increasing the level of log in the JBoss web console?

What operating system do you use?

---

"Aurum nostrom non est aurum vulgo"

Jayadev · ‎01-31-2019

This is a hypothetical situation and may not have an exact answer. One should start the troubleshooting by adjusting the memory and monitor the JVM.

Thanks,

Jayadev

jeesshnasree · ‎01-31-2019

hi @Jayadev,

this is not hypothetical question , if jboss JVM down but there is no information in the logs for stop .

Scott · ‎01-31-2019

Realize that the JBoss app server is a java process. If the process is killed (in a non-sigterm way), it may very well not log in the app server log as the appserver itself was killed. I would look in system logs, or if this is something that's somewhat predictable, stick an strace on it so you can see, from a system level, what the jvm is doing when it is terminated. That might give you an idea.

-STM

jeesshnasree · ‎02-03-2019

Hi @Scott,

could you please provide for enable trace log settings or doucment or link . ( parmeters and settings on Putty mode only and after change the settings JVM restart required or not . dould you please conifrm . could you please share if possible example .

Scott · ‎02-08-2019

I was refererencing the strace command. Take a look at the man page, specifically, how to attach it to a running process, then try it out. If you have further questions after actually working with it, I'd be happy to additionally respond/assist.

"Putty Mode" I don't think this is a thing. Putty is an ssh client tool. strace is a command you run on Linux system's shell. How you get access to that shell is immeterial.

"JVM restart required or not". I would not know because I don't know what it is you're trying to capture. I think if you read the Description section in the strace man page, you could probably get a better idea on whether you wanted to restart the JVM or not. My initial suggestion was to keep it running.

"could you please share if possible example." There are generally an Examples section in man pages. I would turn this back on you though. If you're unable to figure it out, give me the example command you're using, along with any error messages, and ask for assistance. Simply typing in commands people give you does not advance your own proficiency in system administration. However, learning how to run a new tool. Interpreting error messages. Figuring out how to read the output from the tool. These are all skills that a systems administrator should have, so building and practicing them is more valuable to you than me just providing a command for you to exectute.

-STM

jeesshnasree · ‎02-09-2019

Hi @Scott,

thanks for information . Actually I didn’t use strace command . I will check the command if not find in OS level then I will install . I didn’t use strace command .

Kindly find below URL got from google it.

https://linux.die.net/man/1/strace

RuGI · ‎01-31-2019

I ask about the operating system because, in the case of Linux, you can check the syslog and see if there is anything.

Also, try to put DEBUG from the web console the logs of your application and Jboss.

https://access.redhat.com/documentation/en-us/jboss_enterprise_application_platform/6/html/administr...

---

"Aurum nostrom non est aurum vulgo"

jeesshnasree · ‎02-03-2019

Hi @RuGI,

i checked in linux OS only but not able to in syslog and thanks for sharing the link but in sys log did not found any JVM related down/crash log information .

What are the causes for JVM down without error

JVM down causes