[Anthill-pro] What does "TargetError" mean?

[Peter Steele]

It doesn't even make it to a build step. The only error reported is this TargetError in the request log. I suspected there was a conflicting agent configured and decided to stop the agents and delete them. However, after stopping the agents, three of them still showed as online. I tried testing the communication through the Anthill GUI and got the error 

Agent communication failed: com.urbancode.devilfish.services.jms.ReplyTimeoutException: Timeout expired: 20000ms

Even after this error, Anthill lists them as online. I edited the installed.properties files on my five agents, changed the agent names and restarted them, and Anthill lists the new agents as online. I have no problem running my secondary workflow against these agents. I still have the three original agents listed as online, but they are apparently pointing to other hosts than what they should be. What's odd is they don't have a valid hostname or IP under the Host column. For two of them this field is blank, and for a third it's listed as 0.0.0.0.  Unfortunately Anthill won't let me delete them because they are online, but I can't figure out where these agents are actually running.

How do I get rid of these ghost agents?

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com [mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Steve Boone
Sent: Wednesday, November 25, 2009 6:40 AM
To: AnthillPro user and support list.
Subject: Re: [Anthill-pro] What does "TargetError" mean?

Peter,

What step in the job is failing?  Perhaps the none of the steps run and it fails before it has a chance to run any part of the job?

Is there any information in the request log of the secondary workflow?

-Steve

On Wed, Nov 25, 2009 at 8:43 AM, Peter Steele <psteele at maxiscale.com> wrote:

> I have a secondary workflow and have it configured to run against 
> multiple agents, selected by the user. I've configured some new 
> agents, put them in an environment and made that environment available 
> to the workflow, but when I run the secondary and select these new 
> agents, I get the error
>
> 2009-11-25 05:16:32,057 ERROR - TargetError
>
> and nothing more. There is no error recorded in the agent logs at all, 
> and only a slight more expanded error in the server log:
>
> 2009-11-25 05:16:32,057 ERROR Workflow-4 
> com.urbancode.anthill3.services.exception.ExceptionService - 
> TargetError
>
> What does this error mean? I assume I've neglected to configure 
> something on these agents, but they show as being up and available, 
> are listed in the appropriate environment, and appear to be setup 
> identical to other agents that I use with this same workflow. So, what am I missing?
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
_______________________________________________
Anthill-pro mailing list
Anthill-pro at lists.urbancode.com
http://lists.urbancode.com/mailman/listinfo/anthill-pro