Adapter Framework Scheduler may fail to remove a job

[] [] [] [] [] [] [] [] [] [] [] []

  1. Job Scheduler Task view in NWA does not display any tasksSymptom On some systems the Job Scheduler task view does not display any task. In addition there is a TaskDoesNotExistException in the trace file with the following details: Job definition with id...
  2. File adapter metadata changed for adapter attributesSymptom You are using the File Adapter in your business scenario for message processing. During the transport of XI to another system, you notice that the values for some of the File...
  3. File Adapter messages stuck in “To Be Delivered” statusSymptom You have upgraded to PI 7.0 SP 18 and you notice that File Adapter messages are stuck in “TBDL”(To Be Delivered) status. Additionally, the following symptoms are noticed: 1 – File...
  4. File adapter: NegativeArrayException occurs while ArchivingSymptom You have configured the File Adapter in your scenario with following options set in configuration: 1.Files are to be archived (with or without timestamp) after processing. 2.Local file system (and not...
  5. Receiver file adapter thread hangingSymptom The thread of receiver file adapter remains in runnable state while communication channel has the following configuration File Construction Mode=Create, Overwrite Existing File=false, Write Mode= Use Temporary File. Other terms File...
  6. FTP receiver adapter deletes file with append modeSymptom You are using the File Adapter in your business scenario for message processing. During the message processing, you notice, that, the FTP receiver adapter deletes the output file if it encounters...
  7. File sender adapter generates duplicate message IDs.Symptom This note attempts to solve two issues: a) File sender adapter generates duplicate message IDs and sends it to Messaging system. In the Synchronous(Best Effort) scenario cases, Messaging system does not...

Symptom

XI Adapter Framework’s scheduler may fail to remove the scheduled job. When this problem occurs, the affected job may get executed continuously for some period in parallel.
This problem can be suspected when some scheduled job gets executed unexpectedly frequently while others do not get executed.
This scheduler is used by various services of the Adapter Framework, such as the polling sender adapter services (File, JDBC, Mail, etc) and the channel administration service. When this problem occurs and the scheduler fails to remove one sender channel job, the polling action of this channel may be repeatedly executed in a very short period of time until this condition dissolves. In some cases, this problem may overload the system with many concurrently executing threads.

Other terms

Adapter Framework, Scheduler, not polling, File, JDBC ,Mail ,overload

Reason and Prerequisites

Program error
The scheduler used the hashcode operation to order two schedule jobs with the same next execution time. This could potentially result in a collision of two distinct schedule job objects.
It is noted that this problem could occur very rarely, namely when two scheduling jobs with the some object hash values were scheduled exactly at the same millisecond.
In some JVMs, particularly of those 64-bit VM with a large heap size,, this problem may occur more easily than in others, as they tend to generate hash values that can collide.

Solution

This problem has been fixed in this patch by not using an arithemetic operation that results in an underflow.
This patch resolves the issue by using an additional information to maintain the order of scheduled jobs.
Import the appropriate archive for SAP Exchange Infrastructure XI. The archives and the support package stack guide can be found on the SAP service Marketplace as described in SAP Note 952402.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment