March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2028) GMS sometimes ignores view bundling timeout

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2028?page=com.atlassian.jira.plugin.... ] Bela Ban closed JGRP-2028. -------------------------- > GMS sometimes ignores view bundling timeout > ------------------------------------------- > > Key: JGRP-2028 > URL: https://issues.jboss.org/browse/JGRP-2028 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.8 > Reporter: Dan Berindei > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.9, 4.0 > > > {{GMS.ViewHandler.run()}} has this code: > {code} > wait_time=timeout - (System.nanoTime() - start_time); > if(wait_time > 0 && firstRequest.canBeProcessedTogether(firstRequest)) { // JGRP-1438 > long wait_time_ms=TimeUnit.MILLISECONDS.convert(wait_time, TimeUnit.NANOSECONDS); > queue.waitUntilClosed(wait_time_ms); // misnomer: waits until element has been added or q closed > } > {code} > The problem is {{wait_time_ms}} will be {{0}} if {{0 < wait_time < 1_000_000}}. {{queue.waitUntilClosed(wait_time_ms)}} then calls {{Object.wait(0)}} and blocks forever. > Fortunately, the joiners re-sends the {{JOIN_REQ}} message after {{GMS.join_timeout}} (3s by default), so all that happens is that the view is delayed by 3s. It does cause some random failures in tests that expect the view to form in a precise amount of time, though. > {noformat} > 17:04:53,034 DEBUG (ForkThread-3,InitialClusterSizeTest:) [GMS] NodeF-49399: sending JOIN(NodeF-49399) to NodeE-37644 > 17:04:53,034 TRACE (ForkThread-3,InitialClusterSizeTest:) [TCP_NIO2] NodeF-49399: sending msg to NodeE-37644, src=NodeF-49399, headers are GMS: GmsHeader[JOIN_REQ]: mbr=NodeF-49399, UNICAST3: DATA, seqno=1, first, TP: [cluster_name=ISPN] > 17:04:53,035 DEBUG (ForkThread-4,InitialClusterSizeTest:) [GMS] NodeG-49307: sending JOIN(NodeG-49307) to NodeE-37644 > 17:04:53,035 TRACE (ForkThread-4,InitialClusterSizeTest:) [TCP_NIO2] NodeG-49307: sending msg to NodeE-37644, src=NodeG-49307, headers are GMS: GmsHeader[JOIN_REQ]: mbr=NodeG-49307, UNICAST3: DATA, seqno=1, first, TP: [cluster_name=ISPN] > 17:04:53,060 TRACE (INT-1,NodeE-37644:) [TCP_NIO2] NodeE-37644: received [dst: NodeE-37644, src: NodeF-49399 (3 headers), size=0 bytes, flags=OOB|INTERNAL], headers are GMS: GmsHeader[JOIN_REQ]: mbr=NodeF-49399, UNICAST3: DATA, seqno=1, first, TP: [cluster_name=ISPN] > 17:04:53,060 TRACE (INT-2,NodeE-37644:) [TCP_NIO2] NodeE-37644: received [dst: NodeE-37644, src: NodeG-49307 (3 headers), size=0 bytes, flags=OOB|INTERNAL], headers are GMS: GmsHeader[JOIN_REQ]: mbr=NodeG-49307, UNICAST3: DATA, seqno=1, first, TP: [cluster_name=ISPN] > 17:04:53,060 TRACE (INT-1,NodeE-37644:) [UNICAST3] NodeE-37644 <-- DATA(NodeF-49399: #1, conn_id=0, first) > 17:04:53,060 TRACE (INT-2,NodeE-37644:) [UNICAST3] NodeE-37644 <-- DATA(NodeG-49307: #1, conn_id=0, first) > 17:04:53,061 TRACE (INT-2,NodeE-37644:) [UNICAST3] NodeE-37644: delivering NodeG-49307#1 > 17:04:53,061 TRACE (INT-1,NodeE-37644:) [UNICAST3] NodeE-37644: delivering NodeF-49399#1 > 17:04:56,035 WARN (ForkThread-3,InitialClusterSizeTest:) [GMS] NodeF-49399: JOIN(NodeF-49399) sent to NodeE-37644 timed out (after 3000 ms), on try 1 > 17:04:56,035 WARN (ForkThread-4,InitialClusterSizeTest:) [GMS] NodeG-49307: JOIN(NodeG-49307) sent to NodeE-37644 timed out (after 3000 ms), on try 1 > 17:04:56,036 DEBUG (ForkThread-3,InitialClusterSizeTest:) [GMS] NodeF-49399: sending JOIN(NodeF-49399) to NodeE-37644 > 17:04:56,036 TRACE (ForkThread-3,InitialClusterSizeTest:) [TCP_NIO2] NodeF-49399: sending msg to NodeE-37644, src=NodeF-49399, headers are GMS: GmsHeader[JOIN_REQ]: mbr=NodeF-49399, UNICAST3: DATA, seqno=2, TP: [cluster_name=ISPN] > 17:04:56,036 DEBUG (ForkThread-4,InitialClusterSizeTest:) [GMS] NodeG-49307: sending JOIN(NodeG-49307) to NodeE-37644 > 17:04:56,036 TRACE (ForkThread-4,InitialClusterSizeTest:) [TCP_NIO2] NodeG-49307: sending msg to NodeE-37644, src=NodeG-49307, headers are GMS: GmsHeader[JOIN_REQ]: mbr=NodeG-49307, UNICAST3: DATA, seqno=2, TP: [cluster_name=ISPN] > 17:04:56,057 TRACE (INT-1,NodeE-37644:) [TCP_NIO2] NodeE-37644: received [dst: NodeE-37644, src: NodeF-49399 (3 headers), size=0 bytes, flags=OOB|INTERNAL], headers are GMS: GmsHeader[JOIN_REQ]: mbr=NodeF-49399, UNICAST3: DATA, seqno=2, TP: [cluster_name=ISPN] > 17:04:56,057 TRACE (INT-2,NodeE-37644:) [TCP_NIO2] NodeE-37644: received [dst: NodeE-37644, src: NodeG-49307 (3 headers), size=0 bytes, flags=OOB|INTERNAL], headers are GMS: GmsHeader[JOIN_REQ]: mbr=NodeG-49307, UNICAST3: DATA, seqno=2, TP: [cluster_name=ISPN] > 17:04:56,057 TRACE (INT-2,NodeE-37644:) [UNICAST3] NodeE-37644: delivering NodeG-49307#2 > 17:04:56,057 TRACE (INT-1,NodeE-37644:) [UNICAST3] NodeE-37644: delivering NodeF-49399#2 > # finally > 17:04:56,057 TRACE (ViewHandler,NodeE-37644:) [GMS] NodeE-37644: joiners=[NodeG-49307, NodeF-49399], suspected=[], leaving=[], new view: [NodeE-37644|1] (3) [NodeE-37644, NodeG-49307, NodeF-49399] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2033) Replace Java serialization with JGroups marshalling

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2033?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2033. ---------------------------- Resolution: Done > Replace Java serialization with JGroups marshalling > --------------------------------------------------- > > Key: JGRP-2033 > URL: https://issues.jboss.org/browse/JGRP-2033 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.6.9, 4.0 > > > In some cases, even JGroups internal code still uses Java serialization. Replace this with marshalling (using {{Streamable}}). Analysis of all occurrences of {{Util.objectFromXXX()}} calls. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6441) naming context is not setup when starting the persistence unit

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-6441?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-6441: ------------------------------- Fix Version/s: 10.1.0.Final > naming context is not setup when starting the persistence unit > -------------------------------------------------------------- > > Key: WFLY-6441 > URL: https://issues.jboss.org/browse/WFLY-6441 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Affects Versions: JBoss AS7 7.1.1.Final, JBoss AS7 7.2.0.Final, 9.0.2.Final, 10.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.1.0.Final > > > ookup of env-entry throws NameNotFoundException during persistence unit startup > Version-Release number of selected component (if applicable): > How reproducible: > always > Steps to Reproduce: > 1. add env-entry in application.xml > 2. try to lookup during persistent unit startup, e.g. > public class MyType implements UserType { > ... > @Override > public int[] sqlTypes() { > try { > Object ctx = new InitialContext().lookup("java:app/env"); > log.info("java:app/env from JPA = " + ctx); > } catch (Exception e) { > log.error("unable to get java:app/env from JPA", e); > } > return new int[] { Types.VARCHAR }; > } > Actual results: > NameNotFoundException > Expected results: > value of env-entry is available > Additional info: > On 21.03.2016 23:47, Stuart Douglas wrote: > > This should fix it (I think): https://github.com/stuartwdouglas/wildfly/tree/jpa-java-namespace > > > > Stuart -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-475) Update the CLIENT_CERT authentication mechanism to be able to make use of an established security identity

by Farah Juma (JIRA)

Farah Juma created ELY-475: ------------------------------ Summary: Update the CLIENT_CERT authentication mechanism to be able to make use of an established security identity Key: ELY-475 URL: https://issues.jboss.org/browse/ELY-475 Project: WildFly Elytron Issue Type: Task Components: API / SPI, HTTP Reporter: Farah Juma Assignee: Farah Juma There's currently a TODO in [ClientCertAuthenticationMechanism#evaluateRequest|https://github.com/wild...] for making use of an established {{SecurityIdentity}} from an {{SSLSession}}. It should be possible to do this by making use of the API for propagating an identity between domains (ELY-178). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1440) Expression resolver breaks return value for empty lists

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1440?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1440: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1477 > Expression resolver breaks return value for empty lists > ------------------------------------------------------- > > Key: WFCORE-1440 > URL: https://issues.jboss.org/browse/WFCORE-1440 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.CR1 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 3.0.0.Alpha1 > > > ExpressionResolverImpl#resolveExpressionsRecursively > does > {code} > else if (type == ModelType.LIST) { > resolved = node.clone(); > ModelNode list = new ModelNode(); > for (ModelNode current : resolved.asList()) { > list.add(resolveExpressionsRecursively(current)); > } > resolved = list; > } > {code} > for list attributes, but in case that resolved value is empty list it would return list that is undefined instead of empty list. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6445) Upgrade to JBoss Negotiation 3.0.2.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-6445: -------------------------------------- Summary: Upgrade to JBoss Negotiation 3.0.2.Final Key: WFLY-6445 URL: https://issues.jboss.org/browse/WFLY-6445 Project: WildFly Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 10.1.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-940) Release JBoss Negotiation 3.0.2.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-940: ----------------------------------------- Summary: Release JBoss Negotiation 3.0.2.Final Key: SECURITY-940 URL: https://issues.jboss.org/browse/SECURITY-940 Project: PicketBox Issue Type: Release Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_3_0_2_CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-939) Contents of NegotiationContext getting cleared before challenge is sent to client.

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-939: ----------------------------------------- Summary: Contents of NegotiationContext getting cleared before challenge is sent to client. Key: SECURITY-939 URL: https://issues.jboss.org/browse/SECURITY-939 Project: PicketBox Issue Type: Bug Components: Negotiation Affects Versions: Negotiation_3_0_0_Final Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_3_0_2_CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1448) AttributeParser for ObjectListAttributeDefinitions doesn't differentiate between empty and absent object lists

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1448?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1448: ------------------------------------- Fix Version/s: 3.0.0.Alpha1 Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1477 > AttributeParser for ObjectListAttributeDefinitions doesn't differentiate between empty and absent object lists > -------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1448 > URL: https://issues.jboss.org/browse/WFCORE-1448 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.Final > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 3.0.0.Alpha1 > > > Attributes of type ObjectList are left undefined when their enclosing element is empty, which makes it impossible to differentiate an empty object list from an unspecified one. > The ability to distinguish the two scenarios is important in the security manager subsystem. Consider this configuration: > {code:xml} > <subsystem xmlns="urn:jboss:domain:security-manager:1.0"> > <deployment-permissions> > <mininum-set> > .... > </minimum-set> > </deployment-permissions> > </subsystem> > {code} > The maximum-set is absent and this case we want to use a default set with AllPermission. Now consider another configuration: > {code:xml} > <subsystem xmlns="urn:jboss:domain:security-manager:1.0"> > <deployment-permissions> > <mininum-set/> > <maximum-set/> > </deployment-permissions> > </subsystem> > {code} > In this case, maximum-set has been specified but it is empty, which means the admin/user deliberately wants to use an emtpy set, possibly to enforce that no deployments with special permissions requirements get deployed. > The problem is that both scenarios result in an undefined attribute for the maximum-set, which means that the default AllPermission set ends up being used in both cases. The parser doesn't initialize the attribute with an empty list when the enclosing element is present but is empty. So in the end, both approaches result in an undefined attribute. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6444) Apache http classes not found

by Andrei Ivanov (JIRA)

Andrei Ivanov created WFLY-6444: ----------------------------------- Summary: Apache http classes not found Key: WFLY-6444 URL: https://issues.jboss.org/browse/WFLY-6444 Project: WildFly Issue Type: Bug Affects Versions: 10.0.0.Final, 10.1.0.Final Reporter: Andrei Ivanov Assignee: Jason Greene Attachments: wildfly-httpclient-test.zip Hi, I've created a trivial JAX-RS application with a CDI producer for a RestEasy JAX-RS client proxy. I also need to customize the HTTP engine a bit. The app deploys fine on JBoss 7.1.1. Trying to upgrade to WildFly 10.0, I got a weird error: {noformat} DEBUG [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) Catching: org.jboss.weld.resources.spi.ResourceLoadingException: Error while loading class siteaccess.web.backend.service.RestEasyClientProducer at org.jboss.weld.resources.ClassTransformer.getBackedAnnotatedType(ClassTransformer.java:186) at org.jboss.weld.resources.ClassTransformer.getBackedAnnotatedType(ClassTransformer.java:194) at org.jboss.weld.bootstrap.FastAnnotatedTypeLoader.loadAnnotatedType(FastAnnotatedTypeLoader.java:113) at org.jboss.weld.bootstrap.FastAnnotatedTypeLoader.createContext(FastAnnotatedTypeLoader.java:102) at org.jboss.weld.bootstrap.FastAnnotatedTypeLoader.loadAnnotatedType(FastAnnotatedTypeLoader.java:91) at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:97) at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$1.doWork(ConcurrentBeanDeployer.java:65) at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$1.doWork(ConcurrentBeanDeployer.java:62) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:63) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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) at org.jboss.threads.JBossThread.run(JBossThread.java:320) Caused by: java.lang.NoClassDefFoundError: org/apache/http/conn/socket/LayeredConnectionSocketFactory at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671) at java.lang.Class.getDeclaredConstructors(Class.java:2020) at org.jboss.weld.annotated.slim.backed.SecurityActions.getDeclaredConstructors(SecurityActions.java:57) at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$BackedAnnotatedConstructors.computeValue(BackedAnnotatedType.java:163) at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$BackedAnnotatedConstructors.computeValue(BackedAnnotatedType.java:160) at org.jboss.weld.util.LazyValueHolder.get(LazyValueHolder.java:35) at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$EagerlyInitializedLazyValueHolder.<init>(BackedAnnotatedType.java:156) at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$BackedAnnotatedConstructors.<init>(BackedAnnotatedType.java:160) at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$BackedAnnotatedConstructors.<init>(BackedAnnotatedType.java:160) at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType.<init>(BackedAnnotatedType.java:61) at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType.of(BackedAnnotatedType.java:44) at org.jboss.weld.resources.ClassTransformer$TransformClassToBackedAnnotatedType.load(ClassTransformer.java:83) at org.jboss.weld.resources.ClassTransformer$TransformClassToBackedAnnotatedType.load(ClassTransformer.java:80) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3527) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2319) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2282) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2197) at com.google.common.cache.LocalCache.get(LocalCache.java:3937) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3941) at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4824) at org.jboss.weld.util.cache.LoadingCacheUtils.getCacheValue(LoadingCacheUtils.java:49) at org.jboss.weld.util.cache.LoadingCacheUtils.getCastCacheValue(LoadingCacheUtils.java:74) at org.jboss.weld.resources.ClassTransformer.getBackedAnnotatedType(ClassTransformer.java:175) ... 14 more Caused by: java.lang.ClassNotFoundException: org.apache.http.conn.socket.LayeredConnectionSocketFactory from [Module "deployment.wildfly-httpclient-test.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) ... 38 more {noformat} I've upgraded Weld to 2.3.3 and the http client jars to the latest versions (using details from https://developer.jboss.org/thread/242798). Now I get the exception for a different class: {noformat} Caused by: java.lang.ClassNotFoundException: org.apache.http.protocol.HttpContext from [Module "deployment.wildfly-httpclient-test.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) ... 38 more {noformat} I'm getting this exception also when testing with an unmodified WildFly 10.1 snapshot ( Build #2244 (Mar 24, 2016 1:10:44 PM) from https://ci.jboss.org/hudson/job/WildFly-latest-master/lastBuild/) I've first asked for help on the [forum|https://developer.jboss.org/thread/268871], but got no answers :( -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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