Re: Nameserver is (re)started!

You should probably just change the way you run things.  Turn off the 
name service executable parameter and
run the nameservice independently using the tns script provided.   I 
think this change was made to handle
the case where the nameservice would die for some unknown reason, so 
that Shark then could restart it.
If you are using CORBA for other apps, it is probably best not to have 
the nameservice being run by Shark
since it might not even be on the same machine and other apps may depend 
on it.

Dave
David Delbecq wrote:

>Is it me, or does this bug renders shark useless on a production 
>environnement? (aka need to modify shark.conf to not start nameserver when 
>restarting, but need shark to start it at first run). We can not afford to
>restart the whole mainframe each time we need to restart shark (for whatever
>reason we need to restart it).
>
>Or perhaps is there a way to kill the nameserver (this way we would add it
>to startup script).
>Le Mercredi 20 Juillet 2005 19:43, David Forslund a écrit :
>  
>
>>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