Paul Gregoire mondain

Keybase proof

I hereby claim:

I am mondain on github.
I am mondain (https://keybase.io/mondain) on keybase.
I have a public key ASAiorfzeX4Knscdu0yapQ0IXSAoqN6FxhPXBQa-b1XaEgo

To claim this, I am signing this object:

When we run our Java based server on Linux on certain bare-metal servers we're seeing what may be some sort of file handle leak. To give more detail to this question, what would cause additional handles to be consumed outside of file access and socket creation? To get a total count we use lsof -i -n -p JAVA_APP_PID | wc -l to see the entire listing, we use lsof -i -n -p JAVA_APP_PID. On the listing there are entries like these that we don't recognize:

java     30464 mondain    0u      CHR             136,18      0t0       21 /dev/pts/18
java     30464 mondain    1u      CHR             136,18      0t0       21 /dev/pts/18
java     30464 mondain    2u      CHR             136,18      0t0       21 /dev/pts/18
java     30464 mondain  196u     unix 0x0000000000000000      0t0  5488165 type=STREAM
java     30464 mondain  200r     FIFO               0,10      0t0  5491231 pipe

I did some reading and it looks like this particular OOM message simply means to add more memory for the heap; it essentially means one is running too lean. CPU runs hot trying to clear the garbage.

OutOfMemoryError: GC overhead limit exceeded

Excessive GC Time and OutOfMemoryError
The parallel collector will throw an OutOfMemoryError if too much time is being spent in garbage collection: if more than 98% of the total time is spent in garbage collection and less than 2% of the heap is recovered, an OutOfMemoryError will be thrown. This feature is designed to prevent applications from running for an extended period of time while making little or no progress because the heap is too small. If necessary, this feature can be disabled by adding the option -XX:-UseGCOverheadLimit to the command line.

The following modifications to the conf/jee-container.xml should provide a higher availability level than the default configuration set.

For http and ws connections:

<bean name="httpConnector" class="org.red5.server.tomcat.TomcatConnector">
    <property name="protocol" value="org.apache.coyote.http11.Http11Nio2Protocol" />
    <property name="address" value="${http.host}:${http.port}" />
    <property name="redirectPort" value="${https.port}" />
    <property name="connectionProperties">

Configuration Options

When one configures SRT end-points using the provision style submission, the following parameters are available:

{
    "guid": "live/stream1",
    "context": "live",
 "name": "stream1",

	// Welcome! require() some modules from npm (like you were using browserify)
	// and then hit Run Code to run your code on the right side.
	// Modules get downloaded from browserify-cdn and bundled in your browser.

	var Buffer = require('buffer').Buffer;
	var forge = require('node-forge');

	const key = {
	'i': 'w',
	'l': 'x',

	pragma solidity ^0.4.0;


	/*

	Temporary Hash Registrar
	========================

	This is a simplified version of a hash registrar. It is purporsefully limited:
	names cannot be six letters or shorter, new auctions will stop after 4 years.


	/* Java String to C String */
	static int jstr_to_cstr(JNIEnv env, jstring jstr, char cstr) {
	jsize jlen, clen;
	clen = env->GetStringUTFLength(jstr);
	jlen = env->GetStringLength(jstr);
	env->GetStringUTFRegion(jstr, 0, jlen, cstr);
	if (env->ExceptionCheck()) {
	return -EIO;
	}

	Note that mid=5 is the extra video which would be fed by the server, similar to mid=1..3 for audio

	type: answer, sdp: v=0
	o=red5pro_6f1838 5138461613339 3 IN IP4 0.0.0.0
	s=-
	t=0 0
	a=msid-semantic: WMS *
	a=group:BUNDLE 0 1 2 3 4 5 6
	a=ice-options:trickle
	m=audio 9 UDP/TLS/RTP/SAVPF 111

	#!/bin/sh
	ffmpeg -y -r 1 -i $1 -an -s 640x480 -pixel_format yuv420p -f image2 image-%3d.raw