|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
_______________________________________________ slf4j-dev mailing list slf4j-dev@qos.ch http://mailman.qos.ch/mailman/listinfo/slf4j-dev
Hello Ceki Gulcu,
The problem is that libraries that use java.util.logging (i.e. oracle jdbc more specifically) log messages like:
{18=false, 17=0, 2=60000, 1=NO, 0=YES}"2E1E69ED Debug: Session Attributes:
sdu=8192, tdu=32767
nt: host=localhost, port=7522
socket_timeout=60000, socketOptions=
socket=Socket[addr=localhost/127.0.0.1,port=7522,localport=51689]
ntInputStream : java.net.SocketInputStream@228f3979
ntOutputStream: java.net.SocketOutputStream@690648a8
nsInputStream : oracle.net.ns.NetInputStream@1b8c4376
nsOutputStream: oracle.net.ns.NetOutputStream@15a1061b
Client Profile:
{oracle.net.kerberos5_mutual_authentication=false, oracle.net.authentication_services=(), oracle.net.crypto_seed=, oracle.net.encryption_types_client=(), oracle.net.encryption_client=ACCEPTED, oracle.net.crypto_checksum_client=ACCEPTED, oracle.net.crypto_checksum_types_client=()}"
Which are processed alright if you use java.util.logging, but with jul-to-slf4j will cause an Exception if you try to connect to the database.
If you'd like to try it yourself, I can give you more details on how to reproduce it with oracle's jdbc.