September 2017 - jboss-jira - Jboss List Archives

by Bela Ban (JIRA)

Bela Ban created JGRP-2218: ------------------------------ Summary: New buffers Key: JGRP-2218 URL: https://issues.jboss.org/browse/JGRP-2218 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0 h3. Goal Change payload in {{Message}} from byte[] arrays to a {{Buffer}} interface which can have multiple implementations. h3. Motivation Currently, having to pass a byte[] array to a message leads to unnecessary copying: * When an application has a ref to an NIO (direct) {{ByteBuffer}}, the bytes in the byte buffer have to be copied into a byte[] array and then set in the message * When the application sends around byte[] arrays, but also wants to add some additional metadata, e.g. type (1000-byte requests/responses), it needs to create a new byte[] array of (say) 1001 bytes and copy the data (1000 bytes) plus the request type (1 byte) into the new copy. Example: {{MPerf}} and {{UPerf}} h3. Design Instead of copying, the application creates an instance of {{Buffer}} and sets the buffer in {{Message}}. The {{Buffer}} is then passed all the way down into the transport where it is marshalled and sent. There can be a number of buffer implementations, e.g. * {{ArrayBuffer}}: wraps a byte[] array with an offset and length * {{NioDirectBuffer}}: wraps an NIO direct {{ByteBuffer}} * {{NioHeapBuffer}}: wraps an NIO heap-based {{ByteBuffer}} * {{CompositeBuffer}}: wraps multiple Buffers. E.g. type (1 byte) and data (1000 bytes) as described above * {{IntBuffer}}: a single integer * {{PartialBuffer}}: a ref to a {{Buffer}}, with an offset and length The {{Buffer}} interface has methods {{size()}}, {{writeTo(DataOutput)}}, {{readFrom(DataInput)}}, possibly also {{acquire()}} and {{release()}} (for ref-counting). Each buffer impl has an ID and it should be possible to register new impls. A {{BufferFactory}} maintains a mapping between IDs and impl classes. When marshalling a {{Buffer}}, the ID is written first, followed by the buffer's {{writeTo()}} method. When reading buffers, the {{BufferFactory}} is used to create instances from IDs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3276) Fix/unignore test in IdentityOperationsTestCase

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3276?page=com.atlassian.jira.plugi... ] Hynek Švábek updated WFCORE-3276: --------------------------------- Summary: Fix/unignore test in IdentityOperationsTestCase (was: Fix/unignore tests in IdentityOperationsTestCase) > Fix/unignore test in IdentityOperationsTestCase > ----------------------------------------------- > > Key: WFCORE-3276 > URL: https://issues.jboss.org/browse/WFCORE-3276 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Hynek Švábek > Assignee: Tomaz Cerar > Priority: Minor > > Fix/unignore tests in WFCORE org.wildfly.extension.elytron.IdentityOperationsTestCase -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3276) Fix/unignore test in IdentityOperationsTestCase

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3276?page=com.atlassian.jira.plugi... ] Hynek Švábek updated WFCORE-3276: --------------------------------- Description: Fix/unignore test in WFCORE org.wildfly.extension.elytron.IdentityOperationsTestCase (was: Fix/unignore tests in WFCORE org.wildfly.extension.elytron.IdentityOperationsTestCase) > Fix/unignore test in IdentityOperationsTestCase > ----------------------------------------------- > > Key: WFCORE-3276 > URL: https://issues.jboss.org/browse/WFCORE-3276 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Hynek Švábek > Assignee: Tomaz Cerar > Priority: Minor > > Fix/unignore test in WFCORE org.wildfly.extension.elytron.IdentityOperationsTestCase -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3276) Fix/unignore tests in IdentityOperationsTestCase

by Hynek Švábek (JIRA)

Hynek Švábek created WFCORE-3276: ------------------------------------ Summary: Fix/unignore tests in IdentityOperationsTestCase Key: WFCORE-3276 URL: https://issues.jboss.org/browse/WFCORE-3276 Project: WildFly Core Issue Type: Task Components: Test Suite Reporter: Hynek Švábek Assignee: Tomaz Cerar Priority: Minor Fix/unignore tests in WFCORE org.wildfly.extension.elytron.IdentityOperationsTestCase -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9240) SecurityDomain.getCurrent() throws NPE when invoking SLSB using a Weld thread

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-9240?page=com.atlassian.jira.plugin.... ] Martin Kouba updated WFLY-9240: ------------------------------- Description: -The integration code used by Weld 3 to propagate the security context of the current thread to different threads (needed for async events CDI 2.0 feature) is not able to obtain the current {{org.wildfly.security.auth.server.SecurityDomain}} anymore.- -The invocation of [SecurityDomain.getCurrent()|https://github.com/weld/wildfly/blob/11.0.0.B...] returns {{null}}.- UPDATE: The original description was wrong. We wrongly assumed that Elytron is active for a deployment by default which isn't the case. NullPointerException being reported DURING calls to SecurityDomain.getCurrent(): {noformat} Caused by: java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936) at org.wildfly.security.auth.server.SecurityDomain.getCurrent(SecurityDomain.java:171) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:74) at org.jboss.weld.tests.event.async.context.security.Printer$$$view2.print(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:411) at org.jboss.weld.module.ejb.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:128) at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) at org.jboss.weld.module.ejb.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:68) at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:106) at org.jboss.weld.tests.event.async.context.security.Printer$Proxy$_$$_Weld$EnterpriseProxy$.print(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) {noformat} Note that this worked on WildFly *11.0.0.Alpha1*. It's also possible that the test (see also steps to reproduce) is wrong. A review/help from a security expert would be appreciated. was: -The integration code used by Weld 3 to propagate the security context of the current thread to different threads (needed for async events CDI 2.0 feature) is not able to obtain the current {{org.wildfly.security.auth.server.SecurityDomain}} anymore. - -The invocation of [SecurityDomain.getCurrent()|https://github.com/weld/wildfly/blob/11.0.0.B...] returns {{null}}. - NullPointerException being reported DURING calls to SecurityDomain.getCurrent(): - {noformat} Caused by: java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936) at org.wildfly.security.auth.server.SecurityDomain.getCurrent(SecurityDomain.java:171) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:74) at org.jboss.weld.tests.event.async.context.security.Printer$$$view2.print(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:411) at org.jboss.weld.module.ejb.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:128) at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) at org.jboss.weld.module.ejb.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:68) at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:106) at org.jboss.weld.tests.event.async.context.security.Printer$Proxy$_$$_Weld$EnterpriseProxy$.print(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) {noformat} Note that this worked on WildFly *11.0.0.Alpha1*. It's also possible that the test (see also steps to reproduce) is wrong. A review/help from a security expert would be appreciated. > SecurityDomain.getCurrent() throws NPE when invoking SLSB using a Weld thread > ----------------------------------------------------------------------------- > > Key: WFLY-9240 > URL: https://issues.jboss.org/browse/WFLY-9240 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Security > Affects Versions: 11.0.0.Beta1, 11.0.0.CR1 > Reporter: Martin Kouba > Assignee: Darran Lofthouse > Priority: Critical > > -The integration code used by Weld 3 to propagate the security context of the current thread to different threads (needed for async events CDI 2.0 feature) is not able to obtain the current {{org.wildfly.security.auth.server.SecurityDomain}} anymore.- > -The invocation of [SecurityDomain.getCurrent()|https://github.com/weld/wildfly/blob/11.0.0.B...] returns {{null}}.- > UPDATE: The original description was wrong. We wrongly assumed that Elytron is active for a deployment by default which isn't the case. > NullPointerException being reported DURING calls to SecurityDomain.getCurrent(): > {noformat} > Caused by: java.lang.NullPointerException > at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936) > at org.wildfly.security.auth.server.SecurityDomain.getCurrent(SecurityDomain.java:171) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:74) > at org.jboss.weld.tests.event.async.context.security.Printer$$$view2.print(Unknown Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:411) > at org.jboss.weld.module.ejb.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:128) > at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) > at org.jboss.weld.module.ejb.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:68) > at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:106) > at org.jboss.weld.tests.event.async.context.security.Printer$Proxy$_$$_Weld$EnterpriseProxy$.print(Unknown Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > {noformat} > Note that this worked on WildFly *11.0.0.Alpha1*. > It's also possible that the test (see also steps to reproduce) is wrong. A review/help from a security expert would be appreciated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9240) SecurityDomain.getCurrent() throws NPE when invoking SLSB using a Weld thread

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-9240?page=com.atlassian.jira.plugin.... ] Martin Kouba updated WFLY-9240: ------------------------------- Summary: SecurityDomain.getCurrent() throws NPE when invoking SLSB using a Weld thread (was: WeldSecurityServices not able to obtain the current SecurityDomain anymore) > SecurityDomain.getCurrent() throws NPE when invoking SLSB using a Weld thread > ----------------------------------------------------------------------------- > > Key: WFLY-9240 > URL: https://issues.jboss.org/browse/WFLY-9240 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Security > Affects Versions: 11.0.0.Beta1, 11.0.0.CR1 > Reporter: Martin Kouba > Assignee: Darran Lofthouse > Priority: Critical > > -The integration code used by Weld 3 to propagate the security context of the current thread to different threads (needed for async events CDI 2.0 feature) is not able to obtain the current {{org.wildfly.security.auth.server.SecurityDomain}} anymore. - > -The invocation of [SecurityDomain.getCurrent()|https://github.com/weld/wildfly/blob/11.0.0.B...] returns {{null}}. > - > NullPointerException being reported DURING calls to SecurityDomain.getCurrent(): - > {noformat} > Caused by: java.lang.NullPointerException > at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936) > at org.wildfly.security.auth.server.SecurityDomain.getCurrent(SecurityDomain.java:171) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:74) > at org.jboss.weld.tests.event.async.context.security.Printer$$$view2.print(Unknown Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:411) > at org.jboss.weld.module.ejb.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:128) > at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) > at org.jboss.weld.module.ejb.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:68) > at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:106) > at org.jboss.weld.tests.event.async.context.security.Printer$Proxy$_$$_Weld$EnterpriseProxy$.print(Unknown Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > {noformat} > Note that this worked on WildFly *11.0.0.Alpha1*. > It's also possible that the test (see also steps to reproduce) is wrong. A review/help from a security expert would be appreciated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9341) Unignore MessagingClientTestCase.testMessagingClientUsingMessagingPort

by Miroslav Novak (JIRA)

Miroslav Novak created WFLY-9341: ------------------------------------ Summary: Unignore MessagingClientTestCase.testMessagingClientUsingMessagingPort Key: WFLY-9341 URL: https://issues.jboss.org/browse/WFLY-9341 Project: WildFly Issue Type: Task Components: Test Suite Affects Versions: 11.0.0.CR1 Reporter: Miroslav Novak Assignee: Miroslav Novak Priority: Minor Ignore MessagingClientTestCase#testMessagingClientUsingMessagingPort test. Smoke test whether JMS client can connect directly to messaging. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9340) Unignore MessagingClientTestCase.testMessagingClientUsingMessagingPort

by Miroslav Novak (JIRA)

Miroslav Novak created WFLY-9340: ------------------------------------ Summary: Unignore MessagingClientTestCase.testMessagingClientUsingMessagingPort Key: WFLY-9340 URL: https://issues.jboss.org/browse/WFLY-9340 Project: WildFly Issue Type: Task Components: Test Suite Affects Versions: 11.0.0.CR1 Reporter: Miroslav Novak Priority: Minor Ignore MessagingClientTestCase#testMessagingClientUsingMessagingPort test. Smoke test whether JMS client can connect directly to messaging. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9340) Unignore MessagingClientTestCase.testMessagingClientUsingMessagingPort

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-9340?page=com.atlassian.jira.plugin.... ] Miroslav Novak reassigned WFLY-9340: ------------------------------------ Assignee: Miroslav Novak > Unignore MessagingClientTestCase.testMessagingClientUsingMessagingPort > ---------------------------------------------------------------------- > > Key: WFLY-9340 > URL: https://issues.jboss.org/browse/WFLY-9340 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 11.0.0.CR1 > Reporter: Miroslav Novak > Assignee: Miroslav Novak > Priority: Minor > > Ignore MessagingClientTestCase#testMessagingClientUsingMessagingPort test. Smoke test whether JMS client can connect directly to messaging. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3273) sharedState is passed null by PluginAuthenticationCallbackHandler

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3273?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated WFCORE-3273: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1490383 Bugzilla Update: Perform > sharedState is passed null by PluginAuthenticationCallbackHandler > ----------------------------------------------------------------- > > Key: WFCORE-3273 > URL: https://issues.jboss.org/browse/WFCORE-3273 > Project: WildFly Core > Issue Type: Bug > Components: Security > Environment: Fedora 26, using ovirt-engine-wildfly package > Reporter: Roy Golan > Assignee: Darran Lofthouse > > oVirt's ovirt-engine uses an authorization plugin [1] for management interface that recently after upgrading to Wildfly 11 stopped working. The reason is the sharedState passed to the plugin constructor is now null. > A current workaround this would be to avoid adding to plugin into the shareState but that means any delegating plugin would fail to find this plugin and possibly other bad stuff I'm not aware of. > [1] https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=backend/manag... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 September 2017