Skip to Content

AFW Receive Queue

We are running into a situation where we are hitting deadlocks on JDBC updates to an SQL Server database. We are going to address this problem separately, but it brings to light the potential for a problem occurring in one system to hang up the entire adapter engine.

We get 5 messages being delivered to this SQL Server database and then encounter deadlocks. These messages hang, showing status 'delivering' in MDT and nothing else goes through (appears to be a limit of 5 messages actively being delivered). Raising the limit would not be a good solution, as more would just hang.

Is there any way to set up queues by receiver for how messages get executed by the AFW ?

Thanks in advance.

Message was edited by: Tim Walker

Add comment
10|10000 characters needed characters exceeded

2 Answers

  • Posted on Oct 31, 2005 at 07:58 PM

    Hi Tim,

    XI30-SP13 allows access to external Database tables during mapping to use the JDBC adapters in the Integration Directory. Currently, the access is done using a direct JDBC connection. By using the JDBC adapter in mapping, you will no longer need to use the direct-connection

    technique, or trying to get the connection pool to work.

    This will alleviate the need for properties file, which will have to be maintained, to designate the server location in a fail-over situation.

    Thanks

    Prasad

    Add comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 03, 2005 at 04:26 PM

    Found it. SAP Note 791655. Actually, this was the limit of 5 we found. Still looking for a way to queue by service.

    Message was edited by: Tim Walker

    Add comment
    10|10000 characters needed characters exceeded

    • They are already queued by AFW, and there is a max conccurrent total messages that can be active for the AFW. I want to be able to further limit concurrent messages by end point, so I don't believe EOIO will help, unless I make all of the interfaces EOIO, which I do not want to do.