[pathduck]

Hi,

I'll check the server logs tomorrow, if there is something there to explain it.

I have a group of two AS7 that I want to set it for, both state UP. What happens is - at start the field is unset for this group - there is no value. But if I mark it and start typing, RHQ returns with a red "Unhandled exception" message at the top. I just start typing "5" and it gives the error. The Save button is then disabled and I can't change it. Maybe browser related, I use Chrome but will check in FF tomorrow.

We have a lot more servers (50-60) I need to set it for consistency, but I want to start just with these two and hopefully be able to use groups.

If I change it for just one server at a time it seems to go ok but it's a real hassle.

Thomas:  Where can I check if async availability checking is enabled now? Or is this not built for 4.8 yet? I see the BZ still has state "New" so I guess not?

https://bugzilla.redhat.com/show_bug.cgi?id=920214

Stian

[tsegismont]

You must have missed my previous reply. This new parameter has nothing to do with asynchronous availability checking. It's just there to be able to control idle time of kept alive http connections in the pool that as7 plugin uses. Only in rare cases you will need to change the default value.

[pathduck]

Hi Thomas yeah I must've misread you, I was so hung up on the Async stuff...

Here's what I find when trying to set the Connection Timeout for a group of servers:

I can set the value for each server manually, and once all servers in a group has all values set, then it also works with setting it for the group as a whole.

But I can't set it for a group, even if all the servers are UP and I can change other values. Once I try filling in a value it gives the error "Globally uncaught exception" and the Save button is disabled.

There aren't really any errors in the server.log but I get this warning every time I try to change the value:

09:13:10,768 WARN  [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (http-/0.0.0.0:7080-10) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory!

So, some error with Hibernate here?

[mazz]

As for that hibernate warning about "firstResult/maxResults specified with collection fetch; applying in memory!", that is currently in investigation and I believe lukas is about to commit some code to avoid that. See bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=620603 , specifically, Lukas' last comment.

[tsegismont]

This Hibernate warning is not linked to your upgrade issue. There is a BZ for this one: https://bugzilla.redhat.com/show_bug.cgi?id=620603

It looks like group configuration does not work on a paramater added during a plugin upgrade. Will check that.

Oh and in case I did not say it already, keep the default value for  "Management Connection Timeout" parameter, unless you have a very good reason to do so

[tsegismont]

Stian Lund a écrit:

Here's what I find when trying to set the Connection Timeout for a group of servers:

I can set the value for each server manually, and once all servers in a group has all values set, then it also works with setting it for the group as a whole.

But I can't set it for a group, even if all the servers are UP and I can change other values. Once I try filling in a value it gives the error "Globally uncaught exception" and the Save button is disabled.

Verified this behavior, it's a bug and it will be fixed (hopefully soon): https://bugzilla.redhat.com/show_bug.cgi?id=962787

[tsegismont]

mazz a écrit:

> I would like to try the async avail checking but for AS7 I cannot seem to find this under Connection Settings for the AS7 plugin?

that's a mistake and should be fixed. I created a BZ: https://bugzilla.redhat.com/show_bug.cgi?id=920214

The feature has been implemented. Asynchronous availability check is now allowed on Standalone, Domain and Managed Server resources. To enable it configure the "Availability Check Period" in the "Advanced" section of the "Connection Settings" tab.

[pathduck]

Cool - thanks a lot for fixing these Thomas

I guess it will hopefully be in 4.8 - not sure you configure the "Check Period", is it a value to fill out? But I guess I will find out

cheers,

Stian

[tsegismont]

It is fixed in master branch and therefore will be shipped in 4.8. You will find out, I trust you