on 05-23-2011 3:22 PM
Hi All,
I am facing an issue with my sender adapters, which stop polling sometimes. This is not a frequent issue, but happened 2-3 times.
Last time when it happened we restarted J2EE Engine and it worked fine.
Can anyone help me out in finding out the reason and solution for this?
I was going through a few of the blogs/threads and found out that most of the cases was either the J2EE being down or the adapter getting locked.
Here to unlock the adapter I saw that we have to do it from Visual admin. Additionally, I saw a case where it got unlocked when J2EE engine was restarted. Was wondering if my case was the same where the adapters got locked.
Does someone know when/how the adapters get locked?
Please note I am working with XI 3.0.
Many Thanks,
Regards,
Lakshmi.
Hello
See note #831162 FAQ: XI 3.0 / PI 7.0 / PI 7.1 JDBC Adapter - Q.29. How to delete manually hanging Enqueue-Locks. This explains where to check for locks.
Also note #821267 FAQ: XI 3.0 / PI 7.0/ PI 7.1 File Adapter - 46. How to manually delete hanging Enqueue-Locks.
Regards
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
maybe is a Xi bug, I had same problem.
go through SAP note 1083488 to fix it.
Ciao
Fabio
Symptom
Sometimes, some of the XI FTP/JDBC sender channels stopped polling
permanently. However this is resolved by re-starting these channels.
Other terms
FTP sender channels, JDBC sender channels, polling stopped, stopped
polling, polling adapters.
Reason and Prerequisites
Program Error
Solution
For FTP adapter, please set the appropriate FTP timeout parameter in sender
channel configurations. Existing timeout implementation has a bug while
reading from Input. This patch solves this problem.
Edited by: Fabio Boni on May 23, 2011 5:40 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The timeout parameter seems to have done the trick.
We removed the locks via Visual Admin and has now set the timeout parameter for the File and JDBC Sender Channels.
Just wanted to know, if this lock issue can happen for Receiver channels as well. If so, do we set the same timeout values for File and JDBC Receiver channels?
Edited by: Lakshmi Prasanna on Jul 21, 2011 3:49 PM
Hi Lakshmi,
Just wanted to know, if this lock issue can happen for Receiver channels as well.
If so, do we set the same timeout values for File and JDBC Receiver channels?
R.: This issue only happen in Sender Channels.
If the Legacy Database is Oracle, see too:
- [Error occured while posting the job schedule for JDBCAdapter |;
- [Note 1398891 - XI/PI Adapter for Oracle: Overcoming DB Connection Issues|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1398891]
Best Regards.
Pedro Baroni
User | Count |
---|---|
94 | |
11 | |
11 | |
10 | |
9 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.