Project: mulestudio
Issue STUDIO-6773: Studio allows to deploy an app with an ipv4 port already in use
Nowadays, studio is not forcing to use ipv4, so any app can be deployed using any already taken ipv4 port. As a consequence, you can deploy an app in Mule and then deploy the same app in Studio, without errors. Scenario 1 (using Mule 3.7): - Deploy the attached config in Mule 3.7.0. Notice that the port is hardcoded to 8082 - Deploy the same app in Studio. - Check the console and the terminal. Both logs show that the apps are deployed, without errors. Studio app should throw an exception saying that the port is already in use. - Go to a new terminal, and run the command "netstat -an | grep 8082". You will see that the 8082 is listening, with tcp4 and tcp46. (See image1.jpg) - If you make a request to http://localhost:8082, mule will answer that request, and studio will throw a Broken Pipe Exception. This issue does not happen if you run the apps in the inverted order (First studio, Second Mule). In that case, Mule throws an exception saying that the port is already in use. Scenario 2 (using ports of the other programs): - Go to a terminal and run the command "netstat -an" - Look for an already taken port using tcp4 (for example in image2.jpg you can see that the ports 49298 and 63342 are not available) - Deploy the attached app, changing the listener port to one of the previous ones. - The app is deployed instead of saying that the port is already in use.
Story points: 5