I've followed the recommendations for getting JEMH logging set up. However, it's really inconvenient for our users to restart JIRA. Is there a way to get JEMH to being logging WITHOUT a Jira restart?
Appologies, I should have explained better. When you have brought up the JEMH configuration screen (you need to have JIRA admin priv), you will see at the top of the configuration screen as serious of tabs "Welcome" "Profiles" "Blacklisting" etc. the 10 one over from the left, is "Auditing". Click on that, and you should then see the Audit selection. It will be Green if its enabled, or Red if its disabled.
(If you are using a older version of JEMH, then the tabs are located on the left of your screen, instead of the top of your screen)
Without a restart you can go to JIRA logging and profiling, and add the custom package: com.javahollic.jira.emh at DEBUG level you'll get a lot of traffic in the atlassian-jira-incoming-mail.log but it will be horizontally large, and difficult to manage, potentially with many concurrent processings.
To create a dedicated JEMH logfile, you will need to follow the https://thepluginpeople.atlassian.net/wiki/display/JEMH/Installation%2C+Setup+and+Logging page and modify your JIRA_HOME/WEB-INF/classes/log4j.properties file. Such a change does require a restart to take effect.
To answer “How scrum works,” most of the teams I've worked with first addressed the question: “where to start?” That question applies to both implementation and improvements on the Scrum framew...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs