Document Streaming Not Working With B2B Outbound Scenario

(Doc ID 2344733.1)

Last updated on JANUARY 17, 2018

Applies to:

Oracle SOA Suite - Version 12.2.1.2.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.1.2.0 version, B2B Engine

Document Streaming does not work and results in following exception:
--------------------

[2017-09-12T10:50:09.238+00:00] [soa_server1] [ERROR] [][oracle.soa.b2b.engine] [tid: DaemonWorkThread: '9' of WorkManager:'wm/SOAWorkManager'] [userId: <anonymous>] [ecid:ab4c2b6a-2b48-44e5-a982-e715e08f6009-00000edf,0] [APP: soa-infra][partition-name: DOMAIN] [tenant-name: GLOBAL]java.lang.NullPointerException[[
at oracle.tip.b2b.message.AppMessage.getPayload(AppMessage.java:229)
at oracle.tip.b2b.msgproc.MessageHandler.convertToIPMsg(MessageHandler.java:2403)
at oracle.tip.b2b.engine.Engine.outgoingContinueProcess(Engine.java:4451)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:4260)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3774)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:834)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:254)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:184)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:209)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:618)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:39)

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

a. Configure batch with number of messages = 15.
b. Configure Large payload settings in B2B
c. Set b2b.largePayload property in the backend application such as OSB.
d. Send messages (Total size 150k) in a batch.



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