Initially people were skecptical whether this is possible.But then we rationalised that it should be possible, because at the end of day on a system every thing translates to a Socket. And the Computer calculates a socket before assigning it to any application. This calculation mainly uses both IP and Port (which normally you configure for ur server). So we have 2 different IP and same port number, which should essentially translate in to 2 unique socket numbers.
To do this we bound Jboss to the first Ip by passing parameter -b Ip_Address to run.bat present in Jboss_Home/bin.
And for IIS we passed the second Ip value as default web site in IIS properties.
After doing this when we tried to bring both the servers, then we had a problem saying the port is already bound. After digging a little bit found that the problem is with IIS as it is trying to bind to all the IP addresses on the machine during start up. Something similar to when we pass -b 0.0.0.0 param to Jboss run.bat.
To disable this functiobality on IIS we did the following that is obtained from MS support web site:
| 1. | Open a command prompt and make sure you are in the C:\Inetpub\Adminscripts folder (where C is the IIS installation drive). To do this, type the following lines at the command prompt: C:CD\Inetpub\Adminscripts |
| 2. | After you open the Adminscripts folder, type the following line at the command prompt: cscript adsutil.vbs set w3svc/disablesocketpooling true |
| 3. | The command replies as follows: disablesocketpooling : (BOOLEAN) True |
| 4. | Stop and start the IIS Admin service. |
| 5. | Restart the WWW service. |
No comments:
Post a Comment