[
https://issues.apache.org/jira/browse/DIRSERVER-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496041#comment-13496041
]
Emmanuel Lecharny edited comment on DIRSERVER-1762 at 11/13/12 8:44 AM:
------------------------------------------------------------------------
We will also need the server configuraton you are using, because we don't have
any issue starting the server with log in DEBUG mode : it's very likely that
some of your configuration will cause one LOG somewhere to generate a NPE which
stops the server, but we can't easily tell which call to log is the cause...
(we have thousands log calls in the server)
was (Author: elecharny):
We will also need the server configuraton you are using, because we don't
have any issue starting the server with log in DEBUG mode : it's very likely
that some of your configuration will cause one LOG somewhere to generate a NPE
which stops the server, but we can't easily tell which call to log is the
cause... (we have ten of thousands log calls in the server)
> Switching log in debug make the service crash at startup
> --------------------------------------------------------
>
> Key: DIRSERVER-1762
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1762
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: ldap
> Affects Versions: 2.0.0-M8
> Environment: Windows XP SP3
> java version "1.6.0_32"
> Java(TM) SE Runtime Environment (build 1.6.0_32-b05)
> Java HotSpot(TM) Client VM (build 20.7-b02, mixed mode, sharing)
> Reporter: Stéphane Démaret
> Priority: Minor
> Fix For: 2.0.0-M9
>
>
> When I switch the log rootcategory to DEBUG in log4j.properties, I am unable
> to start service.
> The last action logged in the log file is :
> [2012-11-11 20:53:02] DEBUG
> [org.apache.directory.shared.ldap.model.schema.registries.Registries] - USING
> :
> I discovered this issue while investigating a problem with SSL communications
> with postgres which cause another issue in Apache Directory.
--
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
