Symptom
During an upgrade using the SUM tool, the deployment hangs although there are no relevant error entries in SUM traces.
The files DEPLOYMENT_RESULTS_XX.LOG show normal state:
Jun 15, 2017 3:10:23 AM [Info ]: Connecting to Deploy Controller on host <hostname> port 5XXXX with user J2EE_ADMIN.
Jun 15, 2017 3:10:23 AM [Info ]: Connect to DeployCOntroller using P4 connection
Only one relevant Warning entry is logged in default trace shortly after the timestamp:
#2.0#2017 06 15 03:10:24:021#+0200#Warning#com.sap.engine.services.rmi_p4.server#
com.sap.ASJ.rmip4.rt0007#BC-JAS-COR-RMT#p4#C0000A36526701C10000000100005675#731599050000000001##com.sap.engine.services.rmi_p4.server#J2EE_GUEST#0##68D2952F516711E7A76C00002B9B50CA#68d2952f516711e7a76c00002b9b50ca##0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##
Processing RMI-P4 request failed. There are no resources to handle the request. This may happen when the load is too big. Increase the P4 request queue size or number of concurrent threads#
Read more...
Environment
AS Java All versions
Product
Keywords
P4, Deployment, deploy, upgrade, SUM, DEPLOYMENT_RESULTS, DEPLOY-MODEL, defaulttrace, RMI-P4 request failed, queue size, ParallelRequests, requestQueueSize, configtool, no relevant logs, no logs, SOLMAN, hangs, hanging, deployment hanging, deployment hangs, upgrade hangs, upgrade hanging, deploy EDEN Model, RMI , KBA , BC-JAS-COR-RMT , RMI, P4, CORBA, IIOP , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , BC-UPG-TLS-TLJ , Upgrade tools for Java , BC-JAS-DPL , Deployment , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.