[
https://issues.apache.org/jira/browse/OPENMEETINGS-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243129#comment-13243129
]
SebastianWagner commented on OPENMEETINGS-115:
----------------------------------------------
*I guess no matter? *
=> It does matter.
*still the same.*
=> The same like what? What is the output in the log file?
If you still have this error in your openmeetings.log:
org.openmeetings.app.remote.red5.ScopeApplicationAdapter
[Launcher:/openmeetings] - [appStart]
org.springframework.transaction.CannotCreateTransactionException: Could not
open JPA EntityManager for transaction; nested exception is
<openjpa-2.2.0-r422266:1244990 nonfatal user error>
org.apache.openjpa.persistence.ArgumentException: This configuration disallows
runtime optimization, but the following listed types were not enhanced at build
time or at class load time with a javaagent: "
org.openmeetings.app.persistence.beans.sip.asterisk.AsteriskSipUsers
org.openmeetings.app.persistence.beans.sip.asterisk.Extensions
org.openmeetings.app.persistence.beans.sip.asterisk.MeetMe".
at
org.springframework.orm.jpa.JpaTransactionManager.doBegin(JpaTransactionManager.java:382)
~[org.springframework.orm-jar-3.0.6.RELEASE.jar:3.0.6.RELEASE]
at
=> then the compilation was wrong.
You either do an svn update and just compile without -Ddb=mysql cause I have
fixed the derby_persistence.xml to inlcude all persistence classes OR you do
actually add the param but then you are not allowed to manually copy past
persistence.xml files cause they have different content.
> Installation error
> ------------------
>
> Key: OPENMEETINGS-115
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-115
> Project: Openmeetings
> Issue Type: Test
> Components: BuildsAndReleases
> Environment: Debian 6.0.4
> Java 1.6.0_26-b03
> OpenOffice 3.2
> Reporter: useruser
> Assignee: SebastianWagner
> Fix For: 2.0 Apache Incubator Release
>
>
> Trying to install latest revisions (1307724 for instance) I get
> "The server is not yet completely initialized. Please try again in a couple
> of seconds. If this message persists for several minutes contact your
> Sys-Administration. If that message stays forever you should check the logs
> located in openmeetings_install_dir/log folder, probably your database
> user/pwd/host is wrong!"
> There is no error in database settings - tables are created, but they are
> empty.
> With 1305083 revision everything is alright.
> Logs:
> 0.0.0.0_access.2012-03-31.log (http://pastebin.com/LqTQHZTF)
> error.log (empty)
> openmeetings.log (http://pastebin.com/diQEkTv4
> red5.log (http://pastebin.com/tUmwLg71)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
