Error Creating Instance for target process BPM11g

Hi,

When you deploy your BPM process which has a initiator task and try to instantiate the process from BPM workspace, You might get this error   “Error Creating Instance for target process”

Cause :  There might be some business object hanging, means You might have created a business object  but haven’t used in any of the human task, then you get this error

Solution : Delete the business object if it is not required or use the business object as an input to any of the human task.

Cheers,

Letslearnoraclesoa team

Email : letslearnoraclesoa@gmail.com

dvm:lookupValue() issue in BPM 11.1.1.5 ,11.1.1.6

It is a annoying issue that DVM lookup function (dvm:lookupValue()) used inside xsl transformation of a BPM doesn't work.

Solution:  Use a script task and fetch the desired value from DVM look up inside a BPM process.

Cheers

letslearnoraclesoa team

email : letslearnoraclesoa@gmail.com

“Caused by: java.lang.UnsupportedClassVersionError: unsupported classversion 51.0”

Error:

“Caused by: java.lang.UnsupportedClassVersionError: unsupported classversion 51.0”

Replication Of Issue: 

When we try to deploy any service which has been developed/Migrated on JDK which is higher than the JDK version used by the server

Error Stack:

[04:04:30 PM] [Deployer:149193]Operation 'deploy' on application 'ServiceName' has failed on 'Server1'
[04:04:30 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application 'ServiceName' on Server1.: Failed to load webapp: ''ServiceName'.war'.
[04:04:30 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: ''ServiceName'.war'
[04:04:30 PM] Caused by: java.lang.UnsupportedClassVersionError: <Package Name> : unsupported classversion 51.0
[04:04:30 PM]   See server logs or server console for more details.
[04:04:30 PM] weblogic.application.ModuleException: Failed to load webapp: ''ServiceName'.war'
[04:04:30 PM] ####  Deployment incomplete.  ####
[04:04:30 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)

Resolution:

  

1)      1) Check the JDK Requirement of the JDeveloper version which is to be installed. Eg. As per Oracle documentation for Jdev 11.1.1.6.0 the JDK shall be JDK_6.0_27 or above.

2)       2) Check the server jdk version.To do the same t go to location WL_HOME/common/bin/commEnv.cmd ad Look for lines like the ones below (examples are from a WLS install on a Unix machine)

#JAVA_USE_64BIT, true if JVM uses 64 bit operations.

3)      3) Install JDK version which is either server version or lower than that version and then build/migrate your service.

  

Reference: To find the JDK version of your server click here.

JDev : “unable to launch the java virtual machine located at path msvcr71.dll”

Error: 

“unable to launch the java virtual machine located at path msvcr71.dll”

Replication Of Issue: 

Go to path JDEV_Home ->jdev -> bin and try to open any 64 bit Jdeveloper

Screen Shots:

Reason: 

While Installing Jdeveloper, It install JDK (e.g. jdk160_24) inside Oracle1 -> Middleware and JDeveloper referes to this path as JavaHome. But if the Jdeveloper needs Higher version of JDK than the installed one (e.g JDev 11.1.1.6.0 needs jdk160_27 or above) then this error occurs.

Resolution:

1. Install JDK version compatible for the installed version

2. Go to JDEV_HOME\jdev\bin\jdev.conf and changed the set javahome as
 "SetJavaHome C:\Program Files\Java\<The New JDK Installed>

Cheers,

LetsLearnOracleSoa Team