My Oracle Support Banner

"The Process ProcessID is not available" Is Shown In Workspace After Deploying A Project (Doc ID 1322543.1)

Last updated on AUGUST 06, 2018

Applies to:

Oracle Business Process Management Suite - Version: 10.3.1 to 10.3.2 - Release: AS10gR3 to AS10gR3
Information in this document applies to any platform.

Symptoms

After deploying a project, the Engine is not able to start a process. The project status can be seen in BPM Process Administrator as Completely Deployed.

The following error messages could be seen in different logs:

*** in webconsole.log

[<W> 0321 17:40:33.281] Main (<3> http-8686-Processor23): Error BPM-1300761807931
[ (cont) ] Main: The following object(s): 'Roles: [MyRole] External Variables: [courtline] ' were not created since they already exist in the directory:
.
[<D> 0321 17:42:20.296] Main (<3> http-8686-Processor23):  getFieldDefinitionsForVariables() -> courtline
[<D> 0321 17:42:20.296] Main (<3> http-8686-Processor23):  getFieldDefinitionsForVariables()
[<D> 0321 17:42:20.296] Main (<3> http-8686-Processor23):  getFieldDefinitionsForVariables() -> courtLine
[<D> 0321 17:42:20.875] Main (<3> http-8686-Processor23): Converting field size from bytes to characters. Field 'obpmengine.PPROCINSTEVENT.V_COURTLINE, byte length='60', char length='30'
[<D> 0321 17:42:21.156] Main (<3> http-8686-Processor23): Converting field size from bytes to characters. Field 'obpmengine.PPROCINSTANCE.V_COURTLINE, byte length='60', char length='30'
.
[<I> 0321 17:42:22.343] Main (<6> Thread-45): (stdout) Message written by the process execution engine: Start Compiling /MyProcess1#Default-1.0
[ (cont) ] Main: .
[<I> 0321 17:42:22.343] Main (<6> Thread-45): (stdout) Message written by the process execution engine: >> End Compiling /MyProcess1#Default-1.0<<.
[<I> 0321 17:42:22.359] Main (<6> Thread-45): (stdout) Message written by the process execution engine:
[ (cont) ] Main: .
[<I> 0321 17:42:22.546] Main (<5> Thread-46): (stderr) Message written by the process execution engine :
[ (cont) ] Main: Runtime exception Shell.
[ (cont) ] Main: Context details :
[ (cont) ] Main: Process '/MyProcess1#Default-1.0' could not be started up
[ (cont) ] Main:
[ (cont) ] Main:
[ (cont) ] Main: Original stack trace follows ...
[ (cont) ] Main:
[ (cont) ] Main: java.lang.NullPointerException
[ (cont) ] Main:
[ (cont) ] Main: .

*** in Engine log

Process '/MyProcess1#Default-1.0' could not be started.
Details:\njava.lang.NullPointerException
java.lang.NullPointerException
at fuego.metadata.execution.ExternalVariable.getDirectoryVarName(ExternalVariable.java:46)
at fuego.metadata.execution.DeploymentInformation.addExternalVariable(DeploymentInformation.java:201)
at fuego.metadata.execution.compiler.ModelVariableCompilerImpl.compile(ModelVariableCompilerImpl.java:56)
at fuego.metadata.execution.compiler.ModelCompilerImpl.compile(ModelCompilerImpl.java:72)
at fuego.metadata.Process.compile(Process.java:1170)
at fuego.metadata.Process.compileProcess(Process.java:1107)
at fuego.metadata.Process.loadProcess(Process.java:947)
at fuego.metadata.Process.initProcess(Process.java:753)
at fuego.metadata.Process.forName(Process.java:190)
at fuego.server.BaseActiveProcess.getProcess(BaseActiveProcess.java:109)
at fuego.server.ActiveProcessImpl.loadMetadata(ActiveProcessImpl.java:1472)
at fuego.server.ActiveProcessImpl.loadMetadata(ActiveProcessImpl.java:1457)
at fuego.server.ActiveProcessImpl.<init>(ActiveProcessImpl.java:183)
at fuego.server.BaseActiveProcess.<init>(BaseActiveProcess.java:54)
at fuego.fengine.FEngineActiveProcess.<init>(FEngineActiveProcess.java:58)
...

After Workspace login, Workspace UI shows this message:
.
The Process '/MyProcess1#Default-1.0' is not available.
The Process '/MyProcess1#Default-1.0' is not available. Caused by: Process
'/MyProcess1#Default-1.0' not available. Caused by: Process '/MyProcess1#Default-1.0' not found. Detail:Verify that the process is deployed.

Changes

A project variable name was changed in its capitalization, for example,

existing name: courtLine
new name: coutline

Notice the letter "L" in upper and lower case.

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
  Symptoms
  Changes
  Cause
  Solution
  References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

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