Re: Naming Service( 'restarting nameserver' ) problems revisited...

Hi Josh,

Josh Zeidner wrote:

> Dear Shark Users,
>
>  Hello, my name is Joshua Zeidner.  I am posting on this list for the 
> first time, as I have recently opted to utilize the Shark workflow 
> engine for mapping my organizations internal business processes.  I am 
> located in the US, and I would like to congratulate all EU citizens on 
> their recent success against Software Patents in the EU!
>
>  I want to respond to some of the messages posted here concerning the 
> 'restarting nameserver' message and the problem of persistent Naming 
> services.  I am having the same problem.  I would like to either fix 
> it or see it fixed.  Has anyone else resolved this problem?  Please 
> reply to list.
>
I first tried to wrap the call to tnameserv with a script that writes 
its PID into a file and checks this file before starting another 
instance of tnameserv on the same port. Unfortunately that caused some 
obscure racing conditions.

The final solution was to start the naming service independently of 
shark and disable shark's name service restart feature.

If you are working on a unix platform you would have to write a run 
level script that starts the naming service and comment out the 
nameserver.executable property.

Search the mailing list for more on this topic.

Regards,
Dirk

--
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