You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Sascha Naderi (JIRA)" <ji...@apache.org> on 2012/10/26 14:51:12 UTC
[jira] [Created] (OPENMEETINGS-454) Scrennsharing initiated by
invited user ends up in exception report
Sascha Naderi created OPENMEETINGS-454:
------------------------------------------
Summary: Scrennsharing initiated by invited user ends up in exception report
Key: OPENMEETINGS-454
URL: https://issues.apache.org/jira/browse/OPENMEETINGS-454
Project: Openmeetings
Issue Type: Bug
Affects Versions: 2.1 Apache Incubator Release
Environment: apache-openmeetings-incubating-2.1.0.r1401510-23-10-2012_2311 in Ubuntu 12.04.1 LTS in VM Ware
Reporter: Sascha Naderi
Priority: Blocker
When an invited user tries to initiate a Screensharing, the following error occurs:
*********************************************************
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.
Apache Tomcat/6.0.32
***********************************************
I have had the problem with Openmeetings 2.0 Moodle too. I updated to Openmeetings 2.1 because I thought it was the same problem as OPENMEETINGS-343 for which there is suppose to be a bug fix in Openmeetings 2.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OPENMEETINGS-454) Scrennsharing initiated by
invited user ends up in exception report
Posted by "SebastianWagner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
SebastianWagner reassigned OPENMEETINGS-454:
--------------------------------------------
Assignee: SebastianWagner
> Scrennsharing initiated by invited user ends up in exception report
> -------------------------------------------------------------------
>
> Key: OPENMEETINGS-454
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-454
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.1 Apache Incubator Release
> Environment: apache-openmeetings-incubating-2.1.0.r1401510-23-10-2012_2311 in Ubuntu 12.04.1 LTS in VM Ware
> Reporter: Sascha Naderi
> Assignee: SebastianWagner
> Priority: Blocker
>
> When an invited user tries to initiate a Screensharing, the following error occurs:
> *********************************************************
> 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.
> Apache Tomcat/6.0.32
> ***********************************************
> I have had the problem with Openmeetings 2.0 Moodle too. I updated to Openmeetings 2.1 because I thought it was the same problem as OPENMEETINGS-343 for which there is suppose to be a bug fix in Openmeetings 2.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OPENMEETINGS-454) Scrennsharing initiated by
invited user ends up in exception report
Posted by "SebastianWagner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
SebastianWagner resolved OPENMEETINGS-454.
------------------------------------------
Resolution: Cannot Reproduce
Fix Version/s: 2.1 Apache Incubator Release
I have been testing with r1404518 (will be Nightly Build of 02.11.2012 and later).
I could not reproduce the issue.
Please retest with that version.
> Scrennsharing initiated by invited user ends up in exception report
> -------------------------------------------------------------------
>
> Key: OPENMEETINGS-454
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-454
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.1 Apache Incubator Release
> Environment: apache-openmeetings-incubating-2.1.0.r1401510-23-10-2012_2311 in Ubuntu 12.04.1 LTS in VM Ware
> Reporter: Sascha Naderi
> Assignee: SebastianWagner
> Priority: Blocker
> Fix For: 2.1 Apache Incubator Release
>
>
> When an invited user tries to initiate a Screensharing, the following error occurs:
> *********************************************************
> 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.
> Apache Tomcat/6.0.32
> ***********************************************
> I have had the problem with Openmeetings 2.0 Moodle too. I updated to Openmeetings 2.1 because I thought it was the same problem as OPENMEETINGS-343 for which there is suppose to be a bug fix in Openmeetings 2.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENMEETINGS-454) Scrennsharing initiated by
invited user ends up in exception report
Posted by "Sascha Naderi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492216#comment-13492216 ]
Sascha Naderi commented on OPENMEETINGS-454:
--------------------------------------------
OK, thank you. I tried it with a complete new installation and screensharing is working fine.
> Scrennsharing initiated by invited user ends up in exception report
> -------------------------------------------------------------------
>
> Key: OPENMEETINGS-454
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-454
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.1 Apache Incubator Release
> Environment: apache-openmeetings-incubating-2.1.0.r1401510-23-10-2012_2311 in Ubuntu 12.04.1 LTS in VM Ware
> Reporter: Sascha Naderi
> Assignee: SebastianWagner
> Priority: Blocker
> Fix For: 2.1 Apache Incubator Release
>
>
> When an invited user tries to initiate a Screensharing, the following error occurs:
> *********************************************************
> 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.
> Apache Tomcat/6.0.32
> ***********************************************
> I have had the problem with Openmeetings 2.0 Moodle too. I updated to Openmeetings 2.1 because I thought it was the same problem as OPENMEETINGS-343 for which there is suppose to be a bug fix in Openmeetings 2.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira