Why does Lifecycle Project Administration hang after upgrading a CLM 3.0.1 repository to CLM 4.0?
Willy Dhondt (58●2●11●23)
| asked Jul 03 '12, 8:02 p.m.
edited Jul 03 '12, 8:24 p.m. by Geoffrey Clemm (30.1k●3●30●35)
Cannot open Lifecycle Project Administration after upgrading a CLM 3.0.1 repository to CLM 4.0. No errors during the upgrade.
The problem does not occur when installing a new CLM repository. Please advise on resolving this problem Hangs on URL: https://jts.r8w4p0m.ibm.com:20152/admin/oauthCallback?chainedCallback=https%3A%2F%2Fjts.r8w4p0m.ibm.com%3A20152%2Fadmin&oauth_token=cf4f69c03b7a4a1ba9fffc3987372b38&oauth_verifier=bba8586d8652421a9cf0fcc7920d1a85 lpa_user has a "LPA Application Internal" license, is not defined in LDAP Environment: OS: RHEL 6.2 x86_64 WAS 7.0.21 - no IHS DB2 V9.7 openLDAP /etc/hosts: 127.0.0.1 jts.r8w4p0m.ibm.com SystemOut.log: [7/4/12 1:04:21:501 CEST] 00000017 srt W com.ibm.ws.webcontainer.srt.SRTServletResponse addHeader WARNING: Cannot set header. Response already committed. [7/4/12 1:04:21:502 CEST] 00000017 srt W com.ibm.ws.webcontainer.srt.SRTServletResponse addHeader WARNING: Cannot set header. Response already committed. [7/4/12 1:04:21:504 CEST] 00000017 srt W com.ibm.ws.webcontainer.srt.SRTServletResponse setStatus WARNING: Cannot set status. Response already committed. [7/4/12 1:04:27:933 CEST] 0000001a SystemOut O 01:04:27,933 [WebContainer : 4] ERROR net.jazz.ajax.service/auth.DelegatedAuthProvider - Must have a single friend (the JTS) to use delegated auth admin.log: 012-07-04 00:50:51,899 [ WebContainer : 2] INFO com.ibm.team.lpa.config - CRJCA0037I Lifecycle Project Administration Build RJF-I20120531-1400 2012-07-04 00:50:52,363 [ WebContainer : 2] INFO com.ibm.team.lpa.config - com.ibm.team.lpa.app.jtsTargetHost=LpaInit.Default 2012-07-04 00:50:52,363 [ WebContainer : 2] INFO com.ibm.team.lpa.config - com.ibm.team.lpa.app.jtsVirtualHost=LpaInit.Default 2012-07-04 00:50:52,363 [ WebContainer : 2] INFO com.ibm.team.lpa.config - CRJCA0010I Project Administration application running at https://jts.r8w4p0m.ibm.com:20152/admin, using Jazz Team Server at https://jts.r8w4p0m.ibm.com:20152/jts/rootservices 2012-07-04 01:02:33,576 [ WebContainer : 8] ERROR net.jazz.ajax.service/auth.DelegatedAuthProvider - Must have a single friend (the JTS) to use delegated auth 2012-07-04 01:04:27,933 [ WebContainer : 4] ERROR net.jazz.ajax.service/auth.DelegatedAuthProvider - Must have a single friend (the JTS) to use delegated auth 2012-07-04 01:19:47,390 [ WebContainer : 13] ERROR net.jazz.ajax.service/auth.DelegatedAuthProvider - Must have a single friend (the JTS) to use delegated auth 2012-07-04 01:20:00,220 [ WebContainer : 13] ERROR net.jazz.ajax.service/auth.DelegatedAuthProvider - Must have a single friend (the JTS) to use delegated auth 2012-07-04 01:20:11,301 [ WebContainer : 13] ERROR net.jazz.ajax.service/auth.DelegatedAuthProvider - Must have a single friend (the JTS) to use delegated auth 2012-07-04 01:20:59,271 [ WebContainer : 1] ERROR net.jazz.ajax.service/auth.DelegatedAuthProvider - Must have a single friend (the JTS) to use delegated auth ~ |
Accepted answer
Ralph Schoon (63.5k●3●36●46)
| answered Jul 04 '12, 7:46 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Willy, what I would try:
Check the conf/admin folder: There is a friends.rdf file. Please examine that file, especially the URL's. I have seen some with typos from the past that became an issue after upgrades. In addition: Download the CLM2011 Upgrade Workshop from the library. Look into the troubleshooting document and follow it to: - Clear the WAS Caches for admin (and potentially all other applications) - Clear the browser cache The error message is around the connection between JTS and LPA and I don't know what could cause it if everything is properly registered. Ralph Schoon selected this answer as the correct answer
|
3 other answers
|
Ralph Schoon (63.5k●3●36●46)
| answered Jul 04 '12, 2:55 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Willy,
can you open the LPA application at all? If not, try to force a redeploy. From the error message, I would check if LPA is properly registered and I would look into the consumer keys and if the consumer key for LPA matches the settings in the registration, belongs to the lpa user and is trusted. The LPA user does not need to be in LDAP as far as i am aware. |
|
Hi Ralph,
the LPA application does not open at all, browser shows blank screen. I redeployed the admin.war but that did not solve the problem. It looks like the application is properly registered. "Authorized Keys" has an entry: /admin,
trusted "Registered Applications" has an entry: /admin https://jts.r8w4p0m.ibm.com:20152/admin/scr 7d738916e0a048f1b2703445bc8d3bc5 P.S.: I tried adding ldap_user to LDAP (just in case) but it did not solve the problem either. |
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.