1) LCCSREPO.jar doesn't seem to log anything, but since WebDAV works off of apache/httpd then you could look at apache's error logs ( the equivalent /var/log/apache2/error_log). This might say something like "Couldn't PUT your ...............zip file because I didn't have permissions to write to that location". You can also just look through the latest stuff written to your apache logs to see if Adobe servers are even sending you anything ( Windows equivalent to "tail -f /var/log/apache2/error_log" ).
2) Did you look at the debug logger info that Adobe provides *during* a recording session? Using the following in your app:
Just like you, I'm also waiting for Adobe guys to give us some more logging info when something goes wrong on their server.
Thank you all for responses. Howewer, I found the solution in a different way, I set the timeout to 15 seconds from the room console, now it saves the record to my WebDAV after the session ends. Probably I will want to increase this limit though.
P.S. It didn't work until this modification to the room was made (the whole 5 minutes thing).
Yup we face the same thing, wait 5 min AND make sure no clients are connected OR click a button to end it.
In reference to the button that sets isRecording = false, are you referring to the SDK's recording/playback demo application? This client application is just a demo made as a reference guide. Yes, isRecording is set to true to start a recording, and is set to false to stop a recording, but this does not need to happen through button clicks. It could be made 100% programmatic.
Furthermore, if the application is being recorded, the LCCS service will stop the recording and publish it to your WebDAV server when the recorded application stops. So, this should work. Are you sure your application is being recorded? And are you sure your application has stopped?