Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Foglight Agent Manager 7.3.0 - Foglight Agent Manager Development Kit Release Notes

Resolved Issues and Enhancements

Resolved Issues and Enhancements

Resolved issues and Enhancements have been published in the Foglight 7.3.0 Release Notes document. Please review that for more specific information.



Known issues

Known issues

The following is a list of issues known to exist at the time of this release.

Development Kit core

Defect ID

Resolved Issue

FAM-292

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.

Agent harness

Defect ID

Resolved Issue

FAM-4697

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

FAM-4494

A verified submission status is never updated.

FAM-4492

First verified submission is always lost.

FAM-4261

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

FAM-3908

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

FAM-3880

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

FAM-3879

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

FAM-3775

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

FAM-3774

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

FAM-3563

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.

Tooling

Defect ID

Resolved Issue

FAM-4787

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.

FAM-4180

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

FAM-4133

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

FAM-3751

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

 


Development Kit core

Known issues

The following is a list of issues known to exist at the time of this release.

Defect ID

Resolved Issue

FAM-292

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.

Agent harness

Defect ID

Resolved Issue

FAM-4697

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

FAM-4494

A verified submission status is never updated.

FAM-4492

First verified submission is always lost.

FAM-4261

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

FAM-3908

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

FAM-3880

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

FAM-3879

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

FAM-3775

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

FAM-3774

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

FAM-3563

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.

Tooling

Defect ID

Resolved Issue

FAM-4787

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.

FAM-4180

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

FAM-4133

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

FAM-3751

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

 


Agent harness

Known issues

The following is a list of issues known to exist at the time of this release.

Development Kit core

Defect ID

Resolved Issue

FAM-292

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.

Defect ID

Resolved Issue

FAM-4697

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

FAM-4494

A verified submission status is never updated.

FAM-4492

First verified submission is always lost.

FAM-4261

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

FAM-3908

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

FAM-3880

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

FAM-3879

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

FAM-3775

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

FAM-3774

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

FAM-3563

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.

Tooling

Defect ID

Resolved Issue

FAM-4787

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.

FAM-4180

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

FAM-4133

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

FAM-3751

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

 


Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation