Theodul does not load

Steps to reproduce

Steps to reproduce:
1. Build fresh on 3.x
2. Process a recording using a public ACL
3.

Actual Results:
The Theodul error page:
Error
An error occurred. Please reload the page.

Expected Results:
A working player

I don't see any stack traces on either the host system, or the javascript console. Example failure can be found at http://testengage.usask.ca/engage/theodul/ui/core.html?id=6ec72aa2-db92-433b-8970-36d8289272da&debug=true

Activity

Show:
Lars Kiesow
April 24, 2017, 8:25 AM

Try restarting Opencast. I bet it will then work…

Rüdiger Rolf
April 24, 2017, 3:58 PM

In the module ...theodul-plugin-controls is not completly loaded somehow. I saw this on other modules too, but only 4 modules have to run without issues, the rest is optional:

  • theodul-core

  • theodul-plugin-controls

  • theodul-plugin-custom-mhConnection

  • theodul-plugin-video-videojs

I have seen issues like this in the past and, you do not even need to restart Opencast. Restarting the problematic bundles in a Karaf console would already help.

I have no idea if increasing the timeout for loading all components would help. But in general it seems to be an Karaf problems in a way and I have not yet found a way to even see errors within the player itself.

I guess a general workaround for this is to give up the idea of several bundles for the player and simply add all plugins to the one bundle.

Lars Kiesow
April 24, 2017, 4:17 PM

Looking at the Karaf 4.0.9 maintenance release, there are some fixed issues which could be related (as well as some security updates):
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12338821

We should check if we can update and if the issues disappear.

Karaf 4.1.1 is also out already and maybe we should check that one as well but that is more likely an update for develop.

Greg Logan
April 24, 2017, 5:40 PM

Restarting Opencast (or more likely the affected bundles) fixes the issue. I'm going to leave this open and we can either downgrade it if we're going to fix it later, or at least document it as a known issue. It would never occur to me to restart Opencast if there's no trace anywhere of an actual error being thrown

Stephen Marquard
August 9, 2017, 8:53 AM

Still seeing this issue in 3.x - opened a new issue,

Fixed and reviewed

Assignee

Rüdiger Rolf

Reporter

Greg Logan

Severity

Non Functioning

Tags (folksonomy)

None

Components

Fix versions

Affects versions

Priority

Blocker