You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2013/02/07 07:07:15 UTC
[jira] [Resolved] (OPENMEETINGS-423) Installation OM2.0
[ https://issues.apache.org/jira/browse/OPENMEETINGS-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik resolved OPENMEETINGS-423.
-------------------------------------------
Resolution: Invalid
Fix Version/s: 2.1 Apache Release
after downloading and running you need to go to
http://localhost:5080/openmeetings/install
and perform installation
> Installation OM2.0
> ------------------
>
> Key: OPENMEETINGS-423
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-423
> Project: Openmeetings
> Issue Type: Bug
> Components: BuildsAndReleases
> Affects Versions: 2.0 Apache Incubator Release
> Environment: Windows Xp
> Reporter: Kevin.Liu
> Assignee: SebastianWagner
> Fix For: 2.1 Apache Release
>
>
> Last night, I download a OM 2.0, and upzip it.Then i run red5.bat according to install document.
> The red5 is ok, but some problems occured in contexting openmeetings .
> This is part of openmeetings log:
> *******************************************************************************************************
> DEBUG 09-06 14:01:31.763 ContextLoggingListener.java 16 72 ROOT [main] - Starting up context openmeetings
> DEBUG 09-06 14:01:34.825 WhiteBoardObjectListManagerById.java 3078 44 org.openmeetings.app.remote.red5.WhiteBoardObjectListManagerById [Launcher:/openmeetings] - WhiteBoardObjectListManagerById is constructed
> DEBUG 09-06 14:01:35.169 ScopeApplicationAdapter.java 3422 137 org.openmeetings.app.remote.red5.ScopeApplicationAdapter [Launcher:/openmeetings] - webAppPath : E:\VideoMeeting\20120906\webapps\openmeetings
> DEBUG 09-06 14:01:35.169 ScopeApplicationAdapter.java 3422 138 org.openmeetings.app.remote.red5.ScopeApplicationAdapter [Launcher:/openmeetings] - batchFileFir : E:\VideoMeeting\20120906\webapps\openmeetings\streams\
> DEBUG 09-06 14:01:37.091 EmoticonsManager.java 5344 75 org.openmeetings.app.remote.red5.EmoticonsManager [Launcher:/openmeetings] - ##### loadEmot completed
> DEBUG 09-06 14:01:42.981 MeetingReminderJob.java 11234 34 org.openmeetings.app.quartz.scheduler.MeetingReminderJob [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-1] - MeetingReminderJob.execute
> DEBUG 09-06 14:01:42.997 Sessionmanagement.java 11250 468 org.openmeetings.app.data.basic.Sessionmanagement [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-2] - ****** clearSessionTable:
> WARN 09-06 14:01:42.997 Configurationmanagement.java 11250 104 org.openmeetings.app.data.basic.Configurationmanagement [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-1] - Could not find key in configuration CONF_KEY: number.minutes.reminder.send
> DEBUG 09-06 14:01:43.013 Sessionmanagement.java 11266 452 org.openmeetings.app.data.basic.Sessionmanagement [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-2] - Sessions To Delete :: 0
> DEBUG 09-06 14:01:43.028 Sessionmanagement.java 11281 472 org.openmeetings.app.data.basic.Sessionmanagement [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-2] - clearSessionTable: 0
> DEBUG 09-06 14:01:43.091 AppointmentDaoImpl.java 11344 931 org.openmeetings.app.data.calendar.daos.AppointmentDaoImpl [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-1] - startStamp 2012-09-06 14:01:43.013
> DEBUG 09-06 14:01:43.106 AppointmentDaoImpl.java 11359 932 org.openmeetings.app.data.calendar.daos.AppointmentDaoImpl [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-1] - stopStamp 2012-09-06 14:16:43.013
> DEBUG 09-06 14:01:43.106 AppointmentLogic.java 11359 408 org.openmeetings.app.data.calendar.management.AppointmentLogic [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-1] - doScheduledMeetingReminder : no Appointments in range
> *************************************************************************
> and it loops
--
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