Hello ivyteam!

I face a problem with ivy runtime log during starting a job/process in ASTECS project. This job (migration) processes bigger amount of data and runs more days. Unfortulately we have to start it under 32-bit Designer and are able to configure max cca 1700 MB for max heap size. Migration always crashes after couple hours with java heap space problem.

Is there a setup available, which writes logs in log-file in <designer>/logs/ folder only ? No designer runtime-log view/window. We think, this window is the cause of heap-crash under more runtime logs and not enough memory preset. However we require logs at least in log-file.

Example desired configuration: Designer runtime-log (view/window) logging level: FATAL Runtime-log into designer logs/ subfolder level: WARN

I have tried many combinations with adding/removing registered loggers or appenders, without reaching my goal.

Thanks for support! josef koupal

asked 25.05.2015 at 11:50

josef_koupal's gravatar image

josef_koupal
26557
accept rate: 25%

edited 26.05.2015 at 13:27


Instead of using a Designer use an Engine. You can even use an Engine with a Demo Licence. Deploy your project to the Engine. Start your migration job. On the Engine the runtime log is only written to a log file and should not fill up the memory.

link

answered 28.05.2015 at 12:49

Reto%20Weiss's gravatar image

Reto Weiss ♦♦
4.8k172554
accept rate: 74%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×71
×23

Asked: 25.05.2015 at 11:50

Seen: 1,085 times

Last updated: 28.05.2015 at 12:49