Bundle Does Not Work If Present Before First Start Of Opencast

[lkiesow]

If the paella JAR is put into the Opencast (Karaf) deploy folder before Opencast is started for the first time, the Paella player will not work. If it is put there during the runtime of Opencast, everything works as expected. This is possibly caused by a missing dependency which causes the paella bundle to be activated too early.

[lkiesow]

The behavior sounds very much like
http://karaf.922171.n3.nabble.com/Hot-deploy-priority-on-first-start-up-td4047948.html

[miesgre]

@lkiesow, I think this [1] solve this issue.
If so, maybe it can be PR to opencast.

[1] https://groups.google.com/a/opencast.org/forum/#!msg/users/D0joq5Vr5js/7PZx8YzIAAAJ

[lkiesow]

The felix.fileinstall.noInitialDelay = false would cause an initial delay which then is hopefully long enough that it works. That should work, but is still a work-around.

The issue is more a Karaf issue than an Opencast issue and we should try to fix it there if possible. For going forward I would try updating Karaf (Next minor on OC 3.x next major on OC 4.x/develop) and check if the problem persists. If so, we should at least re-open KARAF-4723 …and then maybe apply the work-around ;-D

We have the same problem and the fix linked above didn't work for us. We didn't experiment with the settings yet however. This happens every time you restart the Opencast service. Workaround solution is to stop the Opencast service, delete the .jar file in the Opencast deploy directory, start the Opencast service and copy a new .jar file to the deploy directory a few seconds after. As pointed out, player won't load if the service starts with the .jar file already in the deploy directory.

Using Opencast 3.2 and Paella 5.2.3

[karendolan]

@lkiesow can this issue be closed?
Per KARAF-4723 , the Karaf bug was fixed in Karaf 4.0.8.
Per MH-12742, Opencast is updated to Karaf 4.0.10 in develop (5.x)
Per Merged pull on 4x Opencast 4x is updated to Karaf 4.0.9
Per MH-12295 Update Karaf to 4.0.9 Opencast 3x is updated to Karaf 4.0.9

[lkiesow]

Not sure. Last I've heard, the problem still persisted (I think it was with 4.x).
Hence, you may need to actually test if this problem still persists.

[miesgre]

@lkiesow @karendolan The problem still persists in opencast 6.x. Should we apply the work-around in opencast?