Disabling dynamo.log

[Pedro López]

Hi,

somebody knows how to disable dynamo.log? I cannot find how to do it.

Thanks in advance.

Pedro

[Ronak Shah]

You can try this -- In last config layer you can put GLOBAL.properties and turn of all login -- info, debug=false etc. and you will not get much in dynamo.log . You will still have the file.
I am not sure how stop creating file.
If you wan to disable log for a component than change it false in that that properties file.

[Kelly Goetsch]

Pedro, why would you want to disable dynamo.log? Is it because the file is growing too large?

[Belmont, Adam]

Unfortunatly I don’t think there is a good way to shut off dynamo.log.

You can display info.log,debug.log,error.log via .properties file changes, but the dynamo.log is setup to start listening to system.out and system.err when Nucleus starts.

 

You *might* be able to get away with something like this in a custom nucleus component’s doStartService()

 

atg.core.io.SystemOutRecorder.popLogFile();

 

You’ll still get something written to dynamo.log at startup before this method gets called, but it’ll be small.

Well, assuming this works, I’m just guessing by inspection, I didn’t actually try it out.

 

 -- Adam

 

 

---

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "ATG_Tech" group.
To post to this group, send email to atg_...@googlegroups.com
To unsubscribe from this group, send email to atg_tech-u...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/atg_tech?hl=en
-~----------~----~----~----~------~----~------~--~---

[John Cooke]

You can override the GLOBAL.properties that sets up the event listeners as well.  This would prevent the events from getting to the loggers and effectively disable debug, error, info and warning logging.  Again, you would get the sysout and syserr messages, which I assume you would want to see anyway.

Gordon Cooke

Spark::red

http://www.sparkred.com

[Rickard, Andrew]

I haven't tested this but if you're using DAS on UN?X can't you run the command

 

> startDynamo -logFile /dev/null

 

Andrew

 

---

From: atg_...@googlegroups.com [mailto:atg_...@googlegroups.com] On Behalf Of Belmont, Adam
Sent: Friday, January 11, 2008 2:54 PM
To: atg_...@googlegroups.com
Subject: [atg_tech:471] Re: Disabling dynamo.log

[Rickard, Andrew]

Actually perhaps its even easier then that. According to the usage of the startDynamo command you can run the command with the -c argument. This argument sends all output to the console and doesn't create a dynamo.log file.

Here's the startDynamo usage for reference.


startDynamo [server-name] [-b] [-c] [-debug -debugPort] [-w or -n] [-v or -i][-m
additional-module-list]
-m Run additionally with the specified modules
-w Run ATG Dynamo Control Center and ATG Dynamo Application Server in on
e VM
-n Disable ATG Dynamo Control Center access, document/component indexing

-v Print version info and exit
-i Print IP addresses of this machine and exit
-b Run the base configuration - do not include installed apps
-c Log output only to the console
-j Collapse all the jar files from the classpath into a single jar
file. Useful for avoiding Windows command-line length limitations.
-debug Run with Java remote debugging enabled on port 3000
-debugPort Specifies the port for remote debugging

---
Andrew
Visit my Blog http://metatheory.wordpress.com

________________________________

[Pedro López]

Well, we have a version in production that is filling this log with a
harmless NullPointer error that does not appear in any other log (so
disabling error, info, debug and warning does not work) and I was
wondering how to disable this log temporarily while we go through QA
with the next version.

We are running on WebSphere. Any other idea?

Thanks,

Pedro

[Kelly Goetsch]

Let's try to find a solution to the NPE rather than just shutting off the log. It's likely that the issue is addressed in an ATG patch or hotfix. Can you provide me with the following information?

• All of the stack trace and any relevant output before or after the error
• The version of ATG you're running, including the most recent patch and any hotfixes
• All of the modules you're running on the instances throwing the error
• If running a BigEar, provide the value of atg.dynamo.modules
• If not running a BigEar, whatever modules you passed to runAssembler