Is your persistence.xml valid xml file? Maybe you have typos in it?

On 15 October 2014 06:12, Paul Squires <paul.squi...@perininetworks.com>
wrote:

> Thanks all,
>
> Hmmm. I'm confused. I did all of this yesterday and it worked absolutely
> lovely.
>
> Then, today, I added a few extra bits to finish off the Asterisk
> integration, and now it's complaining "The server is not yet completely
> initialized. Please try again in a couple of seconds." with the "probably
> your database user/pwd/host is wrong!" message.
>
> I did the same as Hadi's advice below - copy the mysql file to persistence
> and no joy. The db / user / pass is definitely there... I connected fine
> via MySQL.
>
> Is there anything which I need to "reset" in terms of getting this
> running...?
>
> Cheers,
> Paul
>
>
>
> ---------- Forwarded message ----------
> From: hadi sumarsono <hdisumars...@gmail.com>
> To: user@openmeetings.apache.org
> Cc:
> Date: Mon, 13 Oct 2014 11:22:50 +0700
> Subject: Re: OM and Asterisk: use MySQL or Derby?
> Hi Solodovnik.
> I have same approach to switch to MySql, but at point-3, what is must
> reinstall?
> with mysql-connector-java-5.1.29 can I connecting OpenMeeting with MySqkl?
>
> On Mon, Oct 13, 2014 at 10:58 AM, Maxim Solodovnik <solomax...@gmail.com>
> wrote:
> Hello Paul,
>
> AFAIK Derby supports only one app at the time, so I would suggest to
> switch to MySql (or Postres maybe) performance might also be better in this
> case :)
> to switch you need to
> 1) copy webapps/openmeeting/WEB-INF/classes/META-INF/mysql_persistence.xml
> webapps/openmeeting/WEB-INF/classes/META-INF/persistence.xml
> 2) set correct host, port, DB name, user, password
> 3) reinstall
>
> in case you have valuable data in your Derby DB you can perform
> export/import to preserve it
>
> On 13 October 2014 06:31, Paul Squires <paul.squi...@perininetworks.com>
> wrote:
> Hi all,
>
> I'm currently working on an installation with both OpenMeetings and
> Asterisk running off the same box.
>
> I used the OM / Asterisk guide:
> http://openmeetings.apache.org/red5sip-integration_3.0.html
>
> and after modifying the socket location in /etc/odbc.ini to point to the
> right place, I ran
> echo "select 1" | isql -v asterisk-connector
>
> and it told me that it can't find a database called "openmeetings". I then
> realised that while the above ini file is looking for MySQL, my current OM
> install is running with Derby.
>
> So, I have a question...
>
> - What do I need to change in the odbc.ini file for it work with Derby?
>
> ... or, if that can't be done...
>
> - What do I need to change in OM config to make it point to a MySQL db
> rather than Derby?
>
> Thanks in advance,
> Paul
>
>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>


-- 
WBR
Maxim aka solomax

Reply via email to