Pablo,
Thanks for the reply, but I think we have a disconnect with what is
currently happening. This happens regardless to whether you are using web
applicaiton or a windows service or application. Also, we are testing in a
test environment without VS installed, so we are for sure running IIS.
The problem comes when two different applications try to attach an endpoint
to the default port of 8081 used by WSE 3.0. Both programs can't use the
same port so an error is thrown. One possible work around is to configure
them to use different ports. My question is whether there is another way and
what the potential pitfalls are of using different ports.
Travis
[quoted text, click to view] "Pablo Cibraro" wrote:
> That happens because you are using Cassini (The web server included in VS).
> In my opinion, it is better if you IIS with different virtual directories
> (Port 80) for each web service in production environments.
> Cassini is ok only when you are developing the application.
>
> Regards,
> Pablo Cibraro
>
http://weblogs.asp.net/cibrax >
> "Travis" <Travis@discussions.microsoft.com> wrote in message
> news:D7EDA63C-2376-4AE2-9037-62BC0F90A6E5@microsoft.com...
> >I am writing in hopes of someone pointing out a best practice. We are
> > running multiple applcations on a server that all use WSE 3.0. If we
> > leave
> > the addresses defaulted to the 8081 port, we get socket and port errors
> > stating only one item can run on the port. A temporary fix seems to be to
> > hardcode in a port on each endpoint we setup on the server. Is this a
> > good
> > idea? What have others done when running two different applications on
> > the
> > same server all using WSE 3.0.
> >
> > Thanks for the help.
> >
> > Travis
>
>
