on 12-18-2007 7:36 PM
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,
Chad
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
VJ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
iSeries is on a separate server altogether. JDBC connection to the iSeries is setup through the communication channel.
Problem is that the network issue that disconnected PI from the iSeries left these communication jobs running on the iSeries.
Rebooting PI only created MORE of these communication jobs.
Thanks for the reply VJ, but I don't believe the poll interval would help me in this case.
Chad
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
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.