DLog | It can be write your debug log

I am working on a p2p application and to make testing simple, I am currently using udp broadcast for the peer discovery in my local network. Each peer binds one udp socket to port 29292 of the ip address of each local network interface (discovered via GetAdaptersInfo) and each socket periodically sends a packet to the broadcast address of its network interface/local address. The sockets are set to allow port reuse (via setsockopt SO_REUSEADDR), which enables me to run multiple peers on the same local machine without any conflicts. In this case there is only a single peer on the entire network though.

This all works perfectly fine (tested with 2 peers on 1 machine and 2 peers on 2 machines) UNTIL a network interface is disconnected. When deactivacting the network adapter of either my wifi or an USB-to-LAN adapter in the windows dialog, or just plugging the usb cable of the adapter, the next call to sendto will fail with return code 10049. It doesn't matter if the other adapter is still connected, or was at the beginning, it will fail. The only thing that doesn't make it fail is deactivating wifi through the fancy win10 dialog through the taskbar, but that isn't really a surprise because that doesn't deactivate or remove the adapter itself.

I initially thought that this makes sense because when the nic is gone, how should the system route the packet. But: The fact that the packet can't reach its target has absolutely nothing to do with the address itsself being invalid (which is what the error means), so I suspect I am missing something here. I was looking for any information I could use to detect this case and distinguish it from simply trying to sendto INADDR_ANY, but I couldn't find anything. I started to log every bit of information which I suspected could have changed, but its all the same on a successfull sendto and the one that crashes (retrieved via getsockopt):

I have a project in Eclipse which uses OptaPlanner (v8.12.0). I want to be able to write temporary debug statements within the OptaPlanner code itself, so I:

1. cloned the repo,
2. checked out branch 8.12.x,
3. built using mvn,
4. imported as a pre-existing Maven project optaplanner-core (again, Eclipse), and
5. removed the optaplanner-core dependency from my Gradle dependencies

Everything compiles and runs just fine, but OptaPlanner no longer responds to my log config changes.

We're using Log4j2 and, when pulling OptaPlanner using the standard build process (Gradle), I can set the log level just fine using the Log4j2 config. But, with the src as a project dependency, it's not working.

I have tried:

• Including a local logback.xml
• Adding adding as a vm arg: -Dlogging.level.org.optaplanner=trace
• Adding adding as a vm arg: -Dlog4j.configurationFile=C:\path\to\log4j2.xml
• Setting an environment variable LOGGING_CONFIG=C:\path\to\logback.xml
• Setting the level programmatically using Configurator

Let's suppose we have a simple Spring-boot app:

pom.xml

I want to run a Docker container with some data source arguments the way I run a Spring Boot app on the terminal with Spring data source arguments. For example:

Follow guide from https://sync.objectbox.io/objectbox-sync-server

I already has my downloaded Objectbox sync server files

1. Download My Objectbox sync-server file (i got it from Objectbox Team) that and extract it
2. Copy my objectbox-model.json (generated file from my flutter app) to the extracted folder

try with

I'm trying to get the average value of every hour from a database. The data looks like this:

And my query looks like this:

I'm running into a problem when migrate to run my Springboot app from Amazon linux 1 to Amazon linux 2. I'm using run file with select the Java version by JAVA_HOME:

• Amazon linux 1: JAVA_HOME=/usr/lib/jvm/jre-1.8.0-openjdk.x86_64
• Amazon linux 2: JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.282.b08-1.amzn2.0.1.x86_64/jre/bin/java

Every thing work normal in Amazon linux 1 but in Amazon linux 2, I got the Unsupported major.minor version 52.0 error. What really confuse me is that when I change the whole java version of the instance (attached image) then everything is running ok again.

I'm guessing the problem is how I point to the java jre but I can't figure it out. Can somebody please help me with this. Thanks in advance.

Edit 1: The sh file i use to run:

I have a JBOSS server (7.0) running an application that uses ServiceWorkers, which requires an HTTPS connection. I was able to update the standalone.xml and Eclipse launch configuration to bind my JBOSS server to my local IP (I'll worry about port forwarding later). Connecting to http://192.168.0.197:8080/[application] works just fine, except that ServiceWorkers won't start because it isn't an HTTPS connection. If I try https://192.168.0.197:8080/[application], the connection fails with the browser reporting "unable to connect".

I've researched several documentation sources and can't figure out what needs to be updated. Please forgive any terminology errors - my background is with application programming and networking tends to be the bane of my existence.

This is the pertinent standalone.xml configuration:

I created a simple logging bot that will log a server to a specific logging server, soon I'll make it a simple and easy to use bot for everyone to use, but I came across a problem.

the code: