It's all about the answers!

Ask a question

JAZZ logs warnings/errors


Norman Dignard (35045799) | asked Jan 16 '14, 8:47 a.m.
CLM 4.0.5 single server install (RTC, QM/DNG) oracle backend

I'm trying to resolve a few issues but having problems understand the what the issue is.  Yesterday a user could not log in via the web even after resetting his password. He kept getting bad user id or password. It had worked in the morning.  We also tried the login from different hosts but got the same error. Other users could still login.  In looking at the logs I noted a lot of errors/warning in various apps.  In any event, last night as no one is using the system, I shutdown JAZZ , moved the log logs aside and restarted. On start up I see this warning in the ccm log.
Note before teh shutdown, there were no active licenses being used.

2014-01-15 21:21:13,874 [http-bio-9443-exec-27 @@ 21:21 hoftyzs /ccm/service/com.ibm.team.scm.common.IScmService]  WARN m.team.repository.common.internal.util.ObjectSizer  - Unhandled ObjectSizer Class Case : 'com.ibm.team.repository.service.internal.rdb.TransactionalCollection$StaticCollection'

What is the cause/issue here? Is it due to user hoftyzs not closing a client (web or RTC) session or is there some other cause?

In the QM log , since our initial deployment we have been having these msgs.  I asked IBM about these and and all they said is that there never have seen this.   Anyone know what the issue may be here?

 2014-01-15 21:20:57,461 [          http-bio-9443-exec-5]  WARN ice.internal.verticalRegistry.ComponentORMProvider  - The Helper reference at VariableMapEntry#value is marked not as a containment reference but it should be. All Helper references should be marked as containment. Please update your model so that the containment is correct.
2014-01-15 21:20:57,468 [          http-bio-9443-exec-5]  WARN ice.internal.verticalRegistry.ComponentORMProvider  - The Item reference at ManualExecutionScript#elements is marked as a containment reference but it should not be. All Item references should be marked as non-containment. Please update your model so that the containment is correct.
2014-01-15 21:20:57,785 [          http-bio-9443-exec-5]  WARN ice.internal.verticalRegistry.ComponentORMProvider  - The Helper reference at VariableMapEntry#value is marked not as a containment reference but it should be. All Helper references should be marked as containment. Please update your model so that the containment is correct.
2014-01-15 21:20:58,140 [          http-bio-9443-exec-5]  WARN ice.internal.verticalRegistry.ComponentORMProvider  - The Helper reference at DatapoolVariable#suggestedType is marked not as a containment reference but it should be. All Helper references should be marked as containment. Please update your model so that the containment is correct.

Again in qm.log I also have the following which appear to be due to users still having open session in JAZZ.  The first error may be related to the ccm error error above but can't realy say. The second error is for a different user/project area. I have quite a few (@100 or so) entries like this and growing. Again this is a fresh restart of JAZZ but it appears to generate these on an on-going basis.

2014-01-15 21:29:23,220 [qm: AsynchronousTaskRunner-4 @@ 21:29] ERROR com.ibm.rqm.defects.service  - RTCHttpsClient:login AQXLM5002E The text for the login error (response code) - 408
Response Body: <html><head><title>Apache Tomcat/7.0.32 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 408 - The time allowed for the login process has been exceeded. If you wish to continue you must either click back twice and re-click the link you requested or close and re-open your browser</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>The time allowed for the login process has been exceeded. If you wish to continue you must either click back twice and re-click the link you requested or close and re-open your browser</u></p><p><b>description</b> <u>The client did not produce a request within the time that the server was prepared to wait.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.32</h3></body></html> error message could not be retrieved.

2014-01-15 21:29:23,244 [qm: AsynchronousTaskRunner-4 @@ 21:29] ERROR com.ibm.rqm.defects.service  - ChangeRequestCollector:runTask AQXCM5001E The OSLC request to connect to a remote server failed.  Project area: STWS (Quality Management); Connection URL: https://jazznc.deveng.local:9443/ccm/oslc/contexts/_KBOe4PL1EeKqudgVKqly4w/workitems/services.xml; Details: The reference to entity "etag" must end with the ';' delimiter..

2014-01-15 22:27:48,455 [qm: AsynchronousTaskRunner-0 @@ 22:27] ERROR com.ibm.rqm.defects.service                        - ChangeRequestCollector:runTask AQXCM5001E The OSLC request to connect to a remote server failed.  Project area: Reporting Server (Quality Management); Connection URL: https://jazznc.deveng.local:9443/ccm/oslc/contexts/_oTQMoFFgEeO_VuEiEkePvQ/workitems/services.xml; Details: The reference to entity "etag" must end with the ';' delimiter..



Comments
Krzysztof Kaźmierczyk commented Jan 16 '14, 9:07 a.m.

Hi Norman,
What do you see when you try reaching following addresses:
https://jazznc.deveng.local:9443/ccm/oslc/contexts/_KBOe4PL1EeKqudgVKqly4w/workitems/services.xml
https://jazznc.deveng.local:9443/ccm/oslc/contexts/_oTQMoFFgEeO_VuEiEkePvQ/workitems/services.xml;
Please also check catalina.out log file from Tomcat directory to search for any issues there.


Norman Dignard commented Jan 16 '14, 12:03 p.m.

The catalina.out file shows the same errors as the qm.log. Belwo iare screenshots of the 2 links

screenshot of link 1

screenshot of link 2


Marty Duchow commented Jun 20 '14, 10:01 a.m.

Hi Norman,

Did you ever get the issue resolved about the excessive error messages in the log for this?

2014-01-15 22:27:48,455 [qm: AsynchronousTaskRunner-0 @@ 22:27] ERROR com.ibm.rqm.defects.service                        - ChangeRequestCollector:runTask AQXCM5001E The OSLC request to connect to a remote server failed.  Project area: Reporting Server (Quality Management); Connection URL ttps://jazznc.deveng.local:9443/ccm/oslc/contexts/_oTQMoFFgEeO_VuEiEkePvQ/workitems/services.xml

Details: The reference to entity "etag" must end with the ';' delimiter..

These message began appearing in our qm.log after upgrade from 4.0.4 to 4.0.6 (we skipped 4.0.5). I'm working with IBM support and they tell me its due to invalid data in artifacts in the linked RTC project, but I can't find any errors and don't buy their explanation.

Thanks,

Marty 


Ara Masrof commented Jun 20 '14, 10:11 a.m.
JAZZ DEVELOPER

Marty,

You may be encountering the following defect

Defect 105403  (AQXCM5001E/AQXLM5002E errors when integrating RTC  as a defect provider.)

Ara

 


Norman Dignard commented Jun 20 '14, 12:43 p.m.

Its a bug. Basically was told to ignore it . The above defect may be the one that is addressing it.  

2 answers



permanent link
Stephanie Bagot (2.1k512) | answered Jan 16 '14, 12:51 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
I would ignore the warnings for now and focus on the user not being able to login and the login time exceeded errors.

Firstly, are you using LDAP or Tomcat file based authentication?
If you are using LDAP, then resetting the password from within RTC will not work. The password needs to be reset from the LDAP server, since RTC (through the application server) will contact the LDAP server for authentication. Can the user log in to their local application using their LDAP ID?
If you are using Tomcat, I would open up the tomcat-users.xml file located in tomcat/conf directory. For the user that is unable to login, change their password in the file to the same hash as your password. This essentially sets their password to yours (the reason I chose yours is because you know what the hash translates to). Save the file and restart RTC. Have the user attempt to login, and once it is successful, reset both your password and the users password.

The login time exceeded errors may be related to latency between the user, the LDAP Server (if using one) and your application server (Tomcat/WAS) hosting RTC. Are your users remote from the server? Are other users complaining about inability to login?

Comments
Norman Dignard commented Jan 16 '14, 2:27 p.m.

We are using tomcat. As for the user can't log in problem - after a jazz restart he can now log in.

The QM.log errors however still persist


permanent link
SEC Servizi (93622244) | answered Sep 18 '17, 9:21 a.m.
On start up I see this warning in the ccm log. Note before teh shutdown, there were no active licenses being used. 2014-01-15 21:21:13,874 [http-bio-9443-exec-27 @@ 21:21 hoftyzs /ccm/service/com.ibm.team.scm.common.IScmService]  WARN m.team.repository.common.internal.util.ObjectSizer  - Unhandled ObjectSizer Class Case : 'com.ibm.team.repository.service.internal.rdb.TransactionalCollection$StaticCollection' What is the cause/issue here? Is it due to user hoftyzs not closing a client (web or RTC) session or is there some other cause? 

hoftyzs is the first user calling the IScmService after a server reboot. We see the same warning message and are looking for cause... (see https://jazz.net/forum/questions/231826/unhandled-objectsizer-class-case-on-first-call-of-iscmservice).



Your answer


Register or to post your answer.