List issue in 3.6

List issue in 3.6 - Klaros Test Management - Forum - Klaros-Testmanagement

Dutch Buckholz, geändert vor 12 Jahren.

List issue in 3.6

Youngling Beiträge: 10 Beitrittsdatum: 18.04.12 Neueste Beiträge

When viewing a large list of tests in Maintain test cases or Maintain test suites, if the list is longer than the view it's no longer possible to move from page to page within the list.

The numbers don't work, the arrows will occasionally stack the next page results on top of the page 1 results, but sets the entire page 1 view to locked and blank when it does. If you click cancel at that point you then have the 2 page view.

This issue was present for about the first hour I had the upgraded install online. It was confirmed by multiple users on multiple machines using multiple browsers, and then started working suddenly.

catalina.2012-04-30.log
Apr 30, 2012 12:29:59 AM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(INFO 0), summary=(Welcome, adutta), detail=(Welcome, adutta)]
Apr 30, 2012 12:32:24 AM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(INFO 0), summary=(Welcome, vgupta), detail=(Welcome, vgupta)]
Apr 30, 2012 3:41:30 AM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(INFO 0), summary=(Welcome, vgupta), detail=(Welcome, vgupta)]
Apr 30, 2012 4:21:02 AM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(INFO 0), summary=(Welcome, adutta), detail=(Welcome, adutta)]
Apr 30, 2012 4:36:43 AM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(INFO 0), summary=(Welcome, adutta), detail=(Welcome, adutta)]
Apr 30, 2012 4:50:37 AM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(INFO 0), summary=(Welcome, adutta), detail=(Welcome, adutta)]
Apr 30, 2012 5:01:42 AM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(INFO 0), summary=(Welcome, adutta), detail=(Welcome, adutta)]
Apr 30, 2012 5:47:51 AM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(INFO 0), summary=(Welcome, adutta), detail=(Welcome, adutta)]
Apr 30, 2012 10:34:16 AM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(WARN 1), summary=(Please log in first), detail=(Please log in first)]
Apr 30, 2012 11:03:05 AM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(INFO 0), summary=(Welcome, dbuckholz), detail=(Welcome, dbuckholz)]
Apr 30, 2012 12:19:53 PM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(WARN 1), summary=(Please log in first), detail=(Please log in first)]
Apr 30, 2012 12:25:57 PM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(WARN 1), summary=(Please log in first), detail=(Please log in first)]
Apr 30, 2012 12:50:30 PM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(WARN 1), summary=(Transaction failed), detail=(Transaction failed)]
Apr 30, 2012 12:53:31 PM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(WARN 1), summary=(Please log in first), detail=(Please log in first)]
Apr 30, 2012 12:53:39 PM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(INFO 0), summary=(Welcome, dbuckholz), detail=(Welcome, dbuckholz)]
Apr 30, 2012 1:44:12 PM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(WARN 1), summary=(Please log in first), detail=(Please log in first)]

Torsten Stolpmann, geändert vor 12 Jahren.

RE: List issue in 3.6

Jedi Council Member Beiträge: 759 Beitrittsdatum: 12.02.09 Neueste Beiträge

Hi Dutch,

I tried to reproduced this on our demo instance http://www.klaros-testmanagement.com/demo/ but could not discover any of the symptoms you are describing.

What do you mean by 'and then started working suddenly' ?

Is there anything special with you setup (Apache mod_proxy or the like)?

Regards,

Torsten

Dutch Buckholz, geändert vor 12 Jahren.

RE: List issue in 3.6

Youngling Beiträge: 10 Beitrittsdatum: 18.04.12 Neueste Beiträge

Hi Torsten,

Nothing as deep as mod_proxy on our setup. We're on a mysql db, the http port has been changed to 80, Apache was set to 1024 max RAM, and the index.html in ROOT was changed to:

"<html>

<head>
<meta http-equiv="refresh" content="0;URL=http://klaros.dev.gt-global.com/klaros-web">
</head>

<body>
</body>

</html>"

When I said it suddenly started working I mean literally that. Moving through the list pages wasn't working for multiple people here. I was in the middle of writing the original post and it started working. No changes were made on our server during that time, no processes were started, stopped, or restarted. There was about 15 minutes of the functionality not working, now it does. I wish I had more insight into this. If we need to restart the server in the future I'll watch for it happening again.

Cheers,
Dutch