December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2060) Remove jgroups.logging.log_factory_class or have LogFactory.setCustomLogFactory take precedence to avoid issues with multiple jgroups in the same JVM

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-2060?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-2060: ----------------------------------------------- Miroslav Sochurek <msochure(a)redhat.com> changed the Status of [bug 1330729|https://bugzilla.redhat.com/show_bug.cgi?id=1330729] from POST to ASSIGNED > Remove jgroups.logging.log_factory_class or have LogFactory.setCustomLogFactory take precedence to avoid issues with multiple jgroups in the same JVM > ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JGRP-2060 > URL: https://issues.jboss.org/browse/JGRP-2060 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.9 > Reporter: Brad Maxwell > Assignee: Bela Ban > Fix For: 3.6.10, 4.0 > > > Remove jgroups.logging.log_factory_class or have LogFactory.setCustomLogFactory take precedence to avoid issues with multiple jgroups in the same JVM -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7754) WELD o.j.w.e.IllegalStateException after saved session does not auto-recover

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7754?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-7754: -------------------------------------- What shows up in the log when this happens? > WELD o.j.w.e.IllegalStateException after saved session does not auto-recover > ---------------------------------------------------------------------------- > > Key: WFLY-7754 > URL: https://issues.jboss.org/browse/WFLY-7754 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: Darryl Miles > Assignee: Stuart Douglas > > When modifying the WELD bean profile between starting/stopping WildFly with persistent session cookies over restart enabled. > It is possible to get an unrecoverable o.j.w.e.IllegalStateException. > What I mean by this is that if the AS knows the HTTP session cookie is a valid ID, but is unable to recover it from the persistence serialization over a restart (due to a change in the WELD BeanIdentifer instances changing to allow the optimization to work in this area). What the AS should do is simply log the problem and invalidate the session cookie completely. All this should happen in a transparent way to the WebApp, so it gets a null return or a brand new HttpSession. > This will automatically allow the HTTP client to recover, by forcing the application to generate a new HTTP session as necessary / or force logout, etc.. > This is unrecoverable since the exception seems to be thrown at a level before it hits any WebApp application code. So it doesn't seem possible for the WebApp developer to correct the problem from the exception. Which makes sense since you need a HttpSession object to invoke #invalidate() on and it is recovering that that is. > Everytime the user refreshes all they get is the error and a HTTP/500 Internal Server Error and the user has to either delete their cookie, or the WildFly admin shutdown and remove any persistent session cookie data. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7757) Infinispan JDBC cache stores missing read/write attribute operations for legacy attributes

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-7757?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-7757: ------------------------------- Description: In WF9, the following commands were valid: /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:read-attribute(name=datasource) /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:write-attribute(name=datasource, value=java:jboss/datasources/ExampleDS) In WF10, these commands result in "Unknown attribute" errors. Even though the "datasource" attribute was deprecated in WF10, these operations should still work, and should return a value translated from the "data-source" attribute. was: In WF9, the following commands were valid: /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:read-attribute(name=datasource) /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:write-attribute(name=datasource, value=java:jboss/datasources/ExampleDS) In WF10, these commands result in "Unknown attribute" errors. Even though the "datasource" attribute was deprecated in WF11, these operations should still work, and should return a value translated from the "data-source" attribute. > Infinispan JDBC cache stores missing read/write attribute operations for legacy attributes > ------------------------------------------------------------------------------------------ > > Key: WFLY-7757 > URL: https://issues.jboss.org/browse/WFLY-7757 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Alpha1 > > > In WF9, the following commands were valid: > /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:read-attribute(name=datasource) > /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:write-attribute(name=datasource, value=java:jboss/datasources/ExampleDS) > In WF10, these commands result in "Unknown attribute" errors. Even though the "datasource" attribute was deprecated in WF10, these operations should still work, and should return a value translated from the "data-source" attribute. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7757) Infinispan JDBC cache stores missing read/write attribute operations for legacy attributes

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-7757?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-7757: ------------------------------- Description: In WF9, the following commands were valid: /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:read-attribute(name=datasource) /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:write-attribute(name=datasource, value=java:jboss/datasources/ExampleDS) In WF10, these commands result in "Unknown attribute" errors. Even though the "datasource" attribute was deprecated in WF11, these operations should still work, and should return a value translated from the "data-source" attribute. was: In WF10, the following commands were valid: /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:read-attribute(name=datasource) /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:write-attribute(name=datasource, value=java:jboss/datasources/ExampleDS) In WF11, these commands result in "Unknown attribute" errors. Even though the "datasource" attribute was deprecated in WF11, these operations should still work, and should return a value translated from the "data-source" attribute. > Infinispan JDBC cache stores missing read/write attribute operations for legacy attributes > ------------------------------------------------------------------------------------------ > > Key: WFLY-7757 > URL: https://issues.jboss.org/browse/WFLY-7757 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Alpha1 > > > In WF9, the following commands were valid: > /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:read-attribute(name=datasource) > /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:write-attribute(name=datasource, value=java:jboss/datasources/ExampleDS) > In WF10, these commands result in "Unknown attribute" errors. Even though the "datasource" attribute was deprecated in WF11, these operations should still work, and should return a value translated from the "data-source" attribute. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7757) Infinispan JDBC cache stores missing read/write attribute operations for legacy attributes

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-7757?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-7757: ------------------------------- Affects Version/s: 10.1.0.Final > Infinispan JDBC cache stores missing read/write attribute operations for legacy attributes > ------------------------------------------------------------------------------------------ > > Key: WFLY-7757 > URL: https://issues.jboss.org/browse/WFLY-7757 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Alpha1 > > > In WF9, the following commands were valid: > /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:read-attribute(name=datasource) > /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:write-attribute(name=datasource, value=java:jboss/datasources/ExampleDS) > In WF10, these commands result in "Unknown attribute" errors. Even though the "datasource" attribute was deprecated in WF11, these operations should still work, and should return a value translated from the "data-source" attribute. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2089) Infinite wildfly boot on StartException in service start

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2089?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2089: ------------------------------------------ [~dlofthouse] I assigned this back to myself by mistake. But if what I suggest in my last comment sounds right to you, I'd be happy to take it on. I hear you are a bit busy. ;) > Infinite wildfly boot on StartException in service start > -------------------------------------------------------- > > Key: WFCORE-2089 > URL: https://issues.jboss.org/browse/WFCORE-2089 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Jan Kalina > Assignee: Brian Stansberry > Priority: Blocker > Attachments: threads-2.txt, threads.txt > > > Following exception (and probably similar too) will cause wildfly frozing during start. Visible especially during integration tests (which will never ends), but reproducible directly too (see steps). > {code:java} > 15:59:37,252 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service org.wildfly.security.security-realm.ManagementRealm: org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.ManagementRealm: WFLYELY00025: Referenced property file is invalid: ELY01006: No realm name found in password property file > at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:185) > at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:164) > at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {code} > *Update:* This problem with infinite boot will occure everytime the start() method of some service throws StartException(). Not an Elytron problem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7758) Infinispan JDBC cache stores missing read/write attribute operations for legacy attributes

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7758: ---------------------------------- Summary: Infinispan JDBC cache stores missing read/write attribute operations for legacy attributes Key: WFLY-7758 URL: https://issues.jboss.org/browse/WFLY-7758 Project: WildFly Issue Type: Bug Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 11.0.0.Alpha1 In WF10, the following commands were valid: /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:read-attribute(name=datasource) /subsystem=infinispan/cache-container=foo/local-cache=bar/store=string-jdbc:write-attribute(name=datasource, value=java:jboss/datasources/ExampleDS) In WF11, these commands result in "Unknown attribute" errors. Even though the "datasource" attribute was deprecated in WF11, these operations should still work, and should return a value translated from the "data-source" attribute. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2094) HC is unaware when managed server's MSC is unstable

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-2094: ---------------------------------------- Summary: HC is unaware when managed server's MSC is unstable Key: WFCORE-2094 URL: https://issues.jboss.org/browse/WFCORE-2094 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry The HC should be aware if a managed server has a service container that cannot stabilize. What it will do with this information can evolve over time, but it should at least log it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2089) Infinite wildfly boot on StartException in service start

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2089?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-2089: ---------------------------------------- Assignee: Brian Stansberry (was: Darran Lofthouse) > Infinite wildfly boot on StartException in service start > -------------------------------------------------------- > > Key: WFCORE-2089 > URL: https://issues.jboss.org/browse/WFCORE-2089 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Jan Kalina > Assignee: Brian Stansberry > Priority: Blocker > Attachments: threads-2.txt, threads.txt > > > Following exception (and probably similar too) will cause wildfly frozing during start. Visible especially during integration tests (which will never ends), but reproducible directly too (see steps). > {code:java} > 15:59:37,252 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service org.wildfly.security.security-realm.ManagementRealm: org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.ManagementRealm: WFLYELY00025: Referenced property file is invalid: ELY01006: No realm name found in password property file > at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:185) > at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:164) > at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {code} > *Update:* This problem with infinite boot will occure everytime the start() method of some service throws StartException(). Not an Elytron problem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1371) Too many classloaders use too much memory for a large rule set

by Bill Tuminaro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1371?page=com.atlassian.jira.plugi... ] Bill Tuminaro closed DROOLS-1371. --------------------------------- Resolution: Won't Fix see my last comment in the jira > Too many classloaders use too much memory for a large rule set > -------------------------------------------------------------- > > Key: DROOLS-1371 > URL: https://issues.jboss.org/browse/DROOLS-1371 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Bill Tuminaro > Assignee: Mario Fusco > Attachments: WhyTwoClassoaders.java, drools-1371.PNG > > > Why are there so many classloaders after I create a KieSession for a KieFileSystem and KieContainer that only contains one rule? > The extra classloaders for each rule are consuming too much memory for a rule set that contains several thousand rules. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 December 2016