We have a problem with a Message inside our J2EE Adapter. The message remains in the status DLNG forever.
We use SAP XI 3.0 Service Stack 13.
We have the following scenario:
When sending messages via the Oracle JDBC connection to the Receiver-Service, the
message keeps the delivering status and never fails if the message
fails on the database level. In this particular case, the message failed on the DB level due to a misconfigured trigger and due to unique constraints. The state of the messages can be resolved by cycling the entire J2EE engine.
How can I handle such a message that stay in DLNG status?! And why is it hanging there? I cannot restart the message, I cannot stop it I also cannot cancel it out of the RWB.
Message was edited by: Nesimi Buelbuel