1 Reply Latest reply on Apr 29, 2013 6:01 AM by Ales Justin

    How to stop CapeDwarf from storing logs in Datastore?

    Paweł Malkiewicz Newbie

      I am using CapeDwarf JBoss AS7 to host classic GAE+GWT application. On server side, I am logging directly to java.util.Logger framework.

      The application works fine, the logs print nice to the console and files.

      However, all my logs, together with some http request logs, are also stored in the datastore. Yes, every log line becomes one datastore entity. This should not surprise me, because it is stated in the docs (http://www.jboss.org/capedwarf/docs) and it is needed in order to display logs in gae-like admin console of CapeDwarf.

      I was looking for a way to disable this useful but expensive feature. I cannot find any docs that would tell me what to do if I do not need/want my logs in the datastore (e.g. right now 98.3% of my datastore are __org.jboss.capedwarf.LogRequest__ and __org.jboss.capedwarf.LogLine__ entities!). Does anyone happen to know how to do it?

      Also, maybe there is an option to disable the entire gae-like admin console? (or at least set a password for it ?)

        • 1. Re: How to stop CapeDwarf from storing logs in Datastore?
          Ales Justin Master

          However, all my logs, together with some http request logs, are also stored in the datastore. Yes, every log line becomes one datastore entity. This should not surprise me, because it is stated in the docs (http://www.jboss.org/capedwarf/docs) and it is needed in order to display logs in gae-like admin console of CapeDwarf.

          I was looking for a way to disable this useful but expensive feature. I cannot find any docs that would tell me what to do if I do not need/want my logs in the datastore (e.g. right now 98.3% of my datastore are __org.jboss.capedwarf.LogRequest__ and __org.jboss.capedwarf.LogLine__ entities!). Does anyone happen to know how to do it?

          With 1.0.0.Beta4 (http://in.relation.to/Bloggers/CapeDwarf100Beta4IsOut) we move the logging into separate cache.

           

          We have an add-on called Compatibility, which is handled via capedwarf-compatibility.properties file:

          * https://github.com/capedwarf/capedwarf-shared/blob/master/src/main/java/org/jboss/capedwarf/shared/compatibility/Compatibility.java

           

          So you can put capedwarf-compatibility.properties file into classpath,

          add "ignore.logging=true" in it, and this will disable GAE-like logging.

           

          Or you can use plain GAE logging.properties file to limit logging as much as possible.

           

           

          Also, maybe there is an option to disable the entire gae-like admin console? (or at least set a password for it ?)

           

          Open standalone-capedwarf.xml and find this

           

                  <subsystem xmlns="urn:jboss:domain:capedwarf:1.0">

                      <admin-auth>false</admin-auth>

                  </subsystem>

           

          and enable it -- this should then enable BASIC auth for admin console.