Custom Adapter module: Sequencing of messages in Message log

Hi All,

I was writing an adapter module (for assigning the EOIO queue based on the payload). I was already using another custom adapter module for some other functionality.

The problem I am facing is that in the message log (message monitoring -> Message log), I see that the audit log entry for my new module and the old module are getting mixed up. For example:

New module:

audit.addAuditLogEntry(key, AuditLogStatus.SUCCESS, " new module Statement 1..." );

Some logic

audit.addAuditLogEntry(key, AuditLogStatus.SUCCESS, " new module Statement 2..." );

Some logic

audit.addAuditLogEntry(key, AuditLogStatus.SUCCESS, " new module Statement 3..." );

Existing module

audit.addAuditLogEntry(key, AuditLogStatus.SUCCESS, " Existing module Statement 1..." );

Some logic

audit.addAuditLogEntry(key, AuditLogStatus.SUCCESS, " Existing module Statement 2..." );

Output in message monitoring log

new module Statement 1...

new module Statement 2...

Existing module Statement 1..

Existing module Statement 2..

new module Statement 3..

Interesting to know that time stamp for such mixing up of message is same. I think this is happening because of some parallel thread processing and may be that sequence of events (1. New module, 2. Existing module) is not same as that of message log display (may be a bug internally for displaying the message).

There does not seem to be a problem in the final output but I am concerned over the sequence of message logs. Has anyone else faced this issue before or can anyone provide logical explanation for this behavior ?

Thanks,

Ravi.