My Oracle Support Banner

SBL-EAI-05006: Failed To Load The JVM Dll When Making an Outbound REST Call From the Dedicated Client. (Doc ID 2553910.1)

Last updated on NOVEMBER 20, 2019

Applies to:

Siebel CRM - Version 18.10 and later
Information in this document applies to any platform.

Symptoms

On : 18.10 version, Siebel EAI

When attempting to invoke an outbound REST service in the dedicated client
the following error occurs.

ERROR
-----------------------
ObjMgrBusServiceLog InvokeMethod 4 000000025d0143b4:0 2019-06-12 14:57:45 Begin: Business Service 'REST Outbound Runtime Service' invoke method: 'PrepareHttpRequest' at d231508

EAITransport EAITransportDebug 4 000000025d0143b4:0 2019-06-12 14:57:45 CSSJavaBusinessService::ReadJavaArch: JVMSybsys name:"JAVA64", JAVA Architecture:32

JVMInit JVMInitInfo 3 000000025d0143b4:0 2019-06-12 14:57:45 JVM subsystem is not found, JVM will be initialized based on the machine configuration, such as Windows registry.

JVMInit JVMInitInfo 3 000000025d0143b4:0 2019-06-12 14:57:45 JVM classpath is empty.

JVMInit JVMInitInfo 3 000000025d0143b4:0 2019-06-12 14:57:45 JVM will be initialized with following parameters:

JVMInit JVMInitInfo 3 000000025d0143b4:0 2019-06-12 14:57:45 JVM dll path = 'jvm.dll'

JVMInit JVMInitInfo 3 000000025d0143b4:0 2019-06-12 14:57:45 VM options:

JVMInit JVMInitInfo 3 000000025d0143b4:0 2019-06-12 14:57:45 -Xmx100m

GenericLog GenericInfo 3 000000025d0143b4:0 2019-06-12 14:57:45 JVM total VMOptions are 2

GenericLog GenericInfo 3 000000025d0143b4:0 2019-06-12 14:57:45 JVM VMOptions for index 0 are -Xmx100m

GenericLog GenericInfo 3 000000025d0143b4:0 2019-06-12 14:57:45 JVM VMOptions for index 1 are vfprintf

EAITransport EAITransportDebug 4 000000025d0143b4:0 2019-06-12 14:57:45 Finished loading JVM DLL.

ObjMgrBusServiceLog Error 1 000000025d0143b4:0 2019-06-12 14:57:45 (javabsvc.cpp (448)) SBL-EAI-05006: Failed to load the JVM Dll. Check that the specified dll name is correct.



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Invoke the dedicated client and call the custom outbound REST interface

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot make outbound REST calls on the dedicated client.
Their ultimate goal was to use Tools in debug mode to debug a script which processes the output of the REST call and this was not possible as the REST call itself was not working on dedicated.
The problem is unrelated to Tools or debug mode though. It happens with dedicated client alone.

Changes

 

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


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