We see a lot of persistence exceptions in the latest ESB packs: org.wso2.carbon.core.persistence.PersistenceException: A transaction is already started. Nested transactions are no longer supported in the new model at org.wso2.carbon.core.persistence.file.ServiceGroupFilePersistenceManager.beginTransaction(ServiceGroupFilePersistenceManager.java:62) at org.wso2.carbon.core.persistence.AbstractPersistenceManager.updateParameter(AbstractPersistenceManager.java:136) at org.wso2.carbon.core.persistence.ServicePersistenceManager.updateServiceParameter(ServicePersistenceManager.java:775) at org.wso2.carbon.core.persistence.ServicePersistenceManager.handleExistingServiceInit(ServicePersistenceManager.java:592) at org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:282) at org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652) at org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406) at org.apache.axis2.engine.AxisConfiguration.addService(AxisConfiguration.java:336) at org.apache.synapse.core.axis2.ProxyService.buildAxisService(ProxyService.java:566) at org.wso2.carbon.mediation.configadmin.ConfigurationUpdater.deployServices(ConfigurationUpdater.java:286)
What does this mean? Things seem to work find in spite of the exceptions though. -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
