System and methods for an automated core dump to a Java heap dump conversion

1. A method for a heap dump conversion, comprising:

storing a core dump file in a network storage by a converter application executing on a first server;

restarting a Java application by a restart application executing on the first server in response to storing the core dump file;

receiving a notification instruction associated with the core dump file by a watcher application executing on a second server;

obtaining metadata information from the core dump file in response to receiving the notification instruction, wherein the metadata information is obtained by a converter application executing on the second server; and

autonomously converting the core dump file into a heap dump file using the metadata information by the converter application executing on the second server.

2. The method of claim 1 , wherein the core dump file comprises a core dump of one or more Java processes of the Java application executing on the first server.

3. The method of claim 1 , further comprising storing the heap dump file in the network storage by the converter application executing on the second server.

4. The method of claim 1 , further comprising receiving the notification instruction by the converter application executing on the second server when detecting the core dump file in the network storage.

5. The method of claim 1 , wherein the metadata information comprises version information of the Java application on the first server.

6. The method of claim 5 , wherein the heap dump file comprises the same version information as the version information of the Java application.

7. The method of claim 1 , further comprising monitoring the network storage to detect the core dump file by the watcher application executing on the second server.

8. A system for a heap dump conversion, comprising:

a network storage device comprising a core dump file;

a first server coupled to the network storage device; and

a second server coupled to the network storage device and to the first server, wherein the second server is configured to:

receive a notification associated with the core dump file;

obtain metadata information from the core dump file in response to receiving the notification;

autonomously convert the core dump file into a heap dump file using the metadata information; and

store the heap dump file in the network storage device.

9. The system of claim 8 , wherein the core dump file comprises a core dump of one or more Java processes of a Java application executing on the first server.

10. The system of claim 9 , wherein the first server is configured to:

store the core dump file in the network storage device; and

restart the Java application in response to storing the core dump file.

11. The system of claim 8 , wherein the second server is configured to receive the notification when detecting the core dump file in the network storage device.

12. The system of claim 11 , wherein the metadata information comprises version information of a Java application on the first server.

13. The system of claim 12 , wherein the heap dump file comprises the same version information as the version information of the Java application.

14. The system of claim 8 , wherein the first server and the second server are configured to access the same file directories in the network storage device.

15. The system of claim 8 , wherein the second server is configured to monitor the network storage device to detect the core dump file.

16. A method for a heap dump conversion implemented by a second server, comprising:

receiving a notification instruction associated with a core dump file in a network storage by a watcher application executing on the second server;

obtaining metadata information from the core dump file in response to receiving the notification instruction, wherein the metadata information is obtained by a converter application executing on the second server;

autonomously converting the core dump file into a heap dump file using the metadata information by the converter application executing on the second server; and

storing the heap dump file in the network storage by the converter application executing on the second server.

17. The method of claim 16 , wherein the core dump file comprises a core dump of one or more Java processes of a Java application that is executing on a first server.

18. The method of claim 17 , further comprising:

storing the core dump file in the network storage by the converter application executing on the second server; and

restarting the Java application in response to storing the core dump file by a restart application executing on the second server.

19. The method of claim 16 , further comprising receiving the notification instruction by the converter application executing on the second server when detecting the core dump file in the network storage.

20. The method of claim 19 , wherein the metadata information comprises version information of a Java application on a first server.

21. The method of claim 20 , wherein the heap dump file comprises the same version information as the version information of the Java application.

22. The method of claim 16 , further comprising providing, to a first server and the second server, access permissions to the same file directories in the network storage by the network storage.

23. The method of claim 16 , further comprising monitoring the network storage to detect the core dump file by the watcher application executing on the second server.