Answers to: Where to find engine 'logs' using the Mac Designer?

Comment by Reguel Wermelinger on Reguel Wermelinger's answer

Reguel Wermelinger — Fri, 28 Feb 2020 03:39:52 -0500

I think the default log level should be 'debug'. However it sound to me as if the symlink fix at least partially works. Most users rarely use the /logs dir but examine the RuntimeLog+ErrorLog view. But don't hesitate to tell us if you have other strange execution behavior related to the logs.

I'll enrich the existing issue regarding runtime logs on mac (XIVY-3526) and try to raise the pressure on this topic.

Comment by sorin on Reguel Wermelinger's answer

sorin — Thu, 27 Feb 2020 15:40:48 -0500

So, apparently adding Ivy.log().setLevel(Level.ALL); as early as possible in the code solves my logging needs inside the Designer, as I can see the log entries in "Runtime log" now.

I guess the default log level was ERROR?

Comment by sorin on Reguel Wermelinger's answer

sorin — Thu, 27 Feb 2020 12:13:00 -0500

Hmm, that's funny, I can't find that error anymore, the one I quoted from above. However, I can still not see any logs in the folder I've linked.

Comment by Reguel Wermelinger on Reguel Wermelinger's answer

Reguel Wermelinger — Thu, 27 Feb 2020 09:57:13 -0500

didn't test it, but maybe a symlinking this /logs directory into your user home will help.

Comment by sorin on Reguel Wermelinger's answer

sorin — Thu, 27 Feb 2020 06:08:18 -0500

Is there a way around this?

I've tried to create the logs directory, I've tried to chmod it to 777, still the same error.

If I move the Designer to a different place rather than /Applications, would it help?

Is there any permission I grant in "System Preferences" that would help?

Comment by sorin on Reguel Wermelinger's answer

sorin — Thu, 27 Feb 2020 06:04:58 -0500

Ok, so I see the error regarding the Designer writing logs, it's trying to write in /Applications/Axon.ivy Designer 7.3.app/Contents/Eclipse/logs and throwing the following error:

java.lang.IllegalArgumentException: Parameter 'directory' is not a directory: /Applications/Axon.ivy Designer 7.3.app/Contents/Eclipse/logs at org.apache.commons.io.FileUtils.validateListFilesParameters(FileUtils.java:541) at org.apache.commons.io.FileUtils.listFiles(FileUtils.java:517) ...

Comment by sorin on Reguel Wermelinger's answer

sorin — Thu, 27 Feb 2020 05:56:57 -0500

The "Runtime log" was my first option, but although it is filtered at "DEBUG" level, I cannot see anything else than errors. I'm trying to log some stuff through Ivy.log().info("something") in Java classes and I cannot see it in the "Runtime log". The standard Eclipse "Error log" windows shows nothing except some IDE-related errors.

Answer by Reguel Wermelinger

Reguel Wermelinger — Thu, 27 Feb 2020 05:33:52 -0500

Workaround for the Axon.ivy Designer logs issue: ...until a fix is available:

there is an open issue that prevents logs files form being written to Axon.ivyDesigner/logs dir under Mac. Due to the way MacOS handles applications. >> fix it as follows until an official fix is ready

create a directory 'xpertivy' in the user home directory
copy the 'log4jconfig.xml' from Axon.ivy Designer.app > Contents > Eclipse > configuration into the 'xpertivy' directory
edit the log4jconfig.xml in this newly created xpertivy directory
in the FileLog appender section. Adjust the 'File' parameter so that after ${user.dir} an additional part ../Eclipse is added. So the final file looks as this: <param name="File" value="${user.dir}/../Eclipse/logs/ivy.log"/>
save log4jconfig.xml and restart your designer.
now logs should be written to the Axon.ivyDesigner app > Contents > Eclipse > logs > ivy.log

Logs for the Design time runtime enviroment can be found in various locations

https://developer.axonivy.com/doc/8.0.2/designer-guide/process-modeling/simulation-debugging.html?highlight=runtime%20log#runtime-log-view
or the standard 'Error Log' view of Eclipse
Axon.ivy Designer.app/Contents/Eclipse/Logs/ivy.log (see workaround above)

If your want logs from the engine used during maven builds:

use the commandline option '-X' e.g. mvn clean verify -X ...to see debug log outputs
some logs are also visible here: http://axonivy.github.io/project-build-plugin/release/8.0/start-test-engine-mojo.html#engineLogFile
in maven builds the engine can be consumed from various locations. Standard location is [user.home]/.m2/repository/.cache/ivy/... /logs
however; if you migrate to 8.0 LTS once ... and can use the latest project-build-plugin:8.0.1 there are more log outputs available: the engine being used is printed to console and one can easily navigate to that directory and examine its log directory.