Skip to Content
avatar image
Former Member

JDBC sender channel is not polling

I am facing issue with JDBC sender channel. The channel is in green and ping status is fine.

Channel monitoring showing only processing started in channel logs and no polling is happening.

I verified below:

1) There is valid data in database and query is running fine when it was executed in database.

2) I checked nwa/locks. I don't see any nwa/locks for JDBC channel.

3) Restarted the java service for JDBC adapter.

4) Restarted the channel multiple times.

5) Created new channel and replace the old channel in ICO.

After doing all above also I dont see any messages coming in PI

Please provide inputs to resolve this.

Thanks,

Vertika

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

8 Answers

  • Jun 19, 2015 at 01:25 AM

    Hmm.. interesting..

    Is it a working interface or new? How many records does your select query return? If the result set is huge, you might want to try reducing the number of records.

    Also just to test, point it to a different table and see if there is any change.

    Do you have any other JDBC channels pointing to that/any other DB?

    Add comment
    10|10000 characters needed characters exceeded

    • As this is a quality(test) system, can you try reducing the result set to 1000 records(update other 16k records manually in DB) just to see if channel can prepare the message?

      Also i'm not sure if you have enabled the advanced mode ->'disconnect from DB after each message processing' but you can give a try.

  • Jun 19, 2015 at 07:04 AM

    Hi Vertika,


    i hope you have double checked the table name which you used and which you have to.


    if not please check that first and also check that table contains records.

    Thanks & Regards,

    Maheswarareddy

    Add comment
    10|10000 characters needed characters exceeded

  • Jun 19, 2015 at 07:18 AM

    Hi Vertika,

    Have you checked?

    - Communication channel monitoring.

    - Check and recheck the connection settings, may be for a typo the DB is in other environment.

    - Message monitoring at Adapter Engine level.

    - If there is any queue locked, for example in dual system SMQ1/SMQ2 transaction.

    To do a dummy scenario, only for testing purpose, in which you can develop a SELECT on the receiver side in order to try to check if there is retrieve the data.

    Regards.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 19, 2015 at 05:34 PM

    Hi Vertika,

    Can you let us know the PI version you are using?

    Can you check the below note:

    831162 FAQ: XI 3.0 / PI 7.0 / PI 7.1 JDBC Adapter


    Regards

    Vishnu

    Add comment
    10|10000 characters needed characters exceeded

  • Jun 20, 2015 at 11:29 AM

    Hi Vertica,

    The JDBC channel is not picking and audit log showing as processing started means, there is java lock on the JDBC sender communication channel. Please remove the lock in NWA and restart the channel.

    NWA->Troubleshooting->Java->locks

    Regards,

    Priyanka

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 21, 2015 at 02:55 PM

    Hi Vertika,

    The point of trigger needs to be reached so that you can see the messages in PI, i.e., the execution of the select query in your sender CC. The channel is simply running and is in active status for now.

    In order to do this in QA, try to trigger from Adapter Engine under Component Monitoring, any sample message. Let it go to error. After that delete the error message from the Adapter Engine, and restart the sender CC. Now check if the same works.

    Regards,

    Souvik

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 24, 2015 at 10:18 AM

    Please implement note 1666377 - Workaround for File/JDBC/Mail Adapter not polling

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 07, 2015 at 08:40 PM

    This was resolved after Basis maintenance activity on quality where they restarted the PI server.

    Add comment
    10|10000 characters needed characters exceeded