Upgrade process is described here: http://openmeetings.apache.org/Upgrade.html Please backup everything before you will start it
On Fri, 5 Oct 2018 at 15:54, Biswajit Jena <expertsm...@gmail.com> wrote: > Thanks for the update. > Is there any way I can direct upgrade from version 3.0.4 to 4.0.4 ? or I > need fresh installation/configuration for new version ? > > > On Fri, Oct 5, 2018 at 1:03 PM Maxim Solodovnik <solomax...@gmail.com> > wrote: > >> *OM version 3.0.4 *is not supported anymore, please update to the latest >> release >> >> According to https://openmeetings.apache.org/NewsArchive.html version >> 3.0.4 was released with signed screen-sharing app >> But most probably it was signed with SHA1 which is now treated as unsecure >> >> >> >> On Fri, 5 Oct 2018 at 14:05, Biswajit Jena <expertsm...@gmail.com> wrote: >> >>> Please check my answers to your queries below. >>> >>> On Thu, Oct 4, 2018 at 1:55 PM Maxim Solodovnik <solomax...@gmail.com> >>> wrote: >>> >>>> What version are you running? * OM version 3.0.4* >>>> What do you mean by "OM screen sharing failed to the LAN user and >>>> getting error 'unable to launch'. "? I* tried to share screen from >>>> 'Share screen option in conference window to other user I get an error in >>>> JNLP.* >>>> What are your steps? *Start conference > Select option from Actions >>>> menu 'Share/record screen' > Download JNLP > public_890.jnlp >* *Open >>>> JNLP file with Javaws > Error Popup window : Unable to launch the >>>> application * >>>> >>> I click the details button and inside 3 different tabs - Launch file + >>> Exception + Console - There is an error showing in exception tab like this : >>> >>> Application Error >>> Unable to launch the application. >>> Unsigned application requesting unrestricted access to system >>> The following resource is signed with a weak signature algorithm >>> MD5withRSA and is treated as unsigned: >>> https:/localhost:5443/screensharing/commons-codec-1.6.jar >>> >>>> >>>> On Thu, 4 Oct 2018 at 15:05, Biswajit Jena <expertsm...@gmail.com> >>>> wrote: >>>> >>>>> Hi Team, >>>>> >>>>> OM screen sharing failed to the LAN user and getting error 'unable to >>>>> launch'. >>>>> >>>>> Here is the server log, >>>>> o.a.v.r.l.Log4JLogChute:168 [http-nio-0.0.0.0-5443-exec-8] - >>>>> Velocimacro : "velocimacro.library" is not set. Trying default library: >>>>> VM_global_library.vm >>>>> o.a.v.r.l.Log4JLogChute:168 [http-nio-0.0.0.0-5443-exec-8] - Could not >>>>> load resource 'VM_global_library.vm' from ResourceLoader >>>>> org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader: >>>>> ClasspathResourceLoader Error: cannot find resource VM_global_library.vm >>>>> o.a.v.r.l.Log4JLogChute:168 [http-nio-0.0.0.0-5443-exec-8] - >>>>> Velocimacro : Default library not found. >>>>> o.a.v.r.l.Log4JLogChute:168 [http-nio-0.0.0.0-5443-exec-8] - >>>>> Velocimacro : allowInline = true : VMs can be defined inline in templates >>>>> o.a.v.r.l.Log4JLogChute:168 [http-nio-0.0.0.0-5443-exec-8] - >>>>> Velocimacro : allowInlineToOverride = false : VMs defined inline may NOT >>>>> replace previous VM definitions >>>>> o.a.v.r.l.Log4JLogChute:168 [http-nio-0.0.0.0-5443-exec-8] - >>>>> Velocimacro : allowInlineLocal = false : VMs defined inline will be global >>>>> in scope if allowed. >>>>> o.a.v.r.l.Log4JLogChute:168 [http-nio-0.0.0.0-5443-exec-8] - >>>>> Velocimacro : autoload off : VM system will not automatically reload >>>>> global >>>>> library macros >>>>> o.a.v.r.l.Log4JLogChute:168 [http-nio-0.0.0.0-5443-exec-8] - >>>>> ResourceManager : found screenshare.vm with loader >>>>> org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader >>>>> >>>> >>>> >>>> -- >>>> WBR >>>> Maxim aka solomax >>>> >>> >> >> -- >> WBR >> Maxim aka solomax >> > -- WBR Maxim aka solomax
