From a3f62d1f30e278192b9e36ca007758e686a56ab2 Mon Sep 17 00:00:00 2001 From: Quentin Dufour Date: Sun, 31 Jan 2021 15:47:01 +0100 Subject: Overide logging + some doc to debug java processes --- app/jitsi/integration/README.md | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) (limited to 'app/jitsi/integration/README.md') diff --git a/app/jitsi/integration/README.md b/app/jitsi/integration/README.md index 82fa91d..c6bedd7 100644 --- a/app/jitsi/integration/README.md +++ b/app/jitsi/integration/README.md @@ -11,9 +11,10 @@ Several server components: - etc. Some libs: - - libjitsi - - jicoco - - jitsi-utils + - libjitsi seems deprecated + - jicoco contains some parent classes to handle Jitsi's Configuration + - [jitsi-utils](https://github.com/jitsi/jitsi-utils) contains the Logger definition for example + - [ice4j](https://github.com/jitsi/ice4j) contains jitsi's implementation of WebRTC - etc. Client components: @@ -62,6 +63,14 @@ instead, we should look at this one: https://github.com/jitsi/jitsi-meet/blob/ma Jitsi can be configured to authenticated through tokens, the postinst file is here: https://github.com/jitsi/jitsi-meet/blob/master/debian/jitsi-meet-tokens.postinst +## Remote debug + +Add this parameter to the java process you want to debug (either jicofo or jvb). It must be added by modifying the entrypoint script, next to the respective Dockerfile of each container. + +``` +-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=*:5005 +``` + ## Resources to understand jitsi - [jicofo/debian/postinst](https://github.com/jitsi/jicofo/blob/master/debian/postinst) -- cgit v1.2.3