Maximo Open Forum

Hi,

Can someone explain what happens during a maximo jvm restart? I know how we do it( going to was and restart the jvms) but i want to know what happens in the background? 

What can happen if we restart the servers frequently like 2 times a week or so?

Thanks in advance.

Hi Trisha S! 

This is very technical and a websphere specialist It might help to be more precise.

When you talk about restarting the JVM, I understand you mean shutting down the Maximo clusters. You proceed to reboot and then turn them on.

Every time you shut it down, it should end by shutting down the corresponding JVM.

What does it do when you do this? It will do the following (they are not ordered)

- Kill connections: With the DB, external services, integrations, users, etc.
- Kill processes: Stop processes (associated with CRONTASK)
- Kill report issuance: In progress, scheduled, etc.

This would stop the system completely and then free up system resources, mainly memory and processing usage (cores, subcores, and threads).

Restarting the server and clusters starts them in a staggered manner (as each cluster starts) until Maximo is fully operational.

I give you an idea. Take a test Maximo environment and activate administration mode. Just keep looking at the screen, and you will see that Maximo notifies you step by step of what it is doing.

Part of what re-initializing the Clusters would do is in that step by step. Then, the release of resources.

Regards!

Hi,

Can someone explain what happens during a maximo jvm restart? I know how we do it( going to was and restart the jvms) but i want to know what happens in the background? 

What can happen if we restart the servers frequently like 2 times a week or so?

Thanks in advance.

Hi Trisha S! 

This is very technical and a websphere specialist It might help to be more precise.

When you talk about restarting the JVM, I understand you mean shutting down the Maximo clusters. You proceed to reboot and then turn them on.

Every time you shut it down, it should end by shutting down the corresponding JVM.

What does it do when you do this? It will do the following (they are not ordered)

- Kill connections: With the DB, external services, integrations, users, etc.
- Kill processes: Stop processes (associated with CRONTASK)
- Kill report issuance: In progress, scheduled, etc.

This would stop the system completely and then free up system resources, mainly memory and processing usage (cores, subcores, and threads).

Restarting the server and clusters starts them in a staggered manner (as each cluster starts) until Maximo is fully operational.

I give you an idea. Take a test Maximo environment and activate administration mode. Just keep looking at the screen, and you will see that Maximo notifies you step by step of what it is doing.

Part of what re-initializing the Clusters would do is in that step by step. Then, the release of resources.

Regards!

Hi,

Can someone explain what happens during a maximo jvm restart? I know how we do it( going to was and restart the jvms) but i want to know what happens in the background? 

What can happen if we restart the servers frequently like 2 times a week or so?

Thanks in advance.

Hi,

Can someone explain what happens during a maximo jvm restart? I know how we do it( going to was and restart the jvms) but i want to know what happens in the background? 

What can happen if we restart the servers frequently like 2 times a week or so?

Thanks in advance.

In WebSphere on Red Hat Linux, If I recall right, the deployment manager (dmgr) runs first. That handles expanding maximo.ear to start the Maximo application. Ideally, if you plan to restart the OS server, stop all the WebSphere related processed. stop HTTP (IBM HTTP server), stop app server, stop nodeagent, stop deployment manager. If you restart the server after that, the processes should have an opportunity to cleanly stop. If you restart without properly shutting down the processes, there's a small chance of corrupt files. If any process is stuck, we will manually kill the java process responsible from the OS.

If you're talking about restarting the MXServer from WebSphere console, I recommend stopping the process, wait a minute, then attempt to start it. That seems more reliable than restarting because you don't know if the stop failed or the start failed. And make sure you tail follow the SystemOut.log so you can see what's going on.

Hi,

Can someone explain what happens during a maximo jvm restart? I know how we do it( going to was and restart the jvms) but i want to know what happens in the background? 

What can happen if we restart the servers frequently like 2 times a week or so?

Thanks in advance.

Thank you for responding,Sun kim. Got what I wanted.

In WebSphere on Red Hat Linux, If I recall right, the deployment manager (dmgr) runs first. That handles expanding maximo.ear to start the Maximo application. Ideally, if you plan to restart the OS server, stop all the WebSphere related processed. stop HTTP (IBM HTTP server), stop app server, stop nodeagent, stop deployment manager. If you restart the server after that, the processes should have an opportunity to cleanly stop. If you restart without properly shutting down the processes, there's a small chance of corrupt files. If any process is stuck, we will manually kill the java process responsible from the OS.

If you're talking about restarting the MXServer from WebSphere console, I recommend stopping the process, wait a minute, then attempt to start it. That seems more reliable than restarting because you don't know if the stop failed or the start failed. And make sure you tail follow the SystemOut.log so you can see what's going on.

Hi,

Can someone explain what happens during a maximo jvm restart? I know how we do it( going to was and restart the jvms) but i want to know what happens in the background? 

What can happen if we restart the servers frequently like 2 times a week or so?

Thanks in advance.