Hi,
On Mon, Mar 26, 2012 at 12:19 PM, Hiranya Jayathilaka <[email protected]>wrote:

>
>
> On Mon, Mar 26, 2012 at 12:11 PM, Kasun Gajasinghe <[email protected]>wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 11:45 AM, Hiranya Jayathilaka 
>> <[email protected]>wrote:
>>
>>> 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.
>>>
>>
>> The way to make sure things work is to restart the server and see whether
>> the changed parameters are still there.
>>
>
> We don't need Axis2 level persistence for proxy services. Synapse has its
> own persistence logic for proxy services, which takes care of saving proxy
> services to the file system.
>

I'm having a concern on this. Does this suggest that proxy services
meta-data are already persisted into file system so that
new persistence model need not handle that?


>
>
>>
>> Does this seen in server startup? If not, please tell me how to reproduce
>> this.
>>
>
> Create a proxy service and then update the ESB configuration from the
> source view.
>
>
>>
>> Thanks,
>> --KasunG
>>
>>
>>>
>>> --
>>> 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
>>>
>>>
>>
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer; WSO2 Inc.; http://wso2.com
>>
>> ,
>> *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe*
>> *
>>  *blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org>
>>
>> *
>> twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>
>>
>> *
>> *
>>
>>
>
>
> --
> 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
>
>


-- 
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

Reply via email to