R12: IBY: Send Separate Remittance Advices (IBY_FD_SRA_FORMAT) Ends in an Error (The Maximum Number of Concurrent Server Connections has Exceeded) (Doc ID 2970601.1)

Last updated on SEPTEMBER 06, 2023

Applies to:

Oracle Payables - Version 12.2.11 and later
Information in this document applies to any platform.

Symptoms

Send Separate Remittance Advices (IBY_FD_SRA_FORMAT) Ends In An Error. "421 4.3.2 The maximum number of concurrent server connections has exceeded a per-source limit, closing transmission channel"

This issue happens only when Microsoft Email Server is used with the default frontend receive connector.
Connections were not closed causing the max connections issue.

The Separate Remittance Advice (IBY_FD_SRA_FORMAT) concurrent program log file shows the following messages / Errors:

Loaded email send-from from DB: Message { Code = IBY_FD_SRA_EMAIL_FROM, Cause = xxxxx@xxxx.com}
Trying to fetch Encoding
After fetching Encoding :: UTF-8
Encoding Fetched from DB:: UTF-8
Loaded email attachment file prefix from DB: Message { Code = IBY_FD_EMAIL_ATT_PRE, Cause = Pagamento}
Preparing for email delivery
SMTP server host: null
Email subject: Dana – Aviso de Pagamentos Executados / Agendados # # Payments Details From xxxxxx
Recipient: xxxx@xxxxxxx.com.br
Content file name: Pagamento295168.html
Email send from: xxxxx@xxxx.com
before calling XDO req.setDocument()
before calling XDO req.submit()
DEBUG: setDebug: JavaMail version 1.6.2
DEBUG: getProvider() returning javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Oracle]
DEBUG SMTP: useEhlo true, useAuth false
DEBUG SMTP: trying to connect to host "mailrelay.dana.com", port 25, isSSL false
421 4.3.2 The maximum number of concurrent server connections has exceeded a per-source limit, closing transmission channel (xxxxx.xx.xxx.xxxx.com)
DEBUG SMTP: could not connect to host "xxxxx.xxxx.com", port: 25, response: 421
java.lang.NullPointerException
at oracle.apps.xdo.delivery.DeliveryUtil.log(Unknown Source)
at oracle.apps.xdo.delivery.smtp.SMTPDeliveryRequestHandler.submitRequest(Unknown Source)
at oracle.apps.xdo.delivery.AbstractDeliveryRequest.submit(Unknown Source)
at oracle.apps.iby.scheduler.SRAAndPayerNotif.doElectronicProcessing(SRAAndPayerNotif.java:899)
at oracle.apps.iby.scheduler.SRAAndPayerNotif.runSRA(SRAAndPayerNotif.java:410)
at oracle.apps.iby.scheduler.SRAAndPayerNotif.runProgram(SRAAndPayerNotif.java:210)
at oracle.apps.iby.scheduler.FDSeparateRemittanceAdvice.runProgram(FDSeparateRemittanceAdvice.java:60)
at oracle.apps.fnd.cp.request.Run.main(Run.java:159)

An error occurred. Roll back any changes.
Done roll back changes.
Request completed in error.
CP main completed runProgram for oracle.apps.iby.scheduler.FDSeparateRemittanceAdvice

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Navigate to Payments Manager
2. Submit the Payment Process Request

Cause

	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

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

R12: IBY: Send Separate Remittance Advices (IBY_FD_SRA_FORMAT) Ends in an Error (The Maximum Number of Concurrent Server Connections has Exceeded) (Doc ID 2970601.1)

Applies to:

Symptoms

Cause

To view full details, sign in with your My Oracle Support account.

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