B2B Inbound Scenario : JVM Crash And Will Not Process Any Files. Error: Unexpected Signal : 11 occurred

(Doc ID 960004.1)

Last updated on APRIL 18, 2010

Applies to:

Oracle Application Server Integration B2B - Version: to - Release: AS10gR2 to AS10gR2
Information in this document applies to any platform.


One of trading partner is using 004010VICS as the EDI Standard.
As per the b2b export configuration, the remote trading partner is the initiator for B2B transaction and Host Trading Partner is the responder.(Inbound Scenario for the Host Trading Partner).

When the host trading partner receives a file, following issue occur :

1. The file is picked up for processing but no reports are generated and no general validation error occurs in the b2b.log file.
A file named hs_err_pid<number>/log gets created at /ORACLE_HOME/ip directory which has the following entries:

An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0xB56B3D36
rd EE+0x61E
Current Java thread:
at com.edifecs.shared.jni.xdata.INativeToXData.ExecuteNative(Native Method)

The file hs_err_pid<number> generation occurs each time the configuration is activated.

2. The b2b.log increases till a certain limit (67096 kb) and a new folder is created at b2b/logs directory and keeps appending entries into b2b.log(no errors) till a certain limit(67096 kb).
The new folders are generated once b2b.log size is 67096 kb.

The above event can be stopped only if the B2B configuration is quiesced.
When the configuration is re-activated, the log file keeps increasing and creating many folders in b2b/logs.


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