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:
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
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 alexei.fedo...@gmail.com wrote:
After some thinking I believe only autoReconnect=true will help us
having DB updated.
--
With
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
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
A collegue of mine told me that JAX-WS RI can be used for SOAP (I believe
it is also part of TomEE)
On Thu, Jun 27, 2013 at 5:15 AM, seba.wag...@gmail.com
seba.wag...@gmail.com wrote:
Some comments:
Quote: *remove *webservices* jar in favor of TomEE like annotation based
REST/SOAP methods*
