Salesforce

How to remove a server from Anypoint Runtime Manager

Printable View
« Go Back

Information

 
Content

GOAL

How to remove a mule server from Anypoint Runtime Manager?

PROCEDURE

To completely remove a server from Anypoint platform please follow these steps:
1. Choose server in Runtime Manager and then click on delete. Note, this step only deletes a server from the UI, but we still need to delete the configuration files from the server.
2. Navigate to <MULE_HOME>/conf and delete these two files when a server is stopped

mule-agent.jks
mule-agent.yml

These two files contain information about Anypoint certificate which is used for secure communication and a server ID and that was stored in the backend database, so if a server is removed from UI it's safe to delete these files.

3. It's enough to complete the first two steps in most of the cases but sometimes you may observe warnings on the next restart of a server
  
WARN 2017-06-09 11:37:19,852 [WrapperListener_start_runner] org.eclipse.jetty.util.component.AbstractLifeCycle: FAILED ServerConnector@6a6eb712{HTTP/1.1}{0.0.0.0:443}: java.net.SocketException: Permission denied
java.net.SocketException: Permission denied
at sun.nio.ch.Net.bind0(Native Method) ~[?:1.8.0_111]
at sun.nio.ch.Net.bind(Net.java:433) ~[?:1.8.0_111]
at sun.nio.ch.Net.bind(Net.java:425) ~[?:1.8.0_111]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) ~[?:1.8.0_111]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) ~[?:1.8.0_111]
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:264) ~[jetty-server-9.0.7.v20131107.jar:9.0.7.v20131107]
at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80) ~[jetty-server-9.0.7.v20131107.jar:9.0.7.v20131107]
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69) ~[jetty-util-9.0.7.v20131107.jar:9.0.7.v20131107]
at com.mulesoft.agent.rest.AgentRestLayer.enable(AgentRestLayer.java:124) ~[?:?]
at com.mulesoft.agent.rest.transport.RestAgentTransport.enableIncomingRequests(RestAgentTransport.java:212) ~[?:?]
at com.mulesoft.agent.AgentTransportManager.enableIncomingRequests(AgentTransportManager.java:115) ~[?:?]
at com.mulesoft.agent.AgentPlugin$1.onAfterStartup(AgentPlugin.java:340) ~[?:?]
at org.mule.module.launcher.MuleDeploymentService.start(MuleDeploymentService.java:140) ~[mule-module-launcher-3.8.2.jar:3.8.2]
at org.mule.module.launcher.MuleContainer.start(MuleContainer.java:172) ~[mule-module-launcher-3.8.2.jar:3.8.2]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_111]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_111]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_111]
at org.mule.module.reboot.MuleContainerWrapper.start(MuleContainerWrapper.java:52) ~[mule-module-boot-ee-3.8.2.jar:3.8.2]
at org.tanukisoftware.wrapper.WrapperManager$11.run(WrapperManager.java:4242) ~[wrapper-3.5.29.jar:3.5.29]
ERROR 2017-06-09 11:37:19,852 [WrapperListener_start_runner] com.mulesoft.agent.AgentTransportManager: Could not enable incoming requests for transport: RestAgentTransport: Unable to start REST http connector. Configuration (host: 0.0.0.0, port: 443, keyStore (alias / file): not configured)

These warnings originating from Mule Agent which is still trying to initialize the RestAgentTransport to connect to Anypoint platform. To solve this issue,

for Mule 3:

navigate to <MULE_HOME>/plugins

for Mule 4

navigate to <MULE_HOME>/server-plugins

and remove mule-agent-plugin after taking a backup.
Attachments
Powered by