Erman Arslan's Oracle Blog: December 2021

Wednesday, December 8, 2021

EBS R12 -- WF Mailer java.lang.StackOverflowError at org.apache.regexp.RE.matchNodes

Today's blog post is about a problem in Workflow Mailer (WF Mailer). This time, I will directly give the definition of the problem along with the solution offer, because I have already written lots of articles on this subject.. So, I think my followers should already know all the things about the WF Mailer itself and the mechanism of the workflow outbound & inbound.

Okay.. Let's get to the point without wasting time.

The problem was in the IMAP side.. Some of the approved orders (approved via emails) was left in not-approved status in the EBS system. It was clear that the Inbound of the WF Mailer couldn't do its job. Besides, the newly approved orders could not be reflected to the EBS system either.

A statement level showed the following;

[Nov 10, 2021 10:04:07 PM EET]:1636574647912:-1:-1:SP-SERVER1:10.10.10.1:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:1505677572:72687:1636574641893:212:UNEXPECTED:[SVC-GSM-WFMLRSVC-695685-10006 : oracle.apps.fnd.cp.gsc.Processor.run()]:java.lang.StackOverflowError

at org.apache.regexp.RE.matchNodes(RE.java:1358)

A search on MOS knowledge base pointed to the following;

Workflow Mailer Stopped Working java.lang.StackOverflowError at org.apache.regexp.RE.matchNodes(RE.java:1104) (Doc ID 1505015.1) ** Especially this one.

Java.lang.StackOverflowError When Mailer Processes Inbound Email (Doc ID 2611474.1)

Once the problematic email was analyzed, we found an unexpected character code there, just beneath the NID line.

Here is the relevant part of the email;

Action:

'Approve'

Note: ''

NID[347449/295312543679791762909718721451122233183@WFMAILPT]

Oracle ACE /

+27201

Explanation & the solution:

There was a problematic email on the IMAP side (an email, with an unexpected content sitting in the inbox of IMAP, or in the PROCESS folder).

Remember, WF Mailer can not easily handle these kinds of unexpected things.. Actually, It could be clearly seen that there was a &#43 character just after the NID line. Note that, this HTML characters correspond to the a plus sign.

The mobile device of the client that responded(Approved or Rejected) this WF Mailer notification may have placed this code into this response. This caused WF mailer to crash with stack overflow.

The WF Mailer just could not process this email, but it couldn't ignore this email either..

It just couldn't continue. So this email must have been removed from the inbox of the EBS WF Mailer's IMAP account. (The required EBS side operation can be done manually in this case).

Once this problematic email that sits on IMAP Inbox/or on PROCESS folder, was removed, and just after the WF Mailer was bounced, the problem dissapeared.. WF Mailer could just do okay and the problem was solved.

Saturday, December 4, 2021

EBS 12.2 -- Can not login after upgrade -- Login failed. Please verify your login information or contact the system administrator.

The issue appears in upgrade customers, and the login page just fails with the following;

Login failed. Please verify your login information or contact the system administrator.

If you have done an EBS 12.2 (for instance EBS 12.2.10, 12.2.11) upgrade and can't login to EBS.. (using SYSADMIN or any other user);

If you face a situation where you end up with Login Failed message when you enter the credenatials on Login page and click submit;

If you tried changing/resetting the passwords using FNDCPASS-like utilities, but the issue still persists;

If FND_WEB_SEC.VALIDATE_LOGIN returns Y for your users,

If there are no significant errors in oacore_server1 out, diag or log files + Apache/OHS diag files,

then ->

run the EBS upgrade Analyzer! Again we have an analyzer to use ! : ) When saying "we" , I don't mean "me", actually Oracle has one :)

E-Business Suite Upgrade Analyzer - 12.X to 12.2.X ( Doc ID 2634237.1 )

So, we run the analyzer and check its output.. ( we don't be lazy for running these analyzers, they actually save us time!)

Most probably, the analyzer will tell you that the following patch is missing in your system;

Patch 32357755: SYSADMIN (WHEN PASSWORD REUSE IS ON) PASSWORD CHANGE DOES NOT WORK AFTER UPGRADE FROM R12.1.3 TO R12.2.

Just apply the patch and the issue will dissapear..

Note that, as you may have already noticed the definition of this patch doesn't directly map to our issue, but the conditions that I gave above actually redirects us to this patch ( even without checking the analyzer output).. This may be the insight of this blog post. When it comes to Oracle patching and documentation and especially the patch definitions, I 'm the voice of the skeptics:)

So that's why I've put that long "if" part in the beginning and only then, that precise "then" part is given :)

EBS 12.2 / ISG enablement - isgDesigner.xml:369: Only deploy or undeploy is supported.

This blog post is for the ones who are trying to enable Integrated SOA Gateway on EBS 12.2.. This task is also done in 12.2 upgrade projects -- if you were already using ISG or planning to use it on your newly upgraded EBS 12.2.

You know what, the things are getting even more complex for EBS world.. I mean, for an upgrade you start with a document, then it redirects you to another one, and that another one redirects you to a different one, and then you come back to the first one and then you find yourself redirected to a new one :) Sometimes, it makes you feel like you are in some kind of a nested redirect loop :)

So please be careful and do your own documentation while doing these things in your TEST environments.. Missing or ignoring a single thing will bring you some catastrophes later -- you can be sure about that : )

Well.. Documentation to follow for this task is as follows:

Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.2 (Doc ID 1311068.1)

Anyways; this issue appears in section 8, while configuring the REST services

Remember -> SOA Suite is REQUIRED when using SOAP web services.

-->

Section 8: Configuring Oracle E-Business Suite Integrated SOA Gateway for REST Services on Release 12.2.x Upgraded From Oracle E-Business Suite Release 12.1.

Here is the failed execution and the error..

ant -f $JAVA_TOP/oracle/apps/fnd/isg/ant/isgDesigner.xml -DserviceType=REST -Dactions=upgrade -Dverbose=ON

Error:

BUILD FAILED

/u01/oracle/PTK12_2/fs2/EBSapps/comn/java/classes/oracle/apps/fnd/isg/ant/isgDesigner.xml:369: Error:

Only deploy or undeploy is supported.

So it seems like there is something wrong with the isgDesigner.xml.. (despite the fact that you may be on AD Delta 13 and TXK Delta 13.)

Don't push yourself hard for analyzing these types of issues, we already have a tool called ISG Setup Analyzer.

EBS Integrated SOA Gateway (ISG) Setup Analyzer (Doc ID 2462729.1)

Okay let's jump to the conclusion.. In this case, ISG analyzer will report you that ISG Consolidated Patch for 12.2 (21_4_3) (Patch) is missing in your EBS system.. So just install the patch and re-execute the failing ant command and that's it !:)

Erman Arslan's Oracle Forum / November 2021 - "Q & A Series"

This month again, I did not break the tradition and continued to support customers and the community despite the load of my work (leading my department, mission critical support activities & projects + intellectual gymnastics - physics and stuff like that ) ! :)

Remember, you can ask questions and get remote support using my forum.

Just click on the link named "Erman Arslan's Oracle Forum is available now.
Click here to ask a question", which is available on the main page of Erman Arslan's Oracle Blog
-- or just use the direct link:

https://ermanarslan.blogspot.com/p/forum.html

Come on, let's see what we've been up to in November+ in the beginning of December 2021. #amaerman

Quantity record with SET1 and SET2 in EBS 12.2.10 by ANIETO

adop fails : ETCC not run in the database node by big

Cannot send testmail: Invalid role by big

Applied patches to patch edition homes by satish

Weblogic conflicts R12.2.5 by satish

APEX login page does not respond by big

Weblogic logon/pwd refused by big

read only filesystem by Roshan

jar signing code failed. by Naseem khan

Datafiles redistribution across mountpoints by Karthik