on 03-10-2006 12:55 PM
Hi,
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.
regards
Nesimi
Message was edited by: Nesimi Buelbuel
any solution to the problem mentioned here ?
we are also facing the same issue.
have tried all kinds of restarts.
any further help will be appreciated.
thanks,
gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nesimi, we have the same problem as you described.
Have you solved this question?
I can't find your email in your business card.
Please tell me if you know.
Thanks and B'Rgds.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.