It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×4,712
×3,951
×403
×94

question asked: Feb 18 '14, 8:01 p.m.
question was seen: 4,679 times
last updated: Feb 19 '14, 3:17 p.m.

Related questions

Data Warehouse "Requirements" Job Fails Every Night

0
Dave Evans (148●1●28●46) | asked Feb 18 '14, 8:01 p.m.
edited Feb 18 '14, 8:07 p.m.

Greetings,

Ever since we upgraded from 401 to 405, the "Requirements" Data Collection Job has failed almost every night. It runs for about 2 hours and 40 minutes. I notice errors in both the jts-etl and jts-etl-driver logs at the time of failure:

java.sql.sqlexception: com.ibm.rational.etl.common.exception.etlexception: java.net.socketexception: Connection reset

Any ideas what would be causing the connection to be reset/this failure to occur?

Thanks,

Dave

jts-etl.log snippet:

ERROR ouse.service.rrc.internal.RemoteRRCSnapshotService  - java.sql.SQLException: com.ibm.rational.etl.common.exception.ETLException: java.net.SocketException: Connection reset
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  - Preceding event: 'CALL' from 'RRCRequirementETL::resetInitialCounts()'
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  - Preceding event: 'CALL' from 'RRCCustomAttributeETL::initPrepareStatements(?)'
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  - Preceding event: 'CALL' from 'RRCCustomAttributeETL::resetInitialCounts'
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  - Preceding event: 'CALL' from 'RRCRequirementsLookupsETL::initPrepareStatements(?)'
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  - Preceding event: 'CALL' from 'RRCRequirementsLookupsETL::resetInitialCounts()'
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  - Preceding event: 'CALL' from 'RRCExternalLinkETL::initPrepareStatements(?)'
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  - Preceding event: 'CALL' from 'RRCExternalLinkETL::resetInitialCounts()'
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  - Preceding event: 'Get page - RRC requirements' from 'RemoteRRCSnapshotService::updateSnapshot(?)'
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  -  Event subject: 0
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  - Preceding event: 'CALL' from 'RemoteRRCSnapshotService::getNextResourcesPage(Connection con, String resourceGroupName, String modifiedSince, int pageSize, boolean linksOnly, boolean[] more'
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  -  Event subjects:
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  -  com.ibm.rational.drivers.jdbc.xml.RDSConnection@2a77a163
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  -  RRC
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  -  2014-01-30 00:00:00.0
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  -  100
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  -  [Z@2a77a15b
 WARN .ibm.team.datawarehouse.service.rrc.util.ETLTracer  - Suspect event: 'Querying the XDC table' from 'RemoteRRCSnapshotService::getNextResPage(?,...)'

Comments
Håkan Kristiansson commented Feb 19 '14, 1:37 a.m.

What do you see in the rm.log and jts.log at the same you get the above error? It might shed some lights on what's going on.

Dave Evans commented Feb 19 '14, 3:16 p.m.

Nothing is reported in the jts or rm logs within an hour of the error reported in jts-etl and jts-etl-driver logs.

One answer

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Ralph Schoon (63.6k●3●36●46) | answered Feb 19 '14, 2:18 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Dave, you probably want to open a PMR with support, or open a work item to be able to share logs and collaborate on this.
Comments
Dave Evans commented Feb 19 '14, 3:17 p.m.

Yes... I always forget about the comment length limitation. I will open a PMR tomorrow if a change I am trying doesn't fix it tonight. Thanks!

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.