|Applies To||RSA Product Set: RSA Identity Governance & Lifecycle |
RSA Version/Condition: 6.9.1, (potentially 7.x as yet unconfirmed)
|Issue||RSA Identity Governance & Lifecycle is not accessible and an attempt to stop RSA Identity Governance & Lifecycle results in the following stack trace:|
The aveksaServer.log file ($AVEKSA_HOME/jboss-4.2.2.GA/server/default/deploy/aveksa.ear/aveksa.war/log) has the following port conflict:
Note: This was seen on RSA Identity Governance & Lifecycle 6.9.1 which is End of Product Support (EOPS) but there is no reason to assume this could not happen in current versions. If you suspect you have this issue, please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log file for your specific deployment. The aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.)
|Cause||The error from the aveksaServer.log:|
indicates that the last time the server started it could not bind to port 4444 due to a conflict.
This can be caused by a number of different events, but the specific cause in this case was that a third party script was written to stop RSA Identity Governance & Lifecycle in order to perform backups and the script was not cleanly stopping the application server. This prevented RSA Identity Governance & Lifecycle from starting cleanly as well.
|Resolution||When designing a custom script to stop the RSA Identity Governance & Lifecycle application in order to perform maintenance tasks such as backups, make sure the script is cleanly stopping the application.|
If assistance is needed in creating a custom script to automate shutdown and run administrative tasks, please contact the RSA Professional Services team or RSA Identity Governance & Lifecycle Customer Support who can connect you with the RSA Professional Services team.