August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7117) High CPU usage during high concurrency of distributed SSO creation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7117?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7117: ------------------------------- Fix Version/s: 11.0.0.CR2 (was: 11.0.0.CR1) > High CPU usage during high concurrency of distributed SSO creation > ------------------------------------------------------------------ > > Key: WFLY-7117 > URL: https://issues.jboss.org/browse/WFLY-7117 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.CR2 > > > Replace usage of KeyAffinityService with AffinityTaggedKey. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7822) The default-security-domain attribute in the Undertow subsystem should not support expressions.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7822?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7822: ------------------------------- Fix Version/s: 11.0.0.CR2 (was: 11.0.0.CR1) > The default-security-domain attribute in the Undertow subsystem should not support expressions. > ----------------------------------------------------------------------------------------------- > > Key: WFLY-7822 > URL: https://issues.jboss.org/browse/WFLY-7822 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Stuart Douglas > Fix For: 11.0.0.CR2 > > > This attribute may be deprecated and removed at some point when we start to transition off PicketBox but for now it leads to a service dependency being set based on the value so should not support expressions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7816) Camel CXF version not compatible with WildFly CXF

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7816?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7816: ------------------------------- Fix Version/s: 11.0.0.CR2 (was: 11.0.0.CR1) > Camel CXF version not compatible with WildFly CXF > ------------------------------------------------- > > Key: WFLY-7816 > URL: https://issues.jboss.org/browse/WFLY-7816 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Affects Versions: 10.1.0.Final > Reporter: Thomas Diesler > Assignee: Alessio Soldano > Fix For: 11.0.0.CR2, 10.2.0.Final > > > cxf-3.1.9 distributed with camel-2.19.x is not compatible with cxf-3.1.6 from wildfly-10.1.0.Final > {code} > Caused by: java.lang.NoSuchMethodError: org.apache.cxf.message.Message.remove(Ljava/lang/Class;)Ljava/lang/Object; > at org.apache.camel.component.cxf.CxfEndpoint$CamelCxfClientImpl.setParameters(CxfEndpoint.java:1239) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:470) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:416) > at org.apache.camel.component.cxf.CxfProducer.process(CxfProducer.java:133) > {code} > CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/1546 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7795) org.jboss.sasl classes still making it into jboss-client.jar

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7795?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7795: ------------------------------- Fix Version/s: 11.0.0.CR2 (was: 11.0.0.CR1) > org.jboss.sasl classes still making it into jboss-client.jar > ------------------------------------------------------------ > > Key: WFLY-7795 > URL: https://issues.jboss.org/browse/WFLY-7795 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 11.0.0.CR2 > > > The dependencies should have been removed but maybe this is still coming in as a transitive dependency from elsewhere. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7537) Review NamingContext.check() method

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7537?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7537: ------------------------------- Fix Version/s: 11.0.0.CR2 (was: 11.0.0.CR1) > Review NamingContext.check() method > ----------------------------------- > > Key: WFLY-7537 > URL: https://issues.jboss.org/browse/WFLY-7537 > Project: WildFly > Issue Type: Task > Components: Naming > Reporter: Darran Lofthouse > Assignee: Farah Juma > Fix For: 11.0.0.CR2 > > > The new naming client is sending in a SimpleName where the lookup was performed using a String. > When a SecurityManager is installed the check() method of NamingContext is called and results in the following error: - > {noformat} > javax.naming.InvalidNameException: Not a composite name: jms > at javax.naming.CompositeName.addAll(CompositeName.java:472) > at org.jboss.as.naming.NamingContext.check(NamingContext.java:592) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:197) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) > at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:127) > at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73) > 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) > {noformat} > A fix has been applied to convert the incoming name to a CompositeName but as we deliberately have a SimpleName to avoid CompositeName I wonder if that is completely correct. > Some other options I think of: - > 1. Stick with current fix. > 2 The client should convert to CompositeName before sending. > 3. Manually iterate the segments if not a CompositeName > 4. Check if the NamingStore really needs to use a CompositeName -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8390) Correct RemotingLoginModule test failures.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-8390?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-8390: ------------------------------- Fix Version/s: 11.0.0.CR2 (was: 11.0.0.CR1) > Correct RemotingLoginModule test failures. > ------------------------------------------ > > Key: WFLY-8390 > URL: https://issues.jboss.org/browse/WFLY-8390 > Project: WildFly > Issue Type: Bug > Components: Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 11.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8250) Ensure all Elytron subsystem resources that depend on the core services also record a capability dependency.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-8250?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-8250: ------------------------------- Fix Version/s: 11.0.0.CR2 (was: 11.0.0.CR1) > Ensure all Elytron subsystem resources that depend on the core services also record a capability dependency. > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-8250 > URL: https://issues.jboss.org/browse/WFLY-8250 > Project: WildFly > Issue Type: Enhancement > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 11.0.0.CR2 > > > This builds on https://issues.jboss.org/browse/WFCORE-1106 so we can skip runtime steps when the dependent services are not available. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7871) Decouple backup/site name from the name of the corresponding resource

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7871?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7871: ------------------------------- Fix Version/s: 11.0.0.CR2 (was: 11.0.0.CR1) > Decouple backup/site name from the name of the corresponding resource > --------------------------------------------------------------------- > > Key: WFLY-7871 > URL: https://issues.jboss.org/browse/WFLY-7871 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.CR2 > > > Currently, the site names defined in the JGroups subsystem RELAY2 protocol, and the backup names defined in the Infinispan subsystem do not allow expressions, since these name are used for the corresponding resource paths. To simplify the use of cross-site replication (specifically, to allow each site to use an identical domain.xml/standalone.xml), we can support expressions if we decouple the site name from the resource name. > e.g. > {noformat} > <backups> > <backup name="remote" site="${...}" strategy="SYNC"/> > </backups> > <relay site="local"> > <remote-site name="local" site-name="${...}" channel=".."/> > <remote-site name="remote" site-name="${...}" channel=".."/> > </relay> > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9261) Cluster connection receives a "consumer created" message from the rebooting node but it has no corresponding binding for it locally

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9261?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9261: ------------------------------- Fix Version/s: 11.0.0.CR2 (was: 11.0.0.CR1) > Cluster connection receives a "consumer created" message from the rebooting node but it has no corresponding binding for it locally > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9261 > URL: https://issues.jboss.org/browse/WFLY-9261 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Flavia Rainone > Assignee: Martyn Taylor > Fix For: 11.0.0.CR2 > > > When rebooting a cluster node that uses singleton cluster mdbs, we get this error message: > {noformat} > 2017-07-25 16:08:54,426 ERROR [org.apache.activemq.artemis.core.server] (Thread-3 (ActiveMQ-client-global-threads)) AMQ224037: cluster connection Failed to handle message: java.lang.IllegalStateException: Cannot find binding for jms.queue.HelloWorldMDBQueuedea3e995-713c-11e7-85f2-b8f6b112daf7 on ClusterConnectionImpl@1129705701[nodeUUID=dabaa1fa-713c-11e7-8f3a-b8f6b112daf7, connector=TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=http-acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=9080&host=localhost, address=jms, server=ActiveMQServerImpl::serverUUID=dabaa1fa-713c-11e7-8f3a-b8f6b112daf7] > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.doConsumerCreated(ClusterConnectionImpl.java:1294) > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.handleNotificationMessage(ClusterConnectionImpl.java:1029) > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.onMessage(ClusterConnectionImpl.java:1004) > at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1001) > at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:49) > at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1124) > at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:101) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9214) Remove experimental Hibernate Search / JGroups integration

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9214?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9214: ------------------------------- Fix Version/s: 11.0.0.CR2 (was: 11.0.0.CR1) > Remove experimental Hibernate Search / JGroups integration > ---------------------------------------------------------- > > Key: WFLY-9214 > URL: https://issues.jboss.org/browse/WFLY-9214 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 11.0.0.CR2 > > > The {{<artifactId>hibernate-search-backend-jgroups</artifactId>}} has never matured from its experimental status, and should not have been included in WildFly. > We never supported it, it's presence is not documented in EAP docs, and should simply be removed as it was a mistake to include it in the first place. > I'll keep the reference to it as an optional dependency from the module, so that people can still drop in the module if they want to. I just don't believe this should be shipped by default. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 August 2017