[jira] [Closed] (MARMOTTA-549) Logging functionality seems to behave strangely

["Fabian Cretton (JIRA)" <ji...@apache.org>]

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

Fabian Cretton closed MARMOTTA-549.
-----------------------------------
    Resolution: Not a Problem

I finally found out why my logs where no more working, and this might interest other users as well as the marmotta-archetype-module, as this did cost me a few hours of investigation.

I did create two new Marmotta modules, and thus DataViewLogging.java and ExtDataSourcesLogging.java were generated.

In this class, both modules had the same getPackages() return, which seemingly was causing my problem (but totally un-noticed):
both modules had: return Collections.singleton("ch.hevs.overLOD");
which I did replace accordingly by:
"ch.hevs.overLOD.dataView"
"ch.hevs.overLOD.extDataSources"

I don't remember if I did change that "ch.hevs.overLOD" value myself or if it was generated by marmotta-archetype-module.

once this was corrected, the logs did work again.


> Logging functionality seems to behave strangely
> -----------------------------------------------
>
>                 Key: MARMOTTA-549
>                 URL: https://issues.apache.org/jira/browse/MARMOTTA-549
>             Project: Marmotta
>          Issue Type: Bug
>          Components: Platform
>    Affects Versions: 3.3.0
>         Environment: windows
>            Reporter: Fabian Cretton
>
> Since an update of my Marmotta 3.3.0 fork a few weeks ago, the logging
> functionality behaves strangely.
> In my 'log' folder, since that update, only "marmotta-security.log" is
> daily updated and seems to contain the valid log.
> But the other files "marmotta-debug.log" and "marmotta-main.log" didn't
> change since 22.09.2014.
> The information displayed in the console also seems corrupted.
> On the "admin/logging.html" page, if I set Console to "DEBUG", those debug information are not displayed.
> Before that code update a few weeks ago, logs were working as expected.
> If you need more information about which merge is concerned, I will have a look.
> Willing to investigate the problem, this morning I did add some
> "System.out.println()" informations in the org.apache.marmotta.platform.core.services.logging.LoggingServiceImpl
> But everything seems fine: the referenced log files are correct, the paths
> are correct, the modules configuration debut levels are correct...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)