BAM 12c : The Payload Cannot Be Parsed By EMS - Date Field Missing Or With Any Value.
(Doc ID 2403804.1)
Last updated on MAY 26, 2018
Applies to:Oracle BAM (Business Activity Monitoring) - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version,
BAM 12c : The payload cannot be parsed by EMS - Date field missing or with any value.
Users are facing a similar issue reported in note Doc ID 1995204.1 (BAM 12c : The payload cannot be parsed by EMS if the Date field is missing (Doc ID 1995204.1)).
Users are trying to write into an internal Data Object using EMS component but we've got a parsing error in date field.
Users performed several tests, sending some date formats or even omitting this field, but the same error occurs.
Even when users tried to edit EMS source, changing Date Time Specification field to some format available or using a custom format date the issue persist.
Users encountered the below errors:
[2018-05-21T11:34:11.222-03:00] [bam_server1] [ERROR]  [oracle.beam.server.service.ems] [tid: JCA-work-instance:JMSAdapter-12] [userId: OracleSystemUser] [ec
id: d46fa54e-a18f-4843-a013-40357bf933a6-00003c82,0] [APP: BamServer] [partition-name: DOMAIN] [tenant-name: GLOBAL] Invalid DateTime specified: 2018-01-13T02:07:11.000-02:00
java.text.ParseException: Unparseable date: "2018-01-13T02:07:11.000-02:00"
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