Sangeetha Hariharan created CLOUDSTACK-305:
----------------------------------------------

             Summary: AWS APi - "Rolling back the transaction" seen in 
management server logs , everytime a soap call is made.
                 Key: CLOUDSTACK-305
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-305
             Project: CloudStack
          Issue Type: Bug
          Components: AWSAPI
    Affects Versions: 4.0.0
         Environment: Tested with:
[root@rhel63 ~]# cloud-sccs
Git Revision: 1ead1730b42564036b8d4ad70d96433732c88bf7
Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git

            Reporter: Sangeetha Hariharan
            Assignee: Rajesh Battala


AWS APi - "Rolling back the transaction" seen in management server logs , 
everytime a soap call is made.

Steps to reproduce the problem:
Install management server.
Enable enable.ec2.api global variable and restart management server.

Register a user.

As this user , make soap calls.

Soap calls succeed.
But I see these kinds of rollback statement in management server logs everytime 
we make a soap call.

2012-10-09 15:48:12,875 DEBUG [db.Transaction.Transaction] 
(catalina-exec-int-9:null) Rolling back the transaction: Time = 1 Name =  
-UserCredentialsDaoImpl.getByCertUniqueId:61-DatabaseCallback.intercept:34-AuthenticationHandler.invoke:118-Phase.invoke:318-AxisEngine.invoke:251-AxisEngine.receive:160-HTTPTransportUtils.processHTTPPostRequest:275-AxisServlet.doPost:133-HttpServlet.service:637-HttpServlet.service:717-ApplicationFilterChain.internalDoFilter:290-ApplicationFilterChain.doFilter:206;
 called by 
-Transaction.rollback:887-Transaction.removeUpTo:830-Transaction.close:649-UserCredentialsDaoImpl.getByCertUniqueId:68-DatabaseCallback.intercept:34-AuthenticationHandler.invoke:118-Phase.invoke:318-AxisEngine.invoke:251-AxisEngine.receive:160-HTTPTransportUtils.processHTTPPostRequest:275-AxisServlet.doPost:133-HttpServlet.service:637


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

Reply via email to