Il file EAR di pubblicazione si blocca su WebSphere 8.0

Question

Recentemente alcuni dei nostri progetti sono stati bloccati durante la pubblicazione su WebSphere 8.0 (testati con 8.0.0.5, 8.0.0.6 e 8.0.0.9), ma ciò non accade tutte le volte.

Si tratta di un normale dettagli sull'installazione

Installing... 
If there are enterprise beans in the application, the EJB deployment process can take several minutes. Do not save the configuration until the process completes. 
Check the SystemOut.log on the deployment manager or server where the application is deployed for specific information about the EJB deployment process as it occurs. 
ADMA5016I: Installation of ImagesServerEAR started. 
ADMA5067I: Resource validation for application ImagesServerEAR completed successfully. 
ADMA5058I: Application and module versions are validated with versions of deployment targets. 
ADMA5005I: The application ImagesServerEAR is configured in the WebSphere Application Server repository. 
ADMA5005I: The application ImagesServerEAR is configured in the WebSphere Application Server repository. 
ADMA5081I: The bootstrap address for client module is configured in the WebSphere Application Server repository. 
ADMA5053I: The library references for the installed optional package are created. 
ADMA5005I: The application ImagesServerEAR is configured in the WebSphere Application Server repository. 
ADMA5001I: The application binaries are saved in C:\IBM\WebSphere\AppServer\profiles\AppSrv11\wstemp\92668751\workspace\cells\SRV-CLI-DEVNode11Cell\applications\ImagesServerEAR.ear\ImagesServerEAR.ear 
ADMA5005I: The application ImagesServerEAR is configured in the WebSphere Application Server repository. 
SECJ0400I: Successfully updated the application ImagesServerEAR with the appContextIDForSecurity information. 
ADMA5005I: The application ImagesServerEAR is configured in the WebSphere Application Server repository. 
ADMA5005I: The application ImagesServerEAR is configured in the WebSphere Application Server repository. 
ADMA5113I: Activation plan created successfully. 
ADMA5011I: The cleanup of the temp directory for application ImagesServerEAR is complete. 
ADMA5013I: Application ImagesServerEAR installed successfully. 
Application ImagesServerEAR installed successfully. 
To start the application, first save changes to the master configuration. 
Changes have been made to your local configuration. You can: 
• Save directly to the master configuration. 
• Review changes before saving or discarding. 

Ma quando si blocca l'implementazione, i registri mostrano solo questo

Installing... 
If there are enterprise beans in the application, the EJB deployment process can take several minutes. Do not save the configuration until the process completes. 
Check the SystemOut.log on the deployment manager or server where the application is deployed for specific information about the EJB deployment process as it occurs. 
ADMA5016I: Installation of ImagesServerEAR started. 
ADMA5067I: Resource validation for application ImagesServerEAR completed successfully. 

e la CPU va al 100% in 4 delle 8 core.

Non c'è nient'altro registrato ovunque.

Qualche idea su cosa può causare questo?

Answer 1

risolto questo problema aumentando la quantità della dimensione heap

Answer 2

Aumentare il manager dimensione heap distribuzione andando a:

1. Amministrazione di sistema -> Deployment Manager
2. Server Infrastructure -> Java e Gestione processo -> Definizione processo
3. Proprietà aggiuntive -> Java Virtual Machine

Default La dimensione massima dell'heap è 256 MB per Websphere 8, quindi impostare un valore più elevato, ad es. 512MB.

È inoltre possibile controllare i registri gestore distribuzione qui per confermare che è causa di un errore di heap

was_dir /profiles/autoWasDmgr/logs/dmgr/SystemOut.log