B4J Question [SOLVED] ABMaterial webserver vs FTPServer conflict

[JackKirk]

I am running an ABMaterial webserver and an FTPServer on the same AWS Windows EC2 instance.

They are both obviously monitoring the same IP address - ABMaterial server is configured to monitor port 51044 and FTPServer is configured to monitor port 21.

When I only have the FTPServer active everything works fine on that server.

If I have both servers active and try to upload a file from an external FTP client the FTP job fails with

java.lang.RuntimeException: Error uploading file.
500 Error: java.net.BindException: Address already in use: bind

I would have thought this should work.

In a production environment I could always run separate AWS EC2 instances but would prefer to avoid this at least during testing and demonstration stages of the exercise.

By any chance does ABMaterial also monitor ports other than those specified by

Server.PortSSL = 51044 ??????????

 

[teddybear]

I am running an ABMaterial webserver and an FTPServer on the same AWS Windows EC2 instance.

They are both obviously monitoring the same IP address - ABMaterial server is configured to monitor port 51044 and FTPServer is configured to monitor port 21.

When I only have the FTPServer active everything works fine on that server.

If I have both servers active and try to upload a file from an external FTP client the FTP job fails with

java.lang.RuntimeException: Error uploading file.
500 Error: java.net.BindException: Address already in use: bind

I would have thought this should work.

In a production environment I could always run separate AWS EC2 instances but would prefer to avoid this at least during testing and demonstration stages of the exercise.

By any chance does ABMaterial also monitor ports other than those specified by

Server.PortSSL = 51044 ??????????

You need to change the data listening port of the FTPServer. It conflicts with ABMaterial webserver. or change the listening port of the webserver .
Such as below

ftpsrvr.SetPorts(21, 10000, 10100)

 

[JackKirk]

You need to change the data listening port of the FTPServer. It conflicts with ABMaterial webserver.

Not quite right in my case but close - based on this prompt I dug a bit deeper and then got reminded about the FTPServer working port range - and sure enough this was where the conflict was - modified that away from the ABMaterial Webserver SSL port and it all works flawlessly.

Many thanks...