Tomcat && log4j vs MySQL

[Арсений Зинченко <se...@gmail.com>]

Hi.

Question are not exactly about Tomcat - but I hope somebody can help with
it.

So - we have Tomcat running. Apllication in it use log4j to write logs.

log4j configured to use syslogd daemon and syslogd uses MySQL to store logs.

Problem is that when we have any error in log - it writes it with newlines
when "at" in trace added.

For example:

14-03-24 13:49:59,574+0200 > 1641034 ERROR [com***l]
(http-8443-Processor25:CN=setevoy, OU=Unknown, O=Unknown, L=Unknown,
ST=Unknown, C=Unknown:10.***.***.15) Error in finding user: 'CN=setevoy,
OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown'
org.s***.EmptyResultDataAccessException: Incorrect result size: expected 1,
actual 0
        at org.***(***.java:1520)
        at com.***(***.java:288)
        at sun.***0(Native Method)

Then - in database table its added again with "newlines" fro every "at'
element and, as it new line, it's added it with new entry for every line.

So tables looks like (this other error trace, not from example above):

mysql> select ID,Message from SystemEvents order by ID desc limit
60;...| 258433 |     at java.lang.Thread.run(Thread.java:662)
                                                        | 258432 |
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
                      | 258431 |     at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
| 258430 |     at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:541)


Instead of add error entirely in one cell of table.

Could it be reconfigured someway?

Thanks.

Re: [OT] Tomcat && log4j vs MySQL

[Christopher Schultz <ch...@christopherschultz.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Арсений,

On 4/7/14, 4:18 AM, Арсений Зинченко wrote:
> Hi.
> 
> Question are not exactly about Tomcat - but I hope somebody can
> help with it.
> 
> So - we have Tomcat running. Apllication in it use log4j to write
> logs.
> 
> log4j configured to use syslogd daemon and syslogd uses MySQL to
> store logs.
> 
> Problem is that when we have any error in log - it writes it with
> newlines when "at" in trace added.
> 
> For example:
> 
> 14-03-24 13:49:59,574+0200 > 1641034 ERROR [com***l] 
> (http-8443-Processor25:CN=setevoy, OU=Unknown, O=Unknown,
> L=Unknown, ST=Unknown, C=Unknown:10.***.***.15) Error in finding
> user: 'CN=setevoy, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown,
> C=Unknown' org.s***.EmptyResultDataAccessException: Incorrect
> result size: expected 1, actual 0 at org.***(***.java:1520) at
> com.***(***.java:288) at sun.***0(Native Method)
> 
> Then - in database table its added again with "newlines" fro every
> "at' element and, as it new line, it's added it with new entry for
> every line.
> 
> So tables looks like (this other error trace, not from example
> above):
> 
> mysql> select ID,Message from SystemEvents order by ID desc limit 
> 60;...| 258433 |     at java.lang.Thread.run(Thread.java:662) |
> 258432 | at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
>
> 
| 258431 |     at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
>
> 
| 258430 |     at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:541)
>
> 
> 
> Instead of add error entirely in one cell of table.
> 
> Could it be reconfigured someway?

I think this is just one of the caveats of using log4j + syslog. You
should probably ask the folks at log4j or guidance.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJTQu+zAAoJEBzwKT+lPKRYM2cP/i/CbnVym1znfRZRAj5jfGjS
lVHAWLHxJ6VAUKFoGQfN41gM8fv0ZhFqMQSesw/L0mxHH1f+dgJLYOhRliocFVBa
OTBJ4lXK/9hgPCZL4utXVnc3f4Xz/odrpMJCLjB3n4TABn78EghRuqH6n8ToNvmp
7iV8tisM/3MjUHxetrhlurYM42NjyP9XwPfKrUe8MXmU4SUZXQ6tuiGOws8OTYj/
d09LSkHdHwYiMcvDOLCSw+kBzYegAp7uotwfuxQJuiFJVXGgwURwvAHx5VdB5Zbz
Y4oRn3d6DOtZ42gWmTD+6AT3gmMuw8Y7zGqLgeH2N3+lvGSt0uA8gpqUcG23YCIK
QKuKUtKunrQVItwE6SSWFMue5aMbnMRxcT9Tx599yhW/DJKLAyZ1jloFN6eO3wWc
HbE9h29NxhCPx+q3QmOAZ84nK6RcYSr8hbNzlAi6M7uBehLJgXUVlFx2HxnlwHHu
hE+o8+/wpWV+yqNdrva1AcK78rqx1Tnj0IenYpUdi8rZFP1oEPotP4SOHIdVGQsf
jDYHadxkPaV0xCfcAAbQ3RkR7WEnhZMrkuB/TkwyWy/M98Fb8IjWtIuqPpzyEmky
WQBjKhX7X5+KBcivQGMJcZtfRo01+szJcHPFSo2rn3y+zw9KwMql7229t81pNuad
ua4a0dEPjngkfqCvyFrT
=FGhe
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org