Hi, i see it right that this is a clientside issue, or? The client must do the change on his regestry, not the server, because he did't bind?
Thanks. Dirk > -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 8. November 2005 17:34 > An: axis-user@ws.apache.org > Betreff: Re: AW: Axis 1.3 Address already in use: connect-> > java.net.BindException > > Dirk wrote: > > So the best is to wait between the requests? > > We made the registry changes as outlined in the original document; > decreased the amount of time spent in TIME_WAIT state, and increased the > number of TCP/IP dynamic ports available--it enabled us to more than > double > the number of virtual users during performance testing without > encountering > these errors. > > If you can't (or don't want to) modify your Windows registry, then you'll > need to keep those simultaneous requests at a lower level, or accept that > some of them will fail... or, as you said, modify your code in some way so > that you don't overload the available ports. > > Meghan > > _________________________________ > Meghan Pietila > Java Middleware Architect > Sales & Service Management Program > US Bank > > > -------------------------------------------------------------------------- > ---- > Electronic Privacy Notice. This e-mail, and any attachments, contains > information that is, or may be, covered by electronic communications > privacy laws, and is also confidential and proprietary in nature. If you > are not the intended recipient, please be advised that you are legally > prohibited from retaining, using, copying, distributing, or otherwise > disclosing this information in any manner. Instead, please reply to the > sender that you have received this communication in error, and then > immediately delete it. Thank you in advance for your cooperation. > ========================================================================== > ====
