brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aledsage <>
Subject [GitHub] incubator-brooklyn pull request: Logging brooklyn-persister thread...
Date Thu, 30 Oct 2014 22:28:20 GMT
Github user aledsage commented on a diff in the pull request:
    --- Diff: usage/logback-includes/src/main/resources/brooklyn/logback-logger-debug-jclouds-split-persistence.xml
    @@ -0,0 +1,46 @@
    +<?xml version="1.0" encoding="UTF-8"?>
    +    Licensed to the Apache Software Foundation (ASF) under one
    +    or more contributor license agreements.  See the NOTICE file
    +    distributed with this work for additional information
    +    regarding copyright ownership.  The ASF licenses this file
    +    to you under the Apache License, Version 2.0 (the
    +    "License"); you may not use this file except in compliance
    +    with the License.  You may obtain a copy of the License at
    +    Unless required by applicable law or agreed to in writing,
    +    software distributed under the License is distributed on an
    +    KIND, either express or implied.  See the License for the
    +    specific language governing permissions and limitations
    +    under the License.
    +    <!--
    +        Including this file after all other debug configuration will move all of the
    +        logging messages to two files, named 'brooklyn-application.jclouds.log' and
    +        'brooklyn-application.jclouds-persister.log'. The latter will contain all messages
    +        logged by Jclouds when called from Brooklyn's persistence thread, the former
    +        contain all other messages logged by Jclouds.
    +        If your server will manage more than ~ 10 entities then it is recommended to
    --- End diff --
    Worth saying something like "if you have configured Brooklyn to persist state to an object-store"
as well.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message