December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBREM-1330) Lease$LeaseTimerTask has a race condition

by Ron Sigal (JIRA)

Ron Sigal created JBREM-1330: -------------------------------- Summary: Lease$LeaseTimerTask has a race condition Key: JBREM-1330 URL: https://issues.jboss.org/browse/JBREM-1330 Project: JBoss Remoting Issue Type: Bug Affects Versions: 2.5.4.SP5 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.4.SP6 org.jboss.remoting.Lease$LeasePinger and org.jboss.remoting.ServerInvoker both access the map of existing Leases. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBREM-1329) Reused ConnectionValidator can hold a reference to a disconnected Client

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/JBREM-1329?page=com.atlassian.jira.plugin... ] Ron Sigal commented on JBREM-1329: ---------------------------------- ConnectionValidator gets value of clientLeasePeriod at creation, instead of reference to a Client. Changes committed to https://svn.jboss.org/repos/jbossremoting/remoting2/branches/2.x > Reused ConnectionValidator can hold a reference to a disconnected Client > ------------------------------------------------------------------------ > > Key: JBREM-1329 > URL: https://issues.jboss.org/browse/JBREM-1329 > Project: JBoss Remoting > Issue Type: Bug > Affects Versions: 2.5.4.SP5 > Reporter: Ron Sigal > Assignee: Ron Sigal > Fix For: 2.5.4.SP6 > > > Instances of org.jboss.remoting.ConnectionValidator hold a reference to an org.jboss.remoting.Client, from which it obtains the value of clientLeasePeriod. If the ConnectionValidator is being reused, and the Client it points to has been disconnected, it gets a value of -1 and it doesn't tie pinging to a Lease. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBREM-1327) Fix synchronization in BlockingCallbackStore

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/JBREM-1327?page=com.atlassian.jira.plugin... ] Ron Sigal commented on JBREM-1327: ---------------------------------- Changes committed to https://svn.jboss.org/repos/jbossremoting/remoting2/branches/2.x > Fix synchronization in BlockingCallbackStore > -------------------------------------------- > > Key: JBREM-1327 > URL: https://issues.jboss.org/browse/JBREM-1327 > Project: JBoss Remoting > Issue Type: Bug > Affects Versions: 2.5.4.SP5 > Reporter: Ron Sigal > Assignee: Ron Sigal > Fix For: 2.5.4.SP6 > > > In org.jboss.remoting.callback.BlockingCallbackStore, add() waits on a lock which is released only when getNext() is called. so a second Callback can be added only after the first is removed. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBREM-1328) LeasePinger should not use a static Timer

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/JBREM-1328?page=com.atlassian.jira.plugin... ] Ron Sigal commented on JBREM-1328: ---------------------------------- Change committed to https://svn.jboss.org/repos/jbossremoting/remoting2/branches/2.x > LeasePinger should not use a static Timer > ----------------------------------------- > > Key: JBREM-1328 > URL: https://issues.jboss.org/browse/JBREM-1328 > Project: JBoss Remoting > Issue Type: Bug > Affects Versions: 2.5.4.SP5 > Reporter: Ron Sigal > Assignee: Ron Sigal > Fix For: 2.5.4.SP6 > > > org.jboss.remoting.LeasePinger currently uses a static Timer. If one LeasePinger gets hung up waiting for a response, it can prevent another LeasePinger from sending a PING, leading to a broken Lease on the server. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBREM-1329) Reused ConnectionValidator can hold a reference to a disconnected Client

by Ron Sigal (JIRA)

Ron Sigal created JBREM-1329: -------------------------------- Summary: Reused ConnectionValidator can hold a reference to a disconnected Client Key: JBREM-1329 URL: https://issues.jboss.org/browse/JBREM-1329 Project: JBoss Remoting Issue Type: Bug Affects Versions: 2.5.4.SP5 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.4.SP6 Instances of org.jboss.remoting.ConnectionValidator hold a reference to an org.jboss.remoting.Client, from which it obtains the value of clientLeasePeriod. If the ConnectionValidator is being reused, and the Client it points to has been disconnected, it gets a value of -1 and it doesn't tie pinging to a Lease. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBREM-1328) LeasePinger should not use a static Timer

by Ron Sigal (JIRA)

Ron Sigal created JBREM-1328: -------------------------------- Summary: LeasePinger should not use a static Timer Key: JBREM-1328 URL: https://issues.jboss.org/browse/JBREM-1328 Project: JBoss Remoting Issue Type: Bug Affects Versions: 2.5.4.SP5 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.4.SP6 org.jboss.remoting.LeasePinger currently uses a static Timer. If one LeasePinger gets hung up waiting for a response, it can prevent another LeasePinger from sending a PING, leading to a broken Lease on the server. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-634) Exception thrown from WorkingMemoryLogger randomly when simultaneous evaluation taking place by different threads

by Jose Cavieres (JIRA)

[ https://issues.jboss.org/browse/DROOLS-634?page=com.atlassian.jira.plugin... ] Jose Cavieres commented on DROOLS-634: -------------------------------------- I am having the same problem in 6.1.0.Final. It happens intermitently in a multi threaded program. The environment is linux 64 bits and the only VM settings is -Xmx2048m > Exception thrown from WorkingMemoryLogger randomly when simultaneous evaluation taking place by different threads > ----------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-634 > URL: https://issues.jboss.org/browse/DROOLS-634 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.CR1 > Reporter: Anantjot Anand > Assignee: Mario Fusco > > Caused by: java.lang.NullPointerException > at org.drools.core.reteoo.RuleTerminalNodeLeftTuple.getDeclarationIds(RuleTerminalNodeLeftTuple.java:394) > at org.drools.core.audit.WorkingMemoryLogger.extractDeclarations(WorkingMemoryLogger.java:325) > at org.drools.core.audit.WorkingMemoryLogger.matchCreated(WorkingMemoryLogger.java:269) > at org.drools.core.event.AgendaEventSupport.fireActivationCreated(AgendaEventSupport.java:58) > at org.drools.core.phreak.PhreakRuleTerminalNode.doLeftTupleInsert(PhreakRuleTerminalNode.java:95) > at org.drools.core.phreak.PhreakRuleTerminalNode.doLeftInserts(PhreakRuleTerminalNode.java:69) > at org.drools.core.phreak.PhreakRuleTerminalNode.doNode(PhreakRuleTerminalNode.java:42) > at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:316) > at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:161) > at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:116) > at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:225) > at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:98) > at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:988) > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1274) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1281) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1254) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4043) Cannot load custom login module

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-4043?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-4043: ---------------------------------------- You need: {code} <login-module code="MyLoginModule" module="name.of.my.module" flag="required"/> {code} > Cannot load custom login module > ------------------------------- > > Key: WFLY-4043 > URL: https://issues.jboss.org/browse/WFLY-4043 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 8.1.0.Final > Environment: Java 1.8.0_25 > Reporter: Rostyslav Smirnov > Assignee: Jason Greene > > When security realm authentication is configured to use JAAS domain, it is not possible to use custom login module, because there is no loader present for deployed classes. LoginContext attempts to load the login module class and fails with ClassNotFoundException. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4043) Cannot load custom login module

by Rostyslav Smirnov (JIRA)

[ https://issues.jboss.org/browse/WFLY-4043?page=com.atlassian.jira.plugin.... ] Rostyslav Smirnov commented on WFLY-4043: ----------------------------------------- The quickstart example is just a way to reproduce this problem. Consider a simple configuration: <security-realm name="ApplicationRealm"> <authentication> <jaas name="my-domain"/> </authentication> </security-realm> ... <security-domain name="my-domain"> <authentication> <login-module code="MyLoginModule" flag="required"/> </authentication> </security-domain> Regardless of whether MyLoginModule.class is deployed inside an EAR or its own Wildfly module, class is not found. It works only when deployed in its own Wildfly module and that module is added as a dependency to "org.wildfly.extension.io" module. > Cannot load custom login module > ------------------------------- > > Key: WFLY-4043 > URL: https://issues.jboss.org/browse/WFLY-4043 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 8.1.0.Final > Environment: Java 1.8.0_25 > Reporter: Rostyslav Smirnov > Assignee: Jason Greene > > When security realm authentication is configured to use JAAS domain, it is not possible to use custom login module, because there is no loader present for deployed classes. LoginContext attempts to load the login module class and fails with ClassNotFoundException. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-458) Operations to read attribute group information

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-458?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-458: ----------------------------------------- Yes; just a flat list. I assume by nested attribute groups, you mean complex attribute "A" which is a member of "capitals" and has a field named "b" which is defined as being a member of group "smalls". > Operations to read attribute group information > ---------------------------------------------- > > Key: WFCORE-458 > URL: https://issues.jboss.org/browse/WFCORE-458 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 1.0.0.Beta1 > > > See "Part III Other possible things to do" in http://lists.jboss.org/pipermail/wildfly-dev/2014-December/003414.html, and Heiko Braun's response thereto. > 1) Add global operation "read-attribute-group(name=<name_of_group>) which functions similarly to read-resource, but only includes in the response those attributes defined as belonging to attribute group "name_of_group". > Besides, the "name" parameter above, parameters and effect thereof should be consistent with "read-resource", except that any parameters dealing with inclusion of child resources should be excluded. > 2) Add global operation "read-attribute-group-names()", which will return a ModelType.LIST whose elements are ModelType.STRING, each element being the name of an attribute-group with which an attribute is associated. Any name only appears once, no entry for the null group to which most attributes belong, response is an empty list if no attribute groups are defined. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2014