When Configuring BTM An Error Occurs When Applying Default Observer Communication Policy To Monitor (Doc ID 1492112.1)

Last updated on MARCH 01, 2016

Applies to:

APM - Application Performance Management - Version 12.1.0.7.0 and later
Information in this document applies to any platform.
***Checked for relevance on 01-Mar-2014***

Goal

In BTM 12c a single btmMonitor is deployed in a WLS 10.3.5 Managed Server and it listens at port 11110.

The Default Observer Communication Policy is configured with Communication path = "Direct to Monitor" and the Monitor port number = 11110.

When trying to apply the policy, the following error is displayed:

Text exceeded 1,000 characters and was truncated; for full text see Data Broker log: http://host:port/btmui/views/pages/common/AmcLogViewer.xhtml?id=uuid:FB4123E4-ECC8-11E1-B8BF-FF0432512A7E.
The agent got errors from the configurations created to implement a set of policies. The errors are Found 1 errors and 0 warnings.
ERROR:Unexpected Exception starting the MessageLogReader: java.net.BindException: Address already in use
Detailed Error Message :: Address already in usenStack Trace :: java.net.BindException: Address already in use.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms