You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openmeetings.apache.org by Maxim Solodovnik <so...@gmail.com> on 2013/05/21 11:57:07 UTC

[ANNOUNCE] upcoming 2.1.1 release

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

Posted by "seba.wagner@gmail.com" <se...@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 your MySQL config ?

Thanks,
Sebastian


2013/6/29 Maxim Solodovnik <so...@gmail.com>

> 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" <ak...@gmail.com> wrote:
>
> > 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 <al...@gmail.com>
> >
> > > 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/dataved/
> > > [3] Join Alexei Fedotov @facebook,
> http://www.facebook.com/openmeetings
> > >
> > >
> > > On Fri, Jun 28, 2013 at 7:17 AM, Maxim Solodovnik <
> solomax666@gmail.com>
> > > wrote:
> > > > 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.wagner@gmail.com <
> > > > seba.wagner@gmail.com> wrote:
> > > >
> > > >> 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 server configured values for client timeouts, or using the
> > > >> Connector/J connection property 'autoReconnect=true' to avoid this
> > > >> problem.
> > > >>
> > > >> is basically an issue that exists since the beginning of
> OpenMeetings,
> > > from
> > > >> my experience this is an environmental issue.
> > > >>
> > > >> There are a couple of 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 your MySQL config ?
> > > >>
> > > >> Thanks,
> > > >> Sebastian
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> 2013/6/27 Maxim Solodovnik <so...@gmail.com>
> > > >>
> > > >> > 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.fedotov@gmail.com
> > >
> > > >> > wrote:
> > > >> >
> > > >> > > 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 Fedotov @linkedin,
> > > http://ru.linkedin.com/in/dataved/
> > > >> > > [3] Join Alexei Fedotov @facebook,
> > > >> http://www.facebook.com/openmeetings
> > > >> > >
> > > >> > >
> > > >> > > On Thu, Jun 27, 2013 at 11:35 AM, Alexei Fedotov
> > > >> > > <al...@gmail.com> wrote:
> > > >> > > > 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 Alexei Fedotov @linkedin,
> > > >> http://ru.linkedin.com/in/dataved/
> > > >> > > > [3] Join Alexei Fedotov @facebook,
> > > >> > http://www.facebook.com/openmeetings
> > > >> > > >
> > > >> > > >
> > > >> > > > On Thu, Jun 27, 2013 at 11:26 AM, Alexei Fedotov
> > > >> > > > <al...@gmail.com> wrote:
> > > >> > > >> 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:
> > > >> > > >>
> > > >> > > >> FailedObject: select c from Sessiondata as c where
> c.session_id
> > > LIKE
> > > >> > > >> :session_id [java.lang.String]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> > > >> > > >>
> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
> > > >> > > >>
> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
> > > >> > > >>
> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:754)
> > > >> > > >>
> > > >>
> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723)
> > > >> > > >>
> > > >>
> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:393)
> > > >> > > >>
> > > >>
> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120)
> > > >> > > >>
> > > >>
> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> > > >> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> > > >> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openmeetings.data.basic.SessiondataDao$$EnhancerByCGLIB$$d3b21640.checkSession(<generated>)
> > > >> > > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openmeetings.servlet.outputhandler.DownloadHandler.service(DownloadHandler.java:96)
> > > >> > > >> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> > > >> > > >> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> > > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> > > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
> > > >> > > >> [red5.jar:na]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> > > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> > > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> > > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> > > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> > > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> > > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> > > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> > > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> > > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> > > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> > > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> > > >> > > >> [na:1.6.0_27]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > > >> > > >> [na:1.6.0_27]
> > > >> > > >> at java.lang.Thread.run(Thread.java:679) [na:1.6.0_27]
> > > >> > > >> Caused by:
> org.apache.openjpa.persistence.PersistenceException:
> > > The
> > > >> > > >> last packet successfully received from the server was 52 524
> > 877
> > > >> > > >> milliseconds ago.  The last packet sent successfully to the
> > > server
> > > >> was
> > > >> > > >> 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 server configured values for client timeouts, or using
> the
> > > >> > > >> Connector/J connection property 'autoReconnect=true' to avoid
> > > this
> > > >> > > >> problem.
> > > >> > > >> at
> > > >> > >
> > > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >>
> > >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.getConnection(JDBCStoreManager.java:240)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:413)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:391)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.jdbc.sql.LogicalUnion$UnionSelect.execute(LogicalUnion.java:427)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:230)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:220)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.open(SelectResultObjectProvider.java:94)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:34)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1251)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1007)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> >
> org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openmeetings.data.basic.SessiondataDao.checkSession(SessiondataDao.java:128)
> > > >> > > >> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openmeetings.data.basic.SessiondataDao$$FastClassByCGLIB$$8a6617e0.invoke(<generated>)
> > > >> > > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> > > >> > > >> at
> net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:191)
> > > >> > > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> > > >> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> > > >> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)
> > > >> > > >>
> > > >>
> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> > > >> ... 23 common frames omitted
> > > >> > > >> Caused by:
> > > com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
> > > >> > > >> The last packet successfully received from the server was 52
> > 524
> > > 877
> > > >> > > >> milliseconds ago.  The last packet sent successfully to the
> > > server
> > > >> was
> > > >> > > >> 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 server configured values for client timeouts, or using
> the
> > > >> > > >> Connector/J connection property 'autoReconnect=true' to avoid
> > > this
> > > >> > > >> problem.
> > > >> > > >> at
> > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > > >> > > >> Method) ~[na:1.6.0_27]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> > > >> > > >> ~[na:1.6.0_27]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> > > >> > > >> ~[na:1.6.0_27]
> > > >> > > >> at
> > > java.lang.reflect.Constructor.newInstance(Constructor.java:532)
> > > >> > > >> ~[na:1.6.0_27]
> > > >> > > >> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
> > > >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> > > >> at
> > > >> > >
> > > >>
> > >
> com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
> > > >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> > > >> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> > > >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> > > >> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2471)
> > > >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> > > >> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)
> > > >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> > > >> at
> > > com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2728)
> > > >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> > > >> at
> > > >> >
> > com.mysql.jdbc.ConnectionImpl.setAutoCommit(ConnectionImpl.java:5075)
> > > >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
> > > >> > > >> ~[commons-dbcp-jar-1.4.jar:1.4]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
> > > >> > > >> ~[commons-dbcp-jar-1.4.jar:1.4]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.setAutoCommit(PoolingDataSource.java:328)
> > > >> > > >> ~[commons-dbcp-jar-1.4.jar:1.4]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.setAutoCommit(ConfiguringConnectionDecorator.java:117)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.<init>(ConfiguringConnectionDecorator.java:111)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator.decorate(ConfiguringConnectionDecorator.java:93)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.lib.jdbc.DecoratingDataSource.decorate(DecoratingDataSource.java:99)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:88)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connectInternal(JDBCStoreManager.java:982)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:967)
> > > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >> ... 44 common frames omitted
> > > >> > > >> Caused by: java.net.SocketException: Broken pipe
> > > >> > > >> at java.net.SocketOutputStream.socketWrite0(Native Method)
> > > >> > > ~[na:1.6.0_27]
> > > >> > > >> at
> > > >> >
> java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
> > > >> > > >> ~[na:1.6.0_27]
> > > >> > > >> at
> > java.net.SocketOutputStream.write(SocketOutputStream.java:153)
> > > >> > > ~[na:1.6.0_27]
> > > >> > > >> at
> > > >> > >
> > > java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> > > >> > > >> ~[na:1.6.0_27]
> > > >> > > >> at
> > > java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> > > >> > > >> ~[na:1.6.0_27]
> > > >> > > >> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3832)
> > > >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> > > >> ... 60 common frames omitted
> > > >> > > >>
> > > >> > > >>
> > > >> > > >> --
> > > >> > > >> 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/dataved/
> > > >> > > >> [3] Join Alexei Fedotov @facebook,
> > > >> > http://www.facebook.com/openmeetings
> > > >> > > >>
> > > >> > > >>
> > > >> > > >> On Sat, Jun 1, 2013 at 10:01 PM, Alexei Fedotov
> > > >> > > >> <al...@gmail.com> wrote:
> > > >> > > >>> There are two possible options.
> > > >> > > >>>
> > > >> > > >>> 1. Test heavily and ship 2.1.1 release.
> > > >> > > >>> 2. Test heavily and ship 3.0 release instead.
> > > >> > > >>> 3. Ship 3.0 pre-release without heavy testing.
> > > >> > > >>>
> > > >> > > >>> Why should we bother about testing in 2.1.1? Haven't we just
> > > >> improved
> > > >> > > >>> a few things? We don't actually know if we have improved
> > things.
> > > >> Any
> > > >> > > >>> change have a risk of breaking something.
> > > >> > > >>>
> > > >> > > >>> My suggestion is to have testing infrastructure implemented,
> > > this
> > > >> > > >>> would help in testing. This will provide feedback. I prefer
> > > option
> > > >> > > >>> (2), or (3) because (1) is a waste of heavy testing effort.
> We
> > > >> don't
> > > >> > > >>> have enough resources to test two branches thoroughly.
> > > >> > > >>>
> > > >> > > >>> I constantly get suggestions (the last one from you one
> > Friday),
> > > >> like
> > > >> > > >>> let's have a low quality development branch, where we will
> > > >> progress,
> > > >> > > >>> and be creative, and let's have someone to produce reliable
> > > >> branches
> > > >> > > >>> from these development branches. For people in a role of
> > support
> > > >> > > >>> engineers it's hard. That's another reason why I prefer (2)
> or
> > > (3)
> > > >> to
> > > >> > > >>> (1).
> > > >> > > >>>
> > > >> > > >>> BTW, here is start of the error log in our 2.1.1
> installation.
> > > One
> > > >> > can
> > > >> > > >>> start fixing existing problems, if we want a release.
> > > >> > > >>>
> > > >> > > >>>     45 at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> > > >> > > >>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >>>      45 at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> > > >> > > >>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> > > >>>      42 Caused by: java.net.SocketException: Broken pipe
> > > >> > > >>>      42 at
> > > >> > >
> > > >>
> > >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
> > > >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >>>      42 at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> > > >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >>>      42 at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
> > > >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >>>      42 at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
> > > >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >>>      42 at
> > > >> > >
> > > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
> > > >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >>>      42 at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
> > > >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> > > >>>      42 at java.net.SocketOutputStream.socketWrite0(Native
> > > Method)
> > > >> > > >>> ~[na:1.6.0_27]
> > > >> > > >>>      42 at
> > > >> > >
> > > >>
> > >
> com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
> > > >> > > >>> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> > > >>>      42 at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> > > >> > > >>> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> > > >>>      32 at
> > > >> > > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > > >> > > >>> Method) ~[na:1.6.0_27]
> > > >> > > >>>      21 at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
> > > >> > > >>>
> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> > > >>>      21 at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> > > >> > > >>>
> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> > > >>>      21 at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
> > > >> > > >>>
> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> > > >>>      19 FailedObject: select c from Sessiondata as c where
> > > >> > > >>> c.session_id LIKE :session_id [java.lang.String]
> > > >> > > >>>      16 java.lang.NullPointerException: null
> > > >> > > >>>      12 at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openmeetings.remote.ConferenceService.getRoomsByOrganisationWithoutType(ConferenceService.java:147)
> > > >> > > >>> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> > > >> > > >>>      10 at
> > > >> > > sun.reflect.GeneratedConstructorAccessor283.newInstance(Unknown
> > > >> > > >>> Source) ~[na:na]
> > > >> > > >>>       4 at
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> org.apache.openmeetings.remote.red5.ScopeApplicationAdapter.roomLeaveByScope(ScopeApplicationAdapter.java:564)
> > > >> > > >>> [openmeetings-2.1.1-SNAPSHOT.jar:na]
> > > >> > > >>>       2 java.lang.Exception: not Authenticated
> > > >> > > >>>       2 ERROR 05-28 20:44:56.425
> o.a.o.r.WhiteBoardService:408
> > > >> > > >>> [NioProcessor-6] - WhiteboardSyncLockObject not found for
> this
> > > >> Client
> > > >> > > >>> {}
> > > >> > > >>>       2 ERROR 05-28 20:44:56.423
> o.a.o.r.WhiteBoardService:408
> > > >> > > >>> [NioProcessor-6] - WhiteboardSyncLockObject not found for
> this
> > > >> Client
> > > >> > > >>> {}
> > > >> > > >>>       2 Caused by:
> > > >> > > >>> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The
> > > last
> > > >> > > >>> packet successfully received from the server was 84 612 291
> > > >> > > >>> milliseconds ago.  The last packet sent successfully to the
> > > server
> > > >> > was
> > > >> > > >>> 84 612 291 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 server configured values for client timeouts, or using
> the
> > > >> > > >>> Connector/J connection property 'autoReconnect=true' to
> avoid
> > > this
> > > >> > > >>> problem.
> > > >> > >
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Sebastian Wagner
> > > >> https://twitter.com/#!/dead_lock
> > > >> http://www.webbase-design.de
> > > >> http://www.wagner-sebastian.com
> > > >> seba.wagner@gmail.com
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > WBR
> > > > Maxim aka solomax
> > >
> >
>



-- 
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com

Re: [ANNOUNCE] upcoming 2.1.1 release

Posted by Maxim Solodovnik <so...@gmail.com>.

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" <ak...@gmail.com> wrote:

> 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 <al...@gmail.com>
>
> > 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/dataved/
> > [3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
> >
> >
> > On Fri, Jun 28, 2013 at 7:17 AM, Maxim Solodovnik <so...@gmail.com>
> > wrote:
> > > 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.wagner@gmail.com <
> > > seba.wagner@gmail.com> wrote:
> > >
> > >> 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 server configured values for client timeouts, or using the
> > >> Connector/J connection property 'autoReconnect=true' to avoid this
> > >> problem.
> > >>
> > >> is basically an issue that exists since the beginning of OpenMeetings,
> > from
> > >> my experience this is an environmental issue.
> > >>
> > >> There are a couple of 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 your MySQL config ?
> > >>
> > >> Thanks,
> > >> Sebastian
> > >>
> > >>
> > >>
> > >>
> > >> 2013/6/27 Maxim Solodovnik <so...@gmail.com>
> > >>
> > >> > 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.fedotov@gmail.com
> >
> > >> > wrote:
> > >> >
> > >> > > 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 Fedotov @linkedin,
> > http://ru.linkedin.com/in/dataved/
> > >> > > [3] Join Alexei Fedotov @facebook,
> > >> http://www.facebook.com/openmeetings
> > >> > >
> > >> > >
> > >> > > On Thu, Jun 27, 2013 at 11:35 AM, Alexei Fedotov
> > >> > > <al...@gmail.com> wrote:
> > >> > > > 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 Alexei Fedotov @linkedin,
> > >> http://ru.linkedin.com/in/dataved/
> > >> > > > [3] Join Alexei Fedotov @facebook,
> > >> > http://www.facebook.com/openmeetings
> > >> > > >
> > >> > > >
> > >> > > > On Thu, Jun 27, 2013 at 11:26 AM, Alexei Fedotov
> > >> > > > <al...@gmail.com> wrote:
> > >> > > >> 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:
> > >> > > >>
> > >> > > >> FailedObject: select c from Sessiondata as c where c.session_id
> > LIKE
> > >> > > >> :session_id [java.lang.String]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> > >> > > >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
> > >> > > >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
> > >> > > >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:754)
> > >> > > >>
> > >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723)
> > >> > > >>
> > >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:393)
> > >> > > >>
> > >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120)
> > >> > > >>
> > >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> > >> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> > >> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openmeetings.data.basic.SessiondataDao$$EnhancerByCGLIB$$d3b21640.checkSession(<generated>)
> > >> > > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openmeetings.servlet.outputhandler.DownloadHandler.service(DownloadHandler.java:96)
> > >> > > >> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> > >> > > >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
> > >> > > >> [red5.jar:na]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> > >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> > >> > > >> [na:1.6.0_27]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > >> > > >> [na:1.6.0_27]
> > >> > > >> at java.lang.Thread.run(Thread.java:679) [na:1.6.0_27]
> > >> > > >> Caused by: org.apache.openjpa.persistence.PersistenceException:
> > The
> > >> > > >> last packet successfully received from the server was 52 524
> 877
> > >> > > >> milliseconds ago.  The last packet sent successfully to the
> > server
> > >> was
> > >> > > >> 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 server configured values for client timeouts, or using the
> > >> > > >> Connector/J connection property 'autoReconnect=true' to avoid
> > this
> > >> > > >> problem.
> > >> > > >> at
> > >> > >
> > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >>
> > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.getConnection(JDBCStoreManager.java:240)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:413)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:391)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.jdbc.sql.LogicalUnion$UnionSelect.execute(LogicalUnion.java:427)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:230)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:220)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.open(SelectResultObjectProvider.java:94)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:34)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1251)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1007)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openmeetings.data.basic.SessiondataDao.checkSession(SessiondataDao.java:128)
> > >> > > >> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openmeetings.data.basic.SessiondataDao$$FastClassByCGLIB$$8a6617e0.invoke(<generated>)
> > >> > > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> > >> > > >> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:191)
> > >> > > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> > >> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> > >> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)
> > >> > > >>
> > >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> > > >> ... 23 common frames omitted
> > >> > > >> Caused by:
> > com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
> > >> > > >> The last packet successfully received from the server was 52
> 524
> > 877
> > >> > > >> milliseconds ago.  The last packet sent successfully to the
> > server
> > >> was
> > >> > > >> 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 server configured values for client timeouts, or using the
> > >> > > >> Connector/J connection property 'autoReconnect=true' to avoid
> > this
> > >> > > >> problem.
> > >> > > >> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > >> > > >> Method) ~[na:1.6.0_27]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> > >> > > >> ~[na:1.6.0_27]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> > >> > > >> ~[na:1.6.0_27]
> > >> > > >> at
> > java.lang.reflect.Constructor.newInstance(Constructor.java:532)
> > >> > > >> ~[na:1.6.0_27]
> > >> > > >> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
> > >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> > > >> at
> > >> > >
> > >>
> > com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
> > >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> > > >> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> > >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> > > >> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2471)
> > >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> > > >> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)
> > >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> > > >> at
> > com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2728)
> > >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> > > >> at
> > >> >
> com.mysql.jdbc.ConnectionImpl.setAutoCommit(ConnectionImpl.java:5075)
> > >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
> > >> > > >> ~[commons-dbcp-jar-1.4.jar:1.4]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
> > >> > > >> ~[commons-dbcp-jar-1.4.jar:1.4]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.setAutoCommit(PoolingDataSource.java:328)
> > >> > > >> ~[commons-dbcp-jar-1.4.jar:1.4]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.setAutoCommit(ConfiguringConnectionDecorator.java:117)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.<init>(ConfiguringConnectionDecorator.java:111)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator.decorate(ConfiguringConnectionDecorator.java:93)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.lib.jdbc.DecoratingDataSource.decorate(DecoratingDataSource.java:99)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:88)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connectInternal(JDBCStoreManager.java:982)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:967)
> > >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >> ... 44 common frames omitted
> > >> > > >> Caused by: java.net.SocketException: Broken pipe
> > >> > > >> at java.net.SocketOutputStream.socketWrite0(Native Method)
> > >> > > ~[na:1.6.0_27]
> > >> > > >> at
> > >> > java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
> > >> > > >> ~[na:1.6.0_27]
> > >> > > >> at
> java.net.SocketOutputStream.write(SocketOutputStream.java:153)
> > >> > > ~[na:1.6.0_27]
> > >> > > >> at
> > >> > >
> > java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> > >> > > >> ~[na:1.6.0_27]
> > >> > > >> at
> > java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> > >> > > >> ~[na:1.6.0_27]
> > >> > > >> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3832)
> > >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> > > >> ... 60 common frames omitted
> > >> > > >>
> > >> > > >>
> > >> > > >> --
> > >> > > >> 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/dataved/
> > >> > > >> [3] Join Alexei Fedotov @facebook,
> > >> > http://www.facebook.com/openmeetings
> > >> > > >>
> > >> > > >>
> > >> > > >> On Sat, Jun 1, 2013 at 10:01 PM, Alexei Fedotov
> > >> > > >> <al...@gmail.com> wrote:
> > >> > > >>> There are two possible options.
> > >> > > >>>
> > >> > > >>> 1. Test heavily and ship 2.1.1 release.
> > >> > > >>> 2. Test heavily and ship 3.0 release instead.
> > >> > > >>> 3. Ship 3.0 pre-release without heavy testing.
> > >> > > >>>
> > >> > > >>> Why should we bother about testing in 2.1.1? Haven't we just
> > >> improved
> > >> > > >>> a few things? We don't actually know if we have improved
> things.
> > >> Any
> > >> > > >>> change have a risk of breaking something.
> > >> > > >>>
> > >> > > >>> My suggestion is to have testing infrastructure implemented,
> > this
> > >> > > >>> would help in testing. This will provide feedback. I prefer
> > option
> > >> > > >>> (2), or (3) because (1) is a waste of heavy testing effort. We
> > >> don't
> > >> > > >>> have enough resources to test two branches thoroughly.
> > >> > > >>>
> > >> > > >>> I constantly get suggestions (the last one from you one
> Friday),
> > >> like
> > >> > > >>> let's have a low quality development branch, where we will
> > >> progress,
> > >> > > >>> and be creative, and let's have someone to produce reliable
> > >> branches
> > >> > > >>> from these development branches. For people in a role of
> support
> > >> > > >>> engineers it's hard. That's another reason why I prefer (2) or
> > (3)
> > >> to
> > >> > > >>> (1).
> > >> > > >>>
> > >> > > >>> BTW, here is start of the error log in our 2.1.1 installation.
> > One
> > >> > can
> > >> > > >>> start fixing existing problems, if we want a release.
> > >> > > >>>
> > >> > > >>>     45 at
> > >> > >
> > >> >
> > >>
> >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> > >> > > >>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >>>      45 at
> > >> > >
> > >> >
> > >>
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> > >> > > >>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> > > >>>      42 Caused by: java.net.SocketException: Broken pipe
> > >> > > >>>      42 at
> > >> > >
> > >>
> > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
> > >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >>>      42 at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> > >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >>>      42 at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
> > >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >>>      42 at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
> > >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >>>      42 at
> > >> > >
> > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
> > >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >>>      42 at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
> > >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> > > >>>      42 at java.net.SocketOutputStream.socketWrite0(Native
> > Method)
> > >> > > >>> ~[na:1.6.0_27]
> > >> > > >>>      42 at
> > >> > >
> > >>
> > com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
> > >> > > >>> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> > > >>>      42 at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> > >> > > >>> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> > > >>>      32 at
> > >> > > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > >> > > >>> Method) ~[na:1.6.0_27]
> > >> > > >>>      21 at
> > >> > >
> > >> >
> > >>
> >
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
> > >> > > >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> > > >>>      21 at
> > >> > >
> > >> >
> > >>
> >
> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> > >> > > >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> > > >>>      21 at
> > >> > >
> > >> >
> > >>
> >
> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
> > >> > > >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> > > >>>      19 FailedObject: select c from Sessiondata as c where
> > >> > > >>> c.session_id LIKE :session_id [java.lang.String]
> > >> > > >>>      16 java.lang.NullPointerException: null
> > >> > > >>>      12 at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openmeetings.remote.ConferenceService.getRoomsByOrganisationWithoutType(ConferenceService.java:147)
> > >> > > >>> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> > >> > > >>>      10 at
> > >> > > sun.reflect.GeneratedConstructorAccessor283.newInstance(Unknown
> > >> > > >>> Source) ~[na:na]
> > >> > > >>>       4 at
> > >> > >
> > >> >
> > >>
> >
> org.apache.openmeetings.remote.red5.ScopeApplicationAdapter.roomLeaveByScope(ScopeApplicationAdapter.java:564)
> > >> > > >>> [openmeetings-2.1.1-SNAPSHOT.jar:na]
> > >> > > >>>       2 java.lang.Exception: not Authenticated
> > >> > > >>>       2 ERROR 05-28 20:44:56.425 o.a.o.r.WhiteBoardService:408
> > >> > > >>> [NioProcessor-6] - WhiteboardSyncLockObject not found for this
> > >> Client
> > >> > > >>> {}
> > >> > > >>>       2 ERROR 05-28 20:44:56.423 o.a.o.r.WhiteBoardService:408
> > >> > > >>> [NioProcessor-6] - WhiteboardSyncLockObject not found for this
> > >> Client
> > >> > > >>> {}
> > >> > > >>>       2 Caused by:
> > >> > > >>> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The
> > last
> > >> > > >>> packet successfully received from the server was 84 612 291
> > >> > > >>> milliseconds ago.  The last packet sent successfully to the
> > server
> > >> > was
> > >> > > >>> 84 612 291 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 server configured values for client timeouts, or using the
> > >> > > >>> Connector/J connection property 'autoReconnect=true' to avoid
> > this
> > >> > > >>> problem.
> > >> > >
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Sebastian Wagner
> > >> https://twitter.com/#!/dead_lock
> > >> http://www.webbase-design.de
> > >> http://www.wagner-sebastian.com
> > >> seba.wagner@gmail.com
> > >>
> > >
> > >
> > >
> > > --
> > > WBR
> > > Maxim aka solomax
> >
>

Re: [ANNOUNCE] upcoming 2.1.1 release

Posted by Artyom Horuzhenko <ak...@gmail.com>.

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 <al...@gmail.com>

> 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/dataved/
> [3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
>
>
> On Fri, Jun 28, 2013 at 7:17 AM, Maxim Solodovnik <so...@gmail.com>
> wrote:
> > 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.wagner@gmail.com <
> > seba.wagner@gmail.com> wrote:
> >
> >> 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 server configured values for client timeouts, or using the
> >> Connector/J connection property 'autoReconnect=true' to avoid this
> >> problem.
> >>
> >> is basically an issue that exists since the beginning of OpenMeetings,
> from
> >> my experience this is an environmental issue.
> >>
> >> There are a couple of 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 your MySQL config ?
> >>
> >> Thanks,
> >> Sebastian
> >>
> >>
> >>
> >>
> >> 2013/6/27 Maxim Solodovnik <so...@gmail.com>
> >>
> >> > 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" <al...@gmail.com>
> >> > wrote:
> >> >
> >> > > 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 Fedotov @linkedin,
> http://ru.linkedin.com/in/dataved/
> >> > > [3] Join Alexei Fedotov @facebook,
> >> http://www.facebook.com/openmeetings
> >> > >
> >> > >
> >> > > On Thu, Jun 27, 2013 at 11:35 AM, Alexei Fedotov
> >> > > <al...@gmail.com> wrote:
> >> > > > 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 Alexei Fedotov @linkedin,
> >> http://ru.linkedin.com/in/dataved/
> >> > > > [3] Join Alexei Fedotov @facebook,
> >> > http://www.facebook.com/openmeetings
> >> > > >
> >> > > >
> >> > > > On Thu, Jun 27, 2013 at 11:26 AM, Alexei Fedotov
> >> > > > <al...@gmail.com> wrote:
> >> > > >> 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:
> >> > > >>
> >> > > >> FailedObject: select c from Sessiondata as c where c.session_id
> LIKE
> >> > > >> :session_id [java.lang.String]
> >> > > >> at
> >> > >
> >> >
> >>
> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> >> > > >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> > > >> at
> >> > >
> >> >
> >>
> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
> >> > > >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> > > >> at
> >> > >
> >> >
> >>
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
> >> > > >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> > > >> at
> >> > >
> >> >
> >>
> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:754)
> >> > > >>
> >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> > > >> at
> >> > >
> >> >
> >>
> org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723)
> >> > > >>
> >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> > > >> at
> >> > >
> >> >
> >>
> org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:393)
> >> > > >>
> >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> > > >> at
> >> > >
> >> >
> >>
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120)
> >> > > >>
> >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> > > >> at
> >> > >
> >> >
> >>
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> >> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> > > >> at
> >> > >
> >> >
> >>
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> >> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openmeetings.data.basic.SessiondataDao$$EnhancerByCGLIB$$d3b21640.checkSession(<generated>)
> >> > > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openmeetings.servlet.outputhandler.DownloadHandler.service(DownloadHandler.java:96)
> >> > > >> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> >> > > >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >> at
> >> > >
> >> >
> >>
> org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
> >> > > >> [red5.jar:na]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> >> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >> at
> >> > >
> >> >
> >>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> >> > > >> [na:1.6.0_27]
> >> > > >> at
> >> > >
> >> >
> >>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> >> > > >> [na:1.6.0_27]
> >> > > >> at java.lang.Thread.run(Thread.java:679) [na:1.6.0_27]
> >> > > >> Caused by: org.apache.openjpa.persistence.PersistenceException:
> The
> >> > > >> last packet successfully received from the server was 52 524 877
> >> > > >> milliseconds ago.  The last packet sent successfully to the
> server
> >> was
> >> > > >> 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 server configured values for client timeouts, or using the
> >> > > >> Connector/J connection property 'autoReconnect=true' to avoid
> this
> >> > > >> problem.
> >> > > >> at
> >> > >
> org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >>
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.getConnection(JDBCStoreManager.java:240)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:413)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:391)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.jdbc.sql.LogicalUnion$UnionSelect.execute(LogicalUnion.java:427)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:230)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:220)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.open(SelectResultObjectProvider.java:94)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:34)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1251)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1007)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openmeetings.data.basic.SessiondataDao.checkSession(SessiondataDao.java:128)
> >> > > >> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openmeetings.data.basic.SessiondataDao$$FastClassByCGLIB$$8a6617e0.invoke(<generated>)
> >> > > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> >> > > >> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:191)
> >> > > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> >> > > >> at
> >> > >
> >> >
> >>
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> >> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> > > >> at
> >> > >
> >> >
> >>
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> >> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> > > >> at
> >> > >
> >> >
> >>
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)
> >> > > >>
> >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> > > >> ... 23 common frames omitted
> >> > > >> Caused by:
> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
> >> > > >> The last packet successfully received from the server was 52 524
> 877
> >> > > >> milliseconds ago.  The last packet sent successfully to the
> server
> >> was
> >> > > >> 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 server configured values for client timeouts, or using the
> >> > > >> Connector/J connection property 'autoReconnect=true' to avoid
> this
> >> > > >> problem.
> >> > > >> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> >> > > >> Method) ~[na:1.6.0_27]
> >> > > >> at
> >> > >
> >> >
> >>
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> >> > > >> ~[na:1.6.0_27]
> >> > > >> at
> >> > >
> >> >
> >>
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> >> > > >> ~[na:1.6.0_27]
> >> > > >> at
> java.lang.reflect.Constructor.newInstance(Constructor.java:532)
> >> > > >> ~[na:1.6.0_27]
> >> > > >> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
> >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> > > >> at
> >> > >
> >>
> com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
> >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> > > >> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> > > >> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2471)
> >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> > > >> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)
> >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> > > >> at
> com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2728)
> >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> > > >> at
> >> > com.mysql.jdbc.ConnectionImpl.setAutoCommit(ConnectionImpl.java:5075)
> >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
> >> > > >> ~[commons-dbcp-jar-1.4.jar:1.4]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
> >> > > >> ~[commons-dbcp-jar-1.4.jar:1.4]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.setAutoCommit(PoolingDataSource.java:328)
> >> > > >> ~[commons-dbcp-jar-1.4.jar:1.4]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.setAutoCommit(ConfiguringConnectionDecorator.java:117)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.<init>(ConfiguringConnectionDecorator.java:111)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator.decorate(ConfiguringConnectionDecorator.java:93)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.lib.jdbc.DecoratingDataSource.decorate(DecoratingDataSource.java:99)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:88)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connectInternal(JDBCStoreManager.java:982)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> at
> >> > >
> >> >
> >>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:967)
> >> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >> ... 44 common frames omitted
> >> > > >> Caused by: java.net.SocketException: Broken pipe
> >> > > >> at java.net.SocketOutputStream.socketWrite0(Native Method)
> >> > > ~[na:1.6.0_27]
> >> > > >> at
> >> > java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
> >> > > >> ~[na:1.6.0_27]
> >> > > >> at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
> >> > > ~[na:1.6.0_27]
> >> > > >> at
> >> > >
> java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> >> > > >> ~[na:1.6.0_27]
> >> > > >> at
> java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> >> > > >> ~[na:1.6.0_27]
> >> > > >> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3832)
> >> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> > > >> ... 60 common frames omitted
> >> > > >>
> >> > > >>
> >> > > >> --
> >> > > >> 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/dataved/
> >> > > >> [3] Join Alexei Fedotov @facebook,
> >> > http://www.facebook.com/openmeetings
> >> > > >>
> >> > > >>
> >> > > >> On Sat, Jun 1, 2013 at 10:01 PM, Alexei Fedotov
> >> > > >> <al...@gmail.com> wrote:
> >> > > >>> There are two possible options.
> >> > > >>>
> >> > > >>> 1. Test heavily and ship 2.1.1 release.
> >> > > >>> 2. Test heavily and ship 3.0 release instead.
> >> > > >>> 3. Ship 3.0 pre-release without heavy testing.
> >> > > >>>
> >> > > >>> Why should we bother about testing in 2.1.1? Haven't we just
> >> improved
> >> > > >>> a few things? We don't actually know if we have improved things.
> >> Any
> >> > > >>> change have a risk of breaking something.
> >> > > >>>
> >> > > >>> My suggestion is to have testing infrastructure implemented,
> this
> >> > > >>> would help in testing. This will provide feedback. I prefer
> option
> >> > > >>> (2), or (3) because (1) is a waste of heavy testing effort. We
> >> don't
> >> > > >>> have enough resources to test two branches thoroughly.
> >> > > >>>
> >> > > >>> I constantly get suggestions (the last one from you one Friday),
> >> like
> >> > > >>> let's have a low quality development branch, where we will
> >> progress,
> >> > > >>> and be creative, and let's have someone to produce reliable
> >> branches
> >> > > >>> from these development branches. For people in a role of support
> >> > > >>> engineers it's hard. That's another reason why I prefer (2) or
> (3)
> >> to
> >> > > >>> (1).
> >> > > >>>
> >> > > >>> BTW, here is start of the error log in our 2.1.1 installation.
> One
> >> > can
> >> > > >>> start fixing existing problems, if we want a release.
> >> > > >>>
> >> > > >>>     45 at
> >> > >
> >> >
> >>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> >> > > >>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >>>      45 at
> >> > >
> >> >
> >>
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> >> > > >>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> > > >>>      42 Caused by: java.net.SocketException: Broken pipe
> >> > > >>>      42 at
> >> > >
> >>
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
> >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >>>      42 at
> >> > >
> >> >
> >>
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >>>      42 at
> >> > >
> >> >
> >>
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
> >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >>>      42 at
> >> > >
> >> >
> >>
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
> >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >>>      42 at
> >> > >
> org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
> >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >>>      42 at
> >> > >
> >> >
> >>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
> >> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> > > >>>      42 at java.net.SocketOutputStream.socketWrite0(Native
> Method)
> >> > > >>> ~[na:1.6.0_27]
> >> > > >>>      42 at
> >> > >
> >>
> com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
> >> > > >>> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> > > >>>      42 at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> >> > > >>> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> > > >>>      32 at
> >> > > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> >> > > >>> Method) ~[na:1.6.0_27]
> >> > > >>>      21 at
> >> > >
> >> >
> >>
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
> >> > > >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> > > >>>      21 at
> >> > >
> >> >
> >>
> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> >> > > >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> > > >>>      21 at
> >> > >
> >> >
> >>
> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
> >> > > >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> > > >>>      19 FailedObject: select c from Sessiondata as c where
> >> > > >>> c.session_id LIKE :session_id [java.lang.String]
> >> > > >>>      16 java.lang.NullPointerException: null
> >> > > >>>      12 at
> >> > >
> >> >
> >>
> org.apache.openmeetings.remote.ConferenceService.getRoomsByOrganisationWithoutType(ConferenceService.java:147)
> >> > > >>> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> >> > > >>>      10 at
> >> > > sun.reflect.GeneratedConstructorAccessor283.newInstance(Unknown
> >> > > >>> Source) ~[na:na]
> >> > > >>>       4 at
> >> > >
> >> >
> >>
> org.apache.openmeetings.remote.red5.ScopeApplicationAdapter.roomLeaveByScope(ScopeApplicationAdapter.java:564)
> >> > > >>> [openmeetings-2.1.1-SNAPSHOT.jar:na]
> >> > > >>>       2 java.lang.Exception: not Authenticated
> >> > > >>>       2 ERROR 05-28 20:44:56.425 o.a.o.r.WhiteBoardService:408
> >> > > >>> [NioProcessor-6] - WhiteboardSyncLockObject not found for this
> >> Client
> >> > > >>> {}
> >> > > >>>       2 ERROR 05-28 20:44:56.423 o.a.o.r.WhiteBoardService:408
> >> > > >>> [NioProcessor-6] - WhiteboardSyncLockObject not found for this
> >> Client
> >> > > >>> {}
> >> > > >>>       2 Caused by:
> >> > > >>> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The
> last
> >> > > >>> packet successfully received from the server was 84 612 291
> >> > > >>> milliseconds ago.  The last packet sent successfully to the
> server
> >> > was
> >> > > >>> 84 612 291 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 server configured values for client timeouts, or using the
> >> > > >>> Connector/J connection property 'autoReconnect=true' to avoid
> this
> >> > > >>> problem.
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Sebastian Wagner
> >> https://twitter.com/#!/dead_lock
> >> http://www.webbase-design.de
> >> http://www.wagner-sebastian.com
> >> seba.wagner@gmail.com
> >>
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
>

Re: [ANNOUNCE] upcoming 2.1.1 release

Posted by Alexei Fedotov <al...@gmail.com>.

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/dataved/
[3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings


On Fri, Jun 28, 2013 at 7:17 AM, Maxim Solodovnik <so...@gmail.com> wrote:
> 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.wagner@gmail.com <
> seba.wagner@gmail.com> wrote:
>
>> 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 server configured values for client timeouts, or using the
>> Connector/J connection property 'autoReconnect=true' to avoid this
>> problem.
>>
>> is basically an issue that exists since the beginning of OpenMeetings, from
>> my experience this is an environmental issue.
>>
>> There are a couple of 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 your MySQL config ?
>>
>> Thanks,
>> Sebastian
>>
>>
>>
>>
>> 2013/6/27 Maxim Solodovnik <so...@gmail.com>
>>
>> > 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" <al...@gmail.com>
>> > wrote:
>> >
>> > > 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 Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
>> > > [3] Join Alexei Fedotov @facebook,
>> http://www.facebook.com/openmeetings
>> > >
>> > >
>> > > On Thu, Jun 27, 2013 at 11:35 AM, Alexei Fedotov
>> > > <al...@gmail.com> wrote:
>> > > > 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 Alexei Fedotov @linkedin,
>> http://ru.linkedin.com/in/dataved/
>> > > > [3] Join Alexei Fedotov @facebook,
>> > http://www.facebook.com/openmeetings
>> > > >
>> > > >
>> > > > On Thu, Jun 27, 2013 at 11:26 AM, Alexei Fedotov
>> > > > <al...@gmail.com> wrote:
>> > > >> 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:
>> > > >>
>> > > >> FailedObject: select c from Sessiondata as c where c.session_id LIKE
>> > > >> :session_id [java.lang.String]
>> > > >> at
>> > >
>> >
>> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
>> > > >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > > >> at
>> > >
>> >
>> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
>> > > >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > > >> at
>> > >
>> >
>> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
>> > > >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > > >> at
>> > >
>> >
>> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:754)
>> > > >>
>> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > > >> at
>> > >
>> >
>> org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723)
>> > > >>
>> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > > >> at
>> > >
>> >
>> org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:393)
>> > > >>
>> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > > >> at
>> > >
>> >
>> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120)
>> > > >>
>> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > > >> at
>> > >
>> >
>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
>> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > > >> at
>> > >
>> >
>> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
>> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > > >> at
>> > >
>> >
>> org.apache.openmeetings.data.basic.SessiondataDao$$EnhancerByCGLIB$$d3b21640.checkSession(<generated>)
>> > > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
>> > > >> at
>> > >
>> >
>> org.apache.openmeetings.servlet.outputhandler.DownloadHandler.service(DownloadHandler.java:96)
>> > > >> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
>> > > >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
>> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >> at
>> > >
>> >
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >> at
>> > >
>> >
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >> at
>> > >
>> >
>> org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
>> > > >> [red5.jar:na]
>> > > >> at
>> > >
>> >
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >> at
>> > >
>> >
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >> at
>> > >
>> >
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >> at
>> > >
>> >
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >> at
>> > >
>> >
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >> at
>> > >
>> >
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >> at
>> > >
>> >
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >> at
>> > >
>> >
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >> at
>> > >
>> >
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >> at
>> > >
>> >
>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >> at
>> > >
>> >
>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >> at
>> > >
>> >
>> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
>> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >> at
>> > >
>> >
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
>> > > >> [na:1.6.0_27]
>> > > >> at
>> > >
>> >
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> > > >> [na:1.6.0_27]
>> > > >> at java.lang.Thread.run(Thread.java:679) [na:1.6.0_27]
>> > > >> Caused by: org.apache.openjpa.persistence.PersistenceException: The
>> > > >> last packet successfully received from the server was 52 524 877
>> > > >> milliseconds ago.  The last packet sent successfully to the server
>> was
>> > > >> 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 server configured values for client timeouts, or using the
>> > > >> Connector/J connection property 'autoReconnect=true' to avoid this
>> > > >> problem.
>> > > >> at
>> > > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.getConnection(JDBCStoreManager.java:240)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:413)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:391)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.jdbc.sql.LogicalUnion$UnionSelect.execute(LogicalUnion.java:427)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > > org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:230)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > > org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:220)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.open(SelectResultObjectProvider.java:94)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:34)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1251)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1007)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openmeetings.data.basic.SessiondataDao.checkSession(SessiondataDao.java:128)
>> > > >> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
>> > > >> at
>> > >
>> >
>> org.apache.openmeetings.data.basic.SessiondataDao$$FastClassByCGLIB$$8a6617e0.invoke(<generated>)
>> > > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
>> > > >> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:191)
>> > > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
>> > > >> at
>> > >
>> >
>> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
>> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > > >> at
>> > >
>> >
>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
>> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > > >> at
>> > >
>> >
>> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)
>> > > >>
>> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > > >> ... 23 common frames omitted
>> > > >> Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
>> > > >> The last packet successfully received from the server was 52 524 877
>> > > >> milliseconds ago.  The last packet sent successfully to the server
>> was
>> > > >> 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 server configured values for client timeouts, or using the
>> > > >> Connector/J connection property 'autoReconnect=true' to avoid this
>> > > >> problem.
>> > > >> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> > > >> Method) ~[na:1.6.0_27]
>> > > >> at
>> > >
>> >
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>> > > >> ~[na:1.6.0_27]
>> > > >> at
>> > >
>> >
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>> > > >> ~[na:1.6.0_27]
>> > > >> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
>> > > >> ~[na:1.6.0_27]
>> > > >> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
>> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> > > >> at
>> > >
>> com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
>> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> > > >> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
>> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> > > >> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2471)
>> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> > > >> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)
>> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> > > >> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2728)
>> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> > > >> at
>> > com.mysql.jdbc.ConnectionImpl.setAutoCommit(ConnectionImpl.java:5075)
>> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> > > >> at
>> > >
>> >
>> org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
>> > > >> ~[commons-dbcp-jar-1.4.jar:1.4]
>> > > >> at
>> > >
>> >
>> org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
>> > > >> ~[commons-dbcp-jar-1.4.jar:1.4]
>> > > >> at
>> > >
>> >
>> org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.setAutoCommit(PoolingDataSource.java:328)
>> > > >> ~[commons-dbcp-jar-1.4.jar:1.4]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.setAutoCommit(ConfiguringConnectionDecorator.java:117)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.<init>(ConfiguringConnectionDecorator.java:111)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator.decorate(ConfiguringConnectionDecorator.java:93)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.lib.jdbc.DecoratingDataSource.decorate(DecoratingDataSource.java:99)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:88)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connectInternal(JDBCStoreManager.java:982)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> at
>> > >
>> >
>> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:967)
>> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >> ... 44 common frames omitted
>> > > >> Caused by: java.net.SocketException: Broken pipe
>> > > >> at java.net.SocketOutputStream.socketWrite0(Native Method)
>> > > ~[na:1.6.0_27]
>> > > >> at
>> > java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
>> > > >> ~[na:1.6.0_27]
>> > > >> at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
>> > > ~[na:1.6.0_27]
>> > > >> at
>> > > java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
>> > > >> ~[na:1.6.0_27]
>> > > >> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
>> > > >> ~[na:1.6.0_27]
>> > > >> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3832)
>> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> > > >> ... 60 common frames omitted
>> > > >>
>> > > >>
>> > > >> --
>> > > >> 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/dataved/
>> > > >> [3] Join Alexei Fedotov @facebook,
>> > http://www.facebook.com/openmeetings
>> > > >>
>> > > >>
>> > > >> On Sat, Jun 1, 2013 at 10:01 PM, Alexei Fedotov
>> > > >> <al...@gmail.com> wrote:
>> > > >>> There are two possible options.
>> > > >>>
>> > > >>> 1. Test heavily and ship 2.1.1 release.
>> > > >>> 2. Test heavily and ship 3.0 release instead.
>> > > >>> 3. Ship 3.0 pre-release without heavy testing.
>> > > >>>
>> > > >>> Why should we bother about testing in 2.1.1? Haven't we just
>> improved
>> > > >>> a few things? We don't actually know if we have improved things.
>> Any
>> > > >>> change have a risk of breaking something.
>> > > >>>
>> > > >>> My suggestion is to have testing infrastructure implemented, this
>> > > >>> would help in testing. This will provide feedback. I prefer option
>> > > >>> (2), or (3) because (1) is a waste of heavy testing effort. We
>> don't
>> > > >>> have enough resources to test two branches thoroughly.
>> > > >>>
>> > > >>> I constantly get suggestions (the last one from you one Friday),
>> like
>> > > >>> let's have a low quality development branch, where we will
>> progress,
>> > > >>> and be creative, and let's have someone to produce reliable
>> branches
>> > > >>> from these development branches. For people in a role of support
>> > > >>> engineers it's hard. That's another reason why I prefer (2) or (3)
>> to
>> > > >>> (1).
>> > > >>>
>> > > >>> BTW, here is start of the error log in our 2.1.1 installation. One
>> > can
>> > > >>> start fixing existing problems, if we want a release.
>> > > >>>
>> > > >>>     45 at
>> > >
>> >
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>> > > >>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >>>      45 at
>> > >
>> >
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>> > > >>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > > >>>      42 Caused by: java.net.SocketException: Broken pipe
>> > > >>>      42 at
>> > >
>> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
>> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >>>      42 at
>> > >
>> >
>> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
>> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >>>      42 at
>> > >
>> >
>> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
>> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >>>      42 at
>> > >
>> >
>> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
>> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >>>      42 at
>> > > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
>> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >>>      42 at
>> > >
>> >
>> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
>> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > > >>>      42 at java.net.SocketOutputStream.socketWrite0(Native Method)
>> > > >>> ~[na:1.6.0_27]
>> > > >>>      42 at
>> > >
>> com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
>> > > >>> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> > > >>>      42 at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
>> > > >>> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> > > >>>      32 at
>> > > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> > > >>> Method) ~[na:1.6.0_27]
>> > > >>>      21 at
>> > >
>> >
>> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
>> > > >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > > >>>      21 at
>> > >
>> >
>> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
>> > > >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > > >>>      21 at
>> > >
>> >
>> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
>> > > >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > > >>>      19 FailedObject: select c from Sessiondata as c where
>> > > >>> c.session_id LIKE :session_id [java.lang.String]
>> > > >>>      16 java.lang.NullPointerException: null
>> > > >>>      12 at
>> > >
>> >
>> org.apache.openmeetings.remote.ConferenceService.getRoomsByOrganisationWithoutType(ConferenceService.java:147)
>> > > >>> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
>> > > >>>      10 at
>> > > sun.reflect.GeneratedConstructorAccessor283.newInstance(Unknown
>> > > >>> Source) ~[na:na]
>> > > >>>       4 at
>> > >
>> >
>> org.apache.openmeetings.remote.red5.ScopeApplicationAdapter.roomLeaveByScope(ScopeApplicationAdapter.java:564)
>> > > >>> [openmeetings-2.1.1-SNAPSHOT.jar:na]
>> > > >>>       2 java.lang.Exception: not Authenticated
>> > > >>>       2 ERROR 05-28 20:44:56.425 o.a.o.r.WhiteBoardService:408
>> > > >>> [NioProcessor-6] - WhiteboardSyncLockObject not found for this
>> Client
>> > > >>> {}
>> > > >>>       2 ERROR 05-28 20:44:56.423 o.a.o.r.WhiteBoardService:408
>> > > >>> [NioProcessor-6] - WhiteboardSyncLockObject not found for this
>> Client
>> > > >>> {}
>> > > >>>       2 Caused by:
>> > > >>> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last
>> > > >>> packet successfully received from the server was 84 612 291
>> > > >>> milliseconds ago.  The last packet sent successfully to the server
>> > was
>> > > >>> 84 612 291 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 server configured values for client timeouts, or using the
>> > > >>> Connector/J connection property 'autoReconnect=true' to avoid this
>> > > >>> problem.
>> > >
>> >
>>
>>
>>
>> --
>> Sebastian Wagner
>> https://twitter.com/#!/dead_lock
>> http://www.webbase-design.de
>> http://www.wagner-sebastian.com
>> seba.wagner@gmail.com
>>
>
>
>
> --
> WBR
> Maxim aka solomax

Re: [ANNOUNCE] upcoming 2.1.1 release

Posted by Maxim Solodovnik <so...@gmail.com>.

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.wagner@gmail.com <
seba.wagner@gmail.com> wrote:

> 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 server configured values for client timeouts, or using the
> Connector/J connection property 'autoReconnect=true' to avoid this
> problem.
>
> is basically an issue that exists since the beginning of OpenMeetings, from
> my experience this is an environmental issue.
>
> There are a couple of 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 your MySQL config ?
>
> Thanks,
> Sebastian
>
>
>
>
> 2013/6/27 Maxim Solodovnik <so...@gmail.com>
>
> > 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" <al...@gmail.com>
> > wrote:
> >
> > > 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 Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
> > > [3] Join Alexei Fedotov @facebook,
> http://www.facebook.com/openmeetings
> > >
> > >
> > > On Thu, Jun 27, 2013 at 11:35 AM, Alexei Fedotov
> > > <al...@gmail.com> wrote:
> > > > 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 Alexei Fedotov @linkedin,
> http://ru.linkedin.com/in/dataved/
> > > > [3] Join Alexei Fedotov @facebook,
> > http://www.facebook.com/openmeetings
> > > >
> > > >
> > > > On Thu, Jun 27, 2013 at 11:26 AM, Alexei Fedotov
> > > > <al...@gmail.com> wrote:
> > > >> 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:
> > > >>
> > > >> FailedObject: select c from Sessiondata as c where c.session_id LIKE
> > > >> :session_id [java.lang.String]
> > > >> at
> > >
> >
> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> > > >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> at
> > >
> >
> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
> > > >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> at
> > >
> >
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
> > > >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> at
> > >
> >
> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:754)
> > > >>
> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> at
> > >
> >
> org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723)
> > > >>
> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> at
> > >
> >
> org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:393)
> > > >>
> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> at
> > >
> >
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120)
> > > >>
> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> at
> > >
> >
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> at
> > >
> >
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> at
> > >
> >
> org.apache.openmeetings.data.basic.SessiondataDao$$EnhancerByCGLIB$$d3b21640.checkSession(<generated>)
> > > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> > > >> at
> > >
> >
> org.apache.openmeetings.servlet.outputhandler.DownloadHandler.service(DownloadHandler.java:96)
> > > >> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> > > >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> at
> > >
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> at
> > >
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> at
> > >
> >
> org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
> > > >> [red5.jar:na]
> > > >> at
> > >
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> at
> > >
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> at
> > >
> >
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> at
> > >
> >
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> at
> > >
> >
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> at
> > >
> >
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> at
> > >
> >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> at
> > >
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> at
> > >
> >
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> at
> > >
> >
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> at
> > >
> >
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> at
> > >
> >
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> > > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >> at
> > >
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> > > >> [na:1.6.0_27]
> > > >> at
> > >
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > > >> [na:1.6.0_27]
> > > >> at java.lang.Thread.run(Thread.java:679) [na:1.6.0_27]
> > > >> Caused by: org.apache.openjpa.persistence.PersistenceException: The
> > > >> last packet successfully received from the server was 52 524 877
> > > >> milliseconds ago.  The last packet sent successfully to the server
> was
> > > >> 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 server configured values for client timeouts, or using the
> > > >> Connector/J connection property 'autoReconnect=true' to avoid this
> > > >> problem.
> > > >> at
> > > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.getConnection(JDBCStoreManager.java:240)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:413)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:391)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.jdbc.sql.LogicalUnion$UnionSelect.execute(LogicalUnion.java:427)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > > org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:230)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > > org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:220)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.open(SelectResultObjectProvider.java:94)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:34)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1251)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1007)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openmeetings.data.basic.SessiondataDao.checkSession(SessiondataDao.java:128)
> > > >> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> > > >> at
> > >
> >
> org.apache.openmeetings.data.basic.SessiondataDao$$FastClassByCGLIB$$8a6617e0.invoke(<generated>)
> > > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> > > >> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:191)
> > > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> > > >> at
> > >
> >
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> at
> > >
> >
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> > > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> at
> > >
> >
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)
> > > >>
> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >> ... 23 common frames omitted
> > > >> Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
> > > >> The last packet successfully received from the server was 52 524 877
> > > >> milliseconds ago.  The last packet sent successfully to the server
> was
> > > >> 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 server configured values for client timeouts, or using the
> > > >> Connector/J connection property 'autoReconnect=true' to avoid this
> > > >> problem.
> > > >> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > > >> Method) ~[na:1.6.0_27]
> > > >> at
> > >
> >
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> > > >> ~[na:1.6.0_27]
> > > >> at
> > >
> >
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> > > >> ~[na:1.6.0_27]
> > > >> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
> > > >> ~[na:1.6.0_27]
> > > >> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> at
> > >
> com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2471)
> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)
> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2728)
> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> at
> > com.mysql.jdbc.ConnectionImpl.setAutoCommit(ConnectionImpl.java:5075)
> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> at
> > >
> >
> org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
> > > >> ~[commons-dbcp-jar-1.4.jar:1.4]
> > > >> at
> > >
> >
> org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
> > > >> ~[commons-dbcp-jar-1.4.jar:1.4]
> > > >> at
> > >
> >
> org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.setAutoCommit(PoolingDataSource.java:328)
> > > >> ~[commons-dbcp-jar-1.4.jar:1.4]
> > > >> at
> > >
> >
> org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.setAutoCommit(ConfiguringConnectionDecorator.java:117)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.<init>(ConfiguringConnectionDecorator.java:111)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator.decorate(ConfiguringConnectionDecorator.java:93)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.lib.jdbc.DecoratingDataSource.decorate(DecoratingDataSource.java:99)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:88)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connectInternal(JDBCStoreManager.java:982)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> at
> > >
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:967)
> > > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >> ... 44 common frames omitted
> > > >> Caused by: java.net.SocketException: Broken pipe
> > > >> at java.net.SocketOutputStream.socketWrite0(Native Method)
> > > ~[na:1.6.0_27]
> > > >> at
> > java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
> > > >> ~[na:1.6.0_27]
> > > >> at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
> > > ~[na:1.6.0_27]
> > > >> at
> > > java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> > > >> ~[na:1.6.0_27]
> > > >> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> > > >> ~[na:1.6.0_27]
> > > >> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3832)
> > > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >> ... 60 common frames omitted
> > > >>
> > > >>
> > > >> --
> > > >> 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/dataved/
> > > >> [3] Join Alexei Fedotov @facebook,
> > http://www.facebook.com/openmeetings
> > > >>
> > > >>
> > > >> On Sat, Jun 1, 2013 at 10:01 PM, Alexei Fedotov
> > > >> <al...@gmail.com> wrote:
> > > >>> There are two possible options.
> > > >>>
> > > >>> 1. Test heavily and ship 2.1.1 release.
> > > >>> 2. Test heavily and ship 3.0 release instead.
> > > >>> 3. Ship 3.0 pre-release without heavy testing.
> > > >>>
> > > >>> Why should we bother about testing in 2.1.1? Haven't we just
> improved
> > > >>> a few things? We don't actually know if we have improved things.
> Any
> > > >>> change have a risk of breaking something.
> > > >>>
> > > >>> My suggestion is to have testing infrastructure implemented, this
> > > >>> would help in testing. This will provide feedback. I prefer option
> > > >>> (2), or (3) because (1) is a waste of heavy testing effort. We
> don't
> > > >>> have enough resources to test two branches thoroughly.
> > > >>>
> > > >>> I constantly get suggestions (the last one from you one Friday),
> like
> > > >>> let's have a low quality development branch, where we will
> progress,
> > > >>> and be creative, and let's have someone to produce reliable
> branches
> > > >>> from these development branches. For people in a role of support
> > > >>> engineers it's hard. That's another reason why I prefer (2) or (3)
> to
> > > >>> (1).
> > > >>>
> > > >>> BTW, here is start of the error log in our 2.1.1 installation. One
> > can
> > > >>> start fixing existing problems, if we want a release.
> > > >>>
> > > >>>     45 at
> > >
> >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> > > >>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >>>      45 at
> > >
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> > > >>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >>>      42 Caused by: java.net.SocketException: Broken pipe
> > > >>>      42 at
> > >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >>>      42 at
> > >
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >>>      42 at
> > >
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >>>      42 at
> > >
> >
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >>>      42 at
> > > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >>>      42 at
> > >
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
> > > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >>>      42 at java.net.SocketOutputStream.socketWrite0(Native Method)
> > > >>> ~[na:1.6.0_27]
> > > >>>      42 at
> > >
> com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
> > > >>> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >>>      42 at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> > > >>> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >>>      32 at
> > > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > > >>> Method) ~[na:1.6.0_27]
> > > >>>      21 at
> > >
> >
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
> > > >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >>>      21 at
> > >
> >
> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> > > >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >>>      21 at
> > >
> >
> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
> > > >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >>>      19 FailedObject: select c from Sessiondata as c where
> > > >>> c.session_id LIKE :session_id [java.lang.String]
> > > >>>      16 java.lang.NullPointerException: null
> > > >>>      12 at
> > >
> >
> org.apache.openmeetings.remote.ConferenceService.getRoomsByOrganisationWithoutType(ConferenceService.java:147)
> > > >>> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> > > >>>      10 at
> > > sun.reflect.GeneratedConstructorAccessor283.newInstance(Unknown
> > > >>> Source) ~[na:na]
> > > >>>       4 at
> > >
> >
> org.apache.openmeetings.remote.red5.ScopeApplicationAdapter.roomLeaveByScope(ScopeApplicationAdapter.java:564)
> > > >>> [openmeetings-2.1.1-SNAPSHOT.jar:na]
> > > >>>       2 java.lang.Exception: not Authenticated
> > > >>>       2 ERROR 05-28 20:44:56.425 o.a.o.r.WhiteBoardService:408
> > > >>> [NioProcessor-6] - WhiteboardSyncLockObject not found for this
> Client
> > > >>> {}
> > > >>>       2 ERROR 05-28 20:44:56.423 o.a.o.r.WhiteBoardService:408
> > > >>> [NioProcessor-6] - WhiteboardSyncLockObject not found for this
> Client
> > > >>> {}
> > > >>>       2 Caused by:
> > > >>> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last
> > > >>> packet successfully received from the server was 84 612 291
> > > >>> milliseconds ago.  The last packet sent successfully to the server
> > was
> > > >>> 84 612 291 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 server configured values for client timeouts, or using the
> > > >>> Connector/J connection property 'autoReconnect=true' to avoid this
> > > >>> problem.
> > >
> >
>
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>



-- 
WBR
Maxim aka solomax

Re: [ANNOUNCE] upcoming 2.1.1 release

Posted by "seba.wagner@gmail.com" <se...@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 server configured values for client timeouts, or using the
Connector/J connection property 'autoReconnect=true' to avoid this
problem.

is basically an issue that exists since the beginning of OpenMeetings, from
my experience this is an environmental issue.

There are a couple of 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 your MySQL config ?

Thanks,
Sebastian




2013/6/27 Maxim Solodovnik <so...@gmail.com>

> 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" <al...@gmail.com>
> wrote:
>
> > 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 Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
> > [3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
> >
> >
> > On Thu, Jun 27, 2013 at 11:35 AM, Alexei Fedotov
> > <al...@gmail.com> wrote:
> > > 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 Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
> > > [3] Join Alexei Fedotov @facebook,
> http://www.facebook.com/openmeetings
> > >
> > >
> > > On Thu, Jun 27, 2013 at 11:26 AM, Alexei Fedotov
> > > <al...@gmail.com> wrote:
> > >> 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:
> > >>
> > >> FailedObject: select c from Sessiondata as c where c.session_id LIKE
> > >> :session_id [java.lang.String]
> > >> at
> >
> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> > >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> at
> >
> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
> > >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> at
> >
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
> > >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> at
> >
> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:754)
> > >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> at
> >
> org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723)
> > >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> at
> >
> org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:393)
> > >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> at
> >
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120)
> > >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> at
> >
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> at
> >
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> at
> >
> org.apache.openmeetings.data.basic.SessiondataDao$$EnhancerByCGLIB$$d3b21640.checkSession(<generated>)
> > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> > >> at
> >
> org.apache.openmeetings.servlet.outputhandler.DownloadHandler.service(DownloadHandler.java:96)
> > >> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> > >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> at
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> at
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> at
> >
> org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
> > >> [red5.jar:na]
> > >> at
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> at
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> at
> >
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> at
> >
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> at
> >
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> at
> >
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> at
> >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> at
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> at
> >
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> at
> >
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> at
> >
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> at
> >
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> > >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >> at
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> > >> [na:1.6.0_27]
> > >> at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > >> [na:1.6.0_27]
> > >> at java.lang.Thread.run(Thread.java:679) [na:1.6.0_27]
> > >> Caused by: org.apache.openjpa.persistence.PersistenceException: The
> > >> last packet successfully received from the server was 52 524 877
> > >> milliseconds ago.  The last packet sent successfully to the server was
> > >> 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 server configured values for client timeouts, or using the
> > >> Connector/J connection property 'autoReconnect=true' to avoid this
> > >> problem.
> > >> at
> > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.getConnection(JDBCStoreManager.java:240)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:413)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:391)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.jdbc.sql.LogicalUnion$UnionSelect.execute(LogicalUnion.java:427)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> > org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:230)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> > org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:220)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.open(SelectResultObjectProvider.java:94)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:34)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1251)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1007)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openmeetings.data.basic.SessiondataDao.checkSession(SessiondataDao.java:128)
> > >> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> > >> at
> >
> org.apache.openmeetings.data.basic.SessiondataDao$$FastClassByCGLIB$$8a6617e0.invoke(<generated>)
> > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> > >> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:191)
> > >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> > >> at
> >
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> at
> >
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> > >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> at
> >
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)
> > >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >> ... 23 common frames omitted
> > >> Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
> > >> The last packet successfully received from the server was 52 524 877
> > >> milliseconds ago.  The last packet sent successfully to the server was
> > >> 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 server configured values for client timeouts, or using the
> > >> Connector/J connection property 'autoReconnect=true' to avoid this
> > >> problem.
> > >> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > >> Method) ~[na:1.6.0_27]
> > >> at
> >
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> > >> ~[na:1.6.0_27]
> > >> at
> >
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> > >> ~[na:1.6.0_27]
> > >> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
> > >> ~[na:1.6.0_27]
> > >> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
> > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> at
> > com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
> > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2471)
> > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)
> > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2728)
> > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> at
> com.mysql.jdbc.ConnectionImpl.setAutoCommit(ConnectionImpl.java:5075)
> > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> at
> >
> org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
> > >> ~[commons-dbcp-jar-1.4.jar:1.4]
> > >> at
> >
> org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
> > >> ~[commons-dbcp-jar-1.4.jar:1.4]
> > >> at
> >
> org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.setAutoCommit(PoolingDataSource.java:328)
> > >> ~[commons-dbcp-jar-1.4.jar:1.4]
> > >> at
> >
> org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.setAutoCommit(ConfiguringConnectionDecorator.java:117)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.<init>(ConfiguringConnectionDecorator.java:111)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator.decorate(ConfiguringConnectionDecorator.java:93)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.lib.jdbc.DecoratingDataSource.decorate(DecoratingDataSource.java:99)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:88)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connectInternal(JDBCStoreManager.java:982)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> at
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:967)
> > >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >> ... 44 common frames omitted
> > >> Caused by: java.net.SocketException: Broken pipe
> > >> at java.net.SocketOutputStream.socketWrite0(Native Method)
> > ~[na:1.6.0_27]
> > >> at
> java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
> > >> ~[na:1.6.0_27]
> > >> at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
> > ~[na:1.6.0_27]
> > >> at
> > java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> > >> ~[na:1.6.0_27]
> > >> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> > >> ~[na:1.6.0_27]
> > >> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3832)
> > >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >> ... 60 common frames omitted
> > >>
> > >>
> > >> --
> > >> 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/dataved/
> > >> [3] Join Alexei Fedotov @facebook,
> http://www.facebook.com/openmeetings
> > >>
> > >>
> > >> On Sat, Jun 1, 2013 at 10:01 PM, Alexei Fedotov
> > >> <al...@gmail.com> wrote:
> > >>> There are two possible options.
> > >>>
> > >>> 1. Test heavily and ship 2.1.1 release.
> > >>> 2. Test heavily and ship 3.0 release instead.
> > >>> 3. Ship 3.0 pre-release without heavy testing.
> > >>>
> > >>> Why should we bother about testing in 2.1.1? Haven't we just improved
> > >>> a few things? We don't actually know if we have improved things. Any
> > >>> change have a risk of breaking something.
> > >>>
> > >>> My suggestion is to have testing infrastructure implemented, this
> > >>> would help in testing. This will provide feedback. I prefer option
> > >>> (2), or (3) because (1) is a waste of heavy testing effort. We don't
> > >>> have enough resources to test two branches thoroughly.
> > >>>
> > >>> I constantly get suggestions (the last one from you one Friday), like
> > >>> let's have a low quality development branch, where we will progress,
> > >>> and be creative, and let's have someone to produce reliable branches
> > >>> from these development branches. For people in a role of support
> > >>> engineers it's hard. That's another reason why I prefer (2) or (3) to
> > >>> (1).
> > >>>
> > >>> BTW, here is start of the error log in our 2.1.1 installation. One
> can
> > >>> start fixing existing problems, if we want a release.
> > >>>
> > >>>     45 at
> >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> > >>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >>>      45 at
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> > >>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >>>      42 Caused by: java.net.SocketException: Broken pipe
> > >>>      42 at
> > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
> > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >>>      42 at
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >>>      42 at
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
> > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >>>      42 at
> >
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
> > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >>>      42 at
> > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
> > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >>>      42 at
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
> > >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >>>      42 at java.net.SocketOutputStream.socketWrite0(Native Method)
> > >>> ~[na:1.6.0_27]
> > >>>      42 at
> > com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
> > >>> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >>>      42 at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> > >>> ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >>>      32 at
> > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > >>> Method) ~[na:1.6.0_27]
> > >>>      21 at
> >
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
> > >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >>>      21 at
> >
> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> > >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >>>      21 at
> >
> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
> > >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >>>      19 FailedObject: select c from Sessiondata as c where
> > >>> c.session_id LIKE :session_id [java.lang.String]
> > >>>      16 java.lang.NullPointerException: null
> > >>>      12 at
> >
> org.apache.openmeetings.remote.ConferenceService.getRoomsByOrganisationWithoutType(ConferenceService.java:147)
> > >>> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> > >>>      10 at
> > sun.reflect.GeneratedConstructorAccessor283.newInstance(Unknown
> > >>> Source) ~[na:na]
> > >>>       4 at
> >
> org.apache.openmeetings.remote.red5.ScopeApplicationAdapter.roomLeaveByScope(ScopeApplicationAdapter.java:564)
> > >>> [openmeetings-2.1.1-SNAPSHOT.jar:na]
> > >>>       2 java.lang.Exception: not Authenticated
> > >>>       2 ERROR 05-28 20:44:56.425 o.a.o.r.WhiteBoardService:408
> > >>> [NioProcessor-6] - WhiteboardSyncLockObject not found for this Client
> > >>> {}
> > >>>       2 ERROR 05-28 20:44:56.423 o.a.o.r.WhiteBoardService:408
> > >>> [NioProcessor-6] - WhiteboardSyncLockObject not found for this Client
> > >>> {}
> > >>>       2 Caused by:
> > >>> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last
> > >>> packet successfully received from the server was 84 612 291
> > >>> milliseconds ago.  The last packet sent successfully to the server
> was
> > >>> 84 612 291 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 server configured values for client timeouts, or using the
> > >>> Connector/J connection property 'autoReconnect=true' to avoid this
> > >>> problem.
> >
>



-- 
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com

Re: [ANNOUNCE] upcoming 2.1.1 release

Posted by Maxim Solodovnik <so...@gmail.com>.

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" <al...@gmail.com> wrote:

> 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 Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
> [3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
>
>
> On Thu, Jun 27, 2013 at 11:35 AM, Alexei Fedotov
> <al...@gmail.com> wrote:
> > 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 Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
> > [3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
> >
> >
> > On Thu, Jun 27, 2013 at 11:26 AM, Alexei Fedotov
> > <al...@gmail.com> wrote:
> >> 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:
> >>
> >> FailedObject: select c from Sessiondata as c where c.session_id LIKE
> >> :session_id [java.lang.String]
> >> at
> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> at
> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
> >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> at
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
> >> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:754)
> >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723)
> >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> at
> org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:393)
> >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120)
> >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> at
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> at
> org.apache.openmeetings.data.basic.SessiondataDao$$EnhancerByCGLIB$$d3b21640.checkSession(<generated>)
> >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> >> at
> org.apache.openmeetings.servlet.outputhandler.DownloadHandler.service(DownloadHandler.java:96)
> >> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> at
> org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
> >> [red5.jar:na]
> >> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> at
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> >> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> >> [na:1.6.0_27]
> >> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> >> [na:1.6.0_27]
> >> at java.lang.Thread.run(Thread.java:679) [na:1.6.0_27]
> >> Caused by: org.apache.openjpa.persistence.PersistenceException: The
> >> last packet successfully received from the server was 52 524 877
> >> milliseconds ago.  The last packet sent successfully to the server was
> >> 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 server configured values for client timeouts, or using the
> >> Connector/J connection property 'autoReconnect=true' to avoid this
> >> problem.
> >> at
> org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.getConnection(JDBCStoreManager.java:240)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:413)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:391)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.jdbc.sql.LogicalUnion$UnionSelect.execute(LogicalUnion.java:427)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:230)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:220)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.open(SelectResultObjectProvider.java:94)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:34)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1251)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1007)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openmeetings.data.basic.SessiondataDao.checkSession(SessiondataDao.java:128)
> >> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> >> at
> org.apache.openmeetings.data.basic.SessiondataDao$$FastClassByCGLIB$$8a6617e0.invoke(<generated>)
> >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> >> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:191)
> >> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> >> at
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> >> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)
> >> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >> ... 23 common frames omitted
> >> Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
> >> The last packet successfully received from the server was 52 524 877
> >> milliseconds ago.  The last packet sent successfully to the server was
> >> 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 server configured values for client timeouts, or using the
> >> Connector/J connection property 'autoReconnect=true' to avoid this
> >> problem.
> >> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> >> Method) ~[na:1.6.0_27]
> >> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> >> ~[na:1.6.0_27]
> >> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> >> ~[na:1.6.0_27]
> >> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
> >> ~[na:1.6.0_27]
> >> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
> >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> at
> com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
> >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2471)
> >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)
> >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2728)
> >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> at com.mysql.jdbc.ConnectionImpl.setAutoCommit(ConnectionImpl.java:5075)
> >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> at
> org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
> >> ~[commons-dbcp-jar-1.4.jar:1.4]
> >> at
> org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
> >> ~[commons-dbcp-jar-1.4.jar:1.4]
> >> at
> org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.setAutoCommit(PoolingDataSource.java:328)
> >> ~[commons-dbcp-jar-1.4.jar:1.4]
> >> at
> org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.setAutoCommit(ConfiguringConnectionDecorator.java:117)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.<init>(ConfiguringConnectionDecorator.java:111)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator.decorate(ConfiguringConnectionDecorator.java:93)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.lib.jdbc.DecoratingDataSource.decorate(DecoratingDataSource.java:99)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:88)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connectInternal(JDBCStoreManager.java:982)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:967)
> >> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >> ... 44 common frames omitted
> >> Caused by: java.net.SocketException: Broken pipe
> >> at java.net.SocketOutputStream.socketWrite0(Native Method)
> ~[na:1.6.0_27]
> >> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
> >> ~[na:1.6.0_27]
> >> at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
> ~[na:1.6.0_27]
> >> at
> java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> >> ~[na:1.6.0_27]
> >> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> >> ~[na:1.6.0_27]
> >> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3832)
> >> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >> ... 60 common frames omitted
> >>
> >>
> >> --
> >> 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/dataved/
> >> [3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
> >>
> >>
> >> On Sat, Jun 1, 2013 at 10:01 PM, Alexei Fedotov
> >> <al...@gmail.com> wrote:
> >>> There are two possible options.
> >>>
> >>> 1. Test heavily and ship 2.1.1 release.
> >>> 2. Test heavily and ship 3.0 release instead.
> >>> 3. Ship 3.0 pre-release without heavy testing.
> >>>
> >>> Why should we bother about testing in 2.1.1? Haven't we just improved
> >>> a few things? We don't actually know if we have improved things. Any
> >>> change have a risk of breaking something.
> >>>
> >>> My suggestion is to have testing infrastructure implemented, this
> >>> would help in testing. This will provide feedback. I prefer option
> >>> (2), or (3) because (1) is a waste of heavy testing effort. We don't
> >>> have enough resources to test two branches thoroughly.
> >>>
> >>> I constantly get suggestions (the last one from you one Friday), like
> >>> let's have a low quality development branch, where we will progress,
> >>> and be creative, and let's have someone to produce reliable branches
> >>> from these development branches. For people in a role of support
> >>> engineers it's hard. That's another reason why I prefer (2) or (3) to
> >>> (1).
> >>>
> >>> BTW, here is start of the error log in our 2.1.1 installation. One can
> >>> start fixing existing problems, if we want a release.
> >>>
> >>>     45 at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> >>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >>>      45 at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> >>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> >>>      42 Caused by: java.net.SocketException: Broken pipe
> >>>      42 at
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
> >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >>>      42 at
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >>>      42 at
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
> >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >>>      42 at
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
> >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >>>      42 at
> org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
> >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >>>      42 at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
> >>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> >>>      42 at java.net.SocketOutputStream.socketWrite0(Native Method)
> >>> ~[na:1.6.0_27]
> >>>      42 at
> com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
> >>> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >>>      42 at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> >>> ~[mysql-connector-java-jar-5.1.22.jar:na]
> >>>      32 at
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> >>> Method) ~[na:1.6.0_27]
> >>>      21 at
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
> >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >>>      21 at
> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >>>      21 at
> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
> >>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> >>>      19 FailedObject: select c from Sessiondata as c where
> >>> c.session_id LIKE :session_id [java.lang.String]
> >>>      16 java.lang.NullPointerException: null
> >>>      12 at
> org.apache.openmeetings.remote.ConferenceService.getRoomsByOrganisationWithoutType(ConferenceService.java:147)
> >>> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> >>>      10 at
> sun.reflect.GeneratedConstructorAccessor283.newInstance(Unknown
> >>> Source) ~[na:na]
> >>>       4 at
> org.apache.openmeetings.remote.red5.ScopeApplicationAdapter.roomLeaveByScope(ScopeApplicationAdapter.java:564)
> >>> [openmeetings-2.1.1-SNAPSHOT.jar:na]
> >>>       2 java.lang.Exception: not Authenticated
> >>>       2 ERROR 05-28 20:44:56.425 o.a.o.r.WhiteBoardService:408
> >>> [NioProcessor-6] - WhiteboardSyncLockObject not found for this Client
> >>> {}
> >>>       2 ERROR 05-28 20:44:56.423 o.a.o.r.WhiteBoardService:408
> >>> [NioProcessor-6] - WhiteboardSyncLockObject not found for this Client
> >>> {}
> >>>       2 Caused by:
> >>> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last
> >>> packet successfully received from the server was 84 612 291
> >>> milliseconds ago.  The last packet sent successfully to the server was
> >>> 84 612 291 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 server configured values for client timeouts, or using the
> >>> Connector/J connection property 'autoReconnect=true' to avoid this
> >>> problem.
>

Re: [ANNOUNCE] upcoming 2.1.1 release

Posted by Alexei Fedotov <al...@gmail.com>.

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 Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
[3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings


On Thu, Jun 27, 2013 at 11:35 AM, Alexei Fedotov
<al...@gmail.com> wrote:
> 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 Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
> [3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
>
>
> On Thu, Jun 27, 2013 at 11:26 AM, Alexei Fedotov
> <al...@gmail.com> wrote:
>> 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:
>>
>> FailedObject: select c from Sessiondata as c where c.session_id LIKE
>> :session_id [java.lang.String]
>> at org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> at org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:754)
>> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723)
>> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:393)
>> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120)
>> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
>> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
>> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> at org.apache.openmeetings.data.basic.SessiondataDao$$EnhancerByCGLIB$$d3b21640.checkSession(<generated>)
>> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
>> at org.apache.openmeetings.servlet.outputhandler.DownloadHandler.service(DownloadHandler.java:96)
>> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> at org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
>> [red5.jar:na]
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
>> [na:1.6.0_27]
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> [na:1.6.0_27]
>> at java.lang.Thread.run(Thread.java:679) [na:1.6.0_27]
>> Caused by: org.apache.openjpa.persistence.PersistenceException: The
>> last packet successfully received from the server was 52 524 877
>> milliseconds ago.  The last packet sent successfully to the server was
>> 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 server configured values for client timeouts, or using the
>> Connector/J connection property 'autoReconnect=true' to avoid this
>> problem.
>> at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.getConnection(JDBCStoreManager.java:240)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:413)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:391)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.jdbc.sql.LogicalUnion$UnionSelect.execute(LogicalUnion.java:427)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:230)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:220)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.open(SelectResultObjectProvider.java:94)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:34)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1251)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1007)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openmeetings.data.basic.SessiondataDao.checkSession(SessiondataDao.java:128)
>> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
>> at org.apache.openmeetings.data.basic.SessiondataDao$$FastClassByCGLIB$$8a6617e0.invoke(<generated>)
>> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
>> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:191)
>> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
>> at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
>> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
>> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)
>> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> ... 23 common frames omitted
>> Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
>> The last packet successfully received from the server was 52 524 877
>> milliseconds ago.  The last packet sent successfully to the server was
>> 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 server configured values for client timeouts, or using the
>> Connector/J connection property 'autoReconnect=true' to avoid this
>> problem.
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> Method) ~[na:1.6.0_27]
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>> ~[na:1.6.0_27]
>> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>> ~[na:1.6.0_27]
>> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
>> ~[na:1.6.0_27]
>> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
>> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
>> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
>> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2471)
>> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)
>> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2728)
>> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> at com.mysql.jdbc.ConnectionImpl.setAutoCommit(ConnectionImpl.java:5075)
>> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> at org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
>> ~[commons-dbcp-jar-1.4.jar:1.4]
>> at org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
>> ~[commons-dbcp-jar-1.4.jar:1.4]
>> at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.setAutoCommit(PoolingDataSource.java:328)
>> ~[commons-dbcp-jar-1.4.jar:1.4]
>> at org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.setAutoCommit(ConfiguringConnectionDecorator.java:117)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.<init>(ConfiguringConnectionDecorator.java:111)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator.decorate(ConfiguringConnectionDecorator.java:93)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.lib.jdbc.DecoratingDataSource.decorate(DecoratingDataSource.java:99)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:88)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connectInternal(JDBCStoreManager.java:982)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:967)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> ... 44 common frames omitted
>> Caused by: java.net.SocketException: Broken pipe
>> at java.net.SocketOutputStream.socketWrite0(Native Method) ~[na:1.6.0_27]
>> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
>> ~[na:1.6.0_27]
>> at java.net.SocketOutputStream.write(SocketOutputStream.java:153) ~[na:1.6.0_27]
>> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
>> ~[na:1.6.0_27]
>> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
>> ~[na:1.6.0_27]
>> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3832)
>> ~[mysql-connector-java-jar-5.1.22.jar:na]
>> ... 60 common frames omitted
>>
>>
>> --
>> 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/dataved/
>> [3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
>>
>>
>> On Sat, Jun 1, 2013 at 10:01 PM, Alexei Fedotov
>> <al...@gmail.com> wrote:
>>> There are two possible options.
>>>
>>> 1. Test heavily and ship 2.1.1 release.
>>> 2. Test heavily and ship 3.0 release instead.
>>> 3. Ship 3.0 pre-release without heavy testing.
>>>
>>> Why should we bother about testing in 2.1.1? Haven't we just improved
>>> a few things? We don't actually know if we have improved things. Any
>>> change have a risk of breaking something.
>>>
>>> My suggestion is to have testing infrastructure implemented, this
>>> would help in testing. This will provide feedback. I prefer option
>>> (2), or (3) because (1) is a waste of heavy testing effort. We don't
>>> have enough resources to test two branches thoroughly.
>>>
>>> I constantly get suggestions (the last one from you one Friday), like
>>> let's have a low quality development branch, where we will progress,
>>> and be creative, and let's have someone to produce reliable branches
>>> from these development branches. For people in a role of support
>>> engineers it's hard. That's another reason why I prefer (2) or (3) to
>>> (1).
>>>
>>> BTW, here is start of the error log in our 2.1.1 installation. One can
>>> start fixing existing problems, if we want a release.
>>>
>>>     45 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>>>      45 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>>>      42 Caused by: java.net.SocketException: Broken pipe
>>>      42 at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
>>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>>>      42 at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
>>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>>>      42 at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
>>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>>>      42 at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
>>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>>>      42 at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
>>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>>>      42 at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
>>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>>>      42 at java.net.SocketOutputStream.socketWrite0(Native Method)
>>> ~[na:1.6.0_27]
>>>      42 at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
>>> ~[mysql-connector-java-jar-5.1.22.jar:na]
>>>      42 at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
>>> ~[mysql-connector-java-jar-5.1.22.jar:na]
>>>      32 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>>> Method) ~[na:1.6.0_27]
>>>      21 at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
>>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>>>      21 at org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
>>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>>>      21 at org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
>>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>>>      19 FailedObject: select c from Sessiondata as c where
>>> c.session_id LIKE :session_id [java.lang.String]
>>>      16 java.lang.NullPointerException: null
>>>      12 at org.apache.openmeetings.remote.ConferenceService.getRoomsByOrganisationWithoutType(ConferenceService.java:147)
>>> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
>>>      10 at sun.reflect.GeneratedConstructorAccessor283.newInstance(Unknown
>>> Source) ~[na:na]
>>>       4 at org.apache.openmeetings.remote.red5.ScopeApplicationAdapter.roomLeaveByScope(ScopeApplicationAdapter.java:564)
>>> [openmeetings-2.1.1-SNAPSHOT.jar:na]
>>>       2 java.lang.Exception: not Authenticated
>>>       2 ERROR 05-28 20:44:56.425 o.a.o.r.WhiteBoardService:408
>>> [NioProcessor-6] - WhiteboardSyncLockObject not found for this Client
>>> {}
>>>       2 ERROR 05-28 20:44:56.423 o.a.o.r.WhiteBoardService:408
>>> [NioProcessor-6] - WhiteboardSyncLockObject not found for this Client
>>> {}
>>>       2 Caused by:
>>> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last
>>> packet successfully received from the server was 84 612 291
>>> milliseconds ago.  The last packet sent successfully to the server was
>>> 84 612 291 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 server configured values for client timeouts, or using the
>>> Connector/J connection property 'autoReconnect=true' to avoid this
>>> problem.

Re: [ANNOUNCE] upcoming 2.1.1 release

Posted by Alexei Fedotov <al...@gmail.com>.

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 Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
[3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings


On Thu, Jun 27, 2013 at 11:26 AM, Alexei Fedotov
<al...@gmail.com> wrote:
> 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:
>
> FailedObject: select c from Sessiondata as c where c.session_id LIKE
> :session_id [java.lang.String]
> at org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:754)
> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723)
> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:393)
> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120)
> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at org.apache.openmeetings.data.basic.SessiondataDao$$EnhancerByCGLIB$$d3b21640.checkSession(<generated>)
> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> at org.apache.openmeetings.servlet.outputhandler.DownloadHandler.service(DownloadHandler.java:96)
> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> at org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
> [red5.jar:na]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> [na:1.6.0_27]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [na:1.6.0_27]
> at java.lang.Thread.run(Thread.java:679) [na:1.6.0_27]
> Caused by: org.apache.openjpa.persistence.PersistenceException: The
> last packet successfully received from the server was 52 524 877
> milliseconds ago.  The last packet sent successfully to the server was
> 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 server configured values for client timeouts, or using the
> Connector/J connection property 'autoReconnect=true' to avoid this
> problem.
> at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.getConnection(JDBCStoreManager.java:240)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:413)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:391)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.jdbc.sql.LogicalUnion$UnionSelect.execute(LogicalUnion.java:427)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:230)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:220)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.open(SelectResultObjectProvider.java:94)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:34)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1251)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1007)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openmeetings.data.basic.SessiondataDao.checkSession(SessiondataDao.java:128)
> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> at org.apache.openmeetings.data.basic.SessiondataDao$$FastClassByCGLIB$$8a6617e0.invoke(<generated>)
> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:191)
> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]
> at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)
> ~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> ... 23 common frames omitted
> Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
> The last packet successfully received from the server was 52 524 877
> milliseconds ago.  The last packet sent successfully to the server was
> 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 server configured values for client timeouts, or using the
> Connector/J connection property 'autoReconnect=true' to avoid this
> problem.
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) ~[na:1.6.0_27]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> ~[na:1.6.0_27]
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> ~[na:1.6.0_27]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
> ~[na:1.6.0_27]
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
> ~[mysql-connector-java-jar-5.1.22.jar:na]
> at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
> ~[mysql-connector-java-jar-5.1.22.jar:na]
> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> ~[mysql-connector-java-jar-5.1.22.jar:na]
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2471)
> ~[mysql-connector-java-jar-5.1.22.jar:na]
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)
> ~[mysql-connector-java-jar-5.1.22.jar:na]
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2728)
> ~[mysql-connector-java-jar-5.1.22.jar:na]
> at com.mysql.jdbc.ConnectionImpl.setAutoCommit(ConnectionImpl.java:5075)
> ~[mysql-connector-java-jar-5.1.22.jar:na]
> at org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
> ~[commons-dbcp-jar-1.4.jar:1.4]
> at org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
> ~[commons-dbcp-jar-1.4.jar:1.4]
> at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.setAutoCommit(PoolingDataSource.java:328)
> ~[commons-dbcp-jar-1.4.jar:1.4]
> at org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.setAutoCommit(ConfiguringConnectionDecorator.java:117)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.<init>(ConfiguringConnectionDecorator.java:111)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator.decorate(ConfiguringConnectionDecorator.java:93)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.lib.jdbc.DecoratingDataSource.decorate(DecoratingDataSource.java:99)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:88)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connectInternal(JDBCStoreManager.java:982)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:967)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
> ... 44 common frames omitted
> Caused by: java.net.SocketException: Broken pipe
> at java.net.SocketOutputStream.socketWrite0(Native Method) ~[na:1.6.0_27]
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
> ~[na:1.6.0_27]
> at java.net.SocketOutputStream.write(SocketOutputStream.java:153) ~[na:1.6.0_27]
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> ~[na:1.6.0_27]
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> ~[na:1.6.0_27]
> at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3832)
> ~[mysql-connector-java-jar-5.1.22.jar:na]
> ... 60 common frames omitted
>
>
> --
> 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/dataved/
> [3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
>
>
> On Sat, Jun 1, 2013 at 10:01 PM, Alexei Fedotov
> <al...@gmail.com> wrote:
>> There are two possible options.
>>
>> 1. Test heavily and ship 2.1.1 release.
>> 2. Test heavily and ship 3.0 release instead.
>> 3. Ship 3.0 pre-release without heavy testing.
>>
>> Why should we bother about testing in 2.1.1? Haven't we just improved
>> a few things? We don't actually know if we have improved things. Any
>> change have a risk of breaking something.
>>
>> My suggestion is to have testing infrastructure implemented, this
>> would help in testing. This will provide feedback. I prefer option
>> (2), or (3) because (1) is a waste of heavy testing effort. We don't
>> have enough resources to test two branches thoroughly.
>>
>> I constantly get suggestions (the last one from you one Friday), like
>> let's have a low quality development branch, where we will progress,
>> and be creative, and let's have someone to produce reliable branches
>> from these development branches. For people in a role of support
>> engineers it's hard. That's another reason why I prefer (2) or (3) to
>> (1).
>>
>> BTW, here is start of the error log in our 2.1.1 installation. One can
>> start fixing existing problems, if we want a release.
>>
>>     45 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>>      45 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>>      42 Caused by: java.net.SocketException: Broken pipe
>>      42 at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>>      42 at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>>      42 at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>>      42 at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>>      42 at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>>      42 at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
>> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>>      42 at java.net.SocketOutputStream.socketWrite0(Native Method)
>> ~[na:1.6.0_27]
>>      42 at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
>> ~[mysql-connector-java-jar-5.1.22.jar:na]
>>      42 at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
>> ~[mysql-connector-java-jar-5.1.22.jar:na]
>>      32 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> Method) ~[na:1.6.0_27]
>>      21 at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>>      21 at org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>>      21 at org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
>> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>>      19 FailedObject: select c from Sessiondata as c where
>> c.session_id LIKE :session_id [java.lang.String]
>>      16 java.lang.NullPointerException: null
>>      12 at org.apache.openmeetings.remote.ConferenceService.getRoomsByOrganisationWithoutType(ConferenceService.java:147)
>> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
>>      10 at sun.reflect.GeneratedConstructorAccessor283.newInstance(Unknown
>> Source) ~[na:na]
>>       4 at org.apache.openmeetings.remote.red5.ScopeApplicationAdapter.roomLeaveByScope(ScopeApplicationAdapter.java:564)
>> [openmeetings-2.1.1-SNAPSHOT.jar:na]
>>       2 java.lang.Exception: not Authenticated
>>       2 ERROR 05-28 20:44:56.425 o.a.o.r.WhiteBoardService:408
>> [NioProcessor-6] - WhiteboardSyncLockObject not found for this Client
>> {}
>>       2 ERROR 05-28 20:44:56.423 o.a.o.r.WhiteBoardService:408
>> [NioProcessor-6] - WhiteboardSyncLockObject not found for this Client
>> {}
>>       2 Caused by:
>> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last
>> packet successfully received from the server was 84 612 291
>> milliseconds ago.  The last packet sent successfully to the server was
>> 84 612 291 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 server configured values for client timeouts, or using the
>> Connector/J connection property 'autoReconnect=true' to avoid this
>> problem.

Re: [ANNOUNCE] upcoming 2.1.1 release

Posted by Alexei Fedotov <al...@gmail.com>.

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:

FailedObject: select c from Sessiondata as c where c.session_id LIKE
:session_id [java.lang.String]
at org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:754)
~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723)
~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:393)
~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120)
~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.apache.openmeetings.data.basic.SessiondataDao$$EnhancerByCGLIB$$d3b21640.checkSession(<generated>)
~[com.springsource.net.sf.cglib-2.2.0.jar:na]
at org.apache.openmeetings.servlet.outputhandler.DownloadHandler.service(DownloadHandler.java:96)
~[openmeetings-2.1.1-SNAPSHOT.jar:na]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
[tomcat-embed-core-jar-7.0.34.jar:7.0.34]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
[tomcat-embed-core-jar-7.0.34.jar:7.0.34]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
[tomcat-embed-core-jar-7.0.34.jar:7.0.34]
at org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
[red5.jar:na]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
[tomcat-embed-core-jar-7.0.34.jar:7.0.34]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
[tomcat-embed-core-jar-7.0.34.jar:7.0.34]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
[tomcat-embed-core-jar-7.0.34.jar:7.0.34]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
[tomcat-embed-core-jar-7.0.34.jar:7.0.34]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
[tomcat-embed-core-jar-7.0.34.jar:7.0.34]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
[tomcat-embed-core-jar-7.0.34.jar:7.0.34]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
[tomcat-embed-core-jar-7.0.34.jar:7.0.34]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
[tomcat-embed-core-jar-7.0.34.jar:7.0.34]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
[tomcat-embed-core-jar-7.0.34.jar:7.0.34]
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
[tomcat-embed-core-jar-7.0.34.jar:7.0.34]
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
[tomcat-embed-core-jar-7.0.34.jar:7.0.34]
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
[tomcat-embed-core-jar-7.0.34.jar:7.0.34]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
[na:1.6.0_27]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[na:1.6.0_27]
at java.lang.Thread.run(Thread.java:679) [na:1.6.0_27]
Caused by: org.apache.openjpa.persistence.PersistenceException: The
last packet successfully received from the server was 52 524 877
milliseconds ago.  The last packet sent successfully to the server was
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 server configured values for client timeouts, or using the
Connector/J connection property 'autoReconnect=true' to avoid this
problem.
at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.getConnection(JDBCStoreManager.java:240)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:413)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.jdbc.sql.SelectImpl.execute(SelectImpl.java:391)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.jdbc.sql.LogicalUnion$UnionSelect.execute(LogicalUnion.java:427)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:230)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.jdbc.sql.LogicalUnion.execute(LogicalUnion.java:220)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.open(SelectResultObjectProvider.java:94)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:34)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1251)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1007)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:863)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openmeetings.data.basic.SessiondataDao.checkSession(SessiondataDao.java:128)
~[openmeetings-2.1.1-SNAPSHOT.jar:na]
at org.apache.openmeetings.data.basic.SessiondataDao$$FastClassByCGLIB$$8a6617e0.invoke(<generated>)
~[com.springsource.net.sf.cglib-2.2.0.jar:na]
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:191)
~[com.springsource.net.sf.cglib-2.2.0.jar:na]
at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)
~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
... 23 common frames omitted
Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
The last packet successfully received from the server was 52 524 877
milliseconds ago.  The last packet sent successfully to the server was
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 server configured values for client timeouts, or using the
Connector/J connection property 'autoReconnect=true' to avoid this
problem.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method) ~[na:1.6.0_27]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
~[na:1.6.0_27]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
~[na:1.6.0_27]
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
~[na:1.6.0_27]
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
~[mysql-connector-java-jar-5.1.22.jar:na]
at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
~[mysql-connector-java-jar-5.1.22.jar:na]
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
~[mysql-connector-java-jar-5.1.22.jar:na]
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2471)
~[mysql-connector-java-jar-5.1.22.jar:na]
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)
~[mysql-connector-java-jar-5.1.22.jar:na]
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2728)
~[mysql-connector-java-jar-5.1.22.jar:na]
at com.mysql.jdbc.ConnectionImpl.setAutoCommit(ConnectionImpl.java:5075)
~[mysql-connector-java-jar-5.1.22.jar:na]
at org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
~[commons-dbcp-jar-1.4.jar:1.4]
at org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)
~[commons-dbcp-jar-1.4.jar:1.4]
at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.setAutoCommit(PoolingDataSource.java:328)
~[commons-dbcp-jar-1.4.jar:1.4]
at org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.lib.jdbc.DelegatingConnection.setAutoCommit(DelegatingConnection.java:167)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.setAutoCommit(ConfiguringConnectionDecorator.java:117)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.<init>(ConfiguringConnectionDecorator.java:111)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator.decorate(ConfiguringConnectionDecorator.java:93)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.lib.jdbc.DecoratingDataSource.decorate(DecoratingDataSource.java:99)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:88)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connectInternal(JDBCStoreManager.java:982)
~[openjpa-bundle-2.2.1.jar:2.2.1]
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:967)
~[openjpa-bundle-2.2.1.jar:2.2.1]
... 44 common frames omitted
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method) ~[na:1.6.0_27]
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
~[na:1.6.0_27]
at java.net.SocketOutputStream.write(SocketOutputStream.java:153) ~[na:1.6.0_27]
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
~[na:1.6.0_27]
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
~[na:1.6.0_27]
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3832)
~[mysql-connector-java-jar-5.1.22.jar:na]
... 60 common frames omitted

--
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/dataved/
[3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings

On Sat, Jun 1, 2013 at 10:01 PM, Alexei Fedotov
<al...@gmail.com> wrote:
> There are two possible options.
>
> 1. Test heavily and ship 2.1.1 release.
> 2. Test heavily and ship 3.0 release instead.
> 3. Ship 3.0 pre-release without heavy testing.
>
> Why should we bother about testing in 2.1.1? Haven't we just improved
> a few things? We don't actually know if we have improved things. Any
> change have a risk of breaking something.
>
> My suggestion is to have testing infrastructure implemented, this
> would help in testing. This will provide feedback. I prefer option
> (2), or (3) because (1) is a waste of heavy testing effort. We don't
> have enough resources to test two branches thoroughly.
>
> I constantly get suggestions (the last one from you one Friday), like
> let's have a low quality development branch, where we will progress,
> and be creative, and let's have someone to produce reliable branches
> from these development branches. For people in a role of support
> engineers it's hard. That's another reason why I prefer (2) or (3) to
> (1).
>
> BTW, here is start of the error log in our 2.1.1 installation. One can
> start fixing existing problems, if we want a release.
>
>     45 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>      45 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>      42 Caused by: java.net.SocketException: Broken pipe
>      42 at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>      42 at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>      42 at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>      42 at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>      42 at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>      42 at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:971)
> ~[openjpa-bundle-2.2.1.jar:2.2.1]
>      42 at java.net.SocketOutputStream.socketWrite0(Native Method)
> ~[na:1.6.0_27]
>      42 at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
> ~[mysql-connector-java-jar-5.1.22.jar:na]
>      42 at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> ~[mysql-connector-java-jar-5.1.22.jar:na]
>      32 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) ~[na:1.6.0_27]
>      21 at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>      21 at org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>      21 at org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>      19 FailedObject: select c from Sessiondata as c where
> c.session_id LIKE :session_id [java.lang.String]
>      16 java.lang.NullPointerException: null
>      12 at org.apache.openmeetings.remote.ConferenceService.getRoomsByOrganisationWithoutType(ConferenceService.java:147)
> ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
>      10 at sun.reflect.GeneratedConstructorAccessor283.newInstance(Unknown
> Source) ~[na:na]
>       4 at org.apache.openmeetings.remote.red5.ScopeApplicationAdapter.roomLeaveByScope(ScopeApplicationAdapter.java:564)
> [openmeetings-2.1.1-SNAPSHOT.jar:na]
>       2 java.lang.Exception: not Authenticated
>       2 ERROR 05-28 20:44:56.425 o.a.o.r.WhiteBoardService:408
> [NioProcessor-6] - WhiteboardSyncLockObject not found for this Client
> {}
>       2 ERROR 05-28 20:44:56.423 o.a.o.r.WhiteBoardService:408
> [NioProcessor-6] - WhiteboardSyncLockObject not found for this Client
> {}
>       2 Caused by:
> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last
> packet successfully received from the server was 84 612 291
> milliseconds ago.  The last packet sent successfully to the server was
> 84 612 291 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 server configured values for client timeouts, or using the
> Connector/J connection property 'autoReconnect=true' to avoid this
> problem.

Re: [ANNOUNCE] upcoming 2.1.1 release

Posted by Maxim Solodovnik <so...@gmail.com>.

I have scheduled the build
Hopefully will be available in nearest couple of hours


On Fri, Jun 7, 2013 at 12:09 PM, seba.wagner@gmail.com <
seba.wagner@gmail.com> wrote:

> I also have only limited internet access next week.
>
> Given the scope of the release (a x.x.1 release, so no major, nore minor,
> more like a bugfix release) I think it should be okay to give it at least a
> try.
>
> Is there a binary version of 2.1.1 somewhere to download right now?
>
> Sebastian
>
>
> 2013/6/7 Maxim Solodovnik <so...@gmail.com>
>
> > The only places refering to 2.1.0 are
> > downloads.xml and "release notes" first one will be changed in trunk only
> > (to provide link to the latest version)
> > second will be updated during release process.
> >
> > I'm going to pack 2.1.1RC1 tonight
> >
> > Please NOTE I'll be on vacation 2013.06.12-2013.06.23 with none internet
> > connection (or maybe with access to email only)
> >
> >
> > On Fri, Jun 7, 2013 at 3:14 AM, seba.wagner@gmail.com <
> > seba.wagner@gmail.com
> > > wrote:
> >
> > > Hi folks,
> > >
> > > I agree on point no 5 with Maxim:
> > > *auto
> > > reconnect feature stopped to work long ago*
> > > => There was never such a feature. It is also rather complicated, cause
> > > reconnect means that you basically out of sync, and the application has
> > no
> > > idea what has happened in between, so in theory you could have a
> > reconnect
> > > after 2 hours and the entire list of participants, screensharing,
> > > whiteboards, et cetera _everything_ has changed. So the only chance I
> see
> > > to realize a *reconnect* is to actually re-login the user into the room
> > and
> > > load everything from scratch.
> > >
> > > But about this entire discussion:
> > > Why is this discussion in the private list at all?
> > > There is no *privileged* channel to request or discuss features and
> bugs.
> > > Please, lets use the dev list and give everyone that would like to be
> > > involved the chance to at least read what you have to say.
> > > @Alexei: For instance anybody reading the Analytics (or error
> > > infrastructure :)) question now, is missing the context as how this
> email
> > > that you wrote was initiated.
> > >
> > > Thanks,
> > > Sebastian
> > >
> > >
> > > 2013/6/7 Maxim Solodovnik <so...@gmail.com>
> > >
> > > > 1) video codec was switched in 2.1.0, this is bug fix release I'm
> sure
> > we
> > > > shouldn't add major changes. Additionally we will need to use h264 in
> > > > 3.0/3.1 since it is html5 compatible.
> > > >
> > > > 2) this behavior was not changed since 2.0. Please file an issue
> > (better
> > > > with patch) if you feel this need to be changed. (I would add
> > > configuration
> > > > value default_gain with default value == 50)
> > > >
> > > > 3) I'll doublecheck
> > > >
> > > > 4) according to VOTE rules every user voting for release must perform
> > > these
> > > > tests
> > > >
> > > > 5) I would vote for adding NOTE regarding flash version to release
> > notes
> > > of
> > > > 2.1.1 and alert to 3.0 (on room enter). Actually auto reconnect works
> > as
> > > > before .... it is just don't reconnect into room :)
> > > > You can file JIRA issue (better with patch), but to be fair I don't
> > > really
> > > > like such "last minute" changes. The release was announced long time
> > ago
> > > > and I feel we should close this branch and focus on 3.0
> > > >  On Jun 6, 2013 7:23 PM, "Alexei Fedotov" <al...@gmail.com>
> > > > wrote:
> > > >
> > > > > Maxim, I've looked through the changes:
> > > > > https://gist.github.com/leshikus/5720534
> > > > > most of them relate to log improvements, thus harmless.
> > > > >
> > > > > Here are few points on 2.1.1 release:
> > > > >
> > > > > 1. We haven't carefully tested H.264. Our customers use H.263
> because
> > > > > H.264 didn't work well for them. H,254 is a default codec for a new
> > > > > release. Won't this be a problem?
> > > > >
> > > > > 2. There are hardcoded microphone settings for silence level, gain,
> > > > > etc. From the other side I noticed that for the new release
> > microphone
> > > > > sensitivity is low, and one needs to set the sensitivity bar to the
> > > > > maximum every time to get it to normal. Or this can be also related
> > to
> > > > > codec.
> > > > >
> > > > > 3. There are several places which incorrectly refer to "2.1.0" and
> > > > > "2.0". The only place where the release is correct is a build file.
> > > > >
> > > > > 4. Who will volunteer to pass all tests for the new release,
> > > > > xdocs/ManualTesting.xml?
> > > > >
> > > > > 5. Our users believe that reliability is most important part of
> > > > > conferences. The last flash version does not work well, and auto
> > > > > reconnect feature stopped to work long ago. How this can be
> > addressed?
> > > > > Should a flash version check be added (against flash 11.6 and
> 11.7),
> > > > > and auto reconnect fixed?
> > > > >
> > > > > --
> > > > > With best regards / с наилучшими пожеланиями,
> > > > > Alexei Fedotov / Алексей Федотов,
> > > > > http://dataved.ru/
> > > > > +7 916 562 8095
> > > > >
> > > > >
> > > > > On Thu, Jun 6, 2013 at 1:42 PM, Alexei Fedotov <
> > > alexei.fedotov@gmail.com
> > > > >
> > > > > wrote:
> > > > > > Maxim, thanks for the tags!
> > > > > > --
> > > > > > With best regards / с наилучшими пожеланиями,
> > > > > > Alexei Fedotov / Алексей Федотов,
> > > > > > http://dataved.ru/
> > > > > > +7 916 562 8095
> > > > > >
> > > > > >
> > > > > > On Mon, Jun 3, 2013 at 2:28 PM, Maxim Solodovnik <
> > > solomax666@gmail.com
> > > > >
> > > > > wrote:
> > > > > >> I believe ""Release early, release often" assumes we use one
> > branch"
> > > > > can be
> > > > > >> followed with any number of branches :)
> > > > > >>
> > > > > >>>> "It is uncool when users come to support engineers"
> > > > > >> I currently feel I'm the only support engineer :)
> > > > > >>
> > > > > >>>> Don't expect it become easier with html5
> > > > > >> I DO expect!, and things are MUCH easier with HTML5 :)
> > > > > >>
> > > > > >>>> How to get 2.1 code?
> > > > > >> http://svn.apache.org/repos/asf/openmeetings/tags/2.1RC3/
> > > > > >>
> > > > > >>>> How to get 2.1.1 code?
> > > > > >> https://svn.apache.org/repos/asf/openmeetings/branches/2.1/
> > > > > >>
> > > > > >>>> Were all these mentioned fixes ported to 3.0 (taking into
> > account
> > > > how
> > > > > many
> > > > > >> times I get no for particular fix, it would be surprising and
> > great
> > > to
> > > > > get
> > > > > >> yes)?
> > > > > >> I'm not sure what do you mean by "all these mentioned fixes",
> all
> > > > fixes
> > > > > >> made by me are in both branches :)
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> On Mon, Jun 3, 2013 at 5:06 PM, Alexei Fedotov <
> > > > > alexei.fedotov@gmail.com>wrote:
> > > > > >>
> > > > > >>> Just one comment. "Release early, release often" assumes we use
> > one
> > > > > branch,
> > > > > >>> where we fix errors quickly. Having two branches gives us the
> > > > expected
> > > > > >>> result that developers care less about users when develop in
> > their
> > > > > >>> development branch. When something is released, developers
> switch
> > > to
> > > > a
> > > > > new
> > > > > >>> develioment branch and continue being cool and creative.
> > > > > >>>
> > > > > >>> It is uncool when users come to support engineers and they feed
> > > them
> > > > > with
> > > > > >>> tweaks and workarounds. You won't imagine the quirkiness of
> > > > workarounds
> > > > > >>> used to demonstrate a SIP video integration.
> > > > > >>>
> > > > > >>> Everyone wants to fix bugs when they are easy to reproduce.
> Most
> > of
> > > > > them
> > > > > >>> are not due to the fact that openmeetings has a lot of
> unreliable
> > > > > >>> technologies at its base.
> > > > > >>>
> > > > > >>> Don't expect it become easier with html5. Contrary, we will get
> > own
> > > > > >>> problems for each browser. That's why testing infrastructure is
> > > > > important
> > > > > >>> before we start releasing things.
> > > > > >>>
> > > > > >>> 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
> > > > > >>> many times I get no for particular fix, it would be surprising
> > and
> > > > > great to
> > > > > >>> get yes)?
> > > > > >>> 02.06.2013 15:06 пользователь "George Kirkham" <
> > > > gkirkham@co2crc.com.au
> > > > > >
> > > > > >>> написал:
> > > > > >>>
> > > > > >>> > Hi,
> > > > > >>> >
> > > > > >>> > My apologies, I had thought that 2.1.1 had been released.
> > > > > >>> >
> > > > > >>> > It would be 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).
> > > > > >>> >
> > > > > >>> > The main point is to have;
> > > > > >>> >  a) a stable released version for production use. The version
> > > would
> > > > > be
> > > > > >>> > used for production while new features are prepared and fixed
> > in
> > > > the
> > > > > >>> > 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 still
> > applicable).
> > > > > >>> >
> > > > > >>> > b) a development version to which new features are added, bug
> > > fixes
> > > > > for
> > > > > >>> > issues discovered in production.  Full testing should be
> > > performed
> > > > > often,
> > > > > >>> > and at least any time a new feature is added.
> > > > > >>> >
> > > > > >>> > At some point, additional features are put on hold, a full
> > > testing
> > > > > >>> > completed, and then the development version can be released
> to
> > > > > update the
> > > > > >>> > production version, after which the development version is
> > > > > incremented
> > > > > >>> and
> > > > > >>> > the cycle continues, the development version is updated with
> > new
> > > > > >>> features.
> > > > > >>> >
> > > > > >>> > One question I would have, do we have a test procedure
> > (document)
> > > > > that
> > > > > >>> > lists all features to be tested?  Such a test procedure can
> be
> > > used
> > > > > to
> > > > > >>> test
> > > > > >>> > a version as it is prepared for production release, and after
> > any
> > > > > time
> > > > > >>> that
> > > > > >>> > bug fixes are applied to the production version.   If we have
> > > such
> > > > a
> > > > > >>> > document, I would suggest it is not complete, as at times I
> > have
> > > > seen
> > > > > >>> > issues that are obvious and have not been removed.
> > > > > >>> >
> > > > > >>> > Thanks,
> > > > > >>> >
> > > > > >>> > George Kirkham
> > > > > >>> >
> > > > > >>> >
> > > > > >>> > -----Original Message-----
> > > > > >>> > From: Maxim Solodovnik [mailto:solomax666@gmail.com]
> > > > > >>> > Sent: Sunday, 2 June 2013 12:30 PM
> > > > > >>> > To: private@openmeetings.apache.org
> > > > > >>> > Subject: Re: [ANNOUNCE] upcoming 2.1.1 release
> > > > > >>> >
> > > > > >>> > I would vote for 2.1.1 release because:
> > > > > >>> > 1) 17 issues were fixed: 1 blocker, 1 critical, 9 major.
> > > > > >>> > 2) logging was improved: there is currently trivial way to
> get
> > > the
> > > > > exact
> > > > > >>> > OM version
> > > > > >>> > 3) 3.0 is not ready yet
> > > > > >>> > 4) "release early, release often" strategy
> > > > > >>> >
> > > > > >>> > PS your grep containing network related issues "Connection
> > > > refused",
> > > > > "not
> > > > > >>> > Authenticated", "Broken pipe" is not very helpful
> > > > > >>> >
> > > > > >>> >
> > > > > >>> > On Sun, Jun 2, 2013 at 1:01 AM, Alexei Fedotov <
> > > > > alexei.fedotov@gmail.com
> > > > > >>> > >wrote:
> > > > > >>> >
> > > > > >>> > > There are two possible options.
> > > > > >>> > >
> > > > > >>> > > 1. Test heavily and ship 2.1.1 release.
> > > > > >>> > > 2. Test heavily and ship 3.0 release instead.
> > > > > >>> > > 3. Ship 3.0 pre-release without heavy testing.
> > > > > >>> > >
> > > > > >>> > > Why should we bother about testing in 2.1.1? Haven't we
> just
> > > > > improved
> > > > > >>> > > a few things? We don't actually know if we have improved
> > > things.
> > > > > Any
> > > > > >>> > > change have a risk of breaking something.
> > > > > >>> > >
> > > > > >>> > > My suggestion is to have testing infrastructure
> implemented,
> > > this
> > > > > >>> > > would help in testing. This will provide feedback. I prefer
> > > > option
> > > > > >>> > > (2), or (3) because (1) is a waste of heavy testing effort.
> > We
> > > > > don't
> > > > > >>> > > have enough resources to test two branches thoroughly.
> > > > > >>> > >
> > > > > >>> > > I constantly get suggestions (the last one from you one
> > > Friday),
> > > > > like
> > > > > >>> > > let's have a low quality development branch, where we will
> > > > > progress,
> > > > > >>> > > and be creative, and let's have someone to produce reliable
> > > > > branches
> > > > > >>> > > from these development branches. For people in a role of
> > > support
> > > > > >>> > > engineers it's hard. That's another reason why I prefer (2)
> > or
> > > > (3)
> > > > > to
> > > > > >>> > > (1).
> > > > > >>> > >
> > > > > >>> > > BTW, here is start of the error log in our 2.1.1
> > installation.
> > > > One
> > > > > can
> > > > > >>> > > start fixing existing problems, if we want a release.
> > > > > >>> > >
> > > > > >>> > >     45 at
> > > > > >>> > >
> > > > >
> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.ja
> > > > > >>> > > va:99) [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > > > >>> > >      45 at
> > > > > >>> > >
> > > > >
> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValv
> > > > > >>> > > e.java:118) [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > > > >>> > >      42 Caused by: java.net.SocketException: Broken pipe
> > > > > >>> > >      42 at
> > > > > >>> > >
> > > > >
> > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:
> > > > > >>> > > 62)
> > > > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > > > >>> > >      42 at
> > > > > >>> > >
> > > > >
> > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:
> > > > > >>> > > 136)
> > > > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > > > >>> > >      42 at
> > > > > >>> > >
> > > > >
> > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:
> > > > > >>> > > 110)
> > > > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > > > >>> > >      42 at
> > > > > >>> > >
> > > > >
> > org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionar
> > > > > >>> > > y.java:4918)
> > > > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > > > >>> > >      42 at
> > > > > >>> > >
> > > > >
> > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958
> > > > > >>> > > )
> > > > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > > > >>> > >      42 at
> > > > > >>> > >
> > > > >
> > org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManag
> > > > > >>> > > er.java:971)
> > > > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > > > >>> > >      42 at java.net.SocketOutputStream.socketWrite0(Native
> > > > Method)
> > > > > >>> > > ~[na:1.6.0_27]
> > > > > >>> > >      42 at
> > > > > >>> > >
> > > > >
> > com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:11
> > > > > >>> > > 17) ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > > > >>> > >      42 at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> > > > > >>> > > ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > > > >>> > >      32 at
> > > > > >>> > >
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > > > > >>> > > Method) ~[na:1.6.0_27]
> > > > > >>> > >      21 at
> > > > > >>> > >
> > > > >
> > org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransact
> > > > > >>> > > ionManager.java:516)
> > > > > >>> > >
> > ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > > > >>> > >      21 at
> > > > > >>> > >
> > > > >
> > org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccess
> > > > > >>> > > ExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> > > > > >>> > >
> > ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > > > >>> > >      21 at
> > > > > >>> > >
> > > > >
> > org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPoss
> > > > > >>> > > ible(DefaultJpaDialect.java:120)
> > > > > >>> > >
> > ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > > > >>> > >      19 FailedObject: select c from Sessiondata as c where
> > > > > >>> > > c.session_id LIKE :session_id [java.lang.String]
> > > > > >>> > >      16 java.lang.NullPointerException: null
> > > > > >>> > >      12 at
> > > > > >>> > >
> > > > >
> > org.apache.openmeetings.remote.ConferenceService.getRoomsByOrganisatio
> > > > > >>> > > nWithoutType(ConferenceService.java:147)
> > > > > >>> > > ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> > > > > >>> > >      10 at
> > > > > >>> > >
> > sun.reflect.GeneratedConstructorAccessor283.newInstance(Unknown
> > > > > >>> > > Source) ~[na:na]
> > > > > >>> > >       4 at
> > > > > >>> > >
> > > > >
> > org.apache.openmeetings.remote.red5.ScopeApplicationAdapter.roomLeaveB
> > > > > >>> > > yScope(ScopeApplicationAdapter.java:564)
> > > > > >>> > > [openmeetings-2.1.1-SNAPSHOT.jar:na]
> > > > > >>> > >       2 java.lang.Exception: not Authenticated
> > > > > >>> > >       2 ERROR 05-28 20:44:56.425
> > o.a.o.r.WhiteBoardService:408
> > > > > >>> > > [NioProcessor-6] - WhiteboardSyncLockObject not found for
> > this
> > > > > Client
> > > > > >>> > > {}
> > > > > >>> > >       2 ERROR 05-28 20:44:56.423
> > o.a.o.r.WhiteBoardService:408
> > > > > >>> > > [NioProcessor-6] - WhiteboardSyncLockObject not found for
> > this
> > > > > Client
> > > > > >>> > > {}
> > > > > >>> > >       2 Caused by:
> > > > > >>> > > com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
> The
> > > last
> > > > > >>> > > packet successfully received from the server was 84 612 291
> > > > > >>> > > milliseconds ago.  The last packet sent successfully to the
> > > > server
> > > > > was
> > > > > >>> > > 84 612 291 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 server configured values for client timeouts, or using
> > the
> > > > > >>> > > Connector/J connection property 'autoReconnect=true' to
> avoid
> > > > this
> > > > > >>> > > problem.
> > > > > >>> > >       2 at
> > > > > >>> > >
> > > > >
> > org.apache.openmeetings.axis.services.FileWebService.getFileExplorerBy
> > > > > >>> > > RoomSelf(FileWebService.java:728)
> > > > > >>> > > ~[openmeetings-WebService-2.1.1-SNAPSHOT.jar:na]
> > > > > >>> > >       1 org.springframework.orm.jpa.JpaSystemException: The
> > > last
> > > > > >>> > > packet successfully received from the server was 84 612 291
> > > > > >>> > > milliseconds ago.  The last packet sent successfully to the
> > > > server
> > > > > was
> > > > > >>> > > 84 612 291 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 server configured values for client timeouts, or using
> > the
> > > > > >>> > > Connector/J connection property 'autoReconnect=true' to
> avoid
> > > > this
> > > > > >>> > > problem.; nested exception is
> <openjpa-2.2.1-r422266:1396819
> > > > fatal
> > > > > >>> > > general error>
> > > > org.apache.openjpa.persistence.PersistenceException:
> > > > > >>> > > The last packet successfully received from the server was
> 84
> > > 612
> > > > > 291
> > > > > >>> > > milliseconds ago.  The last packet sent successfully to the
> > > > server
> > > > > was
> > > > > >>> > > 84 612 291 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 server configured values for client timeouts, or using
> > the
> > > > > >>> > > Connector/J connection property 'autoReconnect=true' to
> avoid
> > > > this
> > > > > >>> > > problem.
> > > > > >>> > >       1
> org.apache.openjpa.persistence.PersistenceException:
> > > The
> > > > > last
> > > > > >>> > > packet successfully received from the server was 39 315 457
> > > > > >>> > > milliseconds ago.  The last packet sent successfully to the
> > > > server
> > > > > was
> > > > > >>> > > 39 315 457 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 server configured values for client timeouts, or using
> > the
> > > > > >>> > > Connector/J connection property 'autoReconnect=true' to
> avoid
> > > > this
> > > > > >>> > > problem.
> > > > > >>> > >       1 java.net.ConnectException: Connection refused
> > > > > >>> > >       1  INFO 05-29 14:53:34.184 o.a.o.d.u.d.UsersDao:163
> > > > > >>> > > [NioProcessor-4] - [getUser] Info: No USER_ID given
> > > > > >>> > >       1  INFO 05-28 15:46:15.535 o.a.o.d.u.d.UsersDao:163
> > > > > >>> > > [NioProcessor-14] - [getUser] Info: No USER_ID given
> > > > > >>> > >       1 FailedObject: select c from User as c where
> > c.user_id =
> > > > > >>> > > :user_id AND c.deleted <> true [java.lang.String]
> > > > > >>> > >
> > > > > >>> >
> > > > > >>> >
> > > > > >>> >
> > > > > >>> > --
> > > > > >>> > WBR
> > > > > >>> > Maxim aka solomax
> > > > > >>> >
> > > > > >>>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >> WBR
> > > > > >> Maxim aka solomax
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Sebastian Wagner
> > > https://twitter.com/#!/dead_lock
> > > http://www.webbase-design.de
> > > http://www.wagner-sebastian.com
> > > seba.wagner@gmail.co <se...@gmail.com>
> > >
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
> >
>
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>



-- 
WBR
Maxim aka solomax

Re: [ANNOUNCE] upcoming 2.1.1 release

Posted by "seba.wagner@gmail.com" <se...@gmail.com>.

I also have only limited internet access next week.

Given the scope of the release (a x.x.1 release, so no major, nore minor,
more like a bugfix release) I think it should be okay to give it at least a
try.

Is there a binary version of 2.1.1 somewhere to download right now?

Sebastian


2013/6/7 Maxim Solodovnik <so...@gmail.com>

> The only places refering to 2.1.0 are
> downloads.xml and "release notes" first one will be changed in trunk only
> (to provide link to the latest version)
> second will be updated during release process.
>
> I'm going to pack 2.1.1RC1 tonight
>
> Please NOTE I'll be on vacation 2013.06.12-2013.06.23 with none internet
> connection (or maybe with access to email only)
>
>
> On Fri, Jun 7, 2013 at 3:14 AM, seba.wagner@gmail.com <
> seba.wagner@gmail.com
> > wrote:
>
> > Hi folks,
> >
> > I agree on point no 5 with Maxim:
> > *auto
> > reconnect feature stopped to work long ago*
> > => There was never such a feature. It is also rather complicated, cause
> > reconnect means that you basically out of sync, and the application has
> no
> > idea what has happened in between, so in theory you could have a
> reconnect
> > after 2 hours and the entire list of participants, screensharing,
> > whiteboards, et cetera _everything_ has changed. So the only chance I see
> > to realize a *reconnect* is to actually re-login the user into the room
> and
> > load everything from scratch.
> >
> > But about this entire discussion:
> > Why is this discussion in the private list at all?
> > There is no *privileged* channel to request or discuss features and bugs.
> > Please, lets use the dev list and give everyone that would like to be
> > involved the chance to at least read what you have to say.
> > @Alexei: For instance anybody reading the Analytics (or error
> > infrastructure :)) question now, is missing the context as how this email
> > that you wrote was initiated.
> >
> > Thanks,
> > Sebastian
> >
> >
> > 2013/6/7 Maxim Solodovnik <so...@gmail.com>
> >
> > > 1) video codec was switched in 2.1.0, this is bug fix release I'm sure
> we
> > > shouldn't add major changes. Additionally we will need to use h264 in
> > > 3.0/3.1 since it is html5 compatible.
> > >
> > > 2) this behavior was not changed since 2.0. Please file an issue
> (better
> > > with patch) if you feel this need to be changed. (I would add
> > configuration
> > > value default_gain with default value == 50)
> > >
> > > 3) I'll doublecheck
> > >
> > > 4) according to VOTE rules every user voting for release must perform
> > these
> > > tests
> > >
> > > 5) I would vote for adding NOTE regarding flash version to release
> notes
> > of
> > > 2.1.1 and alert to 3.0 (on room enter). Actually auto reconnect works
> as
> > > before .... it is just don't reconnect into room :)
> > > You can file JIRA issue (better with patch), but to be fair I don't
> > really
> > > like such "last minute" changes. The release was announced long time
> ago
> > > and I feel we should close this branch and focus on 3.0
> > >  On Jun 6, 2013 7:23 PM, "Alexei Fedotov" <al...@gmail.com>
> > > wrote:
> > >
> > > > Maxim, I've looked through the changes:
> > > > https://gist.github.com/leshikus/5720534
> > > > most of them relate to log improvements, thus harmless.
> > > >
> > > > Here are few points on 2.1.1 release:
> > > >
> > > > 1. We haven't carefully tested H.264. Our customers use H.263 because
> > > > H.264 didn't work well for them. H,254 is a default codec for a new
> > > > release. Won't this be a problem?
> > > >
> > > > 2. There are hardcoded microphone settings for silence level, gain,
> > > > etc. From the other side I noticed that for the new release
> microphone
> > > > sensitivity is low, and one needs to set the sensitivity bar to the
> > > > maximum every time to get it to normal. Or this can be also related
> to
> > > > codec.
> > > >
> > > > 3. There are several places which incorrectly refer to "2.1.0" and
> > > > "2.0". The only place where the release is correct is a build file.
> > > >
> > > > 4. Who will volunteer to pass all tests for the new release,
> > > > xdocs/ManualTesting.xml?
> > > >
> > > > 5. Our users believe that reliability is most important part of
> > > > conferences. The last flash version does not work well, and auto
> > > > reconnect feature stopped to work long ago. How this can be
> addressed?
> > > > Should a flash version check be added (against flash 11.6 and 11.7),
> > > > and auto reconnect fixed?
> > > >
> > > > --
> > > > With best regards / с наилучшими пожеланиями,
> > > > Alexei Fedotov / Алексей Федотов,
> > > > http://dataved.ru/
> > > > +7 916 562 8095
> > > >
> > > >
> > > > On Thu, Jun 6, 2013 at 1:42 PM, Alexei Fedotov <
> > alexei.fedotov@gmail.com
> > > >
> > > > wrote:
> > > > > Maxim, thanks for the tags!
> > > > > --
> > > > > With best regards / с наилучшими пожеланиями,
> > > > > Alexei Fedotov / Алексей Федотов,
> > > > > http://dataved.ru/
> > > > > +7 916 562 8095
> > > > >
> > > > >
> > > > > On Mon, Jun 3, 2013 at 2:28 PM, Maxim Solodovnik <
> > solomax666@gmail.com
> > > >
> > > > wrote:
> > > > >> I believe ""Release early, release often" assumes we use one
> branch"
> > > > can be
> > > > >> followed with any number of branches :)
> > > > >>
> > > > >>>> "It is uncool when users come to support engineers"
> > > > >> I currently feel I'm the only support engineer :)
> > > > >>
> > > > >>>> Don't expect it become easier with html5
> > > > >> I DO expect!, and things are MUCH easier with HTML5 :)
> > > > >>
> > > > >>>> How to get 2.1 code?
> > > > >> http://svn.apache.org/repos/asf/openmeetings/tags/2.1RC3/
> > > > >>
> > > > >>>> How to get 2.1.1 code?
> > > > >> https://svn.apache.org/repos/asf/openmeetings/branches/2.1/
> > > > >>
> > > > >>>> Were all these mentioned fixes ported to 3.0 (taking into
> account
> > > how
> > > > many
> > > > >> times I get no for particular fix, it would be surprising and
> great
> > to
> > > > get
> > > > >> yes)?
> > > > >> I'm not sure what do you mean by "all these mentioned fixes", all
> > > fixes
> > > > >> made by me are in both branches :)
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> On Mon, Jun 3, 2013 at 5:06 PM, Alexei Fedotov <
> > > > alexei.fedotov@gmail.com>wrote:
> > > > >>
> > > > >>> Just one comment. "Release early, release often" assumes we use
> one
> > > > branch,
> > > > >>> where we fix errors quickly. Having two branches gives us the
> > > expected
> > > > >>> result that developers care less about users when develop in
> their
> > > > >>> development branch. When something is released, developers switch
> > to
> > > a
> > > > new
> > > > >>> develioment branch and continue being cool and creative.
> > > > >>>
> > > > >>> It is uncool when users come to support engineers and they feed
> > them
> > > > with
> > > > >>> tweaks and workarounds. You won't imagine the quirkiness of
> > > workarounds
> > > > >>> used to demonstrate a SIP video integration.
> > > > >>>
> > > > >>> Everyone wants to fix bugs when they are easy to reproduce. Most
> of
> > > > them
> > > > >>> are not due to the fact that openmeetings has a lot of unreliable
> > > > >>> technologies at its base.
> > > > >>>
> > > > >>> Don't expect it become easier with html5. Contrary, we will get
> own
> > > > >>> problems for each browser. That's why testing infrastructure is
> > > > important
> > > > >>> before we start releasing things.
> > > > >>>
> > > > >>> 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
> > > > >>> many times I get no for particular fix, it would be surprising
> and
> > > > great to
> > > > >>> get yes)?
> > > > >>> 02.06.2013 15:06 пользователь "George Kirkham" <
> > > gkirkham@co2crc.com.au
> > > > >
> > > > >>> написал:
> > > > >>>
> > > > >>> > Hi,
> > > > >>> >
> > > > >>> > My apologies, I had thought that 2.1.1 had been released.
> > > > >>> >
> > > > >>> > It would be 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).
> > > > >>> >
> > > > >>> > The main point is to have;
> > > > >>> >  a) a stable released version for production use. The version
> > would
> > > > be
> > > > >>> > used for production while new features are prepared and fixed
> in
> > > the
> > > > >>> > 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 still
> applicable).
> > > > >>> >
> > > > >>> > b) a development version to which new features are added, bug
> > fixes
> > > > for
> > > > >>> > issues discovered in production.  Full testing should be
> > performed
> > > > often,
> > > > >>> > and at least any time a new feature is added.
> > > > >>> >
> > > > >>> > At some point, additional features are put on hold, a full
> > testing
> > > > >>> > completed, and then the development version can be released to
> > > > update the
> > > > >>> > production version, after which the development version is
> > > > incremented
> > > > >>> and
> > > > >>> > the cycle continues, the development version is updated with
> new
> > > > >>> features.
> > > > >>> >
> > > > >>> > One question I would have, do we have a test procedure
> (document)
> > > > that
> > > > >>> > lists all features to be tested?  Such a test procedure can be
> > used
> > > > to
> > > > >>> test
> > > > >>> > a version as it is prepared for production release, and after
> any
> > > > time
> > > > >>> that
> > > > >>> > bug fixes are applied to the production version.   If we have
> > such
> > > a
> > > > >>> > document, I would suggest it is not complete, as at times I
> have
> > > seen
> > > > >>> > issues that are obvious and have not been removed.
> > > > >>> >
> > > > >>> > Thanks,
> > > > >>> >
> > > > >>> > George Kirkham
> > > > >>> >
> > > > >>> >
> > > > >>> > -----Original Message-----
> > > > >>> > From: Maxim Solodovnik [mailto:solomax666@gmail.com]
> > > > >>> > Sent: Sunday, 2 June 2013 12:30 PM
> > > > >>> > To: private@openmeetings.apache.org
> > > > >>> > Subject: Re: [ANNOUNCE] upcoming 2.1.1 release
> > > > >>> >
> > > > >>> > I would vote for 2.1.1 release because:
> > > > >>> > 1) 17 issues were fixed: 1 blocker, 1 critical, 9 major.
> > > > >>> > 2) logging was improved: there is currently trivial way to get
> > the
> > > > exact
> > > > >>> > OM version
> > > > >>> > 3) 3.0 is not ready yet
> > > > >>> > 4) "release early, release often" strategy
> > > > >>> >
> > > > >>> > PS your grep containing network related issues "Connection
> > > refused",
> > > > "not
> > > > >>> > Authenticated", "Broken pipe" is not very helpful
> > > > >>> >
> > > > >>> >
> > > > >>> > On Sun, Jun 2, 2013 at 1:01 AM, Alexei Fedotov <
> > > > alexei.fedotov@gmail.com
> > > > >>> > >wrote:
> > > > >>> >
> > > > >>> > > There are two possible options.
> > > > >>> > >
> > > > >>> > > 1. Test heavily and ship 2.1.1 release.
> > > > >>> > > 2. Test heavily and ship 3.0 release instead.
> > > > >>> > > 3. Ship 3.0 pre-release without heavy testing.
> > > > >>> > >
> > > > >>> > > Why should we bother about testing in 2.1.1? Haven't we just
> > > > improved
> > > > >>> > > a few things? We don't actually know if we have improved
> > things.
> > > > Any
> > > > >>> > > change have a risk of breaking something.
> > > > >>> > >
> > > > >>> > > My suggestion is to have testing infrastructure implemented,
> > this
> > > > >>> > > would help in testing. This will provide feedback. I prefer
> > > option
> > > > >>> > > (2), or (3) because (1) is a waste of heavy testing effort.
> We
> > > > don't
> > > > >>> > > have enough resources to test two branches thoroughly.
> > > > >>> > >
> > > > >>> > > I constantly get suggestions (the last one from you one
> > Friday),
> > > > like
> > > > >>> > > let's have a low quality development branch, where we will
> > > > progress,
> > > > >>> > > and be creative, and let's have someone to produce reliable
> > > > branches
> > > > >>> > > from these development branches. For people in a role of
> > support
> > > > >>> > > engineers it's hard. That's another reason why I prefer (2)
> or
> > > (3)
> > > > to
> > > > >>> > > (1).
> > > > >>> > >
> > > > >>> > > BTW, here is start of the error log in our 2.1.1
> installation.
> > > One
> > > > can
> > > > >>> > > start fixing existing problems, if we want a release.
> > > > >>> > >
> > > > >>> > >     45 at
> > > > >>> > >
> > > >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.ja
> > > > >>> > > va:99) [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > > >>> > >      45 at
> > > > >>> > >
> > > >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValv
> > > > >>> > > e.java:118) [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > > >>> > >      42 Caused by: java.net.SocketException: Broken pipe
> > > > >>> > >      42 at
> > > > >>> > >
> > > >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:
> > > > >>> > > 62)
> > > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > > >>> > >      42 at
> > > > >>> > >
> > > >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:
> > > > >>> > > 136)
> > > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > > >>> > >      42 at
> > > > >>> > >
> > > >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:
> > > > >>> > > 110)
> > > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > > >>> > >      42 at
> > > > >>> > >
> > > >
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionar
> > > > >>> > > y.java:4918)
> > > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > > >>> > >      42 at
> > > > >>> > >
> > > >
> org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958
> > > > >>> > > )
> > > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > > >>> > >      42 at
> > > > >>> > >
> > > >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManag
> > > > >>> > > er.java:971)
> > > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > > >>> > >      42 at java.net.SocketOutputStream.socketWrite0(Native
> > > Method)
> > > > >>> > > ~[na:1.6.0_27]
> > > > >>> > >      42 at
> > > > >>> > >
> > > >
> com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:11
> > > > >>> > > 17) ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > > >>> > >      42 at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> > > > >>> > > ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > > >>> > >      32 at
> > > > >>> > > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > > > >>> > > Method) ~[na:1.6.0_27]
> > > > >>> > >      21 at
> > > > >>> > >
> > > >
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransact
> > > > >>> > > ionManager.java:516)
> > > > >>> > >
> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > > >>> > >      21 at
> > > > >>> > >
> > > >
> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccess
> > > > >>> > > ExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> > > > >>> > >
> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > > >>> > >      21 at
> > > > >>> > >
> > > >
> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPoss
> > > > >>> > > ible(DefaultJpaDialect.java:120)
> > > > >>> > >
> ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > > >>> > >      19 FailedObject: select c from Sessiondata as c where
> > > > >>> > > c.session_id LIKE :session_id [java.lang.String]
> > > > >>> > >      16 java.lang.NullPointerException: null
> > > > >>> > >      12 at
> > > > >>> > >
> > > >
> org.apache.openmeetings.remote.ConferenceService.getRoomsByOrganisatio
> > > > >>> > > nWithoutType(ConferenceService.java:147)
> > > > >>> > > ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> > > > >>> > >      10 at
> > > > >>> > >
> sun.reflect.GeneratedConstructorAccessor283.newInstance(Unknown
> > > > >>> > > Source) ~[na:na]
> > > > >>> > >       4 at
> > > > >>> > >
> > > >
> org.apache.openmeetings.remote.red5.ScopeApplicationAdapter.roomLeaveB
> > > > >>> > > yScope(ScopeApplicationAdapter.java:564)
> > > > >>> > > [openmeetings-2.1.1-SNAPSHOT.jar:na]
> > > > >>> > >       2 java.lang.Exception: not Authenticated
> > > > >>> > >       2 ERROR 05-28 20:44:56.425
> o.a.o.r.WhiteBoardService:408
> > > > >>> > > [NioProcessor-6] - WhiteboardSyncLockObject not found for
> this
> > > > Client
> > > > >>> > > {}
> > > > >>> > >       2 ERROR 05-28 20:44:56.423
> o.a.o.r.WhiteBoardService:408
> > > > >>> > > [NioProcessor-6] - WhiteboardSyncLockObject not found for
> this
> > > > Client
> > > > >>> > > {}
> > > > >>> > >       2 Caused by:
> > > > >>> > > com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The
> > last
> > > > >>> > > packet successfully received from the server was 84 612 291
> > > > >>> > > milliseconds ago.  The last packet sent successfully to the
> > > server
> > > > was
> > > > >>> > > 84 612 291 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 server configured values for client timeouts, or using
> the
> > > > >>> > > Connector/J connection property 'autoReconnect=true' to avoid
> > > this
> > > > >>> > > problem.
> > > > >>> > >       2 at
> > > > >>> > >
> > > >
> org.apache.openmeetings.axis.services.FileWebService.getFileExplorerBy
> > > > >>> > > RoomSelf(FileWebService.java:728)
> > > > >>> > > ~[openmeetings-WebService-2.1.1-SNAPSHOT.jar:na]
> > > > >>> > >       1 org.springframework.orm.jpa.JpaSystemException: The
> > last
> > > > >>> > > packet successfully received from the server was 84 612 291
> > > > >>> > > milliseconds ago.  The last packet sent successfully to the
> > > server
> > > > was
> > > > >>> > > 84 612 291 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 server configured values for client timeouts, or using
> the
> > > > >>> > > Connector/J connection property 'autoReconnect=true' to avoid
> > > this
> > > > >>> > > problem.; nested exception is <openjpa-2.2.1-r422266:1396819
> > > fatal
> > > > >>> > > general error>
> > > org.apache.openjpa.persistence.PersistenceException:
> > > > >>> > > The last packet successfully received from the server was 84
> > 612
> > > > 291
> > > > >>> > > milliseconds ago.  The last packet sent successfully to the
> > > server
> > > > was
> > > > >>> > > 84 612 291 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 server configured values for client timeouts, or using
> the
> > > > >>> > > Connector/J connection property 'autoReconnect=true' to avoid
> > > this
> > > > >>> > > problem.
> > > > >>> > >       1 org.apache.openjpa.persistence.PersistenceException:
> > The
> > > > last
> > > > >>> > > packet successfully received from the server was 39 315 457
> > > > >>> > > milliseconds ago.  The last packet sent successfully to the
> > > server
> > > > was
> > > > >>> > > 39 315 457 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 server configured values for client timeouts, or using
> the
> > > > >>> > > Connector/J connection property 'autoReconnect=true' to avoid
> > > this
> > > > >>> > > problem.
> > > > >>> > >       1 java.net.ConnectException: Connection refused
> > > > >>> > >       1  INFO 05-29 14:53:34.184 o.a.o.d.u.d.UsersDao:163
> > > > >>> > > [NioProcessor-4] - [getUser] Info: No USER_ID given
> > > > >>> > >       1  INFO 05-28 15:46:15.535 o.a.o.d.u.d.UsersDao:163
> > > > >>> > > [NioProcessor-14] - [getUser] Info: No USER_ID given
> > > > >>> > >       1 FailedObject: select c from User as c where
> c.user_id =
> > > > >>> > > :user_id AND c.deleted <> true [java.lang.String]
> > > > >>> > >
> > > > >>> >
> > > > >>> >
> > > > >>> >
> > > > >>> > --
> > > > >>> > WBR
> > > > >>> > Maxim aka solomax
> > > > >>> >
> > > > >>>
> > > > >>
> > > > >>
> > > > >>
> > > > >> --
> > > > >> WBR
> > > > >> Maxim aka solomax
> > > >
> > >
> >
> >
> >
> > --
> > Sebastian Wagner
> > https://twitter.com/#!/dead_lock
> > http://www.webbase-design.de
> > http://www.wagner-sebastian.com
> > seba.wagner@gmail.co <se...@gmail.com>
> >
>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com

Re: [ANNOUNCE] upcoming 2.1.1 release

Posted by Maxim Solodovnik <so...@gmail.com>.

The only places refering to 2.1.0 are
downloads.xml and "release notes" first one will be changed in trunk only
(to provide link to the latest version)
second will be updated during release process.

I'm going to pack 2.1.1RC1 tonight

Please NOTE I'll be on vacation 2013.06.12-2013.06.23 with none internet
connection (or maybe with access to email only)


On Fri, Jun 7, 2013 at 3:14 AM, seba.wagner@gmail.com <seba.wagner@gmail.com
> wrote:

> Hi folks,
>
> I agree on point no 5 with Maxim:
> *auto
> reconnect feature stopped to work long ago*
> => There was never such a feature. It is also rather complicated, cause
> reconnect means that you basically out of sync, and the application has no
> idea what has happened in between, so in theory you could have a reconnect
> after 2 hours and the entire list of participants, screensharing,
> whiteboards, et cetera _everything_ has changed. So the only chance I see
> to realize a *reconnect* is to actually re-login the user into the room and
> load everything from scratch.
>
> But about this entire discussion:
> Why is this discussion in the private list at all?
> There is no *privileged* channel to request or discuss features and bugs.
> Please, lets use the dev list and give everyone that would like to be
> involved the chance to at least read what you have to say.
> @Alexei: For instance anybody reading the Analytics (or error
> infrastructure :)) question now, is missing the context as how this email
> that you wrote was initiated.
>
> Thanks,
> Sebastian
>
>
> 2013/6/7 Maxim Solodovnik <so...@gmail.com>
>
> > 1) video codec was switched in 2.1.0, this is bug fix release I'm sure we
> > shouldn't add major changes. Additionally we will need to use h264 in
> > 3.0/3.1 since it is html5 compatible.
> >
> > 2) this behavior was not changed since 2.0. Please file an issue (better
> > with patch) if you feel this need to be changed. (I would add
> configuration
> > value default_gain with default value == 50)
> >
> > 3) I'll doublecheck
> >
> > 4) according to VOTE rules every user voting for release must perform
> these
> > tests
> >
> > 5) I would vote for adding NOTE regarding flash version to release notes
> of
> > 2.1.1 and alert to 3.0 (on room enter). Actually auto reconnect works as
> > before .... it is just don't reconnect into room :)
> > You can file JIRA issue (better with patch), but to be fair I don't
> really
> > like such "last minute" changes. The release was announced long time ago
> > and I feel we should close this branch and focus on 3.0
> >  On Jun 6, 2013 7:23 PM, "Alexei Fedotov" <al...@gmail.com>
> > wrote:
> >
> > > Maxim, I've looked through the changes:
> > > https://gist.github.com/leshikus/5720534
> > > most of them relate to log improvements, thus harmless.
> > >
> > > Here are few points on 2.1.1 release:
> > >
> > > 1. We haven't carefully tested H.264. Our customers use H.263 because
> > > H.264 didn't work well for them. H,254 is a default codec for a new
> > > release. Won't this be a problem?
> > >
> > > 2. There are hardcoded microphone settings for silence level, gain,
> > > etc. From the other side I noticed that for the new release microphone
> > > sensitivity is low, and one needs to set the sensitivity bar to the
> > > maximum every time to get it to normal. Or this can be also related to
> > > codec.
> > >
> > > 3. There are several places which incorrectly refer to "2.1.0" and
> > > "2.0". The only place where the release is correct is a build file.
> > >
> > > 4. Who will volunteer to pass all tests for the new release,
> > > xdocs/ManualTesting.xml?
> > >
> > > 5. Our users believe that reliability is most important part of
> > > conferences. The last flash version does not work well, and auto
> > > reconnect feature stopped to work long ago. How this can be addressed?
> > > Should a flash version check be added (against flash 11.6 and 11.7),
> > > and auto reconnect fixed?
> > >
> > > --
> > > With best regards / с наилучшими пожеланиями,
> > > Alexei Fedotov / Алексей Федотов,
> > > http://dataved.ru/
> > > +7 916 562 8095
> > >
> > >
> > > On Thu, Jun 6, 2013 at 1:42 PM, Alexei Fedotov <
> alexei.fedotov@gmail.com
> > >
> > > wrote:
> > > > Maxim, thanks for the tags!
> > > > --
> > > > With best regards / с наилучшими пожеланиями,
> > > > Alexei Fedotov / Алексей Федотов,
> > > > http://dataved.ru/
> > > > +7 916 562 8095
> > > >
> > > >
> > > > On Mon, Jun 3, 2013 at 2:28 PM, Maxim Solodovnik <
> solomax666@gmail.com
> > >
> > > wrote:
> > > >> I believe ""Release early, release often" assumes we use one branch"
> > > can be
> > > >> followed with any number of branches :)
> > > >>
> > > >>>> "It is uncool when users come to support engineers"
> > > >> I currently feel I'm the only support engineer :)
> > > >>
> > > >>>> Don't expect it become easier with html5
> > > >> I DO expect!, and things are MUCH easier with HTML5 :)
> > > >>
> > > >>>> How to get 2.1 code?
> > > >> http://svn.apache.org/repos/asf/openmeetings/tags/2.1RC3/
> > > >>
> > > >>>> How to get 2.1.1 code?
> > > >> https://svn.apache.org/repos/asf/openmeetings/branches/2.1/
> > > >>
> > > >>>> Were all these mentioned fixes ported to 3.0 (taking into account
> > how
> > > many
> > > >> times I get no for particular fix, it would be surprising and great
> to
> > > get
> > > >> yes)?
> > > >> I'm not sure what do you mean by "all these mentioned fixes", all
> > fixes
> > > >> made by me are in both branches :)
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> On Mon, Jun 3, 2013 at 5:06 PM, Alexei Fedotov <
> > > alexei.fedotov@gmail.com>wrote:
> > > >>
> > > >>> Just one comment. "Release early, release often" assumes we use one
> > > branch,
> > > >>> where we fix errors quickly. Having two branches gives us the
> > expected
> > > >>> result that developers care less about users when develop in their
> > > >>> development branch. When something is released, developers switch
> to
> > a
> > > new
> > > >>> develioment branch and continue being cool and creative.
> > > >>>
> > > >>> It is uncool when users come to support engineers and they feed
> them
> > > with
> > > >>> tweaks and workarounds. You won't imagine the quirkiness of
> > workarounds
> > > >>> used to demonstrate a SIP video integration.
> > > >>>
> > > >>> Everyone wants to fix bugs when they are easy to reproduce. Most of
> > > them
> > > >>> are not due to the fact that openmeetings has a lot of unreliable
> > > >>> technologies at its base.
> > > >>>
> > > >>> Don't expect it become easier with html5. Contrary, we will get own
> > > >>> problems for each browser. That's why testing infrastructure is
> > > important
> > > >>> before we start releasing things.
> > > >>>
> > > >>> 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
> > > >>> many times I get no for particular fix, it would be surprising and
> > > great to
> > > >>> get yes)?
> > > >>> 02.06.2013 15:06 пользователь "George Kirkham" <
> > gkirkham@co2crc.com.au
> > > >
> > > >>> написал:
> > > >>>
> > > >>> > Hi,
> > > >>> >
> > > >>> > My apologies, I had thought that 2.1.1 had been released.
> > > >>> >
> > > >>> > It would be 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).
> > > >>> >
> > > >>> > The main point is to have;
> > > >>> >  a) a stable released version for production use. The version
> would
> > > be
> > > >>> > used for production while new features are prepared and fixed in
> > the
> > > >>> > 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 still applicable).
> > > >>> >
> > > >>> > b) a development version to which new features are added, bug
> fixes
> > > for
> > > >>> > issues discovered in production.  Full testing should be
> performed
> > > often,
> > > >>> > and at least any time a new feature is added.
> > > >>> >
> > > >>> > At some point, additional features are put on hold, a full
> testing
> > > >>> > completed, and then the development version can be released to
> > > update the
> > > >>> > production version, after which the development version is
> > > incremented
> > > >>> and
> > > >>> > the cycle continues, the development version is updated with new
> > > >>> features.
> > > >>> >
> > > >>> > One question I would have, do we have a test procedure (document)
> > > that
> > > >>> > lists all features to be tested?  Such a test procedure can be
> used
> > > to
> > > >>> test
> > > >>> > a version as it is prepared for production release, and after any
> > > time
> > > >>> that
> > > >>> > bug fixes are applied to the production version.   If we have
> such
> > a
> > > >>> > document, I would suggest it is not complete, as at times I have
> > seen
> > > >>> > issues that are obvious and have not been removed.
> > > >>> >
> > > >>> > Thanks,
> > > >>> >
> > > >>> > George Kirkham
> > > >>> >
> > > >>> >
> > > >>> > -----Original Message-----
> > > >>> > From: Maxim Solodovnik [mailto:solomax666@gmail.com]
> > > >>> > Sent: Sunday, 2 June 2013 12:30 PM
> > > >>> > To: private@openmeetings.apache.org
> > > >>> > Subject: Re: [ANNOUNCE] upcoming 2.1.1 release
> > > >>> >
> > > >>> > I would vote for 2.1.1 release because:
> > > >>> > 1) 17 issues were fixed: 1 blocker, 1 critical, 9 major.
> > > >>> > 2) logging was improved: there is currently trivial way to get
> the
> > > exact
> > > >>> > OM version
> > > >>> > 3) 3.0 is not ready yet
> > > >>> > 4) "release early, release often" strategy
> > > >>> >
> > > >>> > PS your grep containing network related issues "Connection
> > refused",
> > > "not
> > > >>> > Authenticated", "Broken pipe" is not very helpful
> > > >>> >
> > > >>> >
> > > >>> > On Sun, Jun 2, 2013 at 1:01 AM, Alexei Fedotov <
> > > alexei.fedotov@gmail.com
> > > >>> > >wrote:
> > > >>> >
> > > >>> > > There are two possible options.
> > > >>> > >
> > > >>> > > 1. Test heavily and ship 2.1.1 release.
> > > >>> > > 2. Test heavily and ship 3.0 release instead.
> > > >>> > > 3. Ship 3.0 pre-release without heavy testing.
> > > >>> > >
> > > >>> > > Why should we bother about testing in 2.1.1? Haven't we just
> > > improved
> > > >>> > > a few things? We don't actually know if we have improved
> things.
> > > Any
> > > >>> > > change have a risk of breaking something.
> > > >>> > >
> > > >>> > > My suggestion is to have testing infrastructure implemented,
> this
> > > >>> > > would help in testing. This will provide feedback. I prefer
> > option
> > > >>> > > (2), or (3) because (1) is a waste of heavy testing effort. We
> > > don't
> > > >>> > > have enough resources to test two branches thoroughly.
> > > >>> > >
> > > >>> > > I constantly get suggestions (the last one from you one
> Friday),
> > > like
> > > >>> > > let's have a low quality development branch, where we will
> > > progress,
> > > >>> > > and be creative, and let's have someone to produce reliable
> > > branches
> > > >>> > > from these development branches. For people in a role of
> support
> > > >>> > > engineers it's hard. That's another reason why I prefer (2) or
> > (3)
> > > to
> > > >>> > > (1).
> > > >>> > >
> > > >>> > > BTW, here is start of the error log in our 2.1.1 installation.
> > One
> > > can
> > > >>> > > start fixing existing problems, if we want a release.
> > > >>> > >
> > > >>> > >     45 at
> > > >>> > >
> > > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.ja
> > > >>> > > va:99) [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >>> > >      45 at
> > > >>> > >
> > > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValv
> > > >>> > > e.java:118) [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > > >>> > >      42 Caused by: java.net.SocketException: Broken pipe
> > > >>> > >      42 at
> > > >>> > >
> > > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:
> > > >>> > > 62)
> > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >>> > >      42 at
> > > >>> > >
> > > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:
> > > >>> > > 136)
> > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >>> > >      42 at
> > > >>> > >
> > > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:
> > > >>> > > 110)
> > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >>> > >      42 at
> > > >>> > >
> > > org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionar
> > > >>> > > y.java:4918)
> > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >>> > >      42 at
> > > >>> > >
> > > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958
> > > >>> > > )
> > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >>> > >      42 at
> > > >>> > >
> > > org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManag
> > > >>> > > er.java:971)
> > > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > > >>> > >      42 at java.net.SocketOutputStream.socketWrite0(Native
> > Method)
> > > >>> > > ~[na:1.6.0_27]
> > > >>> > >      42 at
> > > >>> > >
> > > com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:11
> > > >>> > > 17) ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >>> > >      42 at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> > > >>> > > ~[mysql-connector-java-jar-5.1.22.jar:na]
> > > >>> > >      32 at
> > > >>> > > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > > >>> > > Method) ~[na:1.6.0_27]
> > > >>> > >      21 at
> > > >>> > >
> > > org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransact
> > > >>> > > ionManager.java:516)
> > > >>> > > ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >>> > >      21 at
> > > >>> > >
> > > org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccess
> > > >>> > > ExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> > > >>> > > ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >>> > >      21 at
> > > >>> > >
> > > org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPoss
> > > >>> > > ible(DefaultJpaDialect.java:120)
> > > >>> > > ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > > >>> > >      19 FailedObject: select c from Sessiondata as c where
> > > >>> > > c.session_id LIKE :session_id [java.lang.String]
> > > >>> > >      16 java.lang.NullPointerException: null
> > > >>> > >      12 at
> > > >>> > >
> > > org.apache.openmeetings.remote.ConferenceService.getRoomsByOrganisatio
> > > >>> > > nWithoutType(ConferenceService.java:147)
> > > >>> > > ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> > > >>> > >      10 at
> > > >>> > > sun.reflect.GeneratedConstructorAccessor283.newInstance(Unknown
> > > >>> > > Source) ~[na:na]
> > > >>> > >       4 at
> > > >>> > >
> > > org.apache.openmeetings.remote.red5.ScopeApplicationAdapter.roomLeaveB
> > > >>> > > yScope(ScopeApplicationAdapter.java:564)
> > > >>> > > [openmeetings-2.1.1-SNAPSHOT.jar:na]
> > > >>> > >       2 java.lang.Exception: not Authenticated
> > > >>> > >       2 ERROR 05-28 20:44:56.425 o.a.o.r.WhiteBoardService:408
> > > >>> > > [NioProcessor-6] - WhiteboardSyncLockObject not found for this
> > > Client
> > > >>> > > {}
> > > >>> > >       2 ERROR 05-28 20:44:56.423 o.a.o.r.WhiteBoardService:408
> > > >>> > > [NioProcessor-6] - WhiteboardSyncLockObject not found for this
> > > Client
> > > >>> > > {}
> > > >>> > >       2 Caused by:
> > > >>> > > com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The
> last
> > > >>> > > packet successfully received from the server was 84 612 291
> > > >>> > > milliseconds ago.  The last packet sent successfully to the
> > server
> > > was
> > > >>> > > 84 612 291 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 server configured values for client timeouts, or using the
> > > >>> > > Connector/J connection property 'autoReconnect=true' to avoid
> > this
> > > >>> > > problem.
> > > >>> > >       2 at
> > > >>> > >
> > > org.apache.openmeetings.axis.services.FileWebService.getFileExplorerBy
> > > >>> > > RoomSelf(FileWebService.java:728)
> > > >>> > > ~[openmeetings-WebService-2.1.1-SNAPSHOT.jar:na]
> > > >>> > >       1 org.springframework.orm.jpa.JpaSystemException: The
> last
> > > >>> > > packet successfully received from the server was 84 612 291
> > > >>> > > milliseconds ago.  The last packet sent successfully to the
> > server
> > > was
> > > >>> > > 84 612 291 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 server configured values for client timeouts, or using the
> > > >>> > > Connector/J connection property 'autoReconnect=true' to avoid
> > this
> > > >>> > > problem.; nested exception is <openjpa-2.2.1-r422266:1396819
> > fatal
> > > >>> > > general error>
> > org.apache.openjpa.persistence.PersistenceException:
> > > >>> > > The last packet successfully received from the server was 84
> 612
> > > 291
> > > >>> > > milliseconds ago.  The last packet sent successfully to the
> > server
> > > was
> > > >>> > > 84 612 291 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 server configured values for client timeouts, or using the
> > > >>> > > Connector/J connection property 'autoReconnect=true' to avoid
> > this
> > > >>> > > problem.
> > > >>> > >       1 org.apache.openjpa.persistence.PersistenceException:
> The
> > > last
> > > >>> > > packet successfully received from the server was 39 315 457
> > > >>> > > milliseconds ago.  The last packet sent successfully to the
> > server
> > > was
> > > >>> > > 39 315 457 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 server configured values for client timeouts, or using the
> > > >>> > > Connector/J connection property 'autoReconnect=true' to avoid
> > this
> > > >>> > > problem.
> > > >>> > >       1 java.net.ConnectException: Connection refused
> > > >>> > >       1  INFO 05-29 14:53:34.184 o.a.o.d.u.d.UsersDao:163
> > > >>> > > [NioProcessor-4] - [getUser] Info: No USER_ID given
> > > >>> > >       1  INFO 05-28 15:46:15.535 o.a.o.d.u.d.UsersDao:163
> > > >>> > > [NioProcessor-14] - [getUser] Info: No USER_ID given
> > > >>> > >       1 FailedObject: select c from User as c where c.user_id =
> > > >>> > > :user_id AND c.deleted <> true [java.lang.String]
> > > >>> > >
> > > >>> >
> > > >>> >
> > > >>> >
> > > >>> > --
> > > >>> > WBR
> > > >>> > Maxim aka solomax
> > > >>> >
> > > >>>
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> WBR
> > > >> Maxim aka solomax
> > >
> >
>
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.co <se...@gmail.com>
>



-- 
WBR
Maxim aka solomax

Re: [ANNOUNCE] upcoming 2.1.1 release

Posted by Alexei Fedotov <al...@gmail.com>.

> Why is this discussion in the private list at all?

That's good thing you have moved to the discussion to the dev list.

--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://dataved.ru/
+7 916 562 8095


On Fri, Jun 7, 2013 at 12:14 AM, seba.wagner@gmail.com
<se...@gmail.com> wrote:
> Hi folks,
>
> I agree on point no 5 with Maxim:
> *auto
> reconnect feature stopped to work long ago*
> => There was never such a feature. It is also rather complicated, cause
> reconnect means that you basically out of sync, and the application has no
> idea what has happened in between, so in theory you could have a reconnect
> after 2 hours and the entire list of participants, screensharing,
> whiteboards, et cetera _everything_ has changed. So the only chance I see
> to realize a *reconnect* is to actually re-login the user into the room and
> load everything from scratch.
>
> But about this entire discussion:
> Why is this discussion in the private list at all?
> There is no *privileged* channel to request or discuss features and bugs.
> Please, lets use the dev list and give everyone that would like to be
> involved the chance to at least read what you have to say.
> @Alexei: For instance anybody reading the Analytics (or error
> infrastructure :)) question now, is missing the context as how this email
> that you wrote was initiated.
>
> Thanks,
> Sebastian
>
>
> 2013/6/7 Maxim Solodovnik <so...@gmail.com>
>
>> 1) video codec was switched in 2.1.0, this is bug fix release I'm sure we
>> shouldn't add major changes. Additionally we will need to use h264 in
>> 3.0/3.1 since it is html5 compatible.
>>
>> 2) this behavior was not changed since 2.0. Please file an issue (better
>> with patch) if you feel this need to be changed. (I would add configuration
>> value default_gain with default value == 50)
>>
>> 3) I'll doublecheck
>>
>> 4) according to VOTE rules every user voting for release must perform these
>> tests
>>
>> 5) I would vote for adding NOTE regarding flash version to release notes of
>> 2.1.1 and alert to 3.0 (on room enter). Actually auto reconnect works as
>> before .... it is just don't reconnect into room :)
>> You can file JIRA issue (better with patch), but to be fair I don't really
>> like such "last minute" changes. The release was announced long time ago
>> and I feel we should close this branch and focus on 3.0
>>  On Jun 6, 2013 7:23 PM, "Alexei Fedotov" <al...@gmail.com>
>> wrote:
>>
>> > Maxim, I've looked through the changes:
>> > https://gist.github.com/leshikus/5720534
>> > most of them relate to log improvements, thus harmless.
>> >
>> > Here are few points on 2.1.1 release:
>> >
>> > 1. We haven't carefully tested H.264. Our customers use H.263 because
>> > H.264 didn't work well for them. H,254 is a default codec for a new
>> > release. Won't this be a problem?
>> >
>> > 2. There are hardcoded microphone settings for silence level, gain,
>> > etc. From the other side I noticed that for the new release microphone
>> > sensitivity is low, and one needs to set the sensitivity bar to the
>> > maximum every time to get it to normal. Or this can be also related to
>> > codec.
>> >
>> > 3. There are several places which incorrectly refer to "2.1.0" and
>> > "2.0". The only place where the release is correct is a build file.
>> >
>> > 4. Who will volunteer to pass all tests for the new release,
>> > xdocs/ManualTesting.xml?
>> >
>> > 5. Our users believe that reliability is most important part of
>> > conferences. The last flash version does not work well, and auto
>> > reconnect feature stopped to work long ago. How this can be addressed?
>> > Should a flash version check be added (against flash 11.6 and 11.7),
>> > and auto reconnect fixed?
>> >
>> > --
>> > With best regards / с наилучшими пожеланиями,
>> > Alexei Fedotov / Алексей Федотов,
>> > http://dataved.ru/
>> > +7 916 562 8095
>> >
>> >
>> > On Thu, Jun 6, 2013 at 1:42 PM, Alexei Fedotov <alexei.fedotov@gmail.com
>> >
>> > wrote:
>> > > Maxim, thanks for the tags!
>> > > --
>> > > With best regards / с наилучшими пожеланиями,
>> > > Alexei Fedotov / Алексей Федотов,
>> > > http://dataved.ru/
>> > > +7 916 562 8095
>> > >
>> > >
>> > > On Mon, Jun 3, 2013 at 2:28 PM, Maxim Solodovnik <solomax666@gmail.com
>> >
>> > wrote:
>> > >> I believe ""Release early, release often" assumes we use one branch"
>> > can be
>> > >> followed with any number of branches :)
>> > >>
>> > >>>> "It is uncool when users come to support engineers"
>> > >> I currently feel I'm the only support engineer :)
>> > >>
>> > >>>> Don't expect it become easier with html5
>> > >> I DO expect!, and things are MUCH easier with HTML5 :)
>> > >>
>> > >>>> How to get 2.1 code?
>> > >> http://svn.apache.org/repos/asf/openmeetings/tags/2.1RC3/
>> > >>
>> > >>>> How to get 2.1.1 code?
>> > >> https://svn.apache.org/repos/asf/openmeetings/branches/2.1/
>> > >>
>> > >>>> Were all these mentioned fixes ported to 3.0 (taking into account
>> how
>> > many
>> > >> times I get no for particular fix, it would be surprising and great to
>> > get
>> > >> yes)?
>> > >> I'm not sure what do you mean by "all these mentioned fixes", all
>> fixes
>> > >> made by me are in both branches :)
>> > >>
>> > >>
>> > >>
>> > >>
>> > >>
>> > >> On Mon, Jun 3, 2013 at 5:06 PM, Alexei Fedotov <
>> > alexei.fedotov@gmail.com>wrote:
>> > >>
>> > >>> Just one comment. "Release early, release often" assumes we use one
>> > branch,
>> > >>> where we fix errors quickly. Having two branches gives us the
>> expected
>> > >>> result that developers care less about users when develop in their
>> > >>> development branch. When something is released, developers switch to
>> a
>> > new
>> > >>> develioment branch and continue being cool and creative.
>> > >>>
>> > >>> It is uncool when users come to support engineers and they feed them
>> > with
>> > >>> tweaks and workarounds. You won't imagine the quirkiness of
>> workarounds
>> > >>> used to demonstrate a SIP video integration.
>> > >>>
>> > >>> Everyone wants to fix bugs when they are easy to reproduce. Most of
>> > them
>> > >>> are not due to the fact that openmeetings has a lot of unreliable
>> > >>> technologies at its base.
>> > >>>
>> > >>> Don't expect it become easier with html5. Contrary, we will get own
>> > >>> problems for each browser. That's why testing infrastructure is
>> > important
>> > >>> before we start releasing things.
>> > >>>
>> > >>> 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
>> > >>> many times I get no for particular fix, it would be surprising and
>> > great to
>> > >>> get yes)?
>> > >>> 02.06.2013 15:06 пользователь "George Kirkham" <
>> gkirkham@co2crc.com.au
>> > >
>> > >>> написал:
>> > >>>
>> > >>> > Hi,
>> > >>> >
>> > >>> > My apologies, I had thought that 2.1.1 had been released.
>> > >>> >
>> > >>> > It would be 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).
>> > >>> >
>> > >>> > The main point is to have;
>> > >>> >  a) a stable released version for production use. The version would
>> > be
>> > >>> > used for production while new features are prepared and fixed in
>> the
>> > >>> > 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 still applicable).
>> > >>> >
>> > >>> > b) a development version to which new features are added, bug fixes
>> > for
>> > >>> > issues discovered in production.  Full testing should be performed
>> > often,
>> > >>> > and at least any time a new feature is added.
>> > >>> >
>> > >>> > At some point, additional features are put on hold, a full testing
>> > >>> > completed, and then the development version can be released to
>> > update the
>> > >>> > production version, after which the development version is
>> > incremented
>> > >>> and
>> > >>> > the cycle continues, the development version is updated with new
>> > >>> features.
>> > >>> >
>> > >>> > One question I would have, do we have a test procedure (document)
>> > that
>> > >>> > lists all features to be tested?  Such a test procedure can be used
>> > to
>> > >>> test
>> > >>> > a version as it is prepared for production release, and after any
>> > time
>> > >>> that
>> > >>> > bug fixes are applied to the production version.   If we have such
>> a
>> > >>> > document, I would suggest it is not complete, as at times I have
>> seen
>> > >>> > issues that are obvious and have not been removed.
>> > >>> >
>> > >>> > Thanks,
>> > >>> >
>> > >>> > George Kirkham
>> > >>> >
>> > >>> >
>> > >>> > -----Original Message-----
>> > >>> > From: Maxim Solodovnik [mailto:solomax666@gmail.com]
>> > >>> > Sent: Sunday, 2 June 2013 12:30 PM
>> > >>> > To: private@openmeetings.apache.org
>> > >>> > Subject: Re: [ANNOUNCE] upcoming 2.1.1 release
>> > >>> >
>> > >>> > I would vote for 2.1.1 release because:
>> > >>> > 1) 17 issues were fixed: 1 blocker, 1 critical, 9 major.
>> > >>> > 2) logging was improved: there is currently trivial way to get the
>> > exact
>> > >>> > OM version
>> > >>> > 3) 3.0 is not ready yet
>> > >>> > 4) "release early, release often" strategy
>> > >>> >
>> > >>> > PS your grep containing network related issues "Connection
>> refused",
>> > "not
>> > >>> > Authenticated", "Broken pipe" is not very helpful
>> > >>> >
>> > >>> >
>> > >>> > On Sun, Jun 2, 2013 at 1:01 AM, Alexei Fedotov <
>> > alexei.fedotov@gmail.com
>> > >>> > >wrote:
>> > >>> >
>> > >>> > > There are two possible options.
>> > >>> > >
>> > >>> > > 1. Test heavily and ship 2.1.1 release.
>> > >>> > > 2. Test heavily and ship 3.0 release instead.
>> > >>> > > 3. Ship 3.0 pre-release without heavy testing.
>> > >>> > >
>> > >>> > > Why should we bother about testing in 2.1.1? Haven't we just
>> > improved
>> > >>> > > a few things? We don't actually know if we have improved things.
>> > Any
>> > >>> > > change have a risk of breaking something.
>> > >>> > >
>> > >>> > > My suggestion is to have testing infrastructure implemented, this
>> > >>> > > would help in testing. This will provide feedback. I prefer
>> option
>> > >>> > > (2), or (3) because (1) is a waste of heavy testing effort. We
>> > don't
>> > >>> > > have enough resources to test two branches thoroughly.
>> > >>> > >
>> > >>> > > I constantly get suggestions (the last one from you one Friday),
>> > like
>> > >>> > > let's have a low quality development branch, where we will
>> > progress,
>> > >>> > > and be creative, and let's have someone to produce reliable
>> > branches
>> > >>> > > from these development branches. For people in a role of support
>> > >>> > > engineers it's hard. That's another reason why I prefer (2) or
>> (3)
>> > to
>> > >>> > > (1).
>> > >>> > >
>> > >>> > > BTW, here is start of the error log in our 2.1.1 installation.
>> One
>> > can
>> > >>> > > start fixing existing problems, if we want a release.
>> > >>> > >
>> > >>> > >     45 at
>> > >>> > >
>> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.ja
>> > >>> > > va:99) [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > >>> > >      45 at
>> > >>> > >
>> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValv
>> > >>> > > e.java:118) [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
>> > >>> > >      42 Caused by: java.net.SocketException: Broken pipe
>> > >>> > >      42 at
>> > >>> > >
>> > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:
>> > >>> > > 62)
>> > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > >>> > >      42 at
>> > >>> > >
>> > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:
>> > >>> > > 136)
>> > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > >>> > >      42 at
>> > >>> > >
>> > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:
>> > >>> > > 110)
>> > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > >>> > >      42 at
>> > >>> > >
>> > org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionar
>> > >>> > > y.java:4918)
>> > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > >>> > >      42 at
>> > >>> > >
>> > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958
>> > >>> > > )
>> > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > >>> > >      42 at
>> > >>> > >
>> > org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManag
>> > >>> > > er.java:971)
>> > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
>> > >>> > >      42 at java.net.SocketOutputStream.socketWrite0(Native
>> Method)
>> > >>> > > ~[na:1.6.0_27]
>> > >>> > >      42 at
>> > >>> > >
>> > com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:11
>> > >>> > > 17) ~[mysql-connector-java-jar-5.1.22.jar:na]
>> > >>> > >      42 at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
>> > >>> > > ~[mysql-connector-java-jar-5.1.22.jar:na]
>> > >>> > >      32 at
>> > >>> > > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> > >>> > > Method) ~[na:1.6.0_27]
>> > >>> > >      21 at
>> > >>> > >
>> > org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransact
>> > >>> > > ionManager.java:516)
>> > >>> > > ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > >>> > >      21 at
>> > >>> > >
>> > org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccess
>> > >>> > > ExceptionIfPossible(EntityManagerFactoryUtils.java:326)
>> > >>> > > ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > >>> > >      21 at
>> > >>> > >
>> > org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPoss
>> > >>> > > ible(DefaultJpaDialect.java:120)
>> > >>> > > ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
>> > >>> > >      19 FailedObject: select c from Sessiondata as c where
>> > >>> > > c.session_id LIKE :session_id [java.lang.String]
>> > >>> > >      16 java.lang.NullPointerException: null
>> > >>> > >      12 at
>> > >>> > >
>> > org.apache.openmeetings.remote.ConferenceService.getRoomsByOrganisatio
>> > >>> > > nWithoutType(ConferenceService.java:147)
>> > >>> > > ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
>> > >>> > >      10 at
>> > >>> > > sun.reflect.GeneratedConstructorAccessor283.newInstance(Unknown
>> > >>> > > Source) ~[na:na]
>> > >>> > >       4 at
>> > >>> > >
>> > org.apache.openmeetings.remote.red5.ScopeApplicationAdapter.roomLeaveB
>> > >>> > > yScope(ScopeApplicationAdapter.java:564)
>> > >>> > > [openmeetings-2.1.1-SNAPSHOT.jar:na]
>> > >>> > >       2 java.lang.Exception: not Authenticated
>> > >>> > >       2 ERROR 05-28 20:44:56.425 o.a.o.r.WhiteBoardService:408
>> > >>> > > [NioProcessor-6] - WhiteboardSyncLockObject not found for this
>> > Client
>> > >>> > > {}
>> > >>> > >       2 ERROR 05-28 20:44:56.423 o.a.o.r.WhiteBoardService:408
>> > >>> > > [NioProcessor-6] - WhiteboardSyncLockObject not found for this
>> > Client
>> > >>> > > {}
>> > >>> > >       2 Caused by:
>> > >>> > > com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last
>> > >>> > > packet successfully received from the server was 84 612 291
>> > >>> > > milliseconds ago.  The last packet sent successfully to the
>> server
>> > was
>> > >>> > > 84 612 291 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 server configured values for client timeouts, or using the
>> > >>> > > Connector/J connection property 'autoReconnect=true' to avoid
>> this
>> > >>> > > problem.
>> > >>> > >       2 at
>> > >>> > >
>> > org.apache.openmeetings.axis.services.FileWebService.getFileExplorerBy
>> > >>> > > RoomSelf(FileWebService.java:728)
>> > >>> > > ~[openmeetings-WebService-2.1.1-SNAPSHOT.jar:na]
>> > >>> > >       1 org.springframework.orm.jpa.JpaSystemException: The last
>> > >>> > > packet successfully received from the server was 84 612 291
>> > >>> > > milliseconds ago.  The last packet sent successfully to the
>> server
>> > was
>> > >>> > > 84 612 291 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 server configured values for client timeouts, or using the
>> > >>> > > Connector/J connection property 'autoReconnect=true' to avoid
>> this
>> > >>> > > problem.; nested exception is <openjpa-2.2.1-r422266:1396819
>> fatal
>> > >>> > > general error>
>> org.apache.openjpa.persistence.PersistenceException:
>> > >>> > > The last packet successfully received from the server was 84 612
>> > 291
>> > >>> > > milliseconds ago.  The last packet sent successfully to the
>> server
>> > was
>> > >>> > > 84 612 291 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 server configured values for client timeouts, or using the
>> > >>> > > Connector/J connection property 'autoReconnect=true' to avoid
>> this
>> > >>> > > problem.
>> > >>> > >       1 org.apache.openjpa.persistence.PersistenceException: The
>> > last
>> > >>> > > packet successfully received from the server was 39 315 457
>> > >>> > > milliseconds ago.  The last packet sent successfully to the
>> server
>> > was
>> > >>> > > 39 315 457 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 server configured values for client timeouts, or using the
>> > >>> > > Connector/J connection property 'autoReconnect=true' to avoid
>> this
>> > >>> > > problem.
>> > >>> > >       1 java.net.ConnectException: Connection refused
>> > >>> > >       1  INFO 05-29 14:53:34.184 o.a.o.d.u.d.UsersDao:163
>> > >>> > > [NioProcessor-4] - [getUser] Info: No USER_ID given
>> > >>> > >       1  INFO 05-28 15:46:15.535 o.a.o.d.u.d.UsersDao:163
>> > >>> > > [NioProcessor-14] - [getUser] Info: No USER_ID given
>> > >>> > >       1 FailedObject: select c from User as c where c.user_id =
>> > >>> > > :user_id AND c.deleted <> true [java.lang.String]
>> > >>> > >
>> > >>> >
>> > >>> >
>> > >>> >
>> > >>> > --
>> > >>> > WBR
>> > >>> > Maxim aka solomax
>> > >>> >
>> > >>>
>> > >>
>> > >>
>> > >>
>> > >> --
>> > >> WBR
>> > >> Maxim aka solomax
>> >
>>
>
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.co <se...@gmail.com>

Re: [ANNOUNCE] upcoming 2.1.1 release

Posted by "seba.wagner@gmail.com" <se...@gmail.com>.

Hi folks,

I agree on point no 5 with Maxim:
*auto
reconnect feature stopped to work long ago*
=> There was never such a feature. It is also rather complicated, cause
reconnect means that you basically out of sync, and the application has no
idea what has happened in between, so in theory you could have a reconnect
after 2 hours and the entire list of participants, screensharing,
whiteboards, et cetera _everything_ has changed. So the only chance I see
to realize a *reconnect* is to actually re-login the user into the room and
load everything from scratch.

But about this entire discussion:
Why is this discussion in the private list at all?
There is no *privileged* channel to request or discuss features and bugs.
Please, lets use the dev list and give everyone that would like to be
involved the chance to at least read what you have to say.
@Alexei: For instance anybody reading the Analytics (or error
infrastructure :)) question now, is missing the context as how this email
that you wrote was initiated.

Thanks,
Sebastian


2013/6/7 Maxim Solodovnik <so...@gmail.com>

> 1) video codec was switched in 2.1.0, this is bug fix release I'm sure we
> shouldn't add major changes. Additionally we will need to use h264 in
> 3.0/3.1 since it is html5 compatible.
>
> 2) this behavior was not changed since 2.0. Please file an issue (better
> with patch) if you feel this need to be changed. (I would add configuration
> value default_gain with default value == 50)
>
> 3) I'll doublecheck
>
> 4) according to VOTE rules every user voting for release must perform these
> tests
>
> 5) I would vote for adding NOTE regarding flash version to release notes of
> 2.1.1 and alert to 3.0 (on room enter). Actually auto reconnect works as
> before .... it is just don't reconnect into room :)
> You can file JIRA issue (better with patch), but to be fair I don't really
> like such "last minute" changes. The release was announced long time ago
> and I feel we should close this branch and focus on 3.0
>  On Jun 6, 2013 7:23 PM, "Alexei Fedotov" <al...@gmail.com>
> wrote:
>
> > Maxim, I've looked through the changes:
> > https://gist.github.com/leshikus/5720534
> > most of them relate to log improvements, thus harmless.
> >
> > Here are few points on 2.1.1 release:
> >
> > 1. We haven't carefully tested H.264. Our customers use H.263 because
> > H.264 didn't work well for them. H,254 is a default codec for a new
> > release. Won't this be a problem?
> >
> > 2. There are hardcoded microphone settings for silence level, gain,
> > etc. From the other side I noticed that for the new release microphone
> > sensitivity is low, and one needs to set the sensitivity bar to the
> > maximum every time to get it to normal. Or this can be also related to
> > codec.
> >
> > 3. There are several places which incorrectly refer to "2.1.0" and
> > "2.0". The only place where the release is correct is a build file.
> >
> > 4. Who will volunteer to pass all tests for the new release,
> > xdocs/ManualTesting.xml?
> >
> > 5. Our users believe that reliability is most important part of
> > conferences. The last flash version does not work well, and auto
> > reconnect feature stopped to work long ago. How this can be addressed?
> > Should a flash version check be added (against flash 11.6 and 11.7),
> > and auto reconnect fixed?
> >
> > --
> > With best regards / с наилучшими пожеланиями,
> > Alexei Fedotov / Алексей Федотов,
> > http://dataved.ru/
> > +7 916 562 8095
> >
> >
> > On Thu, Jun 6, 2013 at 1:42 PM, Alexei Fedotov <alexei.fedotov@gmail.com
> >
> > wrote:
> > > Maxim, thanks for the tags!
> > > --
> > > With best regards / с наилучшими пожеланиями,
> > > Alexei Fedotov / Алексей Федотов,
> > > http://dataved.ru/
> > > +7 916 562 8095
> > >
> > >
> > > On Mon, Jun 3, 2013 at 2:28 PM, Maxim Solodovnik <solomax666@gmail.com
> >
> > wrote:
> > >> I believe ""Release early, release often" assumes we use one branch"
> > can be
> > >> followed with any number of branches :)
> > >>
> > >>>> "It is uncool when users come to support engineers"
> > >> I currently feel I'm the only support engineer :)
> > >>
> > >>>> Don't expect it become easier with html5
> > >> I DO expect!, and things are MUCH easier with HTML5 :)
> > >>
> > >>>> How to get 2.1 code?
> > >> http://svn.apache.org/repos/asf/openmeetings/tags/2.1RC3/
> > >>
> > >>>> How to get 2.1.1 code?
> > >> https://svn.apache.org/repos/asf/openmeetings/branches/2.1/
> > >>
> > >>>> Were all these mentioned fixes ported to 3.0 (taking into account
> how
> > many
> > >> times I get no for particular fix, it would be surprising and great to
> > get
> > >> yes)?
> > >> I'm not sure what do you mean by "all these mentioned fixes", all
> fixes
> > >> made by me are in both branches :)
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On Mon, Jun 3, 2013 at 5:06 PM, Alexei Fedotov <
> > alexei.fedotov@gmail.com>wrote:
> > >>
> > >>> Just one comment. "Release early, release often" assumes we use one
> > branch,
> > >>> where we fix errors quickly. Having two branches gives us the
> expected
> > >>> result that developers care less about users when develop in their
> > >>> development branch. When something is released, developers switch to
> a
> > new
> > >>> develioment branch and continue being cool and creative.
> > >>>
> > >>> It is uncool when users come to support engineers and they feed them
> > with
> > >>> tweaks and workarounds. You won't imagine the quirkiness of
> workarounds
> > >>> used to demonstrate a SIP video integration.
> > >>>
> > >>> Everyone wants to fix bugs when they are easy to reproduce. Most of
> > them
> > >>> are not due to the fact that openmeetings has a lot of unreliable
> > >>> technologies at its base.
> > >>>
> > >>> Don't expect it become easier with html5. Contrary, we will get own
> > >>> problems for each browser. That's why testing infrastructure is
> > important
> > >>> before we start releasing things.
> > >>>
> > >>> 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
> > >>> many times I get no for particular fix, it would be surprising and
> > great to
> > >>> get yes)?
> > >>> 02.06.2013 15:06 пользователь "George Kirkham" <
> gkirkham@co2crc.com.au
> > >
> > >>> написал:
> > >>>
> > >>> > Hi,
> > >>> >
> > >>> > My apologies, I had thought that 2.1.1 had been released.
> > >>> >
> > >>> > It would be 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).
> > >>> >
> > >>> > The main point is to have;
> > >>> >  a) a stable released version for production use. The version would
> > be
> > >>> > used for production while new features are prepared and fixed in
> the
> > >>> > 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 still applicable).
> > >>> >
> > >>> > b) a development version to which new features are added, bug fixes
> > for
> > >>> > issues discovered in production.  Full testing should be performed
> > often,
> > >>> > and at least any time a new feature is added.
> > >>> >
> > >>> > At some point, additional features are put on hold, a full testing
> > >>> > completed, and then the development version can be released to
> > update the
> > >>> > production version, after which the development version is
> > incremented
> > >>> and
> > >>> > the cycle continues, the development version is updated with new
> > >>> features.
> > >>> >
> > >>> > One question I would have, do we have a test procedure (document)
> > that
> > >>> > lists all features to be tested?  Such a test procedure can be used
> > to
> > >>> test
> > >>> > a version as it is prepared for production release, and after any
> > time
> > >>> that
> > >>> > bug fixes are applied to the production version.   If we have such
> a
> > >>> > document, I would suggest it is not complete, as at times I have
> seen
> > >>> > issues that are obvious and have not been removed.
> > >>> >
> > >>> > Thanks,
> > >>> >
> > >>> > George Kirkham
> > >>> >
> > >>> >
> > >>> > -----Original Message-----
> > >>> > From: Maxim Solodovnik [mailto:solomax666@gmail.com]
> > >>> > Sent: Sunday, 2 June 2013 12:30 PM
> > >>> > To: private@openmeetings.apache.org
> > >>> > Subject: Re: [ANNOUNCE] upcoming 2.1.1 release
> > >>> >
> > >>> > I would vote for 2.1.1 release because:
> > >>> > 1) 17 issues were fixed: 1 blocker, 1 critical, 9 major.
> > >>> > 2) logging was improved: there is currently trivial way to get the
> > exact
> > >>> > OM version
> > >>> > 3) 3.0 is not ready yet
> > >>> > 4) "release early, release often" strategy
> > >>> >
> > >>> > PS your grep containing network related issues "Connection
> refused",
> > "not
> > >>> > Authenticated", "Broken pipe" is not very helpful
> > >>> >
> > >>> >
> > >>> > On Sun, Jun 2, 2013 at 1:01 AM, Alexei Fedotov <
> > alexei.fedotov@gmail.com
> > >>> > >wrote:
> > >>> >
> > >>> > > There are two possible options.
> > >>> > >
> > >>> > > 1. Test heavily and ship 2.1.1 release.
> > >>> > > 2. Test heavily and ship 3.0 release instead.
> > >>> > > 3. Ship 3.0 pre-release without heavy testing.
> > >>> > >
> > >>> > > Why should we bother about testing in 2.1.1? Haven't we just
> > improved
> > >>> > > a few things? We don't actually know if we have improved things.
> > Any
> > >>> > > change have a risk of breaking something.
> > >>> > >
> > >>> > > My suggestion is to have testing infrastructure implemented, this
> > >>> > > would help in testing. This will provide feedback. I prefer
> option
> > >>> > > (2), or (3) because (1) is a waste of heavy testing effort. We
> > don't
> > >>> > > have enough resources to test two branches thoroughly.
> > >>> > >
> > >>> > > I constantly get suggestions (the last one from you one Friday),
> > like
> > >>> > > let's have a low quality development branch, where we will
> > progress,
> > >>> > > and be creative, and let's have someone to produce reliable
> > branches
> > >>> > > from these development branches. For people in a role of support
> > >>> > > engineers it's hard. That's another reason why I prefer (2) or
> (3)
> > to
> > >>> > > (1).
> > >>> > >
> > >>> > > BTW, here is start of the error log in our 2.1.1 installation.
> One
> > can
> > >>> > > start fixing existing problems, if we want a release.
> > >>> > >
> > >>> > >     45 at
> > >>> > >
> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.ja
> > >>> > > va:99) [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >>> > >      45 at
> > >>> > >
> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValv
> > >>> > > e.java:118) [tomcat-embed-core-jar-7.0.34.jar:7.0.34]
> > >>> > >      42 Caused by: java.net.SocketException: Broken pipe
> > >>> > >      42 at
> > >>> > >
> > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:
> > >>> > > 62)
> > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >>> > >      42 at
> > >>> > >
> > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:
> > >>> > > 136)
> > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >>> > >      42 at
> > >>> > >
> > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:
> > >>> > > 110)
> > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >>> > >      42 at
> > >>> > >
> > org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionar
> > >>> > > y.java:4918)
> > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >>> > >      42 at
> > >>> > >
> > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958
> > >>> > > )
> > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >>> > >      42 at
> > >>> > >
> > org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManag
> > >>> > > er.java:971)
> > >>> > > ~[openjpa-bundle-2.2.1.jar:2.2.1]
> > >>> > >      42 at java.net.SocketOutputStream.socketWrite0(Native
> Method)
> > >>> > > ~[na:1.6.0_27]
> > >>> > >      42 at
> > >>> > >
> > com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:11
> > >>> > > 17) ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >>> > >      42 at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)
> > >>> > > ~[mysql-connector-java-jar-5.1.22.jar:na]
> > >>> > >      32 at
> > >>> > > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > >>> > > Method) ~[na:1.6.0_27]
> > >>> > >      21 at
> > >>> > >
> > org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransact
> > >>> > > ionManager.java:516)
> > >>> > > ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >>> > >      21 at
> > >>> > >
> > org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccess
> > >>> > > ExceptionIfPossible(EntityManagerFactoryUtils.java:326)
> > >>> > > ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >>> > >      21 at
> > >>> > >
> > org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPoss
> > >>> > > ible(DefaultJpaDialect.java:120)
> > >>> > > ~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> > >>> > >      19 FailedObject: select c from Sessiondata as c where
> > >>> > > c.session_id LIKE :session_id [java.lang.String]
> > >>> > >      16 java.lang.NullPointerException: null
> > >>> > >      12 at
> > >>> > >
> > org.apache.openmeetings.remote.ConferenceService.getRoomsByOrganisatio
> > >>> > > nWithoutType(ConferenceService.java:147)
> > >>> > > ~[openmeetings-2.1.1-SNAPSHOT.jar:na]
> > >>> > >      10 at
> > >>> > > sun.reflect.GeneratedConstructorAccessor283.newInstance(Unknown
> > >>> > > Source) ~[na:na]
> > >>> > >       4 at
> > >>> > >
> > org.apache.openmeetings.remote.red5.ScopeApplicationAdapter.roomLeaveB
> > >>> > > yScope(ScopeApplicationAdapter.java:564)
> > >>> > > [openmeetings-2.1.1-SNAPSHOT.jar:na]
> > >>> > >       2 java.lang.Exception: not Authenticated
> > >>> > >       2 ERROR 05-28 20:44:56.425 o.a.o.r.WhiteBoardService:408
> > >>> > > [NioProcessor-6] - WhiteboardSyncLockObject not found for this
> > Client
> > >>> > > {}
> > >>> > >       2 ERROR 05-28 20:44:56.423 o.a.o.r.WhiteBoardService:408
> > >>> > > [NioProcessor-6] - WhiteboardSyncLockObject not found for this
> > Client
> > >>> > > {}
> > >>> > >       2 Caused by:
> > >>> > > com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last
> > >>> > > packet successfully received from the server was 84 612 291
> > >>> > > milliseconds ago.  The last packet sent successfully to the
> server
> > was
> > >>> > > 84 612 291 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 server configured values for client timeouts, or using the
> > >>> > > Connector/J connection property 'autoReconnect=true' to avoid
> this
> > >>> > > problem.
> > >>> > >       2 at
> > >>> > >
> > org.apache.openmeetings.axis.services.FileWebService.getFileExplorerBy
> > >>> > > RoomSelf(FileWebService.java:728)
> > >>> > > ~[openmeetings-WebService-2.1.1-SNAPSHOT.jar:na]
> > >>> > >       1 org.springframework.orm.jpa.JpaSystemException: The last
> > >>> > > packet successfully received from the server was 84 612 291
> > >>> > > milliseconds ago.  The last packet sent successfully to the
> server
> > was
> > >>> > > 84 612 291 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 server configured values for client timeouts, or using the
> > >>> > > Connector/J connection property 'autoReconnect=true' to avoid
> this
> > >>> > > problem.; nested exception is <openjpa-2.2.1-r422266:1396819
> fatal
> > >>> > > general error>
> org.apache.openjpa.persistence.PersistenceException:
> > >>> > > The last packet successfully received from the server was 84 612
> > 291
> > >>> > > milliseconds ago.  The last packet sent successfully to the
> server
> > was
> > >>> > > 84 612 291 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 server configured values for client timeouts, or using the
> > >>> > > Connector/J connection property 'autoReconnect=true' to avoid
> this
> > >>> > > problem.
> > >>> > >       1 org.apache.openjpa.persistence.PersistenceException: The
> > last
> > >>> > > packet successfully received from the server was 39 315 457
> > >>> > > milliseconds ago.  The last packet sent successfully to the
> server
> > was
> > >>> > > 39 315 457 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 server configured values for client timeouts, or using the
> > >>> > > Connector/J connection property 'autoReconnect=true' to avoid
> this
> > >>> > > problem.
> > >>> > >       1 java.net.ConnectException: Connection refused
> > >>> > >       1  INFO 05-29 14:53:34.184 o.a.o.d.u.d.UsersDao:163
> > >>> > > [NioProcessor-4] - [getUser] Info: No USER_ID given
> > >>> > >       1  INFO 05-28 15:46:15.535 o.a.o.d.u.d.UsersDao:163
> > >>> > > [NioProcessor-14] - [getUser] Info: No USER_ID given
> > >>> > >       1 FailedObject: select c from User as c where c.user_id =
> > >>> > > :user_id AND c.deleted <> true [java.lang.String]
> > >>> > >
> > >>> >
> > >>> >
> > >>> >
> > >>> > --
> > >>> > WBR
> > >>> > Maxim aka solomax
> > >>> >
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> WBR
> > >> Maxim aka solomax
> >
>



-- 
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.co <se...@gmail.com>

Re: [ANNOUNCE] upcoming 2.1.1 release

Posted by Alexei Fedotov <al...@gmail.com>.

I remind that anyone who vote for release have to install and test it.
Our users need quality.
--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://dataved.ru/
+7 916 562 8095


On Tue, May 21, 2013 at 3:55 PM, Maxim Solodovnik <so...@gmail.com> wrote:
> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%20%222.1.1%20Apache%20Release%22%20AND%20project%20%3D%20OPENMEETINGS
>
>
> On Tue, May 21, 2013 at 6:52 PM, George Kirkham <gk...@co2crc.com.au>
> wrote:
>>
>> OM 2.1.1 release in a day or two, sounds excellent.
>>
>>
>>
>> Would be curious what fixes would be in the release.
>>
>>
>>
>> Thanks to everyone involved in the work,
>>
>>
>>
>> George Kirkham
>>
>>
>>
>>
>>
>> From: Maxim Solodovnik [mailto:solomax666@gmail.com]
>> Sent: Tuesday, 21 May 2013 7:57 PM
>> To: Openmeetings user-list; dev
>> Subject: [ANNOUNCE] upcoming 2.1.1 release
>>
>>
>>
>> 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
>
>
>
>
> --
> WBR
> Maxim aka solomax

Re: [ANNOUNCE] upcoming 2.1.1 release

Posted by Maxim Solodovnik <so...@gmail.com>.

https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%20%222.1.1%20Apache%20Release%22%20AND%20project%20%3D%20OPENMEETINGS


On Tue, May 21, 2013 at 6:52 PM, George Kirkham <gk...@co2crc.com.au>wrote:

> OM 2.1.1 release in a day or two, sounds excellent. ****
>
> ** **
>
> Would be curious what fixes would be in the release.****
>
> ** **
>
> Thanks to everyone involved in the work,****
>
> ** **
>
> George Kirkham****
>
> ** **
>
> ** **
>
> *From:* Maxim Solodovnik [mailto:solomax666@gmail.com]
> *Sent:* Tuesday, 21 May 2013 7:57 PM
> *To:* Openmeetings user-list; dev
> *Subject:* [ANNOUNCE] upcoming 2.1.1 release****
>
> ** **
>
> 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 ****
>



-- 
WBR
Maxim aka solomax

RE: [ANNOUNCE] upcoming 2.1.1 release

Posted by George Kirkham <gk...@co2crc.com.au>.

OM 2.1.1 release in a day or two, sounds excellent. 

 

Would be curious what fixes would be in the release.

 

Thanks to everyone involved in the work,

 

George Kirkham

 

 

From: Maxim Solodovnik [mailto:solomax666@gmail.com] 
Sent: Tuesday, 21 May 2013 7:57 PM
To: Openmeetings user-list; dev
Subject: [ANNOUNCE] upcoming 2.1.1 release

 

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