Process annotations scripts

[blcham]

process-annotations-service.sh fails due to insufficient memory for JRE. This happens quite often so multiple execution of the script should simulate it.

#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 528482304 bytes for committing reserved memory.
# Possible reasons:
#   The system is out of physical RAM or swap space
#   The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
# Possible solutions:
#   Reduce memory load on the system
#   Increase physical memory or swap space
#   Check if swap backing store is full
#   Decrease Java heap size (-Xmx/-Xms)
#   Decrease number of Java threads
#   Decrease Java thread stack sizes (-Xss)
#   Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#
#  Out of Memory Error (os_linux.cpp:3018), pid=547, tid=548
#
# JRE version:  (11.0.15+10) (build )
# Java VM: OpenJDK 64-Bit Server VM (11.0.15+10-post-Debian-1deb11u1, mixed mode, sharing, tiered, compressed oops, g1 gc, linux-amd64)
# Core dump will be written. Default location: /brat-data/core
#

---------------  S U M M A R Y ------------

Command Line: /opt/java-libs/gate-tools.jar brat2gate --input-text-file BlueSky/DA42-POH--section-7_9-7_14/DA42-POH-44.txt --brat-server-url https://kbss.felk.cvut.cz/19msmt-demo/annotator --brat-data-home-directory /brat-data

Host: Intel Xeon E3-12xx v2 (Ivy Bridge), 16 cores, 31G, Debian GNU/Linux 11 (bullseye)
Time: Tue Jun 28 13:33:07 2022 UTC elapsed time: 0.009551 seconds (0d 0h 0m 0s)

---------------  T H R E A D  ---------------

Current thread (0x00007fdc4c016000):  JavaThread "Unknown thread" [_thread_in_vm, id=548, stack(0x00007fdc53672000,0x00007fdc53773000)]

Stack: [0x00007fdc53672000,0x00007fdc53773000],  sp=0x00007fdc53771210,  free space=1020k
Native frames: (J=compiled Java code, A=aot compiled Java code, j=interpreted, Vv=VM code, C=native code)

How to investigate:

• try to run the script multiple times while being logged in docker container, to find out if it happens there as well