[JBoss JIRA] (WFLY-9170) EJB client from EAP 7.0 is sometimes authenticated as $local even when it is forbidden
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-9170?page=com.atlassian.jira.plugin.... ]
Jan Kalina commented on WFLY-9170:
----------------------------------
The difference in behavior is caused by removing this condition in WFLY-9037:
https://github.com/wildfly/wildfly/commit/15755f79e95ecc91522cd3a667c525f...
> EJB client from EAP 7.0 is sometimes authenticated as $local even when it is forbidden
> --------------------------------------------------------------------------------------
>
> Key: WFLY-9170
> URL: https://issues.jboss.org/browse/WFLY-9170
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Blocker
>
> when running EJB client from EAP 7.0 (EJB client 2.1.x) or the 7.1 legacy client (3.0.x), against EAP 7.1.0.ER3 (and newer) server on the same machine (with the same standalone.xml), even when the client has explicitly forbidden LOCAL authentication, he is sometimes (intermittently) authenticated as the user {{$local}}.
> This does not happen when the server is EAP 7.1.0.ER2, or when using EJB client 4.x.
> Impact: the client is intermittently authenticated as a different user than expected, this also makes invocations randomly fail, because the {{$local}} user typically isn't assigned to authorization roles which are typically required for invocations of some methods. Or the other way around, this could actually elevate the user's privileges in some cases.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9170) EJB client from EAP 7.0 is sometimes authenticated as $local even when it is forbidden
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-9170?page=com.atlassian.jira.plugin.... ]
Jan Kalina moved JBEAP-12525 to WFLY-9170:
------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9170 (was: JBEAP-12525)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: EJB
Security
(was: EJB)
(was: Security)
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.ER3)
Affects Testing: (was: Regression)
> EJB client from EAP 7.0 is sometimes authenticated as $local even when it is forbidden
> --------------------------------------------------------------------------------------
>
> Key: WFLY-9170
> URL: https://issues.jboss.org/browse/WFLY-9170
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Blocker
>
> when running EJB client from EAP 7.0 (EJB client 2.1.x) or the 7.1 legacy client (3.0.x), against EAP 7.1.0.ER3 (and newer) server on the same machine (with the same standalone.xml), even when the client has explicitly forbidden LOCAL authentication, he is sometimes (intermittently) authenticated as the user {{$local}}.
> This does not happen when the server is EAP 7.1.0.ER2, or when using EJB client 4.x.
> Impact: the client is intermittently authenticated as a different user than expected, this also makes invocations randomly fail, because the {{$local}} user typically isn't assigned to authorization roles which are typically required for invocations of some methods. Or the other way around, this could actually elevate the user's privileges in some cases.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JGRP-2031) GMS: replace ViewHandler.queue with BlockingQueue
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2031?page=com.atlassian.jira.plugin.... ]
Bela Ban edited comment on JGRP-2031 at 8/3/17 5:04 AM:
--------------------------------------------------------
Multiple join and merge requests are handled correctly, but multiple suspect events not - they are handled one-by-one. The culprit is Event.SUSPECT which takes as arg a single suspected member. Need to change this into a list of suspected members.
This change affects FD_SOCK, FD_ALL, FD_ALL2, FD and VERIFY_SUSPECT
was (Author: belaban):
Multiple join and merge requests are handled correctly, but multiple suspect events not - they are handled one-by-one. The culprit is Event.SUSPECT which takes as arg a single suspected member. Need to change this into a list of suspected members.
> GMS: replace ViewHandler.queue with BlockingQueue
> -------------------------------------------------
>
> Key: JGRP-2031
> URL: https://issues.jboss.org/browse/JGRP-2031
> Project: JGroups
> Issue Type: Task
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.0.5
>
>
> Replace {{GMS$ViewHandler.Queue}} with {{LinkedBlockingQueue}}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9169) Deadlock on AbstractHandleableCloseable close() method (AIX - IBM JDK/JRE)
by blass megod (JIRA)
[ https://issues.jboss.org/browse/WFLY-9169?page=com.atlassian.jira.plugin.... ]
blass megod updated WFLY-9169:
------------------------------
Description:
Deadlock on AbstractHandleableCloseable close() method (AIX - IBM JDK/JRE):
{code}
3XMTHREADINFO "p0" J9VMThread:0x00000000304BD100, j9thread_t:0x0000010029E423D0, java/lang/Thread:0x0000000408F664F8, state:CW, prio=5
3XMJAVALTHREAD (java/lang/Thread getId:0x8C96, isDaemon:false)
3XMTHREADINFO1 (native thread ID:0x20401E7, native priority:0x5, native policy:UNKNOWN, vmstate:CW, vm thread flags:0x00000101)
3XMCPUTIME CPU usage total: 0.379679000 secs, user: 0.354485000 secs, system: 0.025194000 secs, current category="Application"
3XMTHREADBLOCK Waiting on: java/lang/Object@0x000000040ECC59A0 Owned by: <unowned>
3XMHEAPALLOC Heap bytes allocated since last GC cycle=0 (0x0)
3XMTHREADINFO3 Java callstack:
4XESTACKTRACE at java/lang/Object.wait(Native Method)
4XESTACKTRACE at java/lang/Object.wait(Object.java:172(Compiled Code))
4XESTACKTRACE at org/jboss/remoting3/spi/AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:190(Compiled Code))
5XESTACKTRACE (entered lock: java/lang/Object@0x000000040ECC59A0, entry count: 1)
4XESTACKTRACE at org/jboss/naming/remote/client/EndpointCache.release(EndpointCache.java:67(Compiled Code))
5XESTACKTRACE (entered lock: org/jboss/naming/remote/client/EndpointCache@0x00000004002F3830, entry count: 1)
4XESTACKTRACE at org/jboss/naming/remote/client/EndpointCache$EndpointWrapper.close(EndpointCache.java:183(Compiled Code))
4XESTACKTRACE at org/jboss/naming/remote/client/InitialContextFactory$1.close(InitialContextFactory.java:233(Compiled Code))
4XESTACKTRACE at org/jboss/naming/remote/client/RemoteContext.close(RemoteContext.java:290(Compiled Code))
4XESTACKTRACE at javax/naming/InitialContext.close(InitialContext.java:567(Compiled Code))
...
{code}
This might happen when using remoting client with XNIO version 3.3.4
was:
Deadlock on AbstractHandleableCloseable close() method (AIX - IBM JDK/JRE):
{code}
3XMTHREADINFO "p0" J9VMThread:0x00000000304BD100, j9thread_t:0x0000010029E423D0, java/lang/Thread:0x0000000408F664F8, state:CW, prio=5
3XMJAVALTHREAD (java/lang/Thread getId:0x8C96, isDaemon:false)
3XMTHREADINFO1 (native thread ID:0x20401E7, native priority:0x5, native policy:UNKNOWN, vmstate:CW, vm thread flags:0x00000101)
3XMCPUTIME CPU usage total: 0.379679000 secs, user: 0.354485000 secs, system: 0.025194000 secs, current category="Application"
3XMTHREADBLOCK Waiting on: java/lang/Object@0x000000040ECC59A0 Owned by: <unowned>
3XMHEAPALLOC Heap bytes allocated since last GC cycle=0 (0x0)
3XMTHREADINFO3 Java callstack:
4XESTACKTRACE at java/lang/Object.wait(Native Method)
4XESTACKTRACE at java/lang/Object.wait(Object.java:172(Compiled Code))
4XESTACKTRACE at org/jboss/remoting3/spi/AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:190(Compiled Code))
5XESTACKTRACE (entered lock: java/lang/Object@0x000000040ECC59A0, entry count: 1)
4XESTACKTRACE at org/jboss/naming/remote/client/EndpointCache.release(EndpointCache.java:67(Compiled Code))
5XESTACKTRACE (entered lock: org/jboss/naming/remote/client/EndpointCache@0x00000004002F3830, entry count: 1)
4XESTACKTRACE at org/jboss/naming/remote/client/EndpointCache$EndpointWrapper.close(EndpointCache.java:183(Compiled Code))
4XESTACKTRACE at org/jboss/naming/remote/client/InitialContextFactory$1.close(InitialContextFactory.java:233(Compiled Code))
4XESTACKTRACE at org/jboss/naming/remote/client/RemoteContext.close(RemoteContext.java:290(Compiled Code))
4XESTACKTRACE at javax/naming/InitialContext.close(InitialContext.java:567(Compiled Code))
...
{code}
> Deadlock on AbstractHandleableCloseable close() method (AIX - IBM JDK/JRE)
> --------------------------------------------------------------------------
>
> Key: WFLY-9169
> URL: https://issues.jboss.org/browse/WFLY-9169
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 10.1.0.Final
> Environment: WildFly 10.1.0.Final
> AIX Version 7.2
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pap6480sr3fp22-20161213_02(SR3 FP22))
> IBM J9 VM (build 2.8, JRE 1.8.0 AIX ppc64-64 Compressed References 20161209_329148 (JIT enabled, AOT enabled)
> J9VM - R28_20161209_1345_B329148
> JIT - tr.r14.java.green_20161207_128946
> GC - R28_20161209_1345_B329148_CMPRSS
> J9CL - 20161209_329148)
> JCL - 20161213_01 based on Oracle jdk8u111-b14
> Reporter: blass megod
> Assignee: David Lloyd
> Labels: deadlock, regression, remoting
>
> Deadlock on AbstractHandleableCloseable close() method (AIX - IBM JDK/JRE):
> {code}
> 3XMTHREADINFO "p0" J9VMThread:0x00000000304BD100, j9thread_t:0x0000010029E423D0, java/lang/Thread:0x0000000408F664F8, state:CW, prio=5
> 3XMJAVALTHREAD (java/lang/Thread getId:0x8C96, isDaemon:false)
> 3XMTHREADINFO1 (native thread ID:0x20401E7, native priority:0x5, native policy:UNKNOWN, vmstate:CW, vm thread flags:0x00000101)
> 3XMCPUTIME CPU usage total: 0.379679000 secs, user: 0.354485000 secs, system: 0.025194000 secs, current category="Application"
> 3XMTHREADBLOCK Waiting on: java/lang/Object@0x000000040ECC59A0 Owned by: <unowned>
> 3XMHEAPALLOC Heap bytes allocated since last GC cycle=0 (0x0)
> 3XMTHREADINFO3 Java callstack:
> 4XESTACKTRACE at java/lang/Object.wait(Native Method)
> 4XESTACKTRACE at java/lang/Object.wait(Object.java:172(Compiled Code))
> 4XESTACKTRACE at org/jboss/remoting3/spi/AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:190(Compiled Code))
> 5XESTACKTRACE (entered lock: java/lang/Object@0x000000040ECC59A0, entry count: 1)
> 4XESTACKTRACE at org/jboss/naming/remote/client/EndpointCache.release(EndpointCache.java:67(Compiled Code))
> 5XESTACKTRACE (entered lock: org/jboss/naming/remote/client/EndpointCache@0x00000004002F3830, entry count: 1)
> 4XESTACKTRACE at org/jboss/naming/remote/client/EndpointCache$EndpointWrapper.close(EndpointCache.java:183(Compiled Code))
> 4XESTACKTRACE at org/jboss/naming/remote/client/InitialContextFactory$1.close(InitialContextFactory.java:233(Compiled Code))
> 4XESTACKTRACE at org/jboss/naming/remote/client/RemoteContext.close(RemoteContext.java:290(Compiled Code))
> 4XESTACKTRACE at javax/naming/InitialContext.close(InitialContext.java:567(Compiled Code))
> ...
> {code}
> This might happen when using remoting client with XNIO version 3.3.4
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9169) Deadlock on AbstractHandleableCloseable close() method (AIX - IBM JDK/JRE)
by blass megod (JIRA)
[ https://issues.jboss.org/browse/WFLY-9169?page=com.atlassian.jira.plugin.... ]
blass megod updated WFLY-9169:
------------------------------
Labels: regression remoting (was: )
> Deadlock on AbstractHandleableCloseable close() method (AIX - IBM JDK/JRE)
> --------------------------------------------------------------------------
>
> Key: WFLY-9169
> URL: https://issues.jboss.org/browse/WFLY-9169
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 10.1.0.Final
> Environment: WildFly 10.1.0.Final
> AIX Version 7.2
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pap6480sr3fp22-20161213_02(SR3 FP22))
> IBM J9 VM (build 2.8, JRE 1.8.0 AIX ppc64-64 Compressed References 20161209_329148 (JIT enabled, AOT enabled)
> J9VM - R28_20161209_1345_B329148
> JIT - tr.r14.java.green_20161207_128946
> GC - R28_20161209_1345_B329148_CMPRSS
> J9CL - 20161209_329148)
> JCL - 20161213_01 based on Oracle jdk8u111-b14
> Reporter: blass megod
> Assignee: David Lloyd
> Labels: deadlock, regression, remoting
>
> Deadlock on AbstractHandleableCloseable close() method (AIX - IBM JDK/JRE):
> {code}
> 3XMTHREADINFO "p0" J9VMThread:0x00000000304BD100, j9thread_t:0x0000010029E423D0, java/lang/Thread:0x0000000408F664F8, state:CW, prio=5
> 3XMJAVALTHREAD (java/lang/Thread getId:0x8C96, isDaemon:false)
> 3XMTHREADINFO1 (native thread ID:0x20401E7, native priority:0x5, native policy:UNKNOWN, vmstate:CW, vm thread flags:0x00000101)
> 3XMCPUTIME CPU usage total: 0.379679000 secs, user: 0.354485000 secs, system: 0.025194000 secs, current category="Application"
> 3XMTHREADBLOCK Waiting on: java/lang/Object@0x000000040ECC59A0 Owned by: <unowned>
> 3XMHEAPALLOC Heap bytes allocated since last GC cycle=0 (0x0)
> 3XMTHREADINFO3 Java callstack:
> 4XESTACKTRACE at java/lang/Object.wait(Native Method)
> 4XESTACKTRACE at java/lang/Object.wait(Object.java:172(Compiled Code))
> 4XESTACKTRACE at org/jboss/remoting3/spi/AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:190(Compiled Code))
> 5XESTACKTRACE (entered lock: java/lang/Object@0x000000040ECC59A0, entry count: 1)
> 4XESTACKTRACE at org/jboss/naming/remote/client/EndpointCache.release(EndpointCache.java:67(Compiled Code))
> 5XESTACKTRACE (entered lock: org/jboss/naming/remote/client/EndpointCache@0x00000004002F3830, entry count: 1)
> 4XESTACKTRACE at org/jboss/naming/remote/client/EndpointCache$EndpointWrapper.close(EndpointCache.java:183(Compiled Code))
> 4XESTACKTRACE at org/jboss/naming/remote/client/InitialContextFactory$1.close(InitialContextFactory.java:233(Compiled Code))
> 4XESTACKTRACE at org/jboss/naming/remote/client/RemoteContext.close(RemoteContext.java:290(Compiled Code))
> 4XESTACKTRACE at javax/naming/InitialContext.close(InitialContext.java:567(Compiled Code))
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9169) Deadlock on AbstractHandleableCloseable close() method (AIX - IBM JDK/JRE)
by blass megod (JIRA)
[ https://issues.jboss.org/browse/WFLY-9169?page=com.atlassian.jira.plugin.... ]
blass megod updated WFLY-9169:
------------------------------
Labels: deadlock regression remoting (was: regression remoting)
> Deadlock on AbstractHandleableCloseable close() method (AIX - IBM JDK/JRE)
> --------------------------------------------------------------------------
>
> Key: WFLY-9169
> URL: https://issues.jboss.org/browse/WFLY-9169
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 10.1.0.Final
> Environment: WildFly 10.1.0.Final
> AIX Version 7.2
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pap6480sr3fp22-20161213_02(SR3 FP22))
> IBM J9 VM (build 2.8, JRE 1.8.0 AIX ppc64-64 Compressed References 20161209_329148 (JIT enabled, AOT enabled)
> J9VM - R28_20161209_1345_B329148
> JIT - tr.r14.java.green_20161207_128946
> GC - R28_20161209_1345_B329148_CMPRSS
> J9CL - 20161209_329148)
> JCL - 20161213_01 based on Oracle jdk8u111-b14
> Reporter: blass megod
> Assignee: David Lloyd
> Labels: deadlock, regression, remoting
>
> Deadlock on AbstractHandleableCloseable close() method (AIX - IBM JDK/JRE):
> {code}
> 3XMTHREADINFO "p0" J9VMThread:0x00000000304BD100, j9thread_t:0x0000010029E423D0, java/lang/Thread:0x0000000408F664F8, state:CW, prio=5
> 3XMJAVALTHREAD (java/lang/Thread getId:0x8C96, isDaemon:false)
> 3XMTHREADINFO1 (native thread ID:0x20401E7, native priority:0x5, native policy:UNKNOWN, vmstate:CW, vm thread flags:0x00000101)
> 3XMCPUTIME CPU usage total: 0.379679000 secs, user: 0.354485000 secs, system: 0.025194000 secs, current category="Application"
> 3XMTHREADBLOCK Waiting on: java/lang/Object@0x000000040ECC59A0 Owned by: <unowned>
> 3XMHEAPALLOC Heap bytes allocated since last GC cycle=0 (0x0)
> 3XMTHREADINFO3 Java callstack:
> 4XESTACKTRACE at java/lang/Object.wait(Native Method)
> 4XESTACKTRACE at java/lang/Object.wait(Object.java:172(Compiled Code))
> 4XESTACKTRACE at org/jboss/remoting3/spi/AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:190(Compiled Code))
> 5XESTACKTRACE (entered lock: java/lang/Object@0x000000040ECC59A0, entry count: 1)
> 4XESTACKTRACE at org/jboss/naming/remote/client/EndpointCache.release(EndpointCache.java:67(Compiled Code))
> 5XESTACKTRACE (entered lock: org/jboss/naming/remote/client/EndpointCache@0x00000004002F3830, entry count: 1)
> 4XESTACKTRACE at org/jboss/naming/remote/client/EndpointCache$EndpointWrapper.close(EndpointCache.java:183(Compiled Code))
> 4XESTACKTRACE at org/jboss/naming/remote/client/InitialContextFactory$1.close(InitialContextFactory.java:233(Compiled Code))
> 4XESTACKTRACE at org/jboss/naming/remote/client/RemoteContext.close(RemoteContext.java:290(Compiled Code))
> 4XESTACKTRACE at javax/naming/InitialContext.close(InitialContext.java:567(Compiled Code))
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months