Skip to Content

JDBC Connection Jobs Continue to Run After Network Issues

We've got 7.0 SP13 installed in our DEV and QAS environments. We connect to iSeries DB2 tables using a JDBC connection. We recently experienced a network issue that shutdown PI. Problem is that the system jobs used to connect to the iSeries are still running and still requiring more and more temporary storage. We've rebooted our PI boxes but still these connection jobs continue to run and gobble up more memory.

Are we missing something in our configuration of these communication channels that will force these jobs to end???

Thanks in advance,


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Dec 18, 2007 at 08:43 PM

    Is this happenning in PI box? The memory problem? Check the periodicity of the sender JDBC channel. Shut them off if you do not want to poll the data from DB2


    Add comment
    10|10000 characters needed characters exceeded