Hi Sebastian,
I still can't upload documents to the whiteboard. Eventually I noticed
the following thing in my log:
fileName = d47fbc42b5d3debaa2e704112ec8df04.jpg
DEBUG 11-22 20:32:59.339 DownloadHandler.java 1400435 94
org.openmeetings.servlet.outputhandler.DownloadHandler
[http-0.0.0.0-5080-1] -
parentPath = /
DEBUG 11-22 20:32:59.339 DownloadHandler.java 1400435 107
org.openmeetings.servlet.outputhandler.DownloadHandler
[http-0.0.0.0-5080-1] - sid: 0ec2bab78de6d6e693bcd697eda5a502
DEBUG 11-22 20:32:59.355 DownloadHandler.java 1400451 225
org.openmeetings.servlet.outputhandler.DownloadHandler
[http-0.0.0.0-5080-1] - requestedFile:
d47fbc42b5d3debaa2e704112ec8df04.jpg current_dir: c:\red5\webapps
\openmeetings\upload\files\
DEBUG 11-22 20:32:59.355 DownloadHandler.java 1400451 279
org.openmeetings.servlet.outputhandler.DownloadHandler
[http-0.0.0.0-5080-1] - full_path: c:\red5\webapps\openmeetings\upload
\files\d47fbc42b5d3debaa2e704112ec8df04.jpg
ERROR 11-22 20:32:59.355 DownloadHandler.java 1400451 366
org.openmeetings.servlet.outputhandler.DownloadHandler
[http-0.0.0.0-5080-1] - Error downloading:
java.lang.Exception: Invalid file requested
The file is present. I looked up the code ("DownloadHandler") where
the exception "Invalid file requested" is declared. The exception is
triggered when the "current_dir" doesn't match the beginning of the
"full_path". Then I thought how on earth, the above log shows that
"current_dir" exactly matches the beginning of the "full_path". Then I
looked back at the code and noticed that in the log output actually
this is not "current_dir" but "working_dir" which is declared:
(DownloadHandler line 225)
log.debug("requestedFile: " + requestedFile + " current_dir: " +
working_dir);
And here is my humble request to you Sebastian. Would it be possible
to add in the log output the actual "current_dir" just to make sure
if it triggers the exception or not, for example:
log.debug("requestedFile: " + requestedFile + " current_dir: " +
current_dir + " working_dir: " + working_dir);
For the time being I've tested all versions of openmeetings starting
with 1.6.2 and this one is running smoothly (at least under my XP),
1.7.0 is throwing me out of the room and since 1.8.0 when this "throw
exception" mechanism was introduced, none of 1.8.x file upload is
working for me.
Anyway, it seems you introduced a double checking mechanism as earlier
in the code you already check if the file exists.
Maybe it's something to do with the file management system on XP as I
noticed there were other XP users announcing similar problems.
I know I'm a real pain in the ... bottom, but I like your application
very much and would desperately:) like to use it in elearning with my
students.
Eventually I can do with 1.6.2 which is also splendid :)
Krzysztof
--
You received this message because you are subscribed to the Google Groups
"OpenMeetings User" group.
To post to this group, send email to openmeetings-user@googlegroups.com.
To unsubscribe from this group, send email to
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/openmeetings-user?hl=en.
