ECS is Unable to Send Notification and Throws Error "Unable to connect to Provider : Connection lookup reaches maximum time" (Doc ID 2859316.1)

Last updated on AUGUST 08, 2023

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.8.0 and later
Information in this document applies to any platform.

Scenario:

'BRMGateway' had errors:

2022-03-19 08:32:32.764 MVT ERROR - - - - BRMMessageBundle-18001: Error receiving from JMS : TransportsMessageBundle-0902: Unable to connect to Provider : TransportsMessageBundle-0902: Unable to connect to Provider : Connection lookup reaches maximum time.....
After restart of BRMGateway and Weblogic server the error in BRMGateway is gone, after that ECE is unable to send any notifications. There is no error in BRMGateway.
In Elastic Charging Server (ECS) logs below error is being printed:

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Symptoms

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.