Hi,

we are having the same issue with the proxy and the http 500 error.

However, happens only for one DOORS project.

Steps:

1. open any test case in any project in RQM.

2. go to requirements links section and add any requirement stored in DOORS Project 2.

3. Save. All works ok.

4. In the same test case or a different one (doesn't matter) add another requirement stored in DOORS Project 1.

5. Save. Proxy can't be read, error 500.

In doors, the URL for the requirements is exactly the same which the proxy in RQM is trying to reach. So the problem is not malformed URLs or a configuration problem in the name of the server.

Both Doors projects are on the same server, so the problem can't be the https issue.

Linking the requirements from the DOORS side to RQM works over the OSLC interface as expected.

There is only one requirements provider defined for the application and the project area. Re-adding doors as provider in one project didn't fix the issue.

Does anyone have an idea what could be wrong here? It seems an issue on the DOORS side, but I have no expertise and can't access the logs at the moment.

Thanks in advance for any help.

Unfortunately, I don't get the NPE in connection with this problem.

Actually, I don't see the same error (unable to load /qm/proxy...)  in any of the jazz related logs (qm.log, ccm.log, jazz.log, etc) located under the WebSphere\AppServer\profiles\AppSrv_CLM_JAZZ\logs folder. The only log which adds an error when this behaviour is observed on the web ui is the CLM_Jazz_Server_exception log. The exception logged there has to do with expired tokens and it occurs also without trying to save a requirement link from RQM.

This is the exception which is repeated in that log file over and over again: com.ibm.websphere.security.auth.TokenExpiredException com.ibm.ws.security.ltpa.LTPAServerObject.validate 1267 C:\IBM\WebSphere\AppServer\profiles\AppSrv_CLM_JAZZ\logs\ffdc\CLM_JAZZ_server_3e46fe32_13.04.11_16.21.21.594601035360907823653.txt

We have configured DWA, Doors and RQM as instructed except for the https configuration for DWA. Our DWA server listens on http 8070. This configuration has also been already verified as correct.

Possible causes for this error which I think I can discard are following:

• Wrong configuration of the DWA server - not the problem since we can add links to one Doors project on the same DB using the same instances of DWA, Doors and RQM. The problem is specific to one Doors project.
• Not sufficient rights for the users to set a link in Doors - seems not to be the problem, since the same users can add the "validated by" links from Doors to RQM and save them without any issue (this is also the current workaround)
• Null Pointer Exception due to an unnecessary oAuth validation - seems not to be the problem, since every single time a link is set between Doors and RQM from the RQM side the oAuth.log logs "Parameters validated" and "Signature validated".

After activating the log properties for "support" in the festival configuration in Doors I have found one log file which throws an exception clearly related to this issue. The exception doesn't tell me anything conclusive though. This is the exception thrown in the error_misc.log file:

2013-05-21 15:17:56,104 | DEBUG | [          ErrorUtils:449 ] [Message:Creating unchecked exception: Reason [UNKNOWN_ERROR], Exception [Server Exception:
 status    : Failed
 id        : LocalException - Request Failed
 reason    : UNKNOWN_ERROR
 message   :
 exception : ], Content Type [application/xml], OSLC-Core-Version [2.0]][ClientLoggingId:null][ServletLoggingId:9218177754212817474][rmLoggingId:15][SessionId:3BAC165775BF2CD0BED73CCE84BFD3B2][RequestId:20130521151744411][subSystemId:RM_STACK]

Any other ideas or suggestions how can we solve this issue?

A possibly related problem is we get a "Not Supported" pop-up message in RQM when trying to add links to some requirement modules or views to a requirements collection in a Test plan. However, I see no error messages whatsoever in the log files.

Thanks for any further help.