April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-762) JIT Thread and Calling thread can cause simultaneous access to hibernate sessions

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-762?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-762: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > JIT Thread and Calling thread can cause simultaneous access to hibernate sessions > --------------------------------------------------------------------------------- > > Key: DROOLS-762 > URL: https://issues.jboss.org/browse/DROOLS-762 > Project: Drools > Issue Type: Bug > Affects Versions: 5.6.0.Final > Reporter: Mark Torres > Assignee: Mario Fusco > > When evaluating drools involving uninitialized property of hibernate entities, simultaneous access to a hibernate session can occur. With the existing codebase on 5.5/6.x the jit thread is "launched" prior to rule evaluation. This can cause the calling thread, and jit thread to call lazy property initialization at the same time, which can cause hibernate to throw exceptions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-762) JIT Thread and Calling thread can cause simultaneous access to hibernate sessions

by Mark Torres (JIRA)

Mark Torres created DROOLS-762: ---------------------------------- Summary: JIT Thread and Calling thread can cause simultaneous access to hibernate sessions Key: DROOLS-762 URL: https://issues.jboss.org/browse/DROOLS-762 Project: Drools Issue Type: Bug Affects Versions: 5.6.0.Final Reporter: Mark Torres Assignee: Mark Proctor When evaluating drools involving uninitialized property of hibernate entities, simultaneous access to a hibernate session can occur. With the existing codebase on 5.5/6.x the jit thread is "launched" prior to rule evaluation. This can cause the calling thread, and jit thread to call lazy property initialization at the same time, which can cause hibernate to throw exceptions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4119) Support Slow Consumer Policy

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-4119?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-4119: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/7351 (was: https://github.com/wildfly/wildfly/pull/6997) > Support Slow Consumer Policy > ---------------------------- > > Key: WFLY-4119 > URL: https://issues.jboss.org/browse/WFLY-4119 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > Support HornetQ Slow consumer policy to KILL or NOTIFY if consumers starts to be to slow consuming messages. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4516) Upgrade to HornetQ 2.4.7.Final

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-4516: --------------------------------- Summary: Upgrade to HornetQ 2.4.7.Final Key: WFLY-4516 URL: https://issues.jboss.org/browse/WFLY-4516 Project: WildFly Issue Type: Component Upgrade Components: JMS Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 9.0.0.CR1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-497) Infinispan thread pool injection

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-497?page=com.atlassian.jira.plugin.s... ] Radoslav Husar updated WFLY-497: -------------------------------- Fix Version/s: 9.0.0.CR1 > Infinispan thread pool injection > -------------------------------- > > Key: WFLY-497 > URL: https://issues.jboss.org/browse/WFLY-497 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Reporter: David Lloyd > Assignee: Radoslav Husar > Fix For: 9.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4515) Fix clustering transformers and reenable in mixed-domain tests

by Kabir Khan (JIRA)

Kabir Khan created WFLY-4515: -------------------------------- Summary: Fix clustering transformers and reenable in mixed-domain tests Key: WFLY-4515 URL: https://issues.jboss.org/browse/WFLY-4515 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 9.0.0.Beta2 Reporter: Kabir Khan Assignee: Radoslav Husar Priority: Critical Fix For: 9.0.0.CR1 When running the jgroups and infinispan subsystem tests with -Djboss.test.transformers.eap there are some failures in the transformers tests. Also, in the mixed domain tests it is not possible to enable these subsystems, so I have removed them from DomainAdjuster620 in https://github.com/wildfly/wildfly/pull/7350. They should be reenabled again as part of this Jira. Some info from private mail: {quote} However, when transforming that to 7.2.0 by running: mvn clean install -DallTests -Djboss.test.mixed.domain.dir=/Users/kabir/old-as7-releases/ -pl testsuite/mixed-domain/ -Dtest=MixedDomain_7_2_0_Final_TestSuite I get the following error: 11:59:43,682 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.io.IOException: 1-$-WFLYCTL0300: Transforming resource [ ("profile" => "full-ha"), ("subsystem" => "infinispan"), ("cache-container" => "server"), ("transport" => "TRANSPORT") ] for host controller 'slave' to subsystem 'infinispan' model version '1.4.0' --there were problems with some of the attributes and this resource will need to be ignored on that host. Details of problems: [WFLYCLINF0027: Could not determine 'stack' attribute from JGroups subsystem] I am not totally sure if this is the right solution, but I attempted to add a stack attribute to the transport, but it does not seem to get persisted so it goes away after reloading the DC (out of admin-only to normal mode). I also tried in standalone mode, and executing /subsystem=infinispan/cache-container=server/transport=TRANSPORT:write-attribute(name=stack, value=udp) and the stack does not get persisted. It is probably a simple fix, but since I am not sure if it is the right fix or not, especially since adding this to the writer it also seems to be ignored by the parser. Perhaps this is a candidate for something along the lines of https://github.com/wildfly/wildfly/blob/master/clustering/jgroups/extensi... so that we can support old configs, but not actually use it on a server using the current version? {quote} Note that the above is when I was working on this, the 7.2.0 test has been removed. We now test EAP 6.2.0 and 6.3.0 compatibility. I believe the problem is similar there although I have not dug in very deeply. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-114) Get RuntimeVaultReader into WildFly Core

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-114?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet reassigned WFCORE-114: ---------------------------------------- Assignee: ehsavoie Hugonnet > Get RuntimeVaultReader into WildFly Core > ---------------------------------------- > > Key: WFCORE-114 > URL: https://issues.jboss.org/browse/WFCORE-114 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha8 > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Priority: Blocker > Fix For: 1.0.0.CR1 > > > The only real implementation of AbstractVaultReader isn't in wildfly-core; it's in the wildfly-full security subsystem module. > This means WildFly Core currently doesn't really support vault expressions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-114) Get RuntimeVaultReader into WildFly Core

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-114?page=com.atlassian.jira.plugin... ] Tomaz Cerar commented on WFCORE-114: ------------------------------------ Whoever is doing this, lets just make sure we don't bring picketbox dependency in when this is moved. > Get RuntimeVaultReader into WildFly Core > ---------------------------------------- > > Key: WFCORE-114 > URL: https://issues.jboss.org/browse/WFCORE-114 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha8 > Reporter: Brian Stansberry > Priority: Blocker > Fix For: 1.0.0.CR1 > > > The only real implementation of AbstractVaultReader isn't in wildfly-core; it's in the wildfly-full security subsystem module. > This means WildFly Core currently doesn't really support vault expressions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4514) Remove RuntimeVaultReader from WildFly full as it is now in WildFly-Core

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-4514?page=com.atlassian.jira.plugin.... ] ehsavoie Hugonnet updated WFLY-4514: ------------------------------------ Description: Once WFCORE-114 has been merged there is no need to keep the RuntimeVaultReader in the security subsystem (was: Once WFCORE-114 has been merged the) > Remove RuntimeVaultReader from WildFly full as it is now in WildFly-Core > ------------------------------------------------------------------------ > > Key: WFLY-4514 > URL: https://issues.jboss.org/browse/WFLY-4514 > Project: WildFly > Issue Type: Enhancement > Components: Security > Affects Versions: 9.0.0.Beta2 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > Once WFCORE-114 has been merged there is no need to keep the RuntimeVaultReader in the security subsystem -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4514) Remove RuntimeVaultReader from WildFly full as it is now in WildFly-Core

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFLY-4514: --------------------------------------- Summary: Remove RuntimeVaultReader from WildFly full as it is now in WildFly-Core Key: WFLY-4514 URL: https://issues.jboss.org/browse/WFLY-4514 Project: WildFly Issue Type: Enhancement Components: Security Affects Versions: 9.0.0.Beta2 Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet Once WFCORE-114 has been merged the -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2015