org.mule.umo.provider.ConnectorException: There is already a listener registered on this connector on endpointUri: ftp://user2:pass2@ftpserver. Connector that caused exception is: FtpConnector{this=b29562, started=true, initialised=true, name='connector.ftp.0', disposed=false, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=true, supportedProtocols=[ftp], serviceOverrides=null}

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

Do you know how to solve this issue? Write a tip to help other users and build your expert profile.

Solutions on the web

via MuleSoft JIRA by Milen Dyankov, 1 year ago
There is already a listener registered on this connector on endpointUri: ftp://user2:pass2@ftpserver. Connector that caused exception is: FtpConnector{this=b29562, started=true, initialised=true, name='connector.ftp.0', disposed=false, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=true, supportedProtocols=[ftp], serviceOverrides=null}
via MuleSoft JIRA by Milen Dyankov, 1 year ago
There is already a listener registered on this connector on endpointUri: ftp://user2:pass2@ftpserver. Connector that caused exception is: FtpConnector{this=b29562, started=true, initialised=true, name='connector.ftp.0', disposed=false, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=true, supportedProtocols=[ftp], serviceOverrides=null}
via Google Groups by John Krewson, 2 months ago
Connector that caused exception is: or g.mule.providers.vm.VMConnector@1950198
via Google Groups by antonix, 2 months ago
Connector that caused exception is: org.mule.providers.jdbc.JdbcConnector@c2cfe1
via Mirth Project by john voigt, 1 year ago
There is already a listener registered on this connector on endpointUri: jdbc://query. Connector that caused exception is: com.mirth.connect.connectors.jdbc.JdbcConnector@6c1194fa
via Mirth Project by john voigt, 1 year ago
There is already a listener registered on this connector on endpointUri: jdbc://query. Connector that caused exception is: com.mirth.connect.connectors.jdbc.JdbcConnector@6c1194fa
org.mule.umo.provider.ConnectorException: There is already a listener registered on this connector on endpointUri: ftp://user2:pass2@ftpserver. Connector that caused exception is: FtpConnector{this=b29562, started=true, initialised=true, name='connector.ftp.0', disposed=false, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=true, supportedProtocols=[ftp], serviceOverrides=null}
at org.mule.providers.AbstractConnector.registerListener(AbstractConnector.java:767)
at org.mule.impl.model.AbstractComponent.registerListeners(AbstractComponent.java:537)
at org.mule.impl.model.AbstractComponent.start(AbstractComponent.java:217)
at org.mule.impl.model.AbstractComponent.start(AbstractComponent.java:204)
at org.mule.impl.model.AbstractModel.start(AbstractModel.java:323)
at org.mule.MuleManager.start(MuleManager.java:900)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.