ibatis插入DB2表会导致锁定，导致触发器无法正常工作

Question

I am writing an INSERT into a DB2 table that uses my inserted record as a trigger and have been accused of being the culprit for locking the file and preventing the trigger from working.

Currently I can write the record but it hangs my application and I get no response back from the DB2 database. (although it does write !).

I have been told I might be writing using "UPDATE mode" but I have done nothing specific other than not actually setting any mode:

  <resultMap id = "insertEntry" class = "customer">
        <result property = "supplierNumber"     column = "SUPN"/>
        <result property = "status"          column = "STAT"/>
        <result property = "timeAccepted"   column = "TIMEACC"/>
        <result property = "dateAccepted"   column = "DATEACC"/>
        <result property = "dateCompleted"   column = "DATECOMP"/>
    </resultMap>


<insert id = "insertCUSTRecord" parameterClass="insertEntry">
INSERT INTO ##AKQQ3
(SUPN, STAT, TIMEACC, DATEACC, DATECOMP)
VALUES (#supplierNumber#, #status#, #timeAccepted#, #dateAccepted#, #dateCompleted#)
</insert>

I can only guess at the cause of my application hanging and one guess is that is a result of not having set the relevant mode on an an INSERT statement but I have no idea as to which is relevant from a choice of ibatis' IN, OUT and INOUT parameters.

The RPG team have told me to attempt to somehow try and read the record I have just inserted to release this lock and was wondering if any of these ibatis modes provides that functionality.

The docs state "If a parameter is OUT or INOUT, the actual value of the parameter object property will be changed" but I'm somewhat confused as to what object this refers to. Could setting all my insert values to IN be what I'm looking for ?

I should mention that I have used the Squirrel SQL client to attempt the same insert (using the jt400 JDBC driver) and it hangs and get no confirmation back from the database despite having written the record.

In my application I have resorted to a "fire and forget" approach of dealing with not having a response back from the DB2 database via an ExecutorService that I kill after 3 seconds although I know this is not an ideal solution.

My program integrates struts with spring and ibatis, the code that calls the insert is as follows:

public void insertIntoAKQA(CustomerTriggerDetailsBean customerTriggerDetails) {
    SqlMapClientTemplate template = getSqlMapClientTemplate();
    template.insert("insertCUSTRecord", customerTriggerDetails);
}

Answer 1

The problem turned out to be an RPG trigger which was badly written. Until they resolved it I did however manage a workaround with the Java ServiceExecutor which gave me back control of my application after an assigned time.