EM 12c: Enterprise Manager 12c Cloud Control Agent Logs "Upload timed out before completion" Error and High CPU Usage is Observed on the Repository Database Host (Doc ID 1439797.1)

Last updated on DECEMBER 23, 2016

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.1.0 and later
PeopleSoft Enterprise PT PeopleTools - Version 8.54 to 8.54 [Release 8.4]
Information in this document applies to any platform.

Symptoms

An Enterprise Manager 12c Cloud Control Agent is successfully deployed  to a remote host. But Agent upload logs a timeout error:

From AGENT_INST/sysman/log/gcagent.log:

2012-03-08 09:56:18,052 [101:EB9AE1AB:GC.Executor.8 (Ping OMS)] DEBUG - SSL Cipher Suite: SSL_RSA_WITH_RC4_128_MD5
2012-03-08 09:56:31,405 [30:6ADC4389] INFO - >>> Reporting exception: oracle.sysman.emSDK.agent.client.exception.UploadException: Upload timed out before completion.
Number of files to upload before the uploadNow call: 1426, total size (MB): 36.731606
Remaining number of files to upload: 1427, total size (MB): 36.75589 (TIMEOUT) (request id 1) <<<
oracle.sysman.emSDK.agent.client.exception.UploadException: Upload timed out before completion.
Number of files to upload before the uploadNow call: 1426, total size (MB): 36.731606
Remaining number of files to upload: 1427, total size (MB): 36.75589 (TIMEOUT)
at oracle.sysman.gcagent.dispatch.cxl.UploadAction.satisfyRequest(UploadAction.java:68)
at oracle.sysman.gcagent.dispatch.ProcessRequestAction._call(ProcessRequestAction.java:128)
at oracle.sysman.gcagent.dispatch.ProcessRequestAction.call(ProcessRequestAction.java:93)
at oracle.sysman.gcagent.dispatch.InlineDispatchCoordinator.dispatchRequest(InlineDispatchCoordinator.java:223)
at oracle.sysman.gcagent.dispatch.DispatchRequestsAction.call(DispatchRequestsAction.java:76)
at oracle.sysman.gcagent.dispatch.RequestDispatcher.executeRequests(RequestDispatcher.java:1901)
at oracle.sysman.gcagent.dispatch.RequestDispatcher.dispatchRequests(RequestDispatcher.java:735)
at oracle.sysman.gcagent.comm.agent.http.TMClientProtocolServer.onServiceProtocol(TMClientProtocolServer.java:303)
at oracle.sysman.gcagent.comm.agent.http.HTTPRequestHandler.handle(HTTPRequestHandler.java:186)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:933)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:871)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:245)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113)
at org.eclipse.jetty.server.Server.handle(Server.java:330

 

High database CPU usage is observed on repository database.

 

 

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms