Skip to end of banner
Go to start of banner

Troubleshooting

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Some or all functionality not working at all

In rare cases JIRA has difficulties to enable JSU. Usually this can be solved by uninstall/re-install, reset, reload, etc. things.

We recommend to check the following things:

  • Manage Add-Ons: is the JSU Plugin enabled... and all modules enabled (except one, which is disabled per default!)?
  • Check your log files, serious problems usually leave a stacktrace. Do you see a reference to a class com.googlecode.jsu.*? (to determent which module cannot be loaded)
  • Have you tried to remove JSU plugin and reinstall it? (without restarting JIRA)

If reinstallation of the Add-On does not work, try to do it with a restart of JIRA, follow this steps:

  • Uninstall JSU
  • Stop JIRA
  • Delete the following 2 directories $JIRA_HOME/plugins/.bundled-plugins & $JIRA_HOME/plugins/.osgi-plugins (they will be recreated)
  • Start JIRA
  • Install JSU

Debugging the JSU Plugin

If you want to turn on the 'JSU' debug messages, you may do so as follows:

Temporary (until next JIRA restart):

Log into JIRA as administrator and go to System -> Troubleshooting and Support -> Logging & Profiling. Look for the link "Configure logging level for another package", click on it and enter

com.googlecode.jsu

as Package name and select DEBUG as Logging Level

Permanently:

Add the following lines into the file WEB-INF/classes/log4j.properties:

log4j.category.com.googlecode.jsu = DEBUG, filelog
log4j.additivity.com.googlecode.jsu = false

Debug log messages are very detailed. Your log file will grow very quickly, even performance of the whole system can be affected.

For these reasons we recommend to leave the logging only for a very short time on debug log level.

  • No labels