Slowness in Papi or papi Web Service Methods after Upgrading to 10.3.2 or 10.3.3 (Doc ID 1539009.1)

Last updated on JANUARY 09, 2015

Applies to:

Oracle Business Process Management Suite - Version 10.3.2 and later
Information in this document applies to any platform.

Symptoms

First call to papi application takes a long time. This is expected, but if another user logs in they will also take a long time the first time they login to make the papi call.

 

In the thread dumps you'll see a stack trace like this:

 

"[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=3 tid=0x0000000103504800 nid=0x47 runnable [0xfffffffed98f9000]
   java.lang.Thread.State: RUNNABLE
at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)
at java.util.regex.Pattern$Curly.match0(Pattern.java:3770)
at java.util.regex.Pattern$Curly.match(Pattern.java:3744)
at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)
at java.util.regex.Matcher.match(Matcher.java:1127)
at java.util.regex.Matcher.matches(Matcher.java:502)
at fuego.directory.DirDeployedProcess.getConsolidatedId(DirDeployedProcess.java:6 38)
at fuego.papi.impl.ProcessManager.getAllVersions(ProcessManager.java:317)
at fuego.papi.impl.ProcessManager.getAllVersions(ProcessManager.java:307)
at fuego.papi.impl.ProcessManager.deployProcess(ProcessManager.java:734)
at fuego.papi.impl.ProcessManager.put(ProcessManager.java:1044)
at fuego.papi.impl.ProcessManager.getProcessIds(ProcessManager.java:578)
at fuego.papi.impl.ProcessServiceImpl.getProcessIds(ProcessServiceImpl.java:1356)
at fuego.papi.impl.SessionProcessManager.getCache(SessionProcessManager.java:529)
at fuego.papi.impl.SessionProcessManager.isProcessAvailable(SessionProcessManager .java:81)
at fuego.papi.impl.ProcessServiceSessionImpl.processIsAvailable(ProcessServiceSes sionImpl.java:3952)

 
You may also see stuck threads that look like this:

 

]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
java.util.regex.Pattern$CharProperty.study(Pattern.java:3355)
java.util.regex.Pattern$Curly.study(Pattern.java:3831)
java.util.regex.Pattern$CharProperty.study(Pattern.java:3355)
java.util.regex.Pattern$Start.<init>(Pattern.java:3044)
java.util.regex.Pattern.compile(Pattern.java:1480)
java.util.regex.Pattern.<init>(Pattern.java:1133)
java.util.regex.Pattern.compile(Pattern.java:823)
fuego.directory.DirDeployedProcess.getConsolidatedId(DirDeployedProcess.java:640)
fuego.papi.impl.ProcessManager.getAllVersions(ProcessManager.java:317)
fuego.papi.impl.ProcessManager.getAllVersions(ProcessManager.java:307)
fuego.papi.impl.ProcessManager.deployProcess(ProcessManager.java:734)
fuego.papi.impl.ProcessManager.put(ProcessManager.java:1044)
fuego.papi.impl.ProcessManager.getProcessIds(ProcessManager.java:578)
fuego.papi.impl.ProcessServiceImpl.getProcessIds(ProcessServiceImpl.java:1356)

 

Changes

 Recently upgraded in hotfix or maintenance pack level in 10.3.2 or 10.3.3

Cause

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