[rhq-project/rhq] 2d8969: [BZ 1071330] Try to avoid timeouts on retrieving s...
by Lukas Krejci
Branch: refs/heads/master
Home: https://github.com/rhq-project/rhq
Commit: 2d896974f527317fe418b88fcab59c3e19d1230d
https://github.com/rhq-project/rhq/commit/2d896974f527317fe418b88fcab59c3...
Author: Lukas Krejci <lkrejci(a)redhat.com>
Date: 2014-06-27 (Fri, 27 Jun 2014)
Changed paths:
M modules/core/domain/src/main/java/org/rhq/core/domain/common/composite/SystemSetting.java
M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/system/SystemManagerBean.java
Log Message:
-----------
[BZ 1071330] Try to avoid timeouts on retrieving system settings
This is a bit of a shot in the dark to reduce the possibility of
timeouts when reading system settings in the server under load.
The concurrency on the bean has been changed from the default
container managed with a write lock on each method to bean managed
with a single critical section in the cache loading and writing methods.
Also, the deobfuscation of the password fields happens only on the
cache reload and only if the settings were changed.
All this to minimize the contention on the SystemManagerBean and to
speed up the retrieval of the settings as much as possible.
Commit: 5df5508ac3415ec1d9b2eeb45c1b67b396673fd6
https://github.com/rhq-project/rhq/commit/5df5508ac3415ec1d9b2eeb45c1b67b...
Author: Lukas Krejci <lkrejci(a)redhat.com>
Date: 2014-06-27 (Fri, 27 Jun 2014)
Changed paths:
M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/system/SystemManagerBean.java
Log Message:
-----------
[BZ 1071330] Minimize the duration of the locks
Commit: 4610b91f945e9503fc6291d82a9d50973a840f22
https://github.com/rhq-project/rhq/commit/4610b91f945e9503fc6291d82a9d509...
Author: Lukas Krejci <lkrejci(a)redhat.com>
Date: 2014-06-30 (Mon, 30 Jun 2014)
Changed paths:
M modules/core/domain/src/main/java/org/rhq/core/domain/common/composite/SystemSetting.java
M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/system/SystemManagerBean.java
Log Message:
-----------
Merged pull request #57 from metlos/bug/1071330
[BZ 1071330] Try to avoid timeouts on retrieving system settings
Compare: https://github.com/rhq-project/rhq/compare/f0a5cc74233f...4610b91f945e
9 years, 5 months
[rhq-project/rhq] d7ec3f: BZ 1091128 - Support for object name partial match...
by Heiko W. Rupp
Branch: refs/heads/master
Home: https://github.com/rhq-project/rhq
Commit: d7ec3fab9bc5139fb3c1f80805014ef082ad63f8
https://github.com/rhq-project/rhq/commit/d7ec3fab9bc5139fb3c1f80805014ef...
Author: Elias Ross <elias_ross(a)apple.com>
Date: 2014-06-24 (Tue, 24 Jun 2014)
Changed paths:
M modules/plugins/jmx/src/main/java/org/rhq/plugins/jmx/util/ObjectNameQueryUtility.java
M modules/plugins/jmx/src/test/java/org/rhq/plugins/jmx/test/ObjectNameQueryUtilityDelegateTest.java
M modules/plugins/jmx/src/test/java/org/rhq/plugins/jmx/test/ObjectNameQueryUtilityTest.java
Log Message:
-----------
BZ 1091128 - Support for object name partial matching like :name=IPCLogger-%a%
Note that suffixes or infixes patterns are not supported.
One possible incompatible change is the ObjectName query will include all
object name properties, e.g. if there is
a:key=%value%
the ObjectName query used to be
a:* (and then somehow things would get filtered)
but instead the ObjectName query will be
a:key=*
Commit: f0a5cc74233f7e1ddf052e98834f80c238575b9d
https://github.com/rhq-project/rhq/commit/f0a5cc74233f7e1ddf052e98834f80c...
Author: Heiko W. Rupp <hwr(a)pilhuhn.de>
Date: 2014-06-30 (Mon, 30 Jun 2014)
Changed paths:
M modules/plugins/jmx/src/main/java/org/rhq/plugins/jmx/util/ObjectNameQueryUtility.java
M modules/plugins/jmx/src/test/java/org/rhq/plugins/jmx/test/ObjectNameQueryUtilityDelegateTest.java
M modules/plugins/jmx/src/test/java/org/rhq/plugins/jmx/test/ObjectNameQueryUtilityTest.java
Log Message:
-----------
Merge pull request #63 from genman/BZ1091128
BZ 1091128 - Support for object name partial matching like :name=IPCLogg...
Compare: https://github.com/rhq-project/rhq/compare/9220b2338d26...f0a5cc74233f
9 years, 5 months
[rhq-project/rhq] 38ab85: [1110277] RHQ_EVENT table's detail field limit of ...
by Jay Shaughnessy
Branch: refs/heads/hotfix/jon3.1.2
Home: https://github.com/rhq-project/rhq
Commit: 38ab8524608a3f9c622e609cb369df5d411cabd0
https://github.com/rhq-project/rhq/commit/38ab8524608a3f9c622e609cb369df5...
Author: Jay Shaughnessy <jshaughn(a)redhat.com>
Date: 2014-06-27 (Fri, 27 Jun 2014)
Changed paths:
M modules/core/dbutils/src/main/java/org/rhq/core/db/DatabaseType.java
M modules/core/dbutils/src/main/java/org/rhq/core/db/OracleDatabaseType.java
M modules/core/domain/src/main/java/org/rhq/core/domain/alert/notification/AlertNotificationLog.java
M modules/core/domain/src/main/java/org/rhq/core/domain/event/Event.java
M modules/core/domain/src/main/java/org/rhq/core/domain/resource/Resource.java
M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/alert/AlertManagerBean.java
M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/event/EventManagerBean.java
M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/measurement/CallTimeDataManagerBean.java
Log Message:
-----------
[1110277] RHQ_EVENT table's detail field limit of 4000 character will break when a log message contains multibyte characters (UTF-8)
This is a problem in a few places, not just events. We're not
properly protecting against the 4000 byte limit on oracle, just
the 4000 character limit declared on the varchar2 field.
- Add DatabaseType.getString() which can truncate as needed in
a vendor-specific way.
- Use the new getString() to store safe versions of event detail,
alert notification log message, and calltime dataset destination.
Conflicts:
modules/core/dbutils/src/main/java/org/rhq/core/db/DatabaseType.java
modules/core/dbutils/src/main/java/org/rhq/core/db/OracleDatabaseType.java
modules/core/domain/src/main/java/org/rhq/core/domain/resource/Resource.java
modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/event/EventManagerBean.java
modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/measurement/CallTimeDataManagerBean.java
Cherry-Pick master 1d836a790f8e8d2da79a31e8c796324e85ae7851
(cherry picked from relese/jon3.2.x commit 6a5f14b4089dfe2e17cbc926b22685baec2de206)
Conflicts:
modules/core/dbutils/src/main/java/org/rhq/core/db/DatabaseType.java
modules/core/dbutils/src/main/java/org/rhq/core/db/OracleDatabaseType.java
modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/alert/AlertManagerBean.java
(cherry picked from release/jon3.1.x commit 2d78c7359617bc2c680ab6d5e5266e0ab953656f)
9 years, 5 months
[rhq-project/rhq] 2d78c7: [1110277] RHQ_EVENT table's detail field limit of ...
by Jay Shaughnessy
Branch: refs/heads/release/jon3.1.x
Home: https://github.com/rhq-project/rhq
Commit: 2d78c7359617bc2c680ab6d5e5266e0ab953656f
https://github.com/rhq-project/rhq/commit/2d78c7359617bc2c680ab6d5e5266e0...
Author: Jay Shaughnessy <jshaughn(a)redhat.com>
Date: 2014-06-26 (Thu, 26 Jun 2014)
Changed paths:
M modules/core/dbutils/src/main/java/org/rhq/core/db/DatabaseType.java
M modules/core/dbutils/src/main/java/org/rhq/core/db/OracleDatabaseType.java
M modules/core/domain/src/main/java/org/rhq/core/domain/alert/notification/AlertNotificationLog.java
M modules/core/domain/src/main/java/org/rhq/core/domain/event/Event.java
M modules/core/domain/src/main/java/org/rhq/core/domain/resource/Resource.java
M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/alert/AlertManagerBean.java
M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/event/EventManagerBean.java
M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/measurement/CallTimeDataManagerBean.java
Log Message:
-----------
[1110277] RHQ_EVENT table's detail field limit of 4000 character will break when a log message contains multibyte characters (UTF-8)
This is a problem in a few places, not just events. We're not
properly protecting against the 4000 byte limit on oracle, just
the 4000 character limit declared on the varchar2 field.
- Add DatabaseType.getString() which can truncate as needed in
a vendor-specific way.
- Use the new getString() to store safe versions of event detail,
alert notification log message, and calltime dataset destination.
Conflicts:
modules/core/dbutils/src/main/java/org/rhq/core/db/DatabaseType.java
modules/core/dbutils/src/main/java/org/rhq/core/db/OracleDatabaseType.java
modules/core/domain/src/main/java/org/rhq/core/domain/resource/Resource.java
modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/event/EventManagerBean.java
modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/measurement/CallTimeDataManagerBean.java
Cherry-Pick master 1d836a790f8e8d2da79a31e8c796324e85ae7851
(cherry picked from relese/jon3.2.x commit 6a5f14b4089dfe2e17cbc926b22685baec2de206)
Conflicts:
modules/core/dbutils/src/main/java/org/rhq/core/db/DatabaseType.java
modules/core/dbutils/src/main/java/org/rhq/core/db/OracleDatabaseType.java
modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/alert/AlertManagerBean.java
9 years, 5 months
[rhq-project/rhq] dec8ba: 1070326 - (JON3-42) RFE: Allow AS7 deployments to ...
by Jay Shaughnessy
Branch: refs/heads/master
Home: https://github.com/rhq-project/rhq
Commit: dec8bae46446d4cde46fe13ed76585c2cfc164b8
https://github.com/rhq-project/rhq/commit/dec8bae46446d4cde46fe13ed76585c...
Author: Jay Shaughnessy <jshaughn(a)redhat.com>
Date: 2014-06-27 (Fri, 27 Jun 2014)
Changed paths:
M modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/VersionedRuntimeDiscovery.java
M modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/VersionedSubsystemDiscovery.java
Log Message:
-----------
1070326 - (JON3-42) RFE: Allow AS7 deployments to provide version in the artifact name
Adding one more thing to this feature, prevent discovery of siblings
resolving to the same resource key. In the somewhat unlikely case that
two distinct sibling deployments resolve down to the same logical
deployment, don't let it get past discovery. For example, if the user
has app-1.0.war and app-2.0.war and these are *really* different apps (and
they would probably have to be since EAP would stop deployment if they
had the same context). In this case both would be seen as app.war, and
that is a problem on the RHQ side. In this sutuation generate an
agent log warning that hopefully helps a user resolve the issue.
Note that resource upgrade already prevents an upgrade of siblings with
the same key, so this is an analogous change.
9 years, 5 months