[
https://issues.apache.org/jira/browse/CLOUDSTACK-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573304#comment-13573304
]
ASF subversion and git services commented on CLOUDSTACK-1178:
-------------------------------------------------------------
Commit 18bf69696cf176678132b602bcd3e36500fd6774 in branch refs/heads/4.1 from
[~murali.reddy]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=18bf696 ]
CLOUDSTACK-1178:DB Commit warning logged for every Deploy VM request
removing the regression that introduced premature transaction commit
> 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
>
> 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
