Goran Schwarz
Goran Schwarz
Upgrading Log4J to version 2 has been on my TODO list for a **while** Hopefully I will have time to do it *soon*, but more work than *just* switching to...
Log4j 1.7 has now been replaced with Log4j 2.24.3 I also made a **bunch** of changes (like renaming package from `com.asetune` to `com.dbxtune` and the JAR file is now called...
By the way: What Collector are you using... `AseTune`, `SqlServerTune` or `PostgresTune` Are you using GUI or NO-GUI mode And: Are you also using DbxCentral ???
## Scenario is: * Constant monitoring of one/several servers * Alarm Handling if something happens (for example via email): * A Blocking lock situation * Long running transaction (which may...
Any input on Log4j2 implementation? Does it work as expected? Or did the scanner pick up some _issues_
Close due to: No response from reporter
Just tested with latest SSHD version: **8.1.0.0** (no change) same behavior as above...
@bagajjal Is this fixed in V8.6.0.0 ???
@bagajjal Ok, do you have a "estimated" release... 1 month, 6 month, 1 year... or longer ???
@bagajjal Thanx :)