cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-1178) DB Commit warning logged for every Deploy VM request
Date Thu, 07 Feb 2013 07:45:16 GMT


ASF subversion and git services commented on CLOUDSTACK-1178:

Commit a71fb83c779248f3065a16b3a82bd940e6930496 in branch refs/heads/master from [~murali.reddy]
[;h=a71fb83 ]

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

View raw message