Hello Susheel 1) shutdown works for me as expected, could you share your steps to reproduce the problem? 2) not sure what do you mean here. Re-installation is required as soon as OM internal DB was changed, there is no way to avoid this. You not delete old OM DB, just use different DB name (not sure why)
On Mon, Jun 6, 2016 at 8:02 PM, Susheel Jalali <[email protected]> wrote: > Dear OpenMeetings Developers, > > Can we transfer the following features from 3.0.7 to 3.1.2? > > *(1) Shutdown:* > > In red5-shutdown.sh, there is no port number any more. So, if we change > the port number of jmx.rmi.port=9999 to 8888, it does not shutdown. We > need to change the port number because we are running two instances of red5 > in the same server. > > Is there a place in red5-shutdown where we can specify a different port > number? > > *(2) Installation:* > > Every new installation needs to > · Delete / drop the previous database > · Start a new installation > > Can we not use the previously installed 3.1.2 database for > re-installations like it used to be for 3.0.7---it used to go directly to > the login screen for all future re-installations? > > > -- > > Sincerely, > > Susheel Jalali > Coscend Communications Solutions > www.Coscend.com > ---------------------------------------------------------------- > CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail > Messages from Coscend Communications Solutions' posted at: > http://www.Coscend.com/Terms_and_Conditions.html > -- WBR Maxim aka solomax
