Hi
Looks like CARBON_MEMORY appender is not properly configured in GREG.
Please make sure following properties are there in log4j.properties file
# The memory appender for logging
log4j.appender.CARBON_MEMORY=
*org.wso2.carbon.logging.appender.CarbonMemoryAppender*
log4j.appender.CARBON_MEMORY.bufferSize=2000
log4j.appender.CARBON_MEMORY.layout=org.wso2.carbon.utils.logging.TenantAwarePatternLayout
# ConversionPattern will be overridden by the configuration setting in the
DB
log4j.appender.CARBON_MEMORY.layout.ConversionPattern=TID: [%T] [%S] [%d]
%P%5p {%c} - %x %m {%c}%n
log4j.appender.CARBON_MEMORY.layout.TenantPattern=%U%@%D [%T] [%S]
log4j.appender.CARBON_MEMORY.columnList=%T,%S,%A,%d,%c,%p,%m,%H,%I,%Stacktrace
log4j.appender.CARBON_MEMORY.threshold=DEBUG
and also* CARBON_MEMORY* is added to the root logger.
On Mon, Jul 7, 2014 at 5:24 PM, Denuwanthi De Silva <[email protected]>
wrote:
> Hi,
>
> G-reg 5.0.0 SNAPSHOT display 'null' in management console, when try to
> view 'System logs', with the following message:
> *The log must be configured to use the
> org.wso2.carbon.logging.core.util.MemoryAppender to view entries through
> the admin console*
>
> The corresponding test case, shows that it is due to 'LogViewerStub'
> returning a null 'Logevent', when trying to access system logs.
>
> The JIRA issue can be found in [1]
>
> [1].https://wso2.org/jira/browse/REGISTRY-2219
>
>
>
> Thanks,
> --
> Denuwanthi De Silva
> Software Engineer;
> WSO2 Inc.; http://wso2.com,
> Email: [email protected]
>
>
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Amani Soysa
Associate Technical Lead
Mobile: +94772325528
WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
