Maxim, thanks for that amazingly fast update fix.
Thanks, George Kirkham From: Maxim Solodovnik [mailto:[email protected]] Sent: Thursday, 5 July 2012 3:52 PM To: [email protected] Subject: Re: Screen sharing fails with errors for people attending via Calendar Event invitation - OpenMeetings 2.0 R 1353777 Done https://issues.apache.org/jira/browse/OPENMEETINGS-343 revision 1357469 On Thu, Jul 5, 2012 at 12:35 PM, Maxim Solodovnik <[email protected]> wrote: I was able to reproduce it Will fix ASAP On Thu, Jul 5, 2012 at 11:55 AM, George Kirkham <[email protected]> wrote: Hi, Today when we attempted to have a meeting (by Calendar event) where someone wanted to share their screen, the user got the below error message whenever they tried to share their screen. When the user who needed to share their screen had this error, some of the other Users also tried to users to see if they could share their screen but had the same error message. The owner of the Calendar event meeting had logged into OpenMeetings using their user account, and entered their Meeting room, and we found that the owner was able to screen share their screen. NB: All uses were given Moderator rights so that they could be part of the screen sharing. If we all logged into OpenMeetings with User accounts and the entered into a meeting room (e.g. public Conference room), then it was possible to share our screens (i.e. without the below error message). My conclusion is that the a person who has logged in with a User account can do screen sharing, however users who have logged in via a meeting invitation get the below error message when they attempt to share their screen. HTTP Status 500 - ________________________________ type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.NullPointerException org.apache.velocity.tools.view.VelocityView.performMerge(VelocityView.java:942) org.apache.velocity.tools.view.VelocityView.merge(VelocityView.java:902) org.apache.velocity.tools.view.VelocityViewServlet.mergeTemplate(VelocityViewServlet.java:318) org.apache.velocity.tools.view.VelocityViewServlet.doRequest(VelocityViewServlet.java:220) org.apache.velocity.tools.view.VelocityViewServlet.doGet(VelocityViewServlet.java:182) javax.servlet.http.HttpServlet.service(HttpServlet.java:617) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.openmeetings.servlet.outputhandler.ServletRequestExFilter.doFilter(ServletRequestExFilter.java:49) org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77) note The full stack trace of the root cause is available in the Apache Tomcat/6.0.32 logs. Thanks, George Kirkham -- WBR Maxim aka solomax -- WBR Maxim aka solomax
