JDBC Comm Channel not Polling data

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

Hi,
@Barry,
Yes, it dont poll data from database although it was supposed to do so. We have tried to make some changes and then undo changes and save+activate. But that hasn't work.
@ PT Rao,
We tried that too, that also hasen't work.
@ Sumit,
could you please elaborate?
Sugata

Similar Messages

Comm channel not available in RWB comm channel monitoring

Hi All,
I've gone through this(Comm channel missing in comm channel monitoring) unanwered forum. I've facing the same issue.
In my ID, I created XI receiver adapter comm. channel. And data is flowing successfully to the receiver side through this Comm. channel
I'm aware that XI adapter in ID is used to send data via Proxy.
But why i'm not see that in the Comm. channel monitoring in RWB. If anyone has documentation please let me know.
Thanks.

Hi ,
The XI adapter resides in Integration engine thus you cannot see it in RWB. RWB shows comm channels which are in adapter engine. The simple proof is that you cannot enhance this adapter with your own modules on the Module tab page in the module processor. Here is the link to documentation
http://help.sap.com/saphelp_nw04/helpdata/en/f4/0a1640a991c742e10000000a1550b0/content.htm
regards
Anupam

JDBC adapter is not polling as scheduled

Hi,
we have observed JDBC adapter is not polling database correctly. adapter is scheduled at every 1 second, but it is plooing for every 5 sec or 6 sec.
is there any way the issue can be fixed?
Thank You,
Madhav

hi,
in my mind, the issue is your polling's choice of 1s !
so to have a real-time exchange whereas you use a polling method to reach a server with is not the PI server itself, and perhaps also not on the same network, by opening perhaps also the database connexion at each request in order to call a SQL request or a stored procedure...
I don't know your complete flow, but if you really need a 100% real time, maybe it should be better to trigger the sender JDBC adapter from outside when (and only when) the data is produced / changed in your database....
Anyway, personally, I never recommend to have a polling of 1s. 10s (and often only 60s) is enough is most of the cases... because after the polling you have the XML conversion, the PI mapping, the sending to ECC, the ECC treatment... all these steps take time, and so the interest of checking of every 1s is (in my mind) clearly reduced by all these steps.
(*) I'm sure if SAP will define a polling in milliseconds, some people would like to use a polling of 1ms, but that's a non-sens...
regards.
mickael

JDBC Sender channel not processing the messages

Hello,
From yesterday onwards JDBC Sender channel not processing the messages. In CC monitoring it is showing in Green Led and status is functioning. Cahnnel is polling for messages to DB server as per polling interval. But it is not processing the msg's. Under Processing detials for cluster node it is showing only "Processing Started" for each polling interval.
I have done the check in DB server by executing the query in the channel, whether there are any records are exisitng or not. There are 1000+ records.
Previously the parameter "Disconnect from DB after processing each message" was not set. I have set the parameter and activated in Productiion. Still the messages are not processing by channel
What was the problem? How to rectify with this.
Cheers
Veera

Check in the Visual Admin >Cluster> "LOCKING ADAPTER"
we get a option of Display Locks .Check for an entry with
NAME : $XIDBAD.JDBC2XI
reset the locks and restart the CC ,now it works fine.
Note 1083488 - XI FTP/JDBC sender channel stop polling indefinitely(04/04S)

No adapter registered for this channel FOR JDBC COMM CHANNEL

Hi Friends,
We installed JDBC driver(for Oracle) and it works correctly from Visual Administrator.
We have created comm channel 'jdbc_receiver'.
However, when we check in "Adapter Monitoring", it is not active (Green color) and short text says 'No adapter registered for this channel'. Where should we look further to resolve the issue ? How do we test this comm channel from XI box ?
Thanks.
Niranjan

Hi Niranjan,
How you solved the problem?
I have deployed JDBC driver (sqljdbc4.jar) according tohttp://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b4a020-4ae6-2c10-5a95-fed4ad9a4b60?QuickLink=index&… .
Driver deployed successfully and I have checked it in folder \usr\sap\xxx\DVEBMGS30\j2ee\cluster\bin\ext\com.sap.aii.adapter.lib\lib and it's found ok. But this adapter type not showing in Communication Channel only RFC and SOAP are showing there. I have restarted the server also.

Problem with JDBC Comm Channel from UNIX PI Installation.

Dear Gurus:
Inside a standard scenario, we have a receiver comm channel which use JDBC adapter type to connect to a MS Access remote database.
The database connection is made like this:
JDBC Driver: sun.jdbc.odbc.JdbcOdbcDriver
Connection: jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//10.96.0.10/c$/app/appdb.mdb
Working from a Windows 2003 PI installation, everything works fine..
But we recently have finished a Heterogeneous migration from Windows 2003 + SQL server to UNIX AIX + Oracle servers and that particular interface does not work anymore.
Is there a way to connect to a MS Access from inside a UNIX PI installation..? Is there a native JDBC or ODBC driver that we can use to fix our problem...?
Waiting for your help. Best regards.
Eduardo.

Hi,
In the JDBC receiver CC, Advanced-->Advanced Mode, use poolWaitingTime and taskTimeout parameters and specify
some time using seconds.
Babu

JMS Sender Channel not Polling

Hi Guys,
Scenario: BEA Weblogic -
> JMS Queue -
> Sender Channel JMS -
> SAP XI -
> SAP R3
We had initially setup this scenario using MessageSelector because the provider JMS Queue had mutiple message types on it. As Murphy's law would have it, the MessageSelector stopped polling the day before go-live. Basically, if we pointed one JMS SC to the provider JMS Queue using MessageSelector it worked fine, if we pointed multiple JMS SC's no messages were being picked up from the queue. We still haven't identified why the MessageSelector functionality stopped working but as a quick work around to MessageSelector before go-live we used blog:
[/people/robert.warde3/blog/2009/03/18/pi-basics-generic-message-interface|/people/robert.warde3/blog/2009/03/18/pi-basics-generic-message-interface]
Now we have a situation where, BEA Weblogic manages the provider JMS Queue & they perform a health check 4 times a day & if they encounter a problem they bounce the server & JMS Queue service. XI and the SC seem to re-connect fine most of the time when Weblogic & JMS Queue is back up but there are times when I see a green light in RWB for the SC but it's not polling for messages on the JMS Queue. We use Hermes JMS to monitor messages on the Queue to check if there are in fact messages to be picked up & the messages are queued.
What I'm looking for is a best practice guide for how to manage this. I don't want to keep toggling between Hermes JMS & RWB to verify if the SC is in fact polling messages altho' it shows as green in RWB. Please advise. Thanks.
Regards, Trevor

Thanks Kai & Joel.
Joel, I'm not really looking to add another layer with the JMS Connector Service. For me it's just adds another possible point of failure. At the moment the message passes thru 5 systems including SAP R3 & end system & then the response comes back the same route.
Going out from SAP, the Receiver channel to the JMS queue seems to work fine. With the responses coming back, the Sender Channel seems to re-connect ok (I'm assuming) otherwise it wouldn't be green in RWB but doesn't pick up any messages. It's also an intermittant phenomenon. Manually stopping & re-starting the Sender Comm Channel fixes the problem but we won't know if there's a problem until we check if messages are being picked up from the queue.
Kai's notes led me to some things I could possibly look at like additional parameter in JMS channel config, CONNECTION_TEST_POLL (note 948016). I'm still not sure how we can make this work for us because we essentially need to bounce the JMS channel so it starts polling again in the event of a JMS Queue Provider bounce but I need to first establish that the JMS Queue was bounced.
Note 1088675 will also be irrelevant cos the channel looks like it re-connects, just doesn't poll.
Trevor

Sync/Async - JMS receiver comm. channel not processing

I have a Sync/Async scenario (without bpm) in PI 7.11:
RFC -> PI -> JMS
whereby the JMS receiver comm. channel does not fully process the message.
More specifically, the RFC sender comm. channel gets a message in and passes the message to the JMS channel, but that JMS channel within the RWB comm. channel log only shows the entry:
- Message processing started
The odd twist to this is that when we bring the PI server down, then back up again, (or wait a period of time, still trying to determine this period) the FIRST message attempt does successfully get processed, i.e. the first message on that JMS receiver comm. channel RWB log shows as:
- Channel successfully processed the message: 08499236-387c-11e0-b002-000025bab2c2
- Stored the correlation ID 08499236-387c-11e0-b002-000025bab2c2 of the request JMS message: ID:c3e2d840d4d8d4f24040404040404040c754dc12d8b54ec6 correponding to the XI message: 08499236-387c-11e0-b002-000025bab2c2
- Message processing started
(but then because of an issue on the target system, no response comes back, so then we'll additionally get the log entry:
- Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: no message received
Any suggestions appreciated on what I can check here to try and figure this out. Possibly because the first message eventually errors out, it is stopping the other subsequent msgs from getting processed...
When I check the audit logs of a 'success' msg vs. a not-successful msg, the success msg has an entry (and subsequent entries) of:
14.02.2011 12:50:19 Information Transform: transforming the payload ...
14.02.2011 12:50:19 Information Transform: successfully transformed
14.02.2011 12:50:19 Information ROB: entering RequestOnewayBean
14.02.2011 12:50:19 Information ROB: forwarding the request message
14.02.2011 12:50:19 Information ROB: leaving RequestOnewayBean
14.02.2011 12:50:19 Information JMS Message was forwarded to the JMS provider succesfully."
14.02.2011 12:50:19 Information XMB Message as Binary was forwarded to the SAP XI JMS service succesfully.
14.02.2011 12:50:19 Information WRB: entering WaitResponseBean
14.02.2011 12:50:19 Information WRB: retrieving the message for 08499236-387c-11e0-b002-000025bab2c2 ...
wheras the non-success msg shows only:
14.02.2011 12:55:30 Information Transform: transforming the payload ...
14.02.2011 12:55:30 Information Transform: successfully transformed
14.02.2011 12:55:30 Information ROB: entering RequestOnewayBean
14.02.2011 12:55:30 Information ROB: forwarding the request message
14.02.2011 12:55:30 Information ROB: leaving RequestOnewayBean
So, we can see that the message is not "forwarded to the JMS provider..." in the non-success case.
And also the sxi_monitor shows these messages with a status of "Log version".
Keith

Hi Siddhesh - yes that was a while back and am trying to remember the resolution. I have implemented sync/async bridges (as well as async/sync bridges) successfully, so I don't mind checking your settings, particularly I am interested in the settings within the Module tab of the JMS receiver. I can then compare to mine if you'd like. Also if you can let me know what underlying queuing system in that target system (e.g. MQSeries?) that would be great.
Regards,
Keith

JDBC comm.channel issue with MS SQL select statement

Hello,
We are using JDBC adapter to connect to an MS SQL database.
This is the comm.channel config.
com.microsoft.sqlserver.jdbc.SQLServerDriver
jdbc:sqlserver://<DNSname>:1433;databaseName=PSMI
Activation of channel is successful.
But when starting a select on a table of the database we will get this error for any table there in comm.channel monitoring.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'TABLENAME' (structure 'STATEMENT'): com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'SAP_Header'.
Error processing request in sax parser: Error when executing statement for table/stored proc. 'TABLENAME' (structure 'STATEMENT'): com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'SAP_Header'.
Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'TABLENAME' (structure 'STATEMENT'): com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'SAP_Header'.
The table is existing because we can access it from excel database connect.
The connect address is the same in Excel as in comm.channel.
Installed driver is for JDBC for 2000/2005 (1.2/4). for JDK 1.4
Your help is really appreciated!
Best regards
Dirk

Hi Dirk,
This is the comm.channel config.
com.microsoft.sqlserver.jdbc.SQLServerDriver
jdbc:sqlserver://<DNSname>:1433;databaseName=PSMI
I hope the DNSname you using is your Server name of the SQL Server (IP/ServerName) you trying to connect to.
Please ensure that if you are using Hostname the entry is made in the host file at server level against the IP.
Try using the Connection string as :
jdbc:microsoft:sqlserver://IP(hostname)\ServerName;DatabaseName
Cheers
Dhwani
Edited by: dhwani kamdar on Jun 11, 2010 5:31 PM

ABAP Proxy comm channel not seen in Comm Channel monitoring

We have configured JDBC sender to ABAP proxy receiver.
We are unable to see the receiver channel in comm channel monitoring. Is this normal or are we missing something?
Also, the XI adapter cannot be seen in adapter monitoring...I hope thats fine...
We are able to generate the ABAP proxy but we need to see the comm channel to troubleshoot.
Any help will be appreciated.
Thanks

Hi SAP PI,
As with the above commens this link may help u how to debug proxies.. you may try with this..
For -- Debugging Proxies
https://weblogs.sdn.sap.com/pub/wlg/4098--Debugging [original link is broken] [original link is broken] [original link is broken]
For -- Testing Proxies
XI: Debug your inbound ABAP Proxy implementation
regards,
Kishore

SELECT query in a sender jdbc comm channel

Hi experts,
I would like to access a table in a database and select some rows from there but from a specific date onwards. I mean, i want to retrieve only the rows from, lets say, table.date = 2008-04-05 on.
So i specified somthing like:
*SELECT * FROM table WHERE date >= to_date(2008-04-05) and status ='0'*
UPDATE table SET status='1' WHERE date >= to_date(2008-04-05) and status ='0'
BUT this is throwing following error message:
The JDBC driver returned the following error message: 'java.sql.SQLException: ORA-00911: invalid character '. For details, contact your database server vendor.
Could you please provide some support in order to achieve this?
Thanks in advance and best regards,
David

Hi there,
I tried again without using the 'to_date' function but still doesnt work.
I have no access to the database so i asked the DB team to make some testing there. They say the date format in the DB is 'dd-mm-YYYY' but XI receives 'YYYY-mm-dd' via jdbc adapter!!!!
So, at first i typed 'YYYY-mm-dd' in the query and this was the result:
Database-level error reported by JDBC driver while executing statement 'SELECT * FROM albaranes,lineas WHERE albaranes.albaran = lineas.albaran and albaranes.fecha_albaran >= 2004-06-19 and albaranes.sap_status ='3''. The JDBC driver returned the following error message: 'java.sql.SQLException: ORA-00911: invalid character '. For details, contact your database server vendor.
and shortly afterwards i used 'dd-mm-YYYY' and this is what i got:
Database-level error reported by JDBC driver while executing statement 'SELECT * FROM albaranes,lineas WHERE albaranes.albaran = lineas.albaran and albaranes.fecha_albaran >= '19-06-2004' and albaranes.sap_status ='3''. The JDBC driver returned the following error message: 'java.sql.SQLException: ORA-01843: not a valid month '. For details, contact your database server vendor.
sap_status field is of string type so this is not the point, i think.
Could you please advice?
Best regards,
David
Edited by: Domingo Jimenez Navarrete on May 5, 2008 12:18 PM

Mail Sender Communication channel not polling

Dear all,
In our PI 7.1 Sever, we have observed a issue.
Sender mail communication channel status is green in RWB-->Channel monitoring but the channel does not pick up any mails form the mailbox.
After we stop and then start the channel, it is picking up the mails.
Any pointers on the root casue for this issue and any resolution steps or any SAP Notes to implement will be of great help.
Regards,
Younus

Hi,
Is it like everytime you have to restart the mail channel again and again?
Sometimes it happens, a quick restart will refresh the adapter cache and the messages are processed.
So, its not a problem.
Regards,
Sushama

Mail-to-Mail scenario - Problem with comm. channel not reading message

Good day,
I am setting up a Mail-to-Mail scenario, where a received e-mail with an attachment is both processed into a file, as well as a monitoring e-mail needs to be send. The attachment processing is an existing process and is still working properly, but my e-mail isn't send. I am using Java mapping to create the destination e-mail based on the source e-mail. Everything is set up in the Directory as well, and through the Test Configuration feature I have tested my new addition to the existing process, I am seeing the result that I am expecting. I have sent a test message and XI picks it up just fine and processes it which is tested by both SXMB_MONI and the resulting file from the attachment.
However, the monitoring e-mail is not sent. Using the runtime workbench, there is an error in the receiver communication channel, being the following error from the Audit Log:
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.messaging.util.XMLScanException: java.lang.NullPointerException; nested exception caused by: java.io.IOException: Parsing an empty source. Root element expected!
Looking through the Message Content, I notice there is a SOAP document describing the source message and two payloads. The first payload being the source message in XML format, the second payload is entirely empty. I suspect this empty second payload is causing the NullPointerException, but I am at a loss as to why the payload is empty. The Test Configuration showed me that the message gets through just fine, so what is going wrong?
Here is a link to the configuration of the communication channel, maybe something is wrong here: [Config of communication channel|http://roald.hoolwerf.net/images/cc-config.png]
My question is: What can I do to find what is causing the communication channel to receive an empty payload, and how can I solve this?
Searching for this issue, or the given error on both Google as these forums hasn't given any related posts, if I did miss them in that case I am sorry for posting and please refer to the related topics.
Thank you in advance for taking time to look at this question.
Kind regards,
Roald Hoolwerf
Edited by: Roald Hoolwerf on Feb 1, 2010 3:57 PM

Try this.
Unchecked the configure use authentication.
and use mail package (base64)

PI Sender JMS channel not reading data

Hello All,
Scenario is JMS to Proxy. I have configured the JMS PI sender channel as per the details given by legacy team and they validated and confirmed that the channel configuration is correct.
Also PI JMS Sender channel is with green status and no there are no errors observed on PI channel monitoring page. Legacy team said that they placed 2 messages on the Queue for SAP PI to read. But there is no data flow observed into PI (on Adapter Engine/IE).
I have restarted and reactivated the channel also.
Can you please tell me what might be issue here
Thanks,

Hi Naresh,
Are you able to ping the channel from the Java stack? Normally if it is screen it means that is working but try and ping it and see what response you get back.
What are they using? MQSeries? JNDI? SonicQ?
Use the connection details that they gave you and log onto the queue and check if you can see the messages? Download a free JMS viewer and connect and see if you are able to see those messages? It might that they placed it in the wrong queue or that you are looking at the wrong queue.
Regards,
Jannus

JDBC sender adapter polling data more than once within one polling interval

Hi,
Our sender communciation channel is polling data twice in one polling interval, hence triggering the corresponding BPM twice.
The polling interval for the channel is set to 30 mins.
We dont have an update query and use <test> instead. Currently there is no provision to use an update query in the source system.
Intermitently the polling happens within an interval of few milliseconds, because of which we are in doubt whether the use of Update query will solve our problem
Additionaly in the BPM, we have one channel which deletes the data from source system after the processing is complete by the BPM, but the second BPM is getting triggered before the deletion step is being executed in the first BPM.
Please Advise how we can stop the channel from polling data twice.
Thanks,
Merrilly.

Hi Merrilly,
Please ty to set an advanced mode option in the table(for sender
channel configurations) as follows:
Key name is "clusterSyncMode" and its values are either "scheduler" or
"none".(both are without quotes and case-sensitive)
Default value is "scheduler", this means it prevents 2
messages being generated regardless of 2 server nodes. This is true,
even if you do not add anything in advanced options table.
Also are more information about this parameter of file adapter, what
is the same for jdbc:
#801926 - XI 3.0 File Adapter: Additional Parameters
Regards
SK

JDBC Comm Channel not Polling data

Similar Messages

Maybe you are looking for