This is information about troubleshooting of JSU in general. If you have a problem with a particular module, please also check the documentation for that module. If you did read all the documentation, analysed your log files, tried different configuration, but it still does not work, feel free to submit a support ticket: Troubleshooting Servicedesk .
| Table of Contents |
|---|
Some or all functionality not working at all
...
| Warning |
|---|
Be aware that you might loose some functionality and re-introduce some bugs, that have been fixed in the newer version. So generally it is not a good idea to downgrade JSU. Further if you have saved any configuration with a newer version of JSU (in particular in the area of workflows), the configuration saved with a newer version of JSU might not be compatible with an older version of JSU. (We provide only compatibility for updates of JSU). |
Bean dependency problems with messages in the log file
In rare cases we had reports that user got a 404 error message in the browser, for example when navigation to JSU General Configuration. Checking the log file there had been messages like:
| Code Block |
|---|
Error creating bean with name 'com.googlecode.jsu.actions.ConfigurationAction': Unsatisfied dependency expressed through constructor argument with index 0 of type |
With the following steps, this can be resolved:
- Go to the UPM (Manage Add-Ons)
- Enable Safe Mode
- just enable JSU and try to go to the configuration page
- disable 'Safe Mode' with option to restore the previous configuration
- try again to go to the configuration page.
Debugging the JSU add-on
If you want to turn on the 'JSU' debug messages, you may do so as follows:
...