My Oracle Support Banner

Real Time HTTP Sender Outbound Message Results To Unable To Parse "Content-Type" Header Value: "" (Doc ID 3050308.1)

Last updated on SEPTEMBER 27, 2024

Applies to:

Oracle Utilities Customer Care and Billing - Version 2.9.0.1.1 and later
Information in this document applies to any platform.

Symptoms

**Examples provided in this article do not represent real life personal/confidential information**

**Disclaimer:** This KM article may include the following abbreviations:

CCB - Oracle Utilities Customer Care and Billing

HTTP - HyperText Transfer Protocol

On : Oracle Utilities Customer Care and Billing 2.9.0.1.1 version, SW - System Wide

ACTUAL BEHAVIOR
---------------
Real Time HTTP Sender Outbound Message produces Unable to parse "Content-Type" header value: "" error when transport method is Send.

Outbound message is not created. The external system was able to receive the message but the response was not accepted by CC&B. This causes the outbound message to rollback.

EXPECTED BEHAVIOR
-----------------------
Outbound message will be created in Complete status.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Setup async (one-way) outbound message sender that will return an accepted response (202/200).
2) Setup Real-Time HTTP Outbound Message Type (Invocation Type=Real-time; Message Class=RHTTPSNDR)
3) Trigger creation of outbound message via script/batch.


Changes

 The client previously uses CC&B 2.4 and it the Outbound Message works in their legacy with the same configuration.

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


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