You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Murali Reddy (JIRA)" <ji...@apache.org> on 2013/02/07 09:17:12 UTC
[jira] [Resolved] (CLOUDSTACK-1178) DB Commit warning logged for
every Deploy VM request
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Murali Reddy resolved CLOUDSTACK-1178.
--------------------------------------
Resolution: Fixed
Assignee: Murali Reddy
fixed in both master and 4.1
> DB Commit warning logged for every Deploy VM request
> ----------------------------------------------------
>
> Key: CLOUDSTACK-1178
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1178
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Reporter: Sailaja Mada
> Assignee: Murali Reddy
>
> 1. Configured 4.1 dev environment with latest master code 2. Configured Advanced zone with xen 6.1 as hypervisor 3. Deployed instance with default network offering.
> Observation:
> have observed below warning for every deploy VM request. There is no functional impact but would like to understand if we are making additional DB request to do commit though it’s not required.
> WARN [db.Transaction.Transaction] (9071190@qtp-8057824-32:) txn: Commit called when it is not a transaction: -UserVmManagerImpl.createVirtualMachine:3398-UserVmManagerImpl.createAdvancedVirtualMachine:3096-MethodProxy.invoke:204-Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint:689-ReflectiveMethodInvocation.proceed:150-MethodInvocationProceedingJoinPoint.proceed:80-TransactionContextBuilder.AroundAnyMethod:43-GeneratedMethodAccessor48.invoke:-1-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:616-AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs:621-AbstractAspectJAdvice.invokeAdviceMethod:610
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira