AnsweredAssumed Answered

Deleting AFX connectors

Question asked by Sunita Bhat on Sep 19, 2018
Latest reply on Sep 20, 2018 by Sunita Bhat

Like • Show 0 Likes0
Comment • 2

Hello,

Has anyone tried to delete an AFX connector from the UI. Our experience on RSA7 & RSA7.1 has been that UI will let you delete the connector but in the server log we continue to see these messages.

2018-09-19 20:16:08.569 [INFO] com.aveksa.afx.server.manager.deployment.BaseDeploymentManager:153 - Waiting for the ESB to remove connector application directory /home/oracle/AFX/esb/apps/AFX-CONN-tryHR_SFDC_AFX
2018-09-19 20:16:06.568 [INFO] com.aveksa.afx.server.manager.deployment.BaseDeploymentManager:155 - Connector application directory /home/oracle/AFX/esb/apps/AFX-CONN-tryHR_SFDC_AFX still exists. Will check again in 2 seconds. This was attempt #1
2018-09-19 20:16:06.568 [INFO] com.aveksa.afx.server.manager.deployment.BaseDeploymentManager:155 - Connector application directory /home/oracle/AFX/esb/apps/AFX-CONN-tryHR_SFDC_AFX still exists. Will check again in 2 seconds. This was attempt #2

2018-09-19 20:16:06.568 [INFO] com.aveksa.afx.server.manager.deployment.BaseDeploymentManager:155 - Connector application directory /home/oracle/AFX/esb/apps/AFX-CONN-tryHR_SFDC_AFX still exists. Will check again in 2 seconds. This was attempt #3

.........

2018-09-19 20:18:16.651 [WARN] com.aveksa.afx.server.manager.deployment.BaseDeploymentManager:169 - Connector application directory /home/oracle/AFX/esb/apps/AFX-CONN-tryHR_SFDC_AFX still exists. Failed to undeploy connector application AFX-CONN-tryHR_SFDC_AFX
2018-09-19 20:18:16.652 [WARN] com.aveksa.afx.server.manager.deployment.BaseDeploymentManager:202 - Unable to deploy AFX-CONN-tryHR_SFDC_AFX because the existing revision could not be removed.

Wondering if we have to delete the folder in the /home/oracle/AFX/esb/apps.

No one else has this question

Outcomes

2018-09-19 22:01:51.519 [INFO] com.aveksa.afx.server.manager.deployment.BaseDeploymentManager:120 - Successfully stopped application 'AFX-CONN-textxxxx' 2018-09-19 22:01:51.519 [INFO] com.aveksa.afx.server.manager.deployment.BaseDeploymentManager:149 - Deleted connector application anchor file /home/oracle/AFX/esb/apps/AFX-CONN-textxxxx-anchor.txt 2018-09-19 22:01:51.520 [INFO] com.aveksa.afx.server.manager.deployment.BaseDeploymentManager:153 - Waiting for the ESB to remove connector application directory /home/oracle/AFX/esb/apps/AFX-CONN-textxxxx 2018-09-19 22:01:51.520 [INFO] com.aveksa.afx.server.manager.deployment.BaseDeploymentManager:155 - Connector application directory /home/oracle/AFX/esb/apps/AFX-CONN-textxxxx still exists. Will check again in 2 seconds. This was attempt #1 2018-09-19 22:01:53.521 [INFO] com.aveksa.afx.server.manager.deployment.BaseDeploymentManager:155 - Connector application directory /home/oracle/AFX/esb/apps/AFX-CONN-textxxxx still exists. Will check again in 2 seconds. This was attempt #2 2018-09-19 22:01:55.521 [INFO] com.aveksa.afx.server.manager.deployment.BaseDeploymentManager:155 - Connector application directory /home/oracle/AFX/esb/apps/AFX-CONN-textxxxx still exists. Will check again in 2 seconds. This was attempt #3 2018-09-19 22:01:57.522 [INFO] com.aveksa.afx.server.manager.deployment.BaseDeploymentManager:155 - Connector application directory /home/oracle/AFX/esb/apps/AFX-CONN-textxxxx still exists. Will check again in 2 seconds. This was attempt #4 2018-09-19 22:01:59.523 [INFO] com.aveksa.afx.server.manager.deployment.BaseDeploymentManager:165 - Connector application AFX-CONN-textxxxx was successfully undeployed. 2018-09-19 22:01:59.524 [INFO] com.aveksa.afx.server.component.PrimaryResponseProcessorComponent:135 - Connector textxxxx was successfully deleted.

2 Replies

Boris Lekumovich

Sep 19, 2018 10:31 PM

Tried on my 7.1 instance and it was working as expected

Is the AFX in a running mode?

Was the connector in a running mode or deployed mode?

Actions

Sunita Bhat @ Boris Lekumovich on Sep 20, 2018 11:36 AM
Mark Correct
Correct Answer
Boris,
I have seen this happen to both connector in both Deployed and Running state but this particular stack trace is from a connector which was in deployed state.
Like • Show 0 Likes0
Actions