[ANNOUNCE] upcoming 2.1.1 release

2013-05-21 Thread Maxim Solodovnik
Hello All, I would like to start vote on 2.1.1 release in a day or two. Please let me know if you have any blockers. Thanks! -- WBR Maxim aka solomax

Re: [ANNOUNCE] upcoming 2.1.1 release

2013-06-06 Thread seba.wag...@gmail.com
> >>> > current development version. Fixes for any bugs that are > discovered > > >>> either > > >>> > in production or in development should be made to both this > > production > > >>> > version and to the development version (where s

Re: [ANNOUNCE] upcoming 2.1.1 release

2013-06-06 Thread Maxim Solodovnik
good to release a stable version, whether that be > 2.1.1 > > > or > > > >>> > 3.0.0 I don't care too much (as I do not know the difference > > between > > > >>> > versions). > > > >>> > > > > >>&

Re: [ANNOUNCE] upcoming 2.1.1 release

2013-06-06 Thread seba.wag...@gmail.com
great to > > > > >>> get yes)? > > > > >>> 02.06.2013 15:06 пользователь "George Kirkham" < > > > gkirk...@co2crc.com.au > > > > > > > > > >>> написал: > > > > >>> > > >

Re: [ANNOUNCE] upcoming 2.1.1 release

2013-06-06 Thread Maxim Solodovnik
; > > > > > >>> Maxim, regardless of the discussions. How to get 2.1 code? How > to > > > get > > > > > 2.1.1 > > > > > >>> code? Were all these mentioned fixes ported to 3.0 (taking into > > > > > account how > > >

Re: [ANNOUNCE] upcoming 2.1.1 release

2013-06-06 Thread Alexei Fedotov
>>> > 3.0.0 I don't care too much (as I do not know the difference >> between >> > >>> > versions). >> > >>> > >> > >>> > The main point is to have; >> > >>> > a) a stable released version for

Re: [ANNOUNCE] upcoming 2.1.1 release

2013-06-27 Thread Alexei Fedotov
Hello folks, I investigate a log and found out that we constantly fail to commit objects to the database due to connection breaks (both 2.1.1 and 3.0 are affected). There are several options to resolve this in the error message below. What is a preferable one? Here is a sample exception: FailedO

Re: [ANNOUNCE] upcoming 2.1.1 release

2013-06-27 Thread Alexei Fedotov
The solution should work at least for the case when DB and Openmeetings are on the same server. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 [1] Start using Apache Openmeetings today, http://openmeetings.apache.org/ [2] Join

Re: [ANNOUNCE] upcoming 2.1.1 release

2013-06-27 Thread Alexei Fedotov
After some thinking I believe only autoReconnect=true will help us having DB updated. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 [1] Start using Apache Openmeetings today, http://openmeetings.apache.org/ [2] Join Alexei Fed

Re: [ANNOUNCE] upcoming 2.1.1 release

2013-06-27 Thread Maxim Solodovnik
It is already set :) This should be investigated with OPENJPA community :) PS from the phone, sorry for typos :) WBR solomax On Jun 27, 2013 2:45 PM, "Alexei Fedotov" wrote: > After some thinking I believe only autoReconnect=true will help us > having DB updated. > -- > With best regards / с на

Re: [ANNOUNCE] upcoming 2.1.1 release

2013-06-27 Thread seba.wag...@gmail.com
Hi Alexei, as Maxim confirmed: This parameter is already set. The issue you described: 52 524 877 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the s

Re: [ANNOUNCE] upcoming 2.1.1 release

2013-06-27 Thread Maxim Solodovnik
I believe this issue need to be reported to OpenJPA community with all detail available since it requires lots of time to reproduce and seems to affect nothing On Fri, Jun 28, 2013 at 6:13 AM, seba.wag...@gmail.com < seba.wag...@gmail.com> wrote: > Hi Alexei, > > as Maxim confirmed: This pa

Re: [ANNOUNCE] upcoming 2.1.1 release

2013-06-28 Thread Alexei Fedotov
Artyom, would you please report? Please? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 [1] Start using Apache Openmeetings today, http://openmeetings.apache.org/ [2] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dat

Re: [ANNOUNCE] upcoming 2.1.1 release

2013-06-28 Thread Artyom Horuzhenko
Unfortunately my researches were failed: there are no working solutions in google and no more detailed information about this error. We can use another database, like postgresql, as a last resort. 2013/6/28 Alexei Fedotov > Artyom, would you please report? Please? > -- > With best regards / с н

Re: [ANNOUNCE] upcoming 2.1.1 release

2013-06-28 Thread Maxim Solodovnik
We can publish our configuration to OpenJPA user list. They usually help :) PS from the phone, sorry for typos :) WBR solomax On Jun 29, 2013 12:28 AM, "Artyom Horuzhenko" wrote: > Unfortunately my researches were failed: there are no working solutions in > google and no more detailed informati

Re: [ANNOUNCE] upcoming 2.1.1 release

2013-06-29 Thread seba.wag...@gmail.com
We had those issues quite often in the past with customers and usually fixing the timeout of MySQL. So I can just repeat the offer to help by repeating my questions: What version of MySQL are you using ? What version of the JConnector Jar/Driver are you using ? What is the wait_timeout value in yo