Hello Peter, Thanks for finding this out! can you please try 2.1 rev. 1460576 (this should be fixed)
On Mon, Mar 25, 2013 at 4:44 PM, Maxim Solodovnik <solomax...@gmail.com>wrote: > so the problem should not be reproducible if you drop/create om_test > before import? > > > On Mon, Mar 25, 2013 at 4:39 PM, Peter Dähn <da...@vcrp.de> wrote: > >> Hallo Maxim, >> >> here are the first results. om2 is the om 2.0 installation and om_test is >> om 2.1 >> >> I searched for the private room of the admin-user. >> >> om2=> select fileexploreritem_id , filehash, room_id, deleted from >> fileexploreritem where room_id = 32; >> fileexploreritem_id | filehash | room_id | >> deleted >> ---------------------+--------**------------------------------** >> +---------+--------- >> 95 | 3fb9552e3a5317e8543f8f3b36135a**b3 | 32 | true >> 102 | | 32 | true >> 103 | 6d4feb13deb5b7845e0504f61a52a6**47 | 32 | true >> 104 | 9f1969d37caab6ec144a9144156de6**72 | 32 | true >> 105 | 49b87218674ef34afa97fe363bc81c**85 | 32 | true >> 145 | a0bbcec99435ee4c82057ee2c86948**55.flv | 32 | true >> 254 | 039c60e1652011697324891f69b0dc**7a.flv | 32 | true >> (7 Zeilen) >> >> >> om_test=> select id , filehash, room_id, deleted from fileexploreritem >> where room_id = 601; >> id | filehash | room_id | deleted >> ----+----------+---------+----**----- >> (0 Zeilen) >> >> Why is deleted true set in om 2.0? Anyway the file is there! >> >> During the research I noticed, that in OM 2.0 admin-user has user Id 1 >> and om 2-1 admin got 637. >> >> *Then I go to the room of the user with id 1 in 2.1 installation. and >> there are the files of the admin-user from the 2.0 installation.* The >> problem seems to be, that the user id's were mixed somehow. >> >> Greetings Peter >> >> >> >> Am 23.03.2013 04:04, schrieb Maxim Solodovnik: >> >>> the better query is: >>> >>> select id, filehash, room_id, 0+deleted from fileexploreritem; >>> >>> since room_id might have changed (should not happen with >>> --skip-default-rooms, >>> but who knows) the room id need to be doublechecked. >>> >>> >>> On Sat, Mar 23, 2013 at 9:59 AM, Maxim Solodovnik <solomax...@gmail.com >>> >wrote: >>> >>> detective work then :( >>>> >>>> can you check: >>>> 0) start 2.0 >>>> 1) find the room with the files missing >>>> 2) go to admin -> conference rooms find the room, remember it's id >>>> 3) check the database for 2.0 select should be something like: "select >>>> id, >>>> filehash from fileexploreritem where room_id = 'room id found in step >>>> 2'" >>>> >>>> try to search couple of hashes on your file system: >>>> find $RED5_HOME/webapps/**openmeetings -name <filehash> >>>> >>>> then after import perform same searches on 2.1 >>>> >>>> I can help you investigating this if it is possible for you to give me >>>> access to your system (using ssh+screen, vnc or something) I'll be >>>> available for couple more hours today, then ~13:00 GMT >>>> >>>> I'm not sure what is going on :( no errors in the log >>>> file records should be in DB, and files need to be on file system ... >>>> >>>> >>>> >>>> >>>> On Fri, Mar 22, 2013 at 10:36 PM, Peter Dähn <da...@vcrp.de> wrote: >>>> >>>> unfortunately still empty rooms... :-( >>>>> >>>>> logfile attached >>>>> >>>>> thanks in advanced >>>>> >>>>> Peter >>>>> >>>>> >>>>> Am 22.03.2013 15:51, schrieb Peter Dähn: >>>>> >>>>> Yes i used the commandline admin. >>>>> >>>>>> I will try it out. give me a second.... >>>>>> >>>>>> >>>>>> Am 22.03.2013 15:47, schrieb Maxim Solodovnik: >>>>>> >>>>>> if yes can you try to reinstall using >>>>>>> >>>>>>> ./admin -i -v -file backup.zip --skip-default-rooms (not sure about >>>>>>> exact >>>>>>> syntax) >>>>>>> >>>>>>> >>>>>>> On Fri, Mar 22, 2013 at 9:45 PM, Maxim Solodovnik < >>>>>>> solomax...@gmail.com >>>>>>> >>>>>>>> wrote: >>>>>>>> >>>>>>> have you restore it using commandline admin? >>>>>>> >>>>>>>> >>>>>>>> On Fri, Mar 22, 2013 at 9:43 PM, Peter Dähn <da...@vcrp.de> wrote: >>>>>>>> >>>>>>>> Yes, recorded files were restored, uploaded files are missing. >>>>>>>> >>>>>>>>> There is nothing in the log... >>>>>>>>> >>>>>>>>> The files are in the upload folder. >>>>>>>>> >>>>>>>>> Thanks Peter >>>>>>>>> >>>>>>>>> Am 22.03.2013 15:37, schrieb Maxim Solodovnik: >>>>>>>>> >>>>>>>>> Do you mean files were not restored while import? >>>>>>>>> >>>>>>>>>> any errors in the log? >>>>>>>>>> do you have these files in the upload folder? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Fri, Mar 22, 2013 at 9:14 PM, Peter Dähn <da...@vcrp.de> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> ok.. so far so good, but unfortunately I found something that >>>>>>>>>> is >>>>>>>>>> >>>>>>>>>> missing... :-/ >>>>>>>>>>> >>>>>>>>>>> The files in public and private rooms are missing. Any chance to >>>>>>>>>>> fix >>>>>>>>>>> this? >>>>>>>>>>> >>>>>>>>>>> BR Peter Dähn >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Am 22.03.2013 13:24, schrieb Maxim Solodovnik: >>>>>>>>>>> >>>>>>>>>>> Great! >>>>>>>>>>> >>>>>>>>>>> On Fri, Mar 22, 2013 at 7:22 PM, Peter Dähn <da...@vcrp.de> >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> Hallo everyone, >>>>>>>>>>>> >>>>>>>>>>>> checked out Rev 1459661 today and I was able to import a >>>>>>>>>>>> backup >>>>>>>>>>>> >>>>>>>>>>>>> from >>>>>>>>>>>>> my >>>>>>>>>>>>> 2.0 installation. User, files, config etc. everything is fine. >>>>>>>>>>>>> >>>>>>>>>>>>> Need to check a bit more, but I think thats it. >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks >>>>>>>>>>>>> >>>>>>>>>>>>> @ Maxim special thanks... ;-) >>>>>>>>>>>>> >>>>>>>>>>>>> br Peter Dähn >>>>>>>>>>>>> Am 20.03.2013 15:58, schrieb Maxim Solodovnik: >>>>>>>>>>>>> >>>>>>>>>>>>> can you please send me backup (privately) so I can >>>>>>>>>>>>> investigate >>>>>>>>>>>>> and >>>>>>>>>>>>> fix >>>>>>>>>>>>> >>>>>>>>>>>>> the >>>>>>>>>>>>> >>>>>>>>>>>>>> import? >>>>>>>>>>>>>> or maybe only polls.xml from the zip file will be enough ... >>>>>>>>>>>>>> (not >>>>>>>>>>>>>> sure) >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Mar 20, 2013 at 9:56 PM, Peter Dähn <da...@vcrp.de> >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> I forgot to mention... >>>>>>>>>>>>>> >>>>>>>>>>>>>> the backup i got from 2.0 installation and I tried to >>>>>>>>>>>>>> insert >>>>>>>>>>>>>> it in >>>>>>>>>>>>>> >>>>>>>>>>>>>> 2.1 >>>>>>>>>>>>>>> installation, freshly checked out from trunk 2.1... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> greetings >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Am 20.03.2013 15:50, schrieb Peter Dähn: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hello, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> after inserting the missing lines in persistence.xml is >>>>>>>>>>>>>>> was >>>>>>>>>>>>>>> able to >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> make >>>>>>>>>>>>>>>> a backup (see below). >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Today I tried to import the file via comand lin admin. >>>>>>>>>>>>>>>> Unfortunately >>>>>>>>>>>>>>>> it >>>>>>>>>>>>>>>> failed. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> After compiling I used the command >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> ./admin.sh -i -v -file backup_19_03_2013.zip --drop >>>>>>>>>>>>>>>> --db-type >>>>>>>>>>>>>>>> postgres >>>>>>>>>>>>>>>> --db-host host --db-name om_test --db-user user --db-pass >>>>>>>>>>>>>>>> password >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Output attached. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> What do I Have to do? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> regards and thanks >>>>>>>>>>>>>>>> Peter Dähn >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Am 04.01.2013 08:34, schrieb Peter Dähn: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hello Alexander, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> it is fixed in 2.1! >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> But unfortunately I can not use 2.1 at this time. At first >>>>>>>>>>>>>>>>> I >>>>>>>>>>>>>>>>> needed >>>>>>>>>>>>>>>>> the >>>>>>>>>>>>>>>>> possibility to backup my 2.0-Installation. All the trouble >>>>>>>>>>>>>>>>> happens >>>>>>>>>>>>>>>>> because >>>>>>>>>>>>>>>>> I use a postgresql database. I think now it is possible for >>>>>>>>>>>>>>>>> me to >>>>>>>>>>>>>>>>> install >>>>>>>>>>>>>>>>> OM 2.0 with backup-function and the data from the current >>>>>>>>>>>>>>>>> (running) >>>>>>>>>>>>>>>>> installation. Maybe i just need to run the installer again >>>>>>>>>>>>>>>>> using >>>>>>>>>>>>>>>>> the >>>>>>>>>>>>>>>>> changed persistence.xml. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I need to check this. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Anyway I could backup my data once. So it is fixed somehow. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I just needed to add the few lines in persistence.xml as >>>>>>>>>>>>>>>>> mentioned >>>>>>>>>>>>>>>>> below >>>>>>>>>>>>>>>>> and restart the system. So it is not usable with the >>>>>>>>>>>>>>>>> graphical >>>>>>>>>>>>>>>>> frontend but >>>>>>>>>>>>>>>>> it is posisible to use the command-line admin to make a >>>>>>>>>>>>>>>>> backup. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> greetings and thanks >>>>>>>>>>>>>>>>> Peter Dähn >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Am 03.01.2013 16:52, schrieb Alexander Petrov: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Well can we clarify this? Maxim said it was by design >>>>>>>>>>>>>>>>> and >>>>>>>>>>>>>>>>> fixed in >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> future >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> release. But Peter said another thing. Alexey, can I ask >>>>>>>>>>>>>>>>>> you >>>>>>>>>>>>>>>>>> to >>>>>>>>>>>>>>>>>> view >>>>>>>>>>>>>>>>>> task >>>>>>>>>>>>>>>>>> and say if it is fixed or not? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> четверг, 3 января 2013 г. пользователь Peter Dähn писал: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> ok.. it was not the whole truth... >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> OM start just in debug-mode??? but without the blue >>>>>>>>>>>>>>>>>> bar... but >>>>>>>>>>>>>>>>>> it >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> was >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> possible to make a backup with the command line admin... >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Thanks for your help... >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Am 03.01.2013 12:24, schrieb Peter Dähn: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Happy new year everyone, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> unfortunately it isn't that easy. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> When I add the missing lines in persistence.xml OM >>>>>>>>>>>>>>>>>>> won't >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> start >>>>>>>>>>>>>>>>>>>> anymore. >>>>>>>>>>>>>>>>>>>> So no backup possible. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I can not switch to OM 2.1 because i can not backup 2.0 >>>>>>>>>>>>>>>>>>>> and the >>>>>>>>>>>>>>>>>>>> tool I >>>>>>>>>>>>>>>>>>>> use here even won't work with OM2.1. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> At first I need to backup the Data from the >>>>>>>>>>>>>>>>>>>> 2.0-installation, >>>>>>>>>>>>>>>>>>>> then i >>>>>>>>>>>>>>>>>>>> could try a different revision of OM2.0 and maybe in the >>>>>>>>>>>>>>>>>>>> future >>>>>>>>>>>>>>>>>>>> switch to >>>>>>>>>>>>>>>>>>>> OM2.1. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> With best regards >>>>>>>>>>>>>>>>>>>> Peter Dähn >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Am 25.12.2012 08:38, schrieb Alexei Fedotov: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Alexander, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> would you consider trying another task? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> With best regards / с наилучшими пожеланиями, >>>>>>>>>>>>>>>>>>>>> Alexei Fedotov / Алексей Федотов, >>>>>>>>>>>>>>>>>>>>> http://dataved.ru/ >>>>>>>>>>>>>>>>>>>>> +7 916 562 8095 >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> On Sat, Dec 22, 2012 at 5:47 PM, Maxim Solodovnik < >>>>>>>>>>>>>>>>>>>>> solomax...@gmail.com> >>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> It was by design. Currently fixed in 2.1 >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> On Dec 22, 2012 8:07 PM, "Alexander Petrov" < >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> petrobr...@gmail.com >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Good day. I want to start my work in project >>>>>>>>>>>>>>>>>>>>>> from >>>>>>>>>>>>>>>>>>>>>> the >>>>>>>>>>>>>>>>>>>>>> following >>>>>>>>>>>>>>>>>>>>>> task >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> https://issues.apache.org/************<https://issues.apache.org/**********> >>>>>>>>>>>>>>>>>>>>>> <https://issues.apache.**org/********<https://issues.apache.org/********> >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> <https://issues.apache.**org/********< >>>>>>>>>>>>>>>>>>>>>> https://issues.apache.**org/******<https://issues.apache.org/******> >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> **jira/browse/OPENMEETINGS-******441< >>>>>>>>>>>>>>>>>>>>>> https://issues.apache.org/***<** >>>>>>>>>>>>>>>>>>>>>> https://issues.apache.org/*<https://issues.apache.org/*> >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> *******jira/browse/******OPENMEETINGS-441<https://** >>>>>>>>>>>>>>>>>>>>>> issues.apache.org/******jira/*** >>>>>>>>>>>>>>>>>>>>>> *browse/OPENMEETINGS-441<http://issues.apache.org/******jira/**browse/OPENMEETINGS-441> >>>>>>>>>>>>>>>>>>>>>> <https**://issues.apache.org/******** >>>>>>>>>>>>>>>>>>>>>> jira/browse/OPENMEETINGS-441<https://issues.apache.org/******jira/browse/OPENMEETINGS-441> >>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> **<https://issues.apache.org/*******<https://issues.apache.org/*****> >>>>>>>>>>>>>>>>>>>>>> <https://issues.apache.**org/***<https://issues.apache.org/***> >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> *****jira/browse/OPENMEETINGS-******441< >>>>>>>>>>>>>>>>>>>>>> https://issues.apache.**org/********jira/browse/** >>>>>>>>>>>>>>>>>>>>>> OPENMEETINGS-441<https://** >>>>>>>>>>>>>>>>>>>>>> issues.apache.org/******jira/** >>>>>>>>>>>>>>>>>>>>>> browse/OPENMEETINGS-441<https://issues.apache.org/******jira/browse/OPENMEETINGS-441> >>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> <https://issues.apache.org/*******<https://issues.apache.org/*****> >>>>>>>>>>>>>>>>>>>>>> ***jira/browse/OPENMEETINGS-****< >>>>>>>>>>>>>>>>>>>>>> https://issues.apache.org/***** >>>>>>>>>>>>>>>>>>>>>> ***jira/browse/OPENMEETINGS-**<https://issues.apache.org/******jira/browse/OPENMEETINGS-**> >>>>>>>>>>>>>>>>>>>>>> **> >>>>>>>>>>>>>>>>>>>>>> 441<https://issues.apache.org/****<https://issues.apache.org/**> >>>>>>>>>>>>>>>>>>>>>> ****jira/browse/OPENMEETINGS-****441< >>>>>>>>>>>>>>>>>>>>>> https://issues.apache.**org/****jira/browse/** >>>>>>>>>>>>>>>>>>>>>> OPENMEETINGS-441<https://issues.apache.org/****jira/browse/OPENMEETINGS-441> >>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> <h**ttps://issues.apache.org/*******<http://issues.apache.org/*****> >>>>>>>>>>>>>>>>>>>>>>> <http://issues.apache.org/*****<http://issues.apache.org/***> >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> *****jira/browse/OPENMEETINGS-********< >>>>>>>>>>>>>>>>>>>>>>> http://issues.apache.org/**********jira/browse/**<http://issues.apache.org/********jira/browse/**> >>>>>>>>>>>>>>>>>>>>>>> OPENMEETINGS-**<http://issues.** >>>>>>>>>>>>>>>>>>>>>>> apache.org/******jira/browse/**OPENMEETINGS-**<http://issues.apache.org/******jira/browse/OPENMEETINGS-**> >>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> 441<http://issues.apache.org/*******<http://issues.apache.org/*****> >>>>>>>>>>>>>>>>>>>>>>> <http://issues.apache.org/*****<http://issues.apache.org/***> >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> ***jira/browse/OPENMEETINGS-******441< >>>>>>>>>>>>>>>>>>>>>>> http://issues.apache.org/*** >>>>>>>>>>>>>>>>>>>>>>> ***jira/browse/OPENMEETINGS-****441< >>>>>>>>>>>>>>>>>>>>>>> http://issues.apache.org/*** >>>>>>>>>>>>>>>>>>>>>>> ***jira/browse/OPENMEETINGS-**441<http://issues.apache.org/****jira/browse/OPENMEETINGS-441> >>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> <https://issues.apache.org/*********<https://issues.apache.org/*******> >>>>>>>>>>>>>>>>>>>>>>> <https://issues.apache.**org/*****<https://issues.apache.org/*****> >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> *jira/browse/OPENMEETINGS-441<**** >>>>>>>>>>>>>>>>>>>>>>> https://issues.apache.org/********<https://issues.apache.org/******> >>>>>>>>>>>>>>>>>>>>>>> jira/browse/OPENMEETINGS-441<h** >>>>>>>>>>>>>>>>>>>>>>> ttps://issues.apache.org/****** >>>>>>>>>>>>>>>>>>>>>>> jira/browse/OPENMEETINGS-441<https://issues.apache.org/****jira/browse/OPENMEETINGS-441> >>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> <**https://issues.apache.org/********<https://issues.apache.org/******> >>>>>>>>>>>>>>>>>>>>>>> <https://issues.apache.**org/****<https://issues.apache.org/****> >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> jira/browse/OPENMEETINGS-441<**h** >>>>>>>>>>>>>>>>>>>>>>> ttps://issues.apache.org/**** >>>>>>>>>>>>>>>>>>>>>>> jira/browse/OPENMEETINGS-441<h** >>>>>>>>>>>>>>>>>>>>>>> ttps://issues.apache.org/**** >>>>>>>>>>>>>>>>>>>>>>> jira/browse/OPENMEETINGS-441<https://issues.apache.org/**jira/browse/OPENMEETINGS-441> >>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> **> >>>>>>>>>>>>>>>>>>>>>>> <h**ttps://issues.apache.org/*******<http://issues.apache.org/*****> >>>>>>>>>>>>>>>>>>>>>>> <http://issues.apache.org/*****<http://issues.apache.org/***> >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> ***jira/**browse/OPENMEETINGS-********< >>>>>>>>>>>>>>>>>>>>>>> http://issues.apache.org/********jira/**browse/**<http://issues.apache.org/******jira/**browse/**> >>>>>>>>>>>>>>>>>>>>>>> OPENMEETINGS-**<http://issues.** >>>>>>>>>>>>>>>>>>>>>>> apache.org/****jira/**browse/**OPENMEETINGS-**<http://issues.apache.org/****jira/**browse/OPENMEETINGS-**> >>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> 441<http://issues.apache.org/*******<http://issues.apache.org/*****> >>>>>>>>>>>>>>>>>>>>>>> <http://issues.apache.org/*****<http://issues.apache.org/***> >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> *jira/**browse/OPENMEETINGS-******441< >>>>>>>>>>>>>>>>>>>>>>> http://issues.apache.org/*** >>>>>>>>>>>>>>>>>>>>>>> *jira/**browse/OPENMEETINGS-****441< >>>>>>>>>>>>>>>>>>>>>>> http://issues.apache.org/*** >>>>>>>>>>>>>>>>>>>>>>> *jira/**browse/OPENMEETINGS-**441<http://issues.apache.org/**jira/**browse/OPENMEETINGS-441> >>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> <http://issues.apache.org/**** >>>>>>>>>>>>>>>>>>>>>>> jira/**browse/OPENMEETINGS-****441< >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> http://issues.apache.org/*** >>>>>>>>>>>>>>>>>>>>>>> *jira/**browse/OPENMEETINGS-****441< >>>>>>>>>>>>>>>>>>>>>>> http://issues.apache.org/*** >>>>>>>>>>>>>>>>>>>>>>> *jira/**browse/OPENMEETINGS-**441<http://issues.apache.org/**jira/**browse/OPENMEETINGS-441> >>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> **<http://issues.apache.org/** >>>>>>>>>>>>>>>>>>>>>>> jira/**browse/OPENMEETINGS-****441< >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> http://issues.apache.org/** >>>>>>>>>>>>>>>>>>>>>>> jira/**browse/OPENMEETINGS-**441< >>>>>>>>>>>>>>>>>>>>>>> http://issues.apache.org/** >>>>>>>>>>>>>>>>>>>>>>> jira/**browse/OPENMEETINGS-441<http://issues.apache.org/jira/**browse/OPENMEETINGS-441> >>>>>>>>>>>>>>>>>>>>>>> **> >>>>>>>>>>>>>>>>>>>>>>> **> >>>>>>>>>>>>>>>>>>>>>>> **> >>>>>>>>>>>>>>>>>>>>>>> **> >>>>>>>>>>>>>>>>>>>>>>> **<https://issues.apache.org/*******<https://issues.apache.org/*****> >>>>>>>>>>>>>>>>>>>>>>> <https://issues.apache.**org/***<https://issues.apache.org/***> >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> ***jira/browse/OPENMEETINGS-******441< >>>>>>>>>>>>>>>>>>>>>>> https://issues.apache.org/** >>>>>>>>>>>>>>>>>>>>>>> ****jira/browse/OPENMEETINGS-****441< >>>>>>>>>>>>>>>>>>>>>>> https://issues.apache.**org/****jira/browse/** >>>>>>>>>>>>>>>>>>>>>>> OPENMEETINGS-441<https://issues.apache.org/****jira/browse/OPENMEETINGS-441> >>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> <https://issues.apache.org/*******<https://issues.apache.org/*****> >>>>>>>>>>>>>>>>>>>>>>> *jira/browse/OPENMEETINGS-441<** >>>>>>>>>>>>>>>>>>>>>>> https://issues.apache.org/****** >>>>>>>>>>>>>>>>>>>>>>> jira/browse/OPENMEETINGS-441<https://issues.apache.org/****jira/browse/OPENMEETINGS-441> >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> <**https://issues.apache.org/******<https://issues.apache.org/****> >>>>>>>>>>>>>>>>>>>>>>> jira/browse/OPENMEETINGS-441<h** >>>>>>>>>>>>>>>>>>>>>>> ttps://issues.apache.org/**** >>>>>>>>>>>>>>>>>>>>>>> jira/browse/OPENMEETINGS-441<https://issues.apache.org/**jira/browse/OPENMEETINGS-441> >>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> **> >>>>>>>>>>>>>>>>>>>>>>> <**https://issues.apache.org/*******<https://issues.apache.org/*****> >>>>>>>>>>>>>>>>>>>>>>> <https://issues.apache.**org/***<https://issues.apache.org/***> >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> *jira/browse/OPENMEETINGS-441<**** >>>>>>>>>>>>>>>>>>>>>>> https://issues.apache.org/**** >>>>>>>>>>>>>>>>>>>>>>> jira/browse/OPENMEETINGS-441<h** >>>>>>>>>>>>>>>>>>>>>>> ttps://issues.apache.org/**** >>>>>>>>>>>>>>>>>>>>>>> jira/browse/OPENMEETINGS-441<https://issues.apache.org/**jira/browse/OPENMEETINGS-441> >>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> <**https://issues.apache.org/*****<https://issues.apache.org/***> >>>>>>>>>>>>>>>>>>>>>>> *jira/browse/OPENMEETINGS-441<** >>>>>>>>>>>>>>>>>>>>>>> https://issues.apache.org/**** >>>>>>>>>>>>>>>>>>>>>>> jira/browse/OPENMEETINGS-441<https://issues.apache.org/**jira/browse/OPENMEETINGS-441> >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> <**https://issues.apache.org/****<https://issues.apache.org/**> >>>>>>>>>>>>>>>>>>>>>>> jira/browse/OPENMEETINGS-441<h** >>>>>>>>>>>>>>>>>>>>>>> ttps://issues.apache.org/jira/** >>>>>>>>>>>>>>>>>>>>>>> browse/OPENMEETINGS-441<https://issues.apache.org/jira/browse/OPENMEETINGS-441> >>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> The problem is very easy: >>>>>>>>>>>>>>>>>>>>>>> this class is missing in several xxx_persistence.xml. >>>>>>>>>>>>>>>>>>>>>>> Well >>>>>>>>>>>>>>>>>>>>>>> the >>>>>>>>>>>>>>>>>>>>>>> solution to add few lines in these files. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> -- >>>>>>>> WBR >>>>>>>> Maxim aka solomax >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>> -- >>>> WBR >>>> Maxim aka solomax >>>> >>>> >>> >>> >> > > > -- > WBR > Maxim aka solomax > -- WBR Maxim aka solomax
