Re: Nameserver is (re)started!

This is a bug that should be fixed.  Basically what is happening is that 
you have already run the runAllPOA.sh or the runALL.sh once and it starts
the Nameservice daemon on its own.   The next time you run it, it tries 
to run it again (it doesn't check to see if it is running or can connect 
to it before it tries
to start it).   You need to turn of the executing of the Nameservice in 
Shark.conf after you run it once to keep it from attempting to run it 
again.   Each time it tries to start it after the first, it fails 
because it can't talk on the nameserver port.  But the app doesn't 
understand this and keeps trying anyway.  It is related to trying to 
restart the nameserver periodically believing that it might have 
crashed.  This is a bad idea, in my opinion and should be fixed.

Dave
delbd wrote:

>Hello.
>
>Starting shark corba interface (using runAllPOA.sh) I now get a bunch of
>Nameserver is (re)started!
>followed by a line of information on current java version
>
>The server does ot respond to admin application requiring connection.
>
>
>Then, after a few minutes i get a bunch of 
>java.io.IOException: Too many open files
>
>What did i do wring, it was working before.
>All i did was rerun configure.sh after changing 
>the database in configure.properties to mysql
>
>Help appreciated. :(
>
>  
>
>------------------------------------------------------------------------
>
>
>--
>You receive this message as a subscriber of the [email protected] mailing list.
>To unsubscribe: mailto:[email protected]
>For general help: mailto:[email protected]?subject=help
>ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>  
>

--
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws