[JBoss JIRA] (WFLY-3112) One can't change history and decay with DynamicLoadBalanceFactorProvider
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3112?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3112:
-----------------------------------------------
mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1075215|https://bugzilla.redhat.com/show_bug.cgi?id=1075215] from VERIFIED to CLOSED
> One can't change history and decay with DynamicLoadBalanceFactorProvider
> ------------------------------------------------------------------------
>
> Key: WFLY-3112
> URL: https://issues.jboss.org/browse/WFLY-3112
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: 8.0.0.Final
> Reporter: Michal Babacek
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 8.1.0.CR1, 8.1.0.Final
>
> Attachments: redacted_log
>
>
> I'm under an ugly impression that one can't actually change {{history}} and {{decay}} attributes of *DynamicLoadBalanceFactorProvider*.
> I was trying to figure out why the new test suite of CustomLoadMetric tests does not pass. In order to get load figures without history and decay manipulation, I set the following:
> {code}
> <subsystem xmlns="urn:jboss:domain:modcluster:1.2">
> <mod-cluster-config advertise-socket="modcluster" connector="ajp">
> <dynamic-load-provider history="0">
> <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" weight="1">
> <property name="capacity" value="1000"/>
> <property name="loadfile" value="/tmp/mod_cluster-eapx/loadfileA"/>
> <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
> </custom-load-metric>
> </dynamic-load-provider>
> </mod-cluster-config>
> </subsystem>
> {code}
> The aforementioned {{history=0}} effectively means that there is just 1 "slot" for a one historical value on which decay function should work.
> If you take a look at the code in [DynamicLoadBalanceFactorProvider|https://github.com/modcluster/mod_cluste...] constructor, it is apparent
> that the size of the List that later serves for storing the historical values is set sooner than the actual [setHistory(int history)|https://github.com/modcluster/mod_cluster/blob/master/core/src/m...] method is called.
> The actual size of that List collection wouldn't do any harm by itself but it is being used in the aforementioned class with {{.size()}} to control cycles.
> The same IMHO holds for the decay attribute.
> Anyhow, I put some additional logging to the [DynamicLoadBalanceFactorProvider.java|https://github.com/modcluster/mod_c...]:
> {code}
> // Historical value contribute an exponentially decayed factor
> for (int i = 0; i < queue.size(); ++i) {
> double decay = 1 / Math.pow(decayFactor, i);
> totalDecay += decay;
> this.log.info("KTAG: totalLoad:"+totalLoad+", with decay:"+(totalLoad+queue.get(i).doubleValue() * decay));
> totalLoad += queue.get(i).doubleValue() * decay;
> }
> {code}
> and
> {code}
> try {
> // Normalize load with respect to capacity
> this.recordLoad(metricLoadHistory, metric.getLoad(engine) / metric.getCapacity());
> this.log.info("KTAG metricLoadHistory:"+metricLoadHistory.toString());
> totalWeight += weight;
> totalWeightedLoad += this.average(metricLoadHistory) * weight;
> } catch (Exception e) {
> this.log.error(e.getLocalizedMessage(), e);
> }
> {code}
> with the following being the output: [^redacted_log].
> So, despite having {{history=0}}, which should force the system to keep just 1, the current value, {{metricLoadHistory}} grew from
> {noformat}
> KTAG metricLoadHistory:[0.8]
> {noformat}
> to
> {noformat}
> KTAG metricLoadHistory:[0.9, 0.9, 0.9, 0.9, 0.9, 0.9, 0.9, 0.9, 0.9, 0.8]
> {noformat}
> which is exactly [9|https://github.com/modcluster/mod_cluster/blob/master/core/src/main/jav...] + [1|https://github.com/modcluster/mod_cluster/blob/master/core/src/main/jav...] in size :-)
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (WFLY-1701) Race condition during server start-up - RA not deployed
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1701?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1701:
-----------------------------------------------
mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 984855|https://bugzilla.redhat.com/show_bug.cgi?id=984855] from VERIFIED to CLOSED
> Race condition during server start-up - RA not deployed
> -------------------------------------------------------
>
> Key: WFLY-1701
> URL: https://issues.jboss.org/browse/WFLY-1701
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA
> Affects Versions: 8.0.0.Alpha2
> Environment: JBoss EAP 6.1, MS Windows server
> Reporter: Tom Ross
> Assignee: Stefano Maestri
> Priority: Blocker
> Fix For: 8.0.0.Final
>
>
> A custom RA is not being deployed every during server restart even though it is linked to a MDB via @ResourceAdpater annotation. This only happens during server startup. The RA can be deployed successfully via jboss cli every time. When the deployment fails the following message appear in the log file:
> 11:30:45,303 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.ra.cdd-ra (missing) dependents: [service jboss.deployment.unit."dmgapp.jar".component.CddListenerClientMDB.CREATE]
> When comparing the log file from a successful startup with one from a failed one the only difference seems to be the absence of any output from RaXmlDeployer. See below:
> Successful startup:
> {noformat}
> 11:29:24,991 DEBUG [org.jboss.as.connector.logging] (MSC service thread 1-6) starting Inactive:InactiveResourceAdapterDeployment{module=Module "deployment.cdd-ra.rar:main" from Service Module Loader, connectorXmlDescriptor=org.jboss.as.connector.metadata.xmldescriptors.ConnectorXmlDescriptor@23322e4, deployment='cdd-ra', deploymentUnitName='cdd-ra.rar', registration=org.jboss.as.controller.registry.ConcreteResourceRegistration@6b37a7dc, serviceTarget=org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget@12ed9382}
> 11:29:24,991 DEBUG [org.jboss.as.connector.deployment] (MSC service thread 1-6) DEPLOYMENT name = cdd-ra
> 11:29:24,994 TRACE [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-6) Connector=<?xml version="1.0" encoding="UTF-8"?><connector version="1.5"><display-name>DMG CDD Resource Adapter</display-name><vendor-name>Cassidian</vendor-name><eis-type>CDD Server</eis-type><resourceadapter-version>1.0</resourceadapter-version><resourceadapter><resourceadapter-class>com.xx-yy.dmg.jca.eis.CddResourceAdapter</resourceadapter-class><outbound-resourceadapter><connection-definition><managedconnectionfactory-class>com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory</managedconnectionfactory-class><config-property><config-property-name>hostname</config-property-name><config-property-type>java.lang.String</config-property-type></config-property><config-property><config-property-name>port</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>timeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>probeTimeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface><connectionfactory-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionFactory</connectionfactory-impl-class><connection-interface>javax.resource.cci.Connection</connection-interface><connection-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionImpl</connection-impl-class></connection-definition><transaction-support>NoTransaction</transaction-support><reauthentication-support>false</reauthentication-support></outbound-resourceadapter><inbound-resourceadapter><messageadapter><messagelistener><messagelistener-type>javax.resource.cci.MessageListener</messagelistener-type><activationspec><activationspec-class>com.xx-yy.dmg.jca.eis.CddActivationSpec</activationspec-class><required-config-property><config-property-name>hostname</config-property-name></required-config-property><required-config-property><config-property-name>port</config-property-name></required-config-property><required-config-property><config-property-name>timeout</config-property-name></required-config-property></activationspec></messagelistener></messageadapter></inbound-resourceadapter></resourceadapter></connector>
> 11:29:24,995 TRACE [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-6) IronJacamar=null
> 11:29:24,996 TRACE [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-6) RaXML=null
> 11:29:24,996 TRACE [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-6) ActivateDeployment=false
> 11:29:24,998 DEBUG [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-6) CdMeta: <connection-definition><managedconnectionfactory-class>com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory</managedconnectionfactory-class><config-property><config-property-name>hostname</config-property-name><config-property-type>java.lang.String</config-property-type></config-property><config-property><config-property-name>port</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>timeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>probeTimeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface><connectionfactory-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionFactory</connectionfactory-impl-class><connection-interface>javax.resource.cci.Connection</connection-interface><connection-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionImpl</connection-impl-class></connection-definition>
> 11:29:25,000 DEBUG [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-6) No activation: com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory
> 11:29:25,001 DEBUG [org.jboss.as.connector.deployment] (MSC service thread 1-6) Registering ResourceAdapter cdd-ra
> 11:29:25,005 DEBUG [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-6) Activated: file:/C:/jboss-eap-6.1_test/standalone/tmp/vfs/temp7ab26b3b80d7102a/cdd-ra.rar-eb8a8dd4a3f65805/contents/
> 11:29:25,005 DEBUG [org.jboss.as.connector.deployment] (MSC service thread 1-6) Not activating: cdd-ra
> 11:29:25,009 TRACE [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) Connector=<?xml version="1.0" encoding="UTF-8"?><connector version="1.5"><display-name>DMG CDD Resource Adapter</display-name><vendor-name>Cassidian</vendor-name><eis-type>CDD Server</eis-type><resourceadapter-version>1.0</resourceadapter-version><resourceadapter><resourceadapter-class>com.xx-yy.dmg.jca.eis.CddResourceAdapter</resourceadapter-class><outbound-resourceadapter><connection-definition><managedconnectionfactory-class>com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory</managedconnectionfactory-class><config-property><config-property-name>hostname</config-property-name><config-property-type>java.lang.String</config-property-type></config-property><config-property><config-property-name>port</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>timeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>probeTimeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface><connectionfactory-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionFactory</connectionfactory-impl-class><connection-interface>javax.resource.cci.Connection</connection-interface><connection-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionImpl</connection-impl-class></connection-definition><transaction-support>NoTransaction</transaction-support><reauthentication-support>false</reauthentication-support></outbound-resourceadapter><inbound-resourceadapter><messageadapter><messagelistener><messagelistener-type>javax.resource.cci.MessageListener</messagelistener-type><activationspec><activationspec-class>com.xx-yy.dmg.jca.eis.CddActivationSpec</activationspec-class><required-config-property><config-property-name>hostname</config-property-name></required-config-property><required-config-property><config-property-name>port</config-property-name></required-config-property><required-config-property><config-property-name>timeout</config-property-name></required-config-property></activationspec></messagelistener></messageadapter></inbound-resourceadapter></resourceadapter></connector>
> 11:29:25,010 TRACE [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) IronJacamar=null
> 11:29:25,010 TRACE [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) RaXML=<resource-adapter><archive>cdd-ra.rar</archive><transaction-support>NoTransaction</transaction-support><connection-definitions><connection-definition class-name="com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory" jndi-name="java:jboss/ra/cdd-connector" enabled="true" use-java-context="true" pool-name="ra/cdd-connector" use-ccm="false"><config-property name="port">42006</config-property><config-property name="probeTimeout">10</config-property><config-property name="timeout">45</config-property><config-property name="hostname">localhost</config-property><pool><min-pool-size>0</min-pool-size><max-pool-size>1</max-pool-size><prefill>false</prefill><use-strict-min>false</use-strict-min><flush-strategy>FailingConnectionOnly</flush-strategy></pool><timeout><blocking-timeout-millis>60000</blocking-timeout-millis></timeout><validation><background-validation>false</background-validation><use-fast-fail>false</use-fast-fail></validation></connection-definition></connection-definitions></resource-adapter>
> 11:29:25,012 TRACE [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) ActivateDeployment=true
> 11:29:25,014 TRACE [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) ResourceAdapter: com.xx-yy.dmg.jca.eis.CddResourceAdapter
> 11:29:25,014 TRACE [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) ResourceAdapter defined in classloader: ModuleClassLoader for Module "deployment.cdd-ra.rar:main" from Service Module Loader
> 11:29:25,014 DEBUG [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) CdMeta: <connection-definition><managedconnectionfactory-class>com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory</managedconnectionfactory-class><config-property><config-property-name>hostname</config-property-name><config-property-type>java.lang.String</config-property-type></config-property><config-property><config-property-name>port</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>timeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>probeTimeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface><connectionfactory-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionFactory</connectionfactory-impl-class><connection-interface>javax.resource.cci.Connection</connection-interface><connection-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionImpl</connection-impl-class></connection-definition>
> 11:29:25,015 DEBUG [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) ConnectionDefinitions: 1
> 11:29:25,017 DEBUG [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-6) Activating: <connection-definition class-name="com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory" jndi-name="java:jboss/ra/cdd-connector" enabled="true" use-java-context="true" pool-name="ra/cdd-connector" use-ccm="false"><config-property name="port">42006</config-property><config-property name="probeTimeout">10</config-property><config-property name="timeout">45</config-property><config-property name="hostname">localhost</config-property><pool><min-pool-size>0</min-pool-size><max-pool-size>1</max-pool-size><prefill>false</prefill><use-strict-min>false</use-strict-min><flush-strategy>FailingConnectionOnly</flush-strategy></pool><timeout><blocking-timeout-millis>60000</blocking-timeout-millis></timeout><validation><background-validation>false</background-validation><use-fast-fail>false</use-fast-fail></validation></connection-definition>
> 11:29:25,018 INFO [com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory] (MSC service thread 1-6) setPort() called.
> 11:29:25,019 INFO [com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory] (MSC service thread 1-6) setProbeTiemout() called.
> 11:29:25,021 INFO [com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory] (MSC service thread 1-6) setTimeout() called.
> 11:29:25,021 INFO [com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory] (MSC service thread 1-6) setHostname() called.
> {noformat}
> Failed startup:
> {noformat}
> 11:30:44,391 DEBUG [org.jboss.as.connector.deployment] (MSC service thread 1-5) DEPLOYMENT name = cdd-ra
> 11:30:44,402 TRACE [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-8) DataSource=<datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true" spy="false" use-ccm="true" jta="true"><connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url><driver>h2</driver><pool><min-pool-size>0</min-pool-size><max-pool-size>20</max-pool-size><prefill>false</prefill><use-strict-min>false</use-strict-min><flush-strategy>FailingConnectionOnly</flush-strategy></pool><security><user-name>sa</user-name><password>sa</password></security><validation><validate-on-match>false</validate-on-match><background-validation>false</background-validation><use-fast-fail>false</use-fast-fail></validation><timeout></timeout><statement><track-statements>nowarn</track-statements></statement></datasource>
> 11:30:44,408 TRACE [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) Connector=<?xml version="1.0" encoding="UTF-8"?><connector version="1.5"><display-name>DMG CDD Resource Adapter</display-name><vendor-name>Cassidian</vendor-name><eis-type>CDD Server</eis-type><resourceadapter-version>1.0</resourceadapter-version><resourceadapter><resourceadapter-class>com.xx-yy.dmg.jca.eis.CddResourceAdapter</resourceadapter-class><outbound-resourceadapter><connection-definition><managedconnectionfactory-class>com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory</managedconnectionfactory-class><config-property><config-property-name>hostname</config-property-name><config-property-type>java.lang.String</config-property-type></config-property><config-property><config-property-name>port</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>timeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>probeTimeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface><connectionfactory-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionFactory</connectionfactory-impl-class><connection-interface>javax.resource.cci.Connection</connection-interface><connection-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionImpl</connection-impl-class></connection-definition><transaction-support>NoTransaction</transaction-support><reauthentication-support>false</reauthentication-support></outbound-resourceadapter><inbound-resourceadapter><messageadapter><messagelistener><messagelistener-type>javax.resource.cci.MessageListener</messagelistener-type><activationspec><activationspec-class>com.xx-yy.dmg.jca.eis.CddActivationSpec</activationspec-class><required-config-property><config-property-name>hostname</config-property-name></required-config-property><required-config-property><config-property-name>port</config-property-name></required-config-property><required-config-property><config-property-name>timeout</config-property-name></required-config-property></activationspec></messagelistener></messageadapter></inbound-resourceadapter></resourceadapter></connector>
> 11:30:44,410 TRACE [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) IronJacamar=null
> 11:30:44,410 TRACE [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) RaXML=null
> 11:30:44,410 TRACE [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) ActivateDeployment=false
> 11:30:44,445 DEBUG [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) CdMeta: <connection-definition><managedconnectionfactory-class>com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory</managedconnectionfactory-class><config-property><config-property-name>hostname</config-property-name><config-property-type>java.lang.String</config-property-type></config-property><config-property><config-property-name>port</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>timeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><config-property><config-property-name>probeTimeout</config-property-name><config-property-type>java.lang.Integer</config-property-type></config-property><connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface><connectionfactory-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionFactory</connectionfactory-impl-class><connection-interface>javax.resource.cci.Connection</connection-interface><connection-impl-class>com.xx-yy.dmg.jca.eis.CddConnectionImpl</connection-impl-class></connection-definition>
> 11:30:44,450 DEBUG [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) No activation: com.xx-yy.dmg.jca.eis.CddManagedConnectionFactory
> 11:30:44,452 DEBUG [org.jboss.as.connector.deployment] (MSC service thread 1-5) Registering ResourceAdapter cdd-ra
> 11:30:44,453 DEBUG [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) Activated: file:/C:/jboss-eap-6.1_test/standalone/tmp/vfs/temp3cf601edad306224/cdd-ra.rar-5ec7930ccabd45d/contents/
> 11:30:44,454 DEBUG [org.jboss.as.connector.deployment] (MSC service thread 1-5) Not activating: cdd-ra
> 11:30:44,468 DEBUG [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-8) Adding management datasource: DataSource@1f69b08 xa=false jndiName=java:jboss/datasources/ExampleDS pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@653c2b39 poolconfiguration=PoolConfiguration@5139df1b[minSize=0 maxSize=20 blockingTimeout=30000 idleTimeoutMinutes=30 backgroundValidation=false backgroundValidationMillis=0 prefill=false strictMin=false useFastFail=false] statistics=org.jboss.jca.adapters.jdbc.statistics.JdbcStatisticsPlugin@2e668f46]
> 11:30:44,482 DEBUG [org.jboss.as.connector.deployer.dsdeployer] (MSC service thread 1-8) Adding datasource: java:jboss/datasources/ExampleDS
> 11:30:44,485 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 11:30:44,578 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221034: Waiting to obtain live lock
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (WFLY-3017) OperationContextImpl.readResourceForUpdate assumes all resources represent persistent config
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3017?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3017:
-----------------------------------------------
mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1092206|https://bugzilla.redhat.com/show_bug.cgi?id=1092206] from VERIFIED to CLOSED
> OperationContextImpl.readResourceForUpdate assumes all resources represent persistent config
> --------------------------------------------------------------------------------------------
>
> Key: WFLY-3017
> URL: https://issues.jboss.org/browse/WFLY-3017
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 8.1.0.CR1, 8.1.0.Final
>
>
> The readResourceForUpdate impl makes a few assumptions regarding the fact that a given Resource represents persistent config (i.e. Resource.isRuntime() == true):
> 1) It calls rejectUserDomainServerUpdates() which means an OSH running on a server could not call this.
> 2) It calls authorize(false, READ_WRITE_CONFIG) which means an OSH for an op available to the RBAC Operator role could not call this.
> Places this impacts include LogStoreProbeHandler and LogStoreTransactionDeleteHandler which should be calling readResourceForUpdate but aren't -- and can't because of this bug.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (SECURITY-819) LdapExt login module fetches to many attributes in RoleSearch
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/SECURITY-819?page=com.atlassian.jira.plug... ]
RH Bugzilla Integration commented on SECURITY-819:
--------------------------------------------------
mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1086787|https://bugzilla.redhat.com/show_bug.cgi?id=1086787] from VERIFIED to CLOSED
> LdapExt login module fetches to many attributes in RoleSearch
> -------------------------------------------------------------
>
> Key: SECURITY-819
> URL: https://issues.jboss.org/browse/SECURITY-819
> Project: PicketBox
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JBossSX
> Affects Versions: PicketBox_4_0_21.Beta3
> Reporter: Tom Fonteyne
> Assignee: Tom Fonteyne
>
> An LDAP server with (lets say) 1000 users in a group.
> When authentication, a query is done to retrieve the groups for the user.
> Most LDAP servers will limit the attributes send back based on authorization of the user, but can be configured to return *all* information.
> The cause is:
> / Query for roles matching the role filter
> SearchControls constraints = new SearchControls();
> constraints.setSearchScope(searchScope);
> constraints.setTimeLimit(searchTimeLimit);
> rolesSearch(ctx, constraints, username, userDN, recursion, 0);
> this used to also have:
> constraints.setReturningAttributes(new String[0]);
> at some time this was taken out.
> It needs to go back in
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBMETA-371) DefaultPropertyReplacer + PropertyResolver is broken for vault expressions
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBMETA-371?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on JBMETA-371:
------------------------------------------------
mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1056799|https://bugzilla.redhat.com/show_bug.cgi?id=1056799] from VERIFIED to CLOSED
> DefaultPropertyReplacer + PropertyResolver is broken for vault expressions
> --------------------------------------------------------------------------
>
> Key: JBMETA-371
> URL: https://issues.jboss.org/browse/JBMETA-371
> Project: JBoss Metadata
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: common
> Affects Versions: 7.0.4.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 8.0.0.Final
>
>
> The DefaultPropertyReplacer + PropertyResolver algorithm is broken for vault expressions. It's based on the assumption that the contents of the expression string between "${" and "}" have a fixed format a la the old JBoss AS system properties (e.g. propertyname[: default value]) and then the PropertyResolver tries to resolve "propertyname".
> This is incorrect in the case of vault expressions, which do not follow this format. In particular the ":" char appears multiple places in a vault expression and does not serve as a delimiter between "propertyname" and "default value".
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months