on 01-15-2008 10:31 AM
Hello,
In a JDBC to IDoc scenario, we have a sender JDBC communication channel which was set to poll for data in every 60 sec. It was working fine for long and suddenly it has stopped polling data. It's status was green and the channel was active.We couldn't find the reason so we configured one more comm channel keeping all the parameters same, and it has started working. We couldn't understand why it was not working earlier. Can any body please highlight on this?
Regards,
Sugata
Delete the JDBC channel -> Refresh Cache (SXI_CACHE)-> create New One and this should work
It happens without reason ********
Regards.
Jeet.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey
its a known issue with FTP and JDBC sender communication channels.please check the SAP Note 1083488
Thanx
Aamir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
try to stop and start the CC...as mentioned above check the queues also..
regards
Rao
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sugata,
This also happens sometimes when the queues are not cleared like we have some scheduled messages.
Please delete old LUWs from the queue for in SMQ2(inbound queue).
Regards,
Sumit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have noticed something similar with File/FTP adapter.
If there is a period of inactivity - no data being sent/received, the adapter almost goes in to a dormant state.
when we notice this, we make a change to the adapter, save and activate and it starts up again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sugata ,
I was not able to trace the root cause for this problem yet. But I got an ugly patch work, that solved this problem.
I copied the JDBC sender commn channel to a new name and changed the sender agreement accordingly. This solved my problem. Try this and let me know if it helps.
P.S: Do you have a large load on this channel?
TJ
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
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.