[jira] [Resolved] (QPID-8439) [Broker-J] Stack overflow during logging

["Tomas Vavricka (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/QPID-8439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomas Vavricka resolved QPID-8439.
----------------------------------
    Resolution: Fixed

> [Broker-J] Stack overflow during logging
> ----------------------------------------
>
>                 Key: QPID-8439
>                 URL: https://issues.apache.org/jira/browse/QPID-8439
>             Project: Qpid
>          Issue Type: Bug
>          Components: Broker-J
>    Affects Versions: qpid-java-broker-7.0.6
>            Reporter: Thorsten Meinl
>            Priority: Major
>             Fix For: qpid-java-broker-9.2.1
>
>         Attachments: catalina.out
>
>
> We are occasionally seeing stack overflow during logging in QPid. This completely kills the broker because some data structure are not initialized correctly any more afterwards. The problems lies in the combination of SLf4j use in QPid and the logging in the BDB implementation. BDB is configured using the Slf4jLoggingHandler in {{org.apache.qpid.server.store.berkeleydb.StandardEnvironmentFacade.StandardEnvironmentFacade(StandardEnvironmentConfiguration)}} which eventually ends up at the JDK logger (at least in our setup). However, BDB has a {{com.sleepycat.je.utilint.ConfiguredRedirectHandler}} which is appended to the the JDK logger and logs records from it to the configured Slf4jLoggingHandler. Which in turn forwards them to the JDK logger and there it starts again. The error is so obvious which makes me wonder why nobody else has reported it before. Is there some kind of configuration that we have set wrong?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org