It's all about the answers!

Ask a question

Data Warehouse Reporting Collection Job HTTP 403 : Forbidden error


Bill Kecskes (1621) | asked Jul 15 '12, 8:41 p.m.
Getting an error on the Data Warehouse collection job for requirements.  A Http 403 Forbidden error.  The Requirements job is the only task failing.

From the log file:

2012-07-09 175619,687 [        http-443-Processor1142]  INFO ouse.service.rrc.internal.RemoteRRCSnapshotService  - Starting Requirements Composer ETL jobs
2012-07-09 175619,687 [        http-443-Processor1142]  INFO ouse.service.rrc.internal.RemoteRRCSnapshotService  - Using threshold value 20
2012-07-09 175619,687 [        http-443-Processor1142]  INFO ouse.service.rrc.internal.RemoteRRCSnapshotService  - -=LINKS=-
2012-07-09 175642,437 [        http-443-Processor1142] ERROR ouse.service.rrc.internal.RemoteRRCSnapshotService  - java.sql.SQLException com.ibm.rational.etl.common.exception.ETLException com.ibm.rational.etl.common.exception.ETLException com.ibm.rational.dataservices.client.auth.AuthenticationException CRRRE1417E The HTTP status '403' and the message is 'Forbidden'.
2012-07-09 175642,437 [        http-443-Processor1142]  WARN ouse.service.rrc.internal.RemoteRRCSnapshotService  - Last known operation Getting link types
2012-07-09 175642,437 [        http-443-Processor1142]  WARN ouse.service.rrc.internal.RemoteRRCSnapshotService  - Operation target RRC

Found a tech note that refers to special char. in the password but doesn't seem to apply.

Anyone have any ideas?

Thanks

Bill.


Comments
Brian DiCola commented Mar 04 '14, 2:13 p.m.

Had a similar issue.  The following data collection jobs were failing:
JTS - Requirements
CCM - Build

RQM - Quality Management Jobs

Applied the Data Collection license to etl_user and it was fixed.  Interesting that other jobs succeeded under the same account.

3 answers



permanent link
Benjamin Silverman (4.1k69) | answered Jul 16 '12, 2:44 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Bill,

Are you running the jobs for RTC/QM/JTS, or are you only seeing this problem with the RM data collection jobs?  It looks like an issue with the data collection user.  Can you confirm that the data collection is specified when you look under jts/admin -> Reports and has the "Data Collector" license assigned in jts/admin -> Users?  If the password is wrong for the Requirements job, you might expect to see an error like this, so you may want to try logging in to RRC with that user and updating the password in the "Reports" section of jts/admin for the requirements job if needed.  Hope it helps,

permanent link
Bill Kecskes (1621) | answered Jul 16 '12, 11:37 p.m.

Are you running the jobs for RTC/QM/JTS, or are you only seeing this problem with the RM data collection jobs?  RM only. Other jobs are running fine, including the “Common” and “Star” data collection jobs running for JTS

It looks like an issue with the data collection user. Can you confirm that the data collection is specified when you look under jts/admin -> Reports and has the "Data Collector" license assigned in jts/admin -> Users?  User belongs to JazzAdmin group and has a Data Collection license assigned

If the password is wrong for the Requirements job, you might expect to see an error like this, so you may want to try logging in to RRC with that user and updating the password in the "Reports" section of jts/admin for the requirements job if needed. Other jobs are running fine with this user and user was able to login to RRC



permanent link
Benjamin Silverman (4.1k69) | answered Jul 17 '12, 12:34 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Bill,

In this case, you will probably need to re-configure the logging for the RM ETL to show more details about what is happening during the failure.  To do this, you can modify the log4j.properties file under the <CLM_Install>\server\conf\jts\log4j.properties.  In the section labeled "ETL's", comment out the first two lines and uncomment the 3rd and 4th lines so the file looks like this:

#log4j.logger.com.ibm.rational.drivers.jdbc.xml=OFF
#log4j.logger.com.ibm.rational.etl=OFF
log4j.logger.com.ibm.rational.drivers.jdbc.xml=INFO, etlDriver
log4j.logger.com.ibm.rational.etl=INFO, etlDriver

The jts-etl.log should contain the same error as well as additional data surrounding it, and you also may want to check the rm.log and jts.log for any additional errors logged at the same time as the 403/Forbidden error.  You can post the result here if possible, but it might make more sense to log a PMR with support as the logs might be fairly large, requiring a more thorough investigation.  Hope it helps!

Comments
Bill Kecskes commented Jul 20 '12, 12:04 a.m.

Hi Benjamin,

I enabled the additional logging and the only error turned up in the jts-etl-driver.log. It complained about a URL that could not be accessed. Using a browser I could load a xml file at that address. Not sure if that's the correct response.

First couple of lines -

<ds:datasource xmlns:ds="http://jazz.net/xmlns/alm/rm/datasource/v0.1" xmlns:rm="http://www.ibm.com/xmlns/rdm/rdf/" xmlns:rrm="http://www.ibm.com/xmlns/rrm/1.0/" href="https://jazz.XXX.XXX.au/rm/publish/linktypes/*?size=1&amp;typesPrj=_ATqGUkF0EeGfoYxiGi8Xyw" rel="next"><ds:project><rrm:about>https://jazz.XXX.XXX.au/jts/resource/itemOid/com.ibm.team.process.ProjectArea/_9pfxkkLxEeGwH9wA5N5Pvg</rrm:about><rm:linktype rm:about="https://jazz.XXX.XXX.au/rm/types/_-Hvz8ELxEeGwH9wA5N5Pvg"><rm:sameas rm:resource="http://www.ibm.com/xmlns/rdm/types/Decomposition"/><rm:objecttosubjectlabel>Parent Of</rm:objecttosubjectlabel><rm:subjecttoobjectlabel>Child

Looks like it's returning the right info - reference to RM objects.

I will raise a PMR and see if I can get some official help.

Thanks for your suggestions,

Bill.

Your answer


Register or to post your answer.