unregistered functions seems to be not reported by the server about java-gearman-service HOT 6 CLOSED

Hi DBouyssie,

In some servers, functions are deleted when there are no job or workers. 
However, if you set a job cap on the function, it too is deleted. I keep the 
functions alive to maintain it's state. If there is a memory issue, the garbage 
collector will clean up any unused function to prevent an out of memory error.

In most systems the function names are static and it's not an issue. What 
exactly are you trying to do? Given a good argument, I might change it.

Here is my setup (all on localhost):
- a java-gearman-service server,
- no worker,
- an echo client (written in Scala but using the java-gearman-service API).

When I run the client, it starts but doesn't return.
Because no worker is registered I would have expected to get an error message 
saying there is no available worker able to make the echo job.

Here is the log I have :
févr. 17, 2012 8:55:11 AM org.gearman.GearmanLogger log
Infos: CLIENT@640159b3: [127.0.0.1:4730] : Connected
févr. 17, 2012 8:55:11 AM org.gearman.GearmanLogger log
Infos: CLIENT@640159b3: [127.0.0.1:4730] : OUT : SUBMIT_JOB
févr. 17, 2012 8:55:11 AM org.gearman.GearmanLogger log
Infos: CLIENT@640159b3: [127.0.0.1:4730] : IN : JOB_CREATED

This is the expected behavior. When a job is received without a worker, it sits 
in the queue until a worker can pick it up.

In a gearman application, it's best to know the system's architecture and know 
what servers have (or will have) the applicable workers. Your setup should look 
something like this 
(http://www.moskalyuk.com/blog/wp-content/uploads/image5.png). Something fairly 
static.

Ultimately gearman is just a load-balancing framework. It's not designed for 
building complected dynamic networks.

Ok I didn't realize this point.
Do you know the Java/Scala akka framework ?
Maybe it is better suitted for this kind of task.

Thanks.

Enjoy your week-end !

Sorry, I don't know anything Java/Scala :\

I'm going to close this issue for now. If other users start complaining about 
the functions not being deleted, I'll reconsider changing the behavior.

I think I have found a workaround. Using the telnet interface and sending text 
commands I  can know the list of registered functions on the server. So I will 
extend my clients in order to check that the job they want to perform is well 
registered before sending the request.

For information akka is a framework which supports two implementations one for 
Java and an other one for scala. Just wondered if you have ever heard about it.