April 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-811) NullPointerException in DeploymentRoleToRolesMappingProvider

by Derek Horton (JIRA)

[ https://issues.jboss.org/browse/SECURITY-811?page=com.atlassian.jira.plug... ] Derek Horton reassigned SECURITY-811: ------------------------------------- Assignee: Peter Skopek (was: Derek Horton) > NullPointerException in DeploymentRoleToRolesMappingProvider > ------------------------------------------------------------ > > Key: SECURITY-811 > URL: https://issues.jboss.org/browse/SECURITY-811 > Project: PicketBox > Issue Type: Bug > Components: JBossSX > Affects Versions: JBossSecurity_2.0.8.Final > Reporter: Chao Wang > Assignee: Peter Skopek > Priority: Minor > Attachments: SECURITY-811-picketbox.patch, SECURITY-811.patch > > > {code:title=DeploymentRoleToRolesMappingProvider.java|borderStyle=solid} > RoleGroup assignedRoles = (SimpleRoleGroup)contextMap.get(SecurityConstants.ROLES_IDENTIFIER); > for (Role r: assignedRoles.getRoles()) { > {code} > A null value of assignedRoles causes NullPointerException on server if user have not input username / passoword yet -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (SECURITY-942) NullPointerException in DeploymentRoleToRolesMappingProvider

by Derek Horton (JIRA)

Derek Horton created SECURITY-942: ------------------------------------- Summary: NullPointerException in DeploymentRoleToRolesMappingProvider Key: SECURITY-942 URL: https://issues.jboss.org/browse/SECURITY-942 Project: PicketBox Issue Type: Bug Components: JBossSX Affects Versions: JBossSecurity_2.0.8.Final Reporter: Derek Horton Assignee: Derek Horton Priority: Minor {code:title=DeploymentRoleToRolesMappingProvider.java|borderStyle=solid} RoleGroup assignedRoles = (SimpleRoleGroup)contextMap.get(SecurityConstants.ROLES_IDENTIFIER); for (Role r: assignedRoles.getRoles()) { {code} A null value of assignedRoles causes NullPointerException on server if user have not input username / passoword yet -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (SECURITY-811) NullPointerException in DeploymentRoleToRolesMappingProvider

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-811?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-811: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1327293 Bugzilla Update: Perform > NullPointerException in DeploymentRoleToRolesMappingProvider > ------------------------------------------------------------ > > Key: SECURITY-811 > URL: https://issues.jboss.org/browse/SECURITY-811 > Project: PicketBox > Issue Type: Bug > Components: JBossSX > Affects Versions: JBossSecurity_2.0.8.Final > Reporter: Chao Wang > Assignee: Derek Horton > Priority: Minor > Attachments: SECURITY-811-picketbox.patch, SECURITY-811.patch > > > {code:title=DeploymentRoleToRolesMappingProvider.java|borderStyle=solid} > RoleGroup assignedRoles = (SimpleRoleGroup)contextMap.get(SecurityConstants.ROLES_IDENTIFIER); > for (Role r: assignedRoles.getRoles()) { > {code} > A null value of assignedRoles causes NullPointerException on server if user have not input username / passoword yet -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (SECURITY-811) NullPointerException in DeploymentRoleToRolesMappingProvider

by Derek Horton (JIRA)

[ https://issues.jboss.org/browse/SECURITY-811?page=com.atlassian.jira.plug... ] Derek Horton reassigned SECURITY-811: ------------------------------------- Assignee: Derek Horton (was: Chao Wang) > NullPointerException in DeploymentRoleToRolesMappingProvider > ------------------------------------------------------------ > > Key: SECURITY-811 > URL: https://issues.jboss.org/browse/SECURITY-811 > Project: PicketBox > Issue Type: Bug > Components: JBossSX > Affects Versions: JBossSecurity_2.0.8.Final > Reporter: Chao Wang > Assignee: Derek Horton > Priority: Minor > Attachments: SECURITY-811-picketbox.patch, SECURITY-811.patch > > > {code:title=DeploymentRoleToRolesMappingProvider.java|borderStyle=solid} > RoleGroup assignedRoles = (SimpleRoleGroup)contextMap.get(SecurityConstants.ROLES_IDENTIFIER); > for (Role r: assignedRoles.getRoles()) { > {code} > A null value of assignedRoles causes NullPointerException on server if user have not input username / passoword yet -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (SECURITY-811) NullPointerException in DeploymentRoleToRolesMappingProvider

by Derek Horton (JIRA)

[ https://issues.jboss.org/browse/SECURITY-811?page=com.atlassian.jira.plug... ] Derek Horton updated SECURITY-811: ---------------------------------- Git Pull Request: https://github.com/picketbox/picketbox/pull/59 > NullPointerException in DeploymentRoleToRolesMappingProvider > ------------------------------------------------------------ > > Key: SECURITY-811 > URL: https://issues.jboss.org/browse/SECURITY-811 > Project: PicketBox > Issue Type: Bug > Components: JBossSX > Affects Versions: JBossSecurity_2.0.8.Final > Reporter: Chao Wang > Assignee: Derek Horton > Priority: Minor > Attachments: SECURITY-811-picketbox.patch, SECURITY-811.patch > > > {code:title=DeploymentRoleToRolesMappingProvider.java|borderStyle=solid} > RoleGroup assignedRoles = (SimpleRoleGroup)contextMap.get(SecurityConstants.ROLES_IDENTIFIER); > for (Role r: assignedRoles.getRoles()) { > {code} > A null value of assignedRoles causes NullPointerException on server if user have not input username / passoword yet -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1957) S3_PING: Nodes never removed from .list file

by Mitchell Ackerman (JIRA)

[ https://issues.jboss.org/browse/JGRP-1957?page=com.atlassian.jira.plugin.... ] Mitchell Ackerman commented on JGRP-1957: ----------------------------------------- Stepping through the code, I have confirmed that the scenario is the same as described above: upon a view change the new (correct) member list is written to S3, but then it is overwritten with all the old members. When the old members are added back to the _logical_addr_cache_ they all have their _removable_ field set to false, so that all subsequent evictions skip over these members and they are never removed. Should I open a new Issue? Do you have any other suggestions? > S3_PING: Nodes never removed from .list file > -------------------------------------------- > > Key: JGRP-1957 > URL: https://issues.jboss.org/browse/JGRP-1957 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.4 > Environment: JGroups client running on Mac OS X - Yosemite > JDK 1.7.71 > Reporter: Nick Sawadsky > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.6 > > > I'm not 100% sure, but it seems like there might be a defect here. > I'm using TCP, S3_PING, and MERGE3. > I've set logical_addr_cache_max_size to 2 for testing purposes, although I don't think the value of this setting affects my test results. > I start a single node, node A. Then I start a second node, node B. > I then repeatedly shutdown and restart node B. > Each time node B starts, a new row is added to the .list file stored in S3. > But even if I continue this process for 15 minutes, old rows are never removed from the .list file, so it continues to grow in size. > I've read the docs and mailing list threads, so I'm aware that the list is not immediately updated as soon as a member leaves. But I was expecting that when a view change occurs, nodes no longer in the view would be marked for removal (line 2193 of TP.java) and then after the logical_addr_cache_expiration has been reached and the reaper kicks in, once a new node joins, the expired cache entries would be purged from the file. > I dug in to the code a bit, and what seems to be happening is that the MERGE3 protocol periodically generates a FIND_MBRS event. S3_PING retrieves the membership from the .list file, which includes expired nodes. And then all of these members are re-added to the logical address cache (line 157 of S3_PING.java, line 533 of Discovery.java, line 2263 of TP.java). > So expired nodes are continually re-added to the logical address cache, preventing them from ever being reaped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2041) Getting Socketexception during cluster communication

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2041?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2041: -------------------------------- Well, CTRL-C or kill -9 on the peer would lead to such a message. This is not necessarily bad. > Getting Socketexception during cluster communication > ---------------------------------------------------- > > Key: JGRP-2041 > URL: https://issues.jboss.org/browse/JGRP-2041 > Project: JGroups > Issue Type: Bug > Affects Versions: 2.5.2 > Environment: RHEL > Reporter: Rohit Singh > Assignee: Bela Ban > Fix For: 4.0 > > Attachments: jetty.log.D20160315.T074324.zip > > > We faced issues during our cluster communication which is based on JGroup implementation. > We got below errors in logs. JGroup does not even put full stacktrace of the SocketException. > [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed > [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed > [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed > [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed > [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed > [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated > [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated > [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated > [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated > [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1123) TraitObjectTypeNode isn't serializable

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1123: ----------------------------------- Summary: TraitObjectTypeNode isn't serializable Key: DROOLS-1123 URL: https://issues.jboss.org/browse/DROOLS-1123 Project: Drools Issue Type: Bug Reporter: Mario Fusco Assignee: Mario Fusco TraitObjectTypeNode misses a no-args constructor and then isn't serializable -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-496) Support for JAAS Subject inclusion in SecurityIdentity (via PeerIdentity)

by David Lloyd (JIRA)

David Lloyd created ELY-496: ------------------------------- Summary: Support for JAAS Subject inclusion in SecurityIdentity (via PeerIdentity) Key: ELY-496 URL: https://issues.jboss.org/browse/ELY-496 Project: WildFly Elytron Issue Type: Enhancement Components: API / SPI Reporter: David Lloyd We will probably need a way to configure a security domain to associate an legacy JAAS Subject to a SecurityIdentity. This would fit with the existing capabilities of associating a PeerIdentity to the SecurityIdentity, and transforming the SecurityIdentity. However the way that PeerIdentity performs associations is with a before and after call. We need to support another mechanism that can use e.g. a function to wrap, because the only way to associate a Subject in JAAS is to create an AccessControlContext with a SubjectDomainCombiner, and to associate an AccessControlContext one must use doPrivileged. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6501) EJB with AroundConstruct interceptor with Object return type fails to deploy

by Dmitrii Tikhomirov (JIRA)

[ https://issues.jboss.org/browse/WFLY-6501?page=com.atlassian.jira.plugin.... ] Dmitrii Tikhomirov updated WFLY-6501: ------------------------------------- Attachment: myintercepter.tar.gz reproducer, 1) maven clean package 2) deploy to wildfly 3) check console > EJB with AroundConstruct interceptor with Object return type fails to deploy > ---------------------------------------------------------------------------- > > Key: WFLY-6501 > URL: https://issues.jboss.org/browse/WFLY-6501 > Project: WildFly > Issue Type: Bug > Components: EE, EJB > Affects Versions: 10.0.0.Final > Reporter: Tomas Remes > Assignee: Dmitrii Tikhomirov > Attachments: myintercepter.tar.gz > > > Having: > {code} > @Stateless > @Interceptors(AroundConstructInterceptor.class) > public class AroundConstructSLSB { > ... > } > {code} > and > {code} > public class AroundConstructInterceptor { > public static volatile boolean intercepted = false; > @AroundConstruct > private Object aroundConstruct(InvocationContext ctx) throws Exception { > intercepted = true; > return ctx.proceed(); > } > } > {code} > fails with following exception: > {noformat} > 08:18:55,464 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."bcc899ab-39cf-44dc-a2ba-e364d53091cc.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."bcc899ab-39cf-44dc-a2ba-e364d53091cc.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "bcc899ab-39cf-44dc-a2ba-e364d53091cc.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > 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) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0024: Could not configure component AroundConstructSLSB > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:96) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0175: No method found with id: Method aroundConstruct(javax.interceptor.InvocationContext) on class (or its super class) class org.jboss.as.test.integration.ejb.interceptor.aroundconstruct.returnObject.AroundConstructInterceptor > at org.jboss.as.server.deployment.reflect.ClassReflectionIndexUtil.findRequiredMethod(ClassReflectionIndexUtil.java:79) > at org.jboss.as.ee.component.DefaultInterceptorConfigurator$1.handleInterceptorClass(DefaultInterceptorConfigurator.java:177) > at org.jboss.as.ee.component.DefaultInterceptorConfigurator$1.handle(DefaultInterceptorConfigurator.java:158) > at org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:54) > at org.jboss.as.ee.component.DefaultInterceptorConfigurator.configure(DefaultInterceptorConfigurator.java:188) > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:82) > ... 6 more > {noformat} > I cannot see any statement in Interceptor spec forbidding this. Testcase is available at https://github.com/tremes/wildfly/tree/intercept_ejb. I think the problem is class description having this method return type as void. I guess it occurs at first at https://github.com/wildfly/wildfly/blob/master/ee/src/main/java/org/jboss... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016