Not a major question, but I'm curious.
The MBean Object Name for the JMXConfigurator is
"Name=default,Type=ch.qos.logback.classic.jmx.JMXConfigurator". The key
names in the key property list appear to be inconsistent with Oracle's JMX
best practices
<http://www.oracle.com/technetwork/java/javase/tech/best-practices-jsp-13602…>
document, which recommend using "type" and "name" as the keys, not "Type"
and "Name". Per the same document, "Object Names are case sensitive." So
these keys do not match the Oracle recommended keys.
Was this inconsistency known or intended?
The only real consequence I can think of for this is that tools that know
how to interpret and display the standard "type" and "name" properties may
not work properly with Logback's MBean.
Hi,
If using a user-agent that prefer IPv6 such as the Squid proxy, a timeout
may frequently occur on logback.qos.ch.
It seems to me that the IPv6 site does not exist.
References:
- http://ready.chair6.net/?url=https://logback.qos.ch
- http://ipv6-test.com/validate.php
In addition, it seems that AAAA records may not be returned depending on
DNS query timing.
```
$ date; dig +noall +answer @8.8.8.8 logback.qos.ch aaaa
Thu Mar 30 22:34:03 DST 2017
logback.qos.ch. 279 IN CNAME yvo.qos.ch.
yvo.qos.ch. 279 IN AAAA 2a02:121e:969:1:201:c0ff:
fe1c:5f7c
$ date; dig +noall +answer @8.8.8.8 logback.qos.ch aaaa
Thu Mar 30 22:34:05 DST 2017
logback.qos.ch. 299 IN CNAME te.qos.ch.
```
Would you please investigate this?
Regards,
Takuma Tsutsumi
