March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6615) Invalid definition for HC root resource remote domain controller

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6615?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6615: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Invalid definition for HC root resource remote domain controller > ---------------------------------------------------------------- > > Key: AS7-6615 > URL: https://issues.jboss.org/browse/AS7-6615 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.2.0.Alpha1 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > HostResourceDefinition.DC_REMOTE does not include the security-realm and username fields. -- 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-5794) JMX over remoting pollutes query results with ModelController objects

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5794?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5794: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > JMX over remoting pollutes query results with ModelController objects > --------------------------------------------------------------------- > > Key: AS7-5794 > URL: https://issues.jboss.org/browse/AS7-5794 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, JMX > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tristan Tarrant > Assignee: Kabir Khan > Fix For: 8.0.0.Alpha1 > > > When issuing MBean queries over JMX remoting, the AS is returning a list of org.jboss.as.controller.ModelController objects in addition to those matching the query. > This is a transcript of a chat we had about it on IRC: > Oct 15 14:51:46 <ttarrant> darranl, if I issue a jmx query over jmx-remoting I get many more objects than expected > Oct 15 14:51:55 <ttarrant> darranl, i.e. ones that do not match the query > Oct 15 14:52:09 <ttarrant> darranl, this is with 7.1.x > Oct 15 14:52:57 <ttarrant> darranl, this works if I use the standard JMX over RMI > Oct 15 14:53:08 --> fnasser (~fnasser(a)CPE602ad07ab726-CM602ad07ab723.cpe.net.cable.rogers.com) has joined #jboss-as7 > Oct 15 14:53:09 <-- fnasser has quit (Changing host) > Oct 15 14:53:09 --> fnasser (~fnasser@redhat/jboss/fnasser) has joined #jboss-as7 > Oct 15 14:53:09 --- ChanServ gives voice to fnasser > Oct 15 14:53:16 <ttarrant> darranl, do you just pass the query the the mbeanserver ? > Oct 15 14:53:39 <darranl> ttarrant: what kind of objects? within AS7 I think there are two things that could affec > t this 1 - The Remoting JMX protocol, 2 - The domain management representation over JMX > Oct 15 14:53:54 <darranl> For #1 yes we just pass it to the MBEanServer and return whatever it returns > Oct 15 14:54:04 <darranl> if it was a Remoting JMX bug maybe we are messing up the query > Oct 15 14:54:16 <ttarrant> darranl, the query is as follows: *:type=CacheManager,component=Interpreter,name=* > Oct 15 14:54:16 <darranl> But not sure if #2 could be the reason more is getting added > Oct 15 14:54:32 <ttarrant> darranl, wait a sec > Oct 15 14:54:57 <darranl> ttarrant: I would suggest getting a Jira raised and assigned to me, I can verify if it i > s a remoting jmx issue or pass over if it is a domain management integration issue > Oct 15 14:55:20 <darranl> regardless of where it is happenign it sounds like you may have discovered a bug > Oct 15 14:56:23 <ttarrant> darranl, let me get the objects it's returning > Oct 15 14:56:39 <darranl> ttarrant: when you enable the RMI approach you bypass both Remoting JMX AND the domain m > anagement integration > Oct 15 14:56:42 <darranl> ok > Oct 15 15:26:08 <ttarrant> darranl, ok, my query actually returns the object I queried for and a bunch of org.jboss.as.controller.ModelController (one for each subsystem) > Oct 15 15:51:24 <darranl> ttarrant: ok that does then sound like it is the domain management integration that is 'poluting' the query results > Oct 15 15:51:53 <darranl> ttarrant: going RMI was just bypassing that as well > Oct 15 15:52:05 <ttarrant> darranl, shall I open a Jira ? > Oct 15 15:52:34 <ttarrant> darranl, I work around the issue by manually filtering the returned objects based on class name > Oct 15 15:53:23 <darranl> ttarrant: it would probably be one for kkhan to look into, think he is just back today so may be worth the Jira so he can have a look once he has caught back up ;-) -- 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-4894) HA Singleton deployer for applications

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4894?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4894: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > HA Singleton deployer for applications > -------------------------------------- > > Key: AS7-4894 > URL: https://issues.jboss.org/browse/AS7-4894 > Project: Application Server 7 > Issue Type: Feature Request > Components: Clustering, Domain Management > Reporter: Wolf-Dieter Fink > Assignee: Paul Ferraro > Labels: deployers, hasingleton > Fix For: 8.0.0.Alpha1 > > > A HASingleton deployer should be provided in standalone and domain mode. > To be able to migrate such singleton applications from former AS versions. -- 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-370) Add Notification support to the domain management API

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-370?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry updated AS7-370: --------------------------------- Fix Version/s: (was: 7.3.0.Alpha1) > Add Notification support to the domain management API > ----------------------------------------------------- > > Key: AS7-370 > URL: https://issues.jboss.org/browse/AS7-370 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > Management resource should be able to emit notifications; clients can register listeners. -- 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-3694) Allow management client to associate metadata with DeploymentUnit

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-3694?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-3694: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Allow management client to associate metadata with DeploymentUnit > ----------------------------------------------------------------- > > Key: AS7-3694 > URL: https://issues.jboss.org/browse/AS7-3694 > Project: Application Server 7 > Issue Type: Feature Request > Components: OSGi, Server > Reporter: Thomas Diesler > Assignee: Brian Stansberry > Priority: Critical > Fix For: 8.0.0.Alpha1 > > > Currently there is no way to pass some metadata through the deployment API such that they could show up with the DU. > As a client I'd like to say autostart=false and in my DUP I'd like to pick that up and not start a deployment (i.e. a bundle) automatically > Generally it should be possible for the client to set some properties for the deployment in a generic way such that they get associated with the DeploymentUnit > For an OSGi deployment it would be necessary to be able to define that start behaviour and the start level. -- 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-4460) Speed up clustering test suite using ARQ custom containers

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4460?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4460: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.2.0.Alpha1) > Speed up clustering test suite using ARQ custom containers > ---------------------------------------------------------- > > Key: AS7-4460 > URL: https://issues.jboss.org/browse/AS7-4460 > Project: Application Server 7 > Issue Type: Feature Request > Components: Clustering, Test Suite > Affects Versions: 7.1.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Leveraging ARQ-850. -- 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-6681) ClusteredSingleSignOn ClassCastException with non-distributable apps

by Dennis Reed (JIRA)

[ https://issues.jboss.org/browse/AS7-6681?page=com.atlassian.jira.plugin.s... ] Dennis Reed edited comment on AS7-6681 at 3/5/13 6:53 PM: ---------------------------------------------------------- This issue was introduced in AS7-5144. was (Author: dereed): This was added in EAP 6 to override the options sent to session.expire(). If the session is not a ClusteredSession, it should just fall-back to calling session.expire(). > ClusteredSingleSignOn ClassCastException with non-distributable apps > -------------------------------------------------------------------- > > Key: AS7-6681 > URL: https://issues.jboss.org/browse/AS7-6681 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.1.3.Final (EAP) > Reporter: Dennis Reed > Assignee: Dennis Reed > Attachments: test.war > > > When ClusteredSingleSignOn is enabled, and a user has an active session in a non-distributable web application, invalidating any session in the same SSO from a different AS instance in the cluster causes the following exception (logged numerous times in various ways): > ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (OOB-20,null) ISPN000136: Execution error: org.infinispan.CacheException: Caught exception [java.lang.ClassCastException] while invoking method [public void org.jboss.as.clustering.web.sso.infinispan.SSOClusterManager.cacheEntryRemoved(org.infinispan.notifications.cachelistener.event.CacheEntryRemovedEvent)] on listener instance: org.jboss.as.clustering.web.sso.infinispan.SSOClusterManager@28e13c84 > ... > Caused by: java.lang.ClassCastException: org.apache.catalina.session.StandardSession cannot be cast to org.jboss.as.web.session.ClusteredSession > at org.jboss.as.web.sso.ClusteredSingleSignOn.deregisterLocal(ClusteredSingleSignOn.java:523) [jboss-as-web-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4] > ... -- 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-6681) ClusteredSingleSignOn ClassCastException with non-distributable apps

by Dennis Reed (JIRA)

[ https://issues.jboss.org/browse/AS7-6681?page=com.atlassian.jira.plugin.s... ] Dennis Reed commented on AS7-6681: ---------------------------------- This was added in EAP 6 to override the options sent to session.expire(). If the session is not a ClusteredSession, it should just fall-back to calling session.expire(). > ClusteredSingleSignOn ClassCastException with non-distributable apps > -------------------------------------------------------------------- > > Key: AS7-6681 > URL: https://issues.jboss.org/browse/AS7-6681 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.1.3.Final (EAP) > Reporter: Dennis Reed > Assignee: Dennis Reed > Attachments: test.war > > > When ClusteredSingleSignOn is enabled, and a user has an active session in a non-distributable web application, invalidating any session in the same SSO from a different AS instance in the cluster causes the following exception (logged numerous times in various ways): > ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (OOB-20,null) ISPN000136: Execution error: org.infinispan.CacheException: Caught exception [java.lang.ClassCastException] while invoking method [public void org.jboss.as.clustering.web.sso.infinispan.SSOClusterManager.cacheEntryRemoved(org.infinispan.notifications.cachelistener.event.CacheEntryRemovedEvent)] on listener instance: org.jboss.as.clustering.web.sso.infinispan.SSOClusterManager@28e13c84 > ... > Caused by: java.lang.ClassCastException: org.apache.catalina.session.StandardSession cannot be cast to org.jboss.as.web.session.ClusteredSession > at org.jboss.as.web.sso.ClusteredSingleSignOn.deregisterLocal(ClusteredSingleSignOn.java:523) [jboss-as-web-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4] > ... -- 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-6681) ClusteredSingleSignOn ClassCastException with non-distributable apps

by Dennis Reed (JIRA)

[ https://issues.jboss.org/browse/AS7-6681?page=com.atlassian.jira.plugin.s... ] Dennis Reed commented on AS7-6681: ---------------------------------- The bug is in the following line in ClusteredSingleSignOn#deregisterLocal: // Invalidate this session, but do not propagate to other nodes ClusteredSession<OutgoingDistributableSessionData> clusteredSession = (ClusteredSession<OutgoingDistributableSessionData>) session ; It incorrectly assumes every session tied to the SSO is a ClusteredSession, which is not true for non-distributable applications. > ClusteredSingleSignOn ClassCastException with non-distributable apps > -------------------------------------------------------------------- > > Key: AS7-6681 > URL: https://issues.jboss.org/browse/AS7-6681 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.1.3.Final (EAP) > Reporter: Dennis Reed > Assignee: Dennis Reed > Attachments: test.war > > > When ClusteredSingleSignOn is enabled, and a user has an active session in a non-distributable web application, invalidating any session in the same SSO from a different AS instance in the cluster causes the following exception (logged numerous times in various ways): > ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (OOB-20,null) ISPN000136: Execution error: org.infinispan.CacheException: Caught exception [java.lang.ClassCastException] while invoking method [public void org.jboss.as.clustering.web.sso.infinispan.SSOClusterManager.cacheEntryRemoved(org.infinispan.notifications.cachelistener.event.CacheEntryRemovedEvent)] on listener instance: org.jboss.as.clustering.web.sso.infinispan.SSOClusterManager@28e13c84 > ... > Caused by: java.lang.ClassCastException: org.apache.catalina.session.StandardSession cannot be cast to org.jboss.as.web.session.ClusteredSession > at org.jboss.as.web.sso.ClusteredSingleSignOn.deregisterLocal(ClusteredSingleSignOn.java:523) [jboss-as-web-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4] > ... -- 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-6681) ClusteredSingleSignOn ClassCastException with non-distributable apps

by Dennis Reed (JIRA)

[ https://issues.jboss.org/browse/AS7-6681?page=com.atlassian.jira.plugin.s... ] Dennis Reed edited comment on AS7-6681 at 3/5/13 6:41 PM: ---------------------------------------------------------- The bug is in the following line in ClusteredSingleSignOn#deregisterLocal: ClusteredSession<OutgoingDistributableSessionData> clusteredSession = (ClusteredSession<OutgoingDistributableSessionData>) session ; It incorrectly assumes every session tied to the SSO is a ClusteredSession, which is not true for non-distributable applications. was (Author: dereed): The bug is in the following line in ClusteredSingleSignOn#deregisterLocal: // Invalidate this session, but do not propagate to other nodes ClusteredSession<OutgoingDistributableSessionData> clusteredSession = (ClusteredSession<OutgoingDistributableSessionData>) session ; It incorrectly assumes every session tied to the SSO is a ClusteredSession, which is not true for non-distributable applications. > ClusteredSingleSignOn ClassCastException with non-distributable apps > -------------------------------------------------------------------- > > Key: AS7-6681 > URL: https://issues.jboss.org/browse/AS7-6681 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.1.3.Final (EAP) > Reporter: Dennis Reed > Assignee: Dennis Reed > Attachments: test.war > > > When ClusteredSingleSignOn is enabled, and a user has an active session in a non-distributable web application, invalidating any session in the same SSO from a different AS instance in the cluster causes the following exception (logged numerous times in various ways): > ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (OOB-20,null) ISPN000136: Execution error: org.infinispan.CacheException: Caught exception [java.lang.ClassCastException] while invoking method [public void org.jboss.as.clustering.web.sso.infinispan.SSOClusterManager.cacheEntryRemoved(org.infinispan.notifications.cachelistener.event.CacheEntryRemovedEvent)] on listener instance: org.jboss.as.clustering.web.sso.infinispan.SSOClusterManager@28e13c84 > ... > Caused by: java.lang.ClassCastException: org.apache.catalina.session.StandardSession cannot be cast to org.jboss.as.web.session.ClusteredSession > at org.jboss.as.web.sso.ClusteredSingleSignOn.deregisterLocal(ClusteredSingleSignOn.java:523) [jboss-as-web-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4] > ... -- 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