ERR_BAD_LOGIN_RESULT Or ERR_NAP_CONNECT_FAILED Error When Multiple Threads Are Trying To Connect To CM
Last updated on JUNE 22, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
***Checked for relevance on 17-Mar-2011***
Checked for relevance on 2-Jul-2014
*** Checked for relevance on 12-04-2015 ***
Developed a multi-threaded java application in which all the threads are sharing the same PortalContext variable to improve the performance planning for developing a Connection pool application.
When multiple threads are trying to connect the CM, it is working fine for the first 10-20 connections; but after some time, the connectivity to the cm will become unavailable and CM throws error ERR_BAD_LOGIN_RESULT or ERR_NAP_CONNECT_FAILED.
Need more details of the ConnectionPool class or details for creating a connection pool for using it further.
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