A join time-out for an All (AND) join condition specifies how long the Integration Server waits for all of the documents specified in the join condition. When Integration Server pulls a document from the webMethods messaging trigger queue, it determines which condition the document satisfies. If the document satisfies an All (AND) join condition, the Integration Server starts the join time-out period and moves the document from the webMethods messaging trigger queue to the ISInternal database. Integration Server assigns the document a status of “pending.” Integration Server then waits for the remaining documents in the join condition. Only documents with the same activation ID as the first received document will satisfy the join condition.

If Integration Server receives all of the documents specified in the join condition (and processes the documents from the trigger queue) before the time-out period elapses, it executes the service specified in the condition. If Integration Server does not receive all of the documents before the time-out period elapses, Integration Server removes the pending documents from the database and generates a journal log message.

When the time-out period elapses, the next document in the webMethods messaging trigger queue that satisfies the All (AND) condition causes the time-out period to start again. Integration Server places the document in the database and assigns a status of “pending” even if the document has the same activation ID as an earlier document that satisfied the join condition. Integration Server then waits for the remaining documents in the join condition.