meanwhile the service become unavailable, you might grab the latest Logfile: http://demo.openmeetings.de/jvm.stdout
I might switch back to the previous version later today. We might at least agree on a road to take to solve those issues. Sebastian 2011/8/8 Maxim Solodovnik <[email protected]> > Hello Alexei, > > should i take a look at all these issues? Vasiliy is on vacation right now. > > > On Mon, Aug 8, 2011 at 00:43, [email protected] <[email protected] > > wrote: > >> Hi, >> >> there are a number of Issues with openJPA and the migration. >> The demo server is now updated but I needed several hours to get the basic >> functions running again. >> >> Also the shift with the user_ids in the import/export is still todo for >> the profiles_$userId thing. >> Somehow we could agree that we make a unique MD5 hash for each user for >> his profile path. >> >> The user sign up process is basically fixed, however when you repress the >> button to sign up again, or you just enter an existing user again, it will >> show the message that you have successfully signup, instead of showing a >> message that the user/login is already taken (which is what already >> implemented). >> >> I think there is really quite a bit to test and fix, the openmeetings >> service became unresponsible/did not react to any user interaction after >> just 30 minutes without any message about the reason in the logfile. >> >> Also there are Issue with the Caching. Example: >> I do create a new conference room with type restricted, max number 16, >> type public >> goto conference rooms, see the conference room, >> go back to administration, edit that room set max number to 100, >> goto conference rooms, see the conference room => STILL 16 >> >> => That is really bad, cause to track down this problem you really will >> need to rethink the hole procedure of insert/update/delete and how it >> behaves by running in multiple Threads. This behaviour can lead to various >> unpredictable situations, strongly depending on what usage scenario and how >> many records you already have in the database >> I've spend weeks to track down such problems with the previous >> implementation, where the only really solution is to use the spring injected >> session and let spring manage the session-context. However it really needs >> some in depth testing. We can hardly release a package right now. >> >> Sebastian >> >> >> -- >> Sebastian Wagner >> http://www.webbase-design.de >> http://openmeetings.googlecode.com >> http://www.wagner-sebastian.com >> [email protected] >> > > > > -- > WBR > Maxim aka solomax > -- Sebastian Wagner http://www.webbase-design.de http://openmeetings.googlecode.com http://www.wagner-sebastian.com [email protected] -- You received this message because you are subscribed to the Google Groups "OpenMeetings developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/openmeetings-dev?hl=en.
