Re: [JXTA discuss] How to start the tutorial client server examples on a single machine?

Dont change the ports on both peers to the same thing. Make them 
different or they will collide.
This problems should be detected and avoided by the configuration 
optimizers. This is a very important problem, because it causes many 
newbie testers to think that jxta doesn't work.

Please, please, someone contact whomever is responsible for the jxta 
auto config process and ask him to include a tcp port availability check 
(it should be simple, just loop over ServerSockets and IOExceptions 
until you find an open port).

Thanks,

Alex

Hartmut Benz wrote:

> Hi,
>
> Both peers default to the same ports...
> From memory:
> Clean out one of the directories (the .jxta) and start again.
> When the configuration screen comes up, go to the "advances" tab and  
> change the two instances of 9701 to something else, e.g. 19701.
> Hartmut
>
> On Thu, 18 Aug 2005 21:13:53 +0200, Bikash Agarwalla  
> <[email protected]> wrote:
>
>> Sorry if you receive multiple copies - I have trying the example  
>> included in the jxta programmer tutorial - "PipeService". I keep 
>> getting  the error "java.net.BindException: Address already in use
>> " when I run the client and server on the same machine. I have tried 
>> to  run the client and server from different directories (as 
>> recommended in  the tutorial), but I still get the same error as 
>> follows:
>> "<FATAL 2005-08-18 15:12:29,527  
>> IncomingUnicastServer::openServerSocket:368> Cannot bind ServerSocket 
>> on  /0.0.0.0:9701"
>>
>> It seems both client and server are trying to bind to port 9701 for 
>> the  default peer group initialization. How do I get around this 
>> problem?
>>
>> Thanks for your help.
>> Bikash
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>