March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4637) Get core resources and operations out of the controller module

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4637?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4637: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Get core resources and operations out of the controller module > -------------------------------------------------------------- > > Key: AS7-4637 > URL: https://issues.jboss.org/browse/AS7-4637 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > The controller module has a lot of classes related to core resources (resource defs, op handlers, description providers for things like interfaces) that are only in there so they can be commonly accessible to both server and host-controller. This is unnecessary, since host-controller depends on server. > Either move these to server or create a separate module for this stuff; restrict the controller module to the true core ModelController stuff. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-1916) Using pre-digested passwords, having all installations with the same realm could reduce the effectiveness

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-1916?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-1916: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Using pre-digested passwords, having all installations with the same realm could reduce the effectiveness > --------------------------------------------------------------------------------------------------------- > > Key: AS7-1916 > URL: https://issues.jboss.org/browse/AS7-1916 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: Realm_Management > Fix For: 8.0.0.Alpha1 > > > Can we generate a name of first boot? Possibly even separate the internal name use to link from the realm to the name presented to the end users? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-5033) Add support to specify ciphers available with Remoting

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5033?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5033: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Add support to specify ciphers available with Remoting > ------------------------------------------------------ > > Key: AS7-5033 > URL: https://issues.jboss.org/browse/AS7-5033 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management, Remoting, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-2487) Implementation of a more complex ACL scheme for domain management

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-2487?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-2487: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Implementation of a more complex ACL scheme for domain management > ----------------------------------------------------------------- > > Key: AS7-2487 > URL: https://issues.jboss.org/browse/AS7-2487 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: Authorization, Realm_Management > Fix For: 8.0.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-4196) Update the pluggable user store SPI to allow for modifications to the store through domain operations

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4196?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4196: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Update the pluggable user store SPI to allow for modifications to the store through domain operations > ----------------------------------------------------------------------------------------------------- > > Key: AS7-4196 > URL: https://issues.jboss.org/browse/AS7-4196 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: Realm_Management > Fix For: 8.0.0.Alpha1 > > > This should be something along the lines of 'If the user store implements interface X expose domain management ops to update the store' > This would be optional so either read only stores or fully manageable stores can be used with AS7 realms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-3974) Loopback addresses in the range 127.0.0.2 - 127.255.255.255 should be supported

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-3974?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-3974: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Loopback addresses in the range 127.0.0.2 - 127.255.255.255 should be supported > ------------------------------------------------------------------------------- > > Key: AS7-3974 > URL: https://issues.jboss.org/browse/AS7-3974 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 7.1.0.Final > Environment: Linux Fedora 13 > Reporter: Bela Ban > Fix For: 8.0.0.Alpha1 > > > When starting JBoss like this: "standalone.sh -b 127.0.0.2 -c standalone-ha.xml", the startup fails because 127.0.0.2 cannot be resolved. > However, a loopback address should be recognized even if it doesn't resolve to an interface. The code below works for example: > {code} > InetAddress addr=InetAddress.getByName("127.0.0.5"); > boolean is_loopback=addr.isLoopback(); // should be true > {code} > Loopback addresses are very useful for local testing, ie. starting of multiple JBoss instances on the same box. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-4009) Domain Mode JMX access through the HostController

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4009?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4009: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Domain Mode JMX access through the HostController > ------------------------------------------------- > > Key: AS7-4009 > URL: https://issues.jboss.org/browse/AS7-4009 > Project: Application Server 7 > Issue Type: Task > Components: JMX, Remoting > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: JMX > Fix For: 8.0.0.Alpha1 > > > This task is first to review if this should be considered. > At the moment access to JMX is provided through the remoting connector of each AS instance - this task is to consider if we should actually make it available through the host controller with the host controller acting as a proxy. > The main motivation being to separate management and app traffic. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1941) Messaging deadlocks on AspectManager

by Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1941?page=com.atlassian.jira.... ] Aaron Ogburn edited comment on JBMESSAGING-1941 at 3/5/13 10:23 PM: -------------------------------------------------------------------- Saw another occurrence of this. It's a bit different but fundamentally the same: {noformat} "WorkManager(2)-2" daemon prio=10 tid=0x000000004079b000 nid=0x1f99 waiting for monitor entry [0x00007f2d94a00000] java.lang.Thread.State: BLOCKED (on object monitor) at org.jboss.aop.AspectManager.getAdvisor(AspectManager.java:728) - waiting to lock <0x000000077039a500> (a org.jboss.aop.AspectManager) at org.jboss.jms.client.delegate.ClientConnectionDelegate.<clinit>(ClientConnectionDelegate.java) <-- native classloader lock grabbed at org.jboss.jms.delegate.CreateConnectionResult.read(CreateConnectionResult.java:106) at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateResponse.read(ConnectionFactoryCreateConnectionDelegateResponse.java:71) at org.jboss.jms.wireformat.JMSWireFormat.read(JMSWireFormat.java:298) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedRead(MicroSocketClientInvoker.java:1301) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:907) at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:461) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:167) at org.jboss.remoting.Client.invoke(Client.java:2034) at org.jboss.remoting.Client.invoke(Client.java:877) "WorkManager(2)-3" daemon prio=10 tid=0x00007f2d9811d000 nid=0x2003 in Object.wait() [0x00007f2d94125000] java.lang.Thread.State: RUNNABLE at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:296) <-- waiting for that native cl lock - locked <0x000000077039a500> (a org.jboss.aop.AspectManager) at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:170) at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:108) at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java) at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:91) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:157) {noformat} So we're deadlocked still on the same locks. WorkManager(2)-2 is grabbing the native cl lock then the AspectManager, while WorkManager(2)-3 grabs the AspectManager then the native cl lock. I think the problem is the AspectManager synchronization that was added in JBMESSAGING-797 as a JBM level workaround for JBAOP-360. This JBM level fix was likely fine until synchronization was added in AOP to fix JBAOP-360 as well, and that AOP level fix is in EAP 5 now to conflict with that prior messaging fix. JBAOP-360 resulted in AspectManager.getAdvisor being made a synchronized method and would address the old AOP deadlock issue without JBMESSAGING-797s changes. JBAOP-360 and JBMESSAGING-797 together though causes this new issue as it introduces potential inverse use of the AspectManager and native cl lock. The synchronization in AspectManager has been changed even further beyond JBAOP-360 (by JBAOP-501 & JBAOP-653 for instance), but it seems pretty clear the synchronization we have in place from JBMESSAGING-797 is a relic at this point not necessarily needed any longer with the current AOP branch used on EAP 5. Can we remove the JBMESSAGING-797 changes to address this current deadlock issue? If any AOP deadlock were to crop back up similar to JBMESSAGING-797/JBAOP-360, then I think it should be fixed in AOP. was (Author: aogburn): Saw another occurrence of this. It's a bit different but fundamentally the same: {noformat} "WorkManager(2)-2" daemon prio=10 tid=0x000000004079b000 nid=0x1f99 waiting for monitor entry [0x00007f2d94a00000] java.lang.Thread.State: BLOCKED (on object monitor) at org.jboss.aop.AspectManager.getAdvisor(AspectManager.java:728) - waiting to lock <0x000000077039a500> (a org.jboss.aop.AspectManager) at org.jboss.jms.client.delegate.ClientConnectionDelegate.<clinit>(ClientConnectionDelegate.java) <-- native classloader lock grabbed at org.jboss.jms.delegate.CreateConnectionResult.read(CreateConnectionResult.java:106) at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateResponse.read(ConnectionFactoryCreateConnectionDelegateResponse.java:71) at org.jboss.jms.wireformat.JMSWireFormat.read(JMSWireFormat.java:298) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedRead(MicroSocketClientInvoker.java:1301) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:907) at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:461) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:167) at org.jboss.remoting.Client.invoke(Client.java:2034) at org.jboss.remoting.Client.invoke(Client.java:877) "WorkManager(2)-3" daemon prio=10 tid=0x00007f2d9811d000 nid=0x2003 in Object.wait() [0x00007f2d94125000] java.lang.Thread.State: RUNNABLE at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:296) <-- waiting for that native cl lock - locked <0x000000077039a500> (a org.jboss.aop.AspectManager) at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:170) at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:108) at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java) at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:91) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:157) {noformat} So we're deadlocked still on the same locks. WorkManager(2)-2 is grabbing the native cl lock then the AspectManager, while WorkManager(2)-3 grabs the AspectManager then the native cl lock. I think the problem is the AspectManager synchronization that was added in JBMESSAGING-797 as a JBM level workaround for JBAOP-360. I think this was fine until synchronization was added in AOP to fix JBAOP-360 as well, and that AOP level fix is in EAP 5 now to conflict with that prior messaging fix. JBAOP-360 resulted in AspectManager.getAdvisor being made a synchronized method and would address the issue without JBMESSAGING-797. JBAOP-360 and JBMESSAGING-797 together though causes the issue as it introduces potential inverse use of the AspectManager and native cl lock. The synchronization in AspectManager has been changed even further beyond JBAOP-360 (by JBAOP-501 & JBAOP-653 for instance), but it seems pretty clear the synchronization we have in place from JBMESSAGING-797 is a relic at this point not necessarily needed any longer with the current AOP branch used on EAP 5. Can we remove the JBMESSAGING-797 changes to address this issue? If any AOP deadlock were to crop back up similar to JBMESSAGING-797, then I think it should be fixed in AOP. > Messaging deadlocks on AspectManager > ------------------------------------ > > Key: JBMESSAGING-1941 > URL: https://issues.jboss.org/browse/JBMESSAGING-1941 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.4.8.SP9 > Environment: -JBoss Enterprise Application Platform (EAP) 5 > Reporter: Aaron Ogburn > Attachments: 00779442testpatch.diff > > > Messaging can stall JBoss at start up. The hang occurs as the main thread blocks in different locations in JMS trying to acquire the AspectManager instance lock: > {noformat} > "main" prio=10 tid=0x00007fe69c1e1000 nid=0x3613 waiting for monitor entry [0x00007fe6828e5000] > java.lang.Thread.State: BLOCKED (on object monitor) > at org.jboss.aop.AspectManager.getAdvisor(AspectManager.java:728) > - waiting to lock <0x00000000a5e43e50> (a org.jboss.aop.AspectManager) > at org.jboss.jms.server.endpoint.advised.SessionAdvised.<clinit>(SessionAdvised.java) > at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.createSessionDelegate(ServerConnectionEndpoint.java:273) > - locked <0x00000000a5600f48> (a org.jboss.aop.asintegration.jboss5.ScopedVFSClassLoaderDomain) > at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.createSessionDelegate(ServerConnectionEndpoint.java:229) > {noformat} > Since the main thread is stalled, so too is start up. This lock is always held by another making a similar call like so: > {noformat} > "WorkManager(2)-1" daemon prio=10 tid=0x00007fe62dd96000 nid=0x363e in > Object.wait() [0x00007fe68029a000] > java.lang.Thread.State: RUNNABLE > at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.createSessionDelegate(ServerConnectionEndpoint.java:273) > - locked <0x00000000a5e43e50> (a org.jboss.aop.AspectManager) > at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.createSessionDelegate(ServerConnectionEndpoint.java:229) > {noformat} > The code there at line 273 is simple enough and shouldn't cause a long stall: > {code:title=org.jboss.jms.server.endpoint.ServerConnectionEndpoint.java|borderStyle=solid} > synchronized (AspectManager.instance()) > { > advised = new SessionAdvised(ep); // line 273 > } > {code} > Nonetheless, it does clearly hang at this line as WorkManager(2)-1 never progresses. There's no GC/CPU issues or anything of that nature, but we get a slight in the thread dump as WorkManager(2)-1 is shown to be in Object.wait(). Checking the thread through pstack, we can see the issue. It is waiting in native/JDK level operations required to initialize the SessionAdvised class: > {noformat} > Thread 2 (Thread 0x7fe68029d700 (LWP 13886)): > #0 0x0000003b3e40b43c in pthread_cond_wait@(a)GLIBC_2.3.2 () from /lib64/libpthread.so.0 > #1 0x00007fe6a12d447e in os:latformEvent:ark() () from /opt/app/jvm/jdk1.6.0_38/jre/lib/amd64/server/libjvm.so > #2 0x00007fe6a12c54fa in ObjectMonitor::wait(long, bool, Thread*) () from /opt/app/jvm/jdk1.6.0_38/jre/lib/amd64/server/libjvm.so > #3 0x00007fe6a13ab5f0 in ObjectSynchronizer::waitUninterruptibly(Handle, long, Thread*) () from /opt/app/jvm/jdk1.6.0_38/jre/lib/amd64/server/libjvm.so > #4 0x00007fe6a107115b in instanceKlass::initialize_impl(instanceKlassHandle, Thread*) () from /opt/app/jvm/jdk1.6.0_38/jre/lib/amd64/server/libjvm.so > #5 0x00007fe6a107077a in instanceKlass::initialize(Thread*) () from /opt/app/jvm/jdk1.6.0_38/jre/lib/amd64/server/libjvm.so > #6 0x00007fe6a1097c5c in InterpreterRuntime::_new(JavaThread*, constantPoolOopDesc*, int) () from /opt/app/jvm/jdk1.6.0_38/jre/lib/amd64/server/libjvm.so > {noformat} > These calls are naturally synchronized internally in the JVM so only one thread can proceed through initialization of a class at a given time. Checking for any threads in process of initializing SessionAdvised, we can see only the main thread is. But the main thread is still blocked for the AspectManager lock. > So we have a deadlock here. The main thread holds the initialization lock while waiting for the AspectManager lock, while the WorkManager(2)-1 thread holds the AspectManager lock while waiting for the initialization lock. > The initialization of SessionAdvised is wrapped in the synchronized block so the main thread should not have been able to proceed into the initialization at all without already possessing the AspectManager lock. It locks the ScopedVFSClassLoaderDomain, which extends the AspectManager. This is different from the actual AspectManager though that main tries to lock in the clinit call and that it deadlocks on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-3407) Authorization check for JNDI

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-3407?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-3407: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Authorization check for JNDI > ---------------------------- > > Key: AS7-3407 > URL: https://issues.jboss.org/browse/AS7-3407 > Project: Application Server 7 > Issue Type: Sub-task > Components: Naming, Remoting, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: Authorization > Fix For: 8.0.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-3406) Authorization check for JMX

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-3406?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-3406: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Authorization check for JMX > --------------------------- > > Key: AS7-3406 > URL: https://issues.jboss.org/browse/AS7-3406 > Project: Application Server 7 > Issue Type: Sub-task > Components: JMX, Remoting, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: Authorization > Fix For: 8.0.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 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 2013