Dump

You can generate a dump file that includes information about the runtime GigaSpaces environment for a specific GSCClosed or across the entire environment. Start the GigaSpaces Management Center , move into the Hosts tab and select the relevant option: Full environment dump:

dump0.jpg

Specific machine dump:

dump1.jpg

Specific GSC dump:

dump3.jpg

Any of the above will display the following dialog. Place the location of the dump file , select the desired options and click the Generate button.

dump2.jpg

Make sure the user that started the GigaSpaces Management Center has write permissions to the location of the dump file.

Dump File Structure

The dump file structure would look like this:

dump_file.zip gsa-10.10.10.249-23610--1284928573201 network.txt summary.txt threads.txt logs 2010-09-19~08.22-gigaspaces-gsa-10.10.10.249-23610.log gsc-10.10.10.249-23739--1284928573169 network.txt summary.txt threads.txt logs 2010-09-19~08.22-gigaspaces-gsc_1-10.10.10.249-23739.log processing-units space 1 pu This is the unit of packaging and deployment in the GigaSpaces Data Grid, and is essentially the main GigaSpaces service. The Processing Unit (PU) itself is typically deployed onto the Service Grid. When a Processing Unit is deployed, a Processing Unit instance is the actual runtime entity..xml spaces space summary.txt gsc-10.10.10.249-23766--1284928573079 network.txt summary.txt threads.txt logs 2010-09-19~08.22-gigaspaces-gsc_2-10.10.10.249-23766.log processing-units mirror 1 pu.xml spaces mirror summary.txt space 1_1 pu.xml spaces space summary.txt gsm-10.10.10.249-24112--1284928573193 network.txt summary.txt threads.txt logs 2010-09-19~08.22-gigaspaces-gsm_3-10.10.10.249-24112.log lus-10.10.10.249-24127--1284928573201 network.txt summary.txt threads.txt logs 2010-09-19~08.22-gigaspaces-lus_4-10.10.10.249-24127.log