Hi Anjana, On Sat, Jun 30, 2012 at 2:55 PM, Anjana Fernando <[email protected]> wrote:
> Hi Prabath, > > On Fri, Jun 29, 2012 at 10:28 AM, Prabath Abeysekera <[email protected]>wrote: > >> Hi Anjana, >> >> On Fri, Jun 29, 2012 at 9:00 AM, Anjana Fernando <[email protected]> wrote: >> >>> Hi, >>> >>> On Thu, Jun 28, 2012 at 8:44 PM, Prabath Abeysekera >>> <[email protected]>wrote: >>> >>>> Hi Supun, >>>> >>>> I ll have a look. >>>> >>> >>> We should remove this component soon, we have the new ndatasource >>> component, and the UI is also finished as I know . So we should just move >>> to that. >>> >> >> Okay. If we're going to deprecate the use of the data-sources component, >> I believe, we might want to formally inform all the product teams who are >> using that component to migrate to ndatasources as part of the release >> effort. Then everybody can focus on testing and other release related >> activities (in which datasources are involved) using the new implementation. >> > > +1, I was actually waiting for the UI to be completed for products which > uses the UI to manage data sources. Products like BPS was already informed > to move into the new component, where they don't use the UI but uses the > configuration file. > I moved to the new component, server starts without a problem, but I see so many exceptions while running the integration tests. I like to sit with you have a closer look at these issues. The tests get successfully run when I move back to the old datasource component. Unless we sort out these issues, we cannot move to the new component. some exceptions: [1] MySQL: Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: Lock wait timeout exceeded; try restarting transaction {prepstmnt 1521328010 DELETE FROM ODE_MESSAGE_EXCHANGE WHERE MESSAGE_EXCHANGE_ID = ? [params=?]} [code=1205, state=41000] at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:247) at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:223) at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingConnectionDecorator.java:72) at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:1162) at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:272) at org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1741) at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:267) at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:118) ... 55 more NestedThrowables: java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055) [2] H2: 2012-07-01 10:43:39,347] INFO {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - NestedThrowables: [2012-07-01 10:43:39,347] INFO {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-140] [2012-07-01 10:43:39,347] INFO {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at org.h2.message.DbException.getJdbcSQLException(DbException.java:327) [2012-07-01 10:43:39,347] INFO {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at org.h2.message.DbException.get(DbException.java:167) Thanks, Waruna > > Cheers, > Anjana. > > >> >> >>> >>> Cheers, >>> Anjana. >>> >>> >>>> >>>> >>>> Regards, >>>> Prabath >>>> >>>> On Thu, Jun 28, 2012 at 7:22 PM, Supun Malinga <[email protected]> wrote: >>>> >>>>> Please have a look, >>>>> [2012-06-28 19:19:01,127] [0] [Application Server]ERROR >>>>> {org.wso2.carbon.datasource.internal.DataSourceServiceComponent} - >>>>> org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to >>>>> obtain the user realm for tenant: 0. >>>>> [2012-06-28 19:19:01,128] [0] [Application Server]ERROR >>>>> {org.wso2.carbon.datasource.internal.DataSourceServiceComponent} - Error >>>>> in retrieving SystemRegistry from Registry Service >>>>> [2012-06-28 19:19:01,168] [0] [Application Server]ERROR >>>>> {org.wso2.carbon.datasource.internal.DataSourceServiceComponent} - >>>>> org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to >>>>> obtain the user realm for tenant: 0. >>>>> [2012-06-28 19:19:01,169] [0] [Application Server]ERROR >>>>> {org.wso2.carbon.datasource.internal.DataSourceServiceComponent} - Error >>>>> in retrieving SystemRegistry from Registry Service >>>>> [2012-06-28 19:19:01,183] [0] [Application Server]ERROR >>>>> {org.wso2.carbon.datasource.internal.DataSourceServiceComponent} - >>>>> org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to >>>>> obtain the user realm for tenant: 0. >>>>> [2012-06-28 19:19:01,184] [0] [Application Server]ERROR >>>>> {org.wso2.carbon.datasource.internal.DataSourceServiceComponent} - Error >>>>> in retrieving SystemRegistry from Registry Service >>>>> [2012-06-28 19:19:01,211] [0] [Application Server]ERROR >>>>> {org.wso2.carbon.datasource.internal.DataSourceServiceComponent} - >>>>> org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to >>>>> obtain the user realm for tenant: 0. >>>>> [2012-06-28 19:19:01,212] [0] [Application Server]ERROR >>>>> {org.wso2.carbon.datasource.internal.DataSourceServiceComponent} - Error >>>>> in retrieving SystemRegistry from Registry Service >>>>> [2012-06-28 19:19:01,434] [0] [Application Server]ERROR >>>>> {org.wso2.carbon.datasource.internal.DataSourceServiceComponent} - >>>>> org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to >>>>> obtain the user realm for tenant: 0. >>>>> [2012-06-28 19:19:01,435] [0] [Application Server]ERROR >>>>> {org.wso2.carbon.datasource.internal.DataSourceServiceComponent} - Error >>>>> in retrieving SystemRegistry from Registry Service >>>>> [2012-06-28 19:19:01,441] [0] [Application Server]ERROR >>>>> {org.wso2.carbon.datasource.internal.DataSourceServiceComponent} - >>>>> org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to >>>>> obtain the user realm for tenant: 0. >>>>> >>>>> thanks, >>>>> -- >>>>> Supun Malinga, >>>>> >>>>> Software Engineer, >>>>> WSO2 Inc. >>>>> http://wso2.com >>>>> http://wso2.org >>>>> email - [email protected] <[email protected]> >>>>> mobile - 071 56 91 321 >>>>> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Prabath Abeysekara >>>> Software Engineer >>>> WSO2 Inc. >>>> Email: [email protected] <[email protected]> >>>> Mobile: +94774171471 >>>> >>>> <http://harshana05.blogspot.com/> >>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Anjana Fernando* >>> Associate Technical Lead >>> WSO2 Inc. | http://wso2.com >>> lean . enterprise . middleware >>> >> >> >> >> -- >> Prabath Abeysekara >> Software Engineer >> WSO2 Inc. >> Email: [email protected] <[email protected]> >> Mobile: +94774171471 >> >> <http://harshana05.blogspot.com/> >> >> > > > -- > *Anjana Fernando* > Associate Technical Lead > WSO2 Inc. | http://wso2.com > lean . enterprise . middleware > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- ------------------------------------------------------------------------- Waruna Ranasinghe Senior Software Engineer, WSO2 Mobile: +94 724 318285 BLOG: http://warunapw.blogspot.com www.wso2.com - "Lean . Enterprise . Middleware"
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
