The init-agent-manifest-props macro in fglam-ant-macros fails if the manifest file uses a namespace prefix, because the <xmlproperty> tag creates variables with the namespace prefix in the name.

The Agent harness shows topology property updates multiple times in message trees.

A verified submission status is never updated.

First verified submission is always lost.

The Agent harness reports the following error on debug level 1: java.lang.IndexOutOfBoundsException: Index: 10, Size: 10

A NullPointerException is thrown while an agent instance created by the AgentControlService is displayed under the Agent Type node in the tree.

Adding additional agent instances of the same type can cause a null pointer exception as a result of a call to the JTree.updateUI().

The ASP string editor in the Agent harness interprets "\n" as a new line.

Setting a label on an enum type property in the agent-definition.xml can cause a fatal error.

The Agent harness cannot write some configuration files to the state directory.

A core dump occurs while generating a heap dump from the Agent Harness menu on a Red Hat Enterprise Linux 6.x OS virtual machine

An old agent running with a newer cartridge on the Management Server with an updated and incompatible ASP schema causes a NullPointerException in the agent's generated property wrappers.

Up-to-date check for topology wrappers is invalid.

TopologyValidator should ignore user-defined topology types that are only referenced from dynamic properties.

Core properties of a topology type that is a subtype of the TopologyObject type are being overridden.