March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2616) Allow AS7 Arquillian container to pass credentials/securely authenticate

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-2616?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-2616: --------------------------------------- That's from standalone.xml. > Allow AS7 Arquillian container to pass credentials/securely authenticate > ------------------------------------------------------------------------ > > Key: AS7-2616 > URL: https://issues.jboss.org/browse/AS7-2616 > Project: Application Server 7 > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 7.1.0.Alpha1 > Reporter: Karel Piwko > Assignee: Aslak Knutsen > Priority: Critical > Labels: arq_qe_blocker > Fix For: 7.1.0.Final > > > As AS7 is going the secure way, all the tooling including Arquillian should be able to access secured management APIs. > An example how this can be implemented is present here: > https://github.com/jbossas/jboss-as-maven-plugin/commit/8dd544a51ce0bf23b... > We definitely need a way how to securely access AS7, either by user/name pair or by a more secure means. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6784) StabilityMonitors used in AS code base are leaking services

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6784?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-6784: ----------------------------- Description: This issue causes that deployment are never un-deployed and GCd which causes OOM in our testsuite. Currently most prominent issue is JSF2.2 upgrade that fails with OOM because of this. Result is that JSF2.2 support cannot be added to master as it would always fail testsuite. was: This issue causes that deployment are never un-deployed and GCd which causes OOM in our testsuite. Currently most prominent issue is JSF2.2 upgrade that fails with OOM because of this. > StabilityMonitors used in AS code base are leaking services > ----------------------------------------------------------- > > Key: AS7-6784 > URL: https://issues.jboss.org/browse/AS7-6784 > Project: Application Server 7 > Issue Type: Bug > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Blocker > Fix For: 8.0.0.Alpha1 > > > This issue causes that deployment are never un-deployed and GCd which causes OOM in our testsuite. > Currently most prominent issue is JSF2.2 upgrade that fails with OOM because of this. > Result is that JSF2.2 support cannot be added to master as it would always fail testsuite. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6784) StabilityMonitors used in AS code base are leaking services

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6784?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-6784: ----------------------------- Description: This issue causes that deployment are never un-deployed and GCd which causes OOM in our testsuite. Currently most prominent issue is JSF2.2 upgrade that fails with OOM because of this. > StabilityMonitors used in AS code base are leaking services > ----------------------------------------------------------- > > Key: AS7-6784 > URL: https://issues.jboss.org/browse/AS7-6784 > Project: Application Server 7 > Issue Type: Bug > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Blocker > Fix For: 8.0.0.Alpha1 > > > This issue causes that deployment are never un-deployed and GCd which causes OOM in our testsuite. > Currently most prominent issue is JSF2.2 upgrade that fails with OOM because of this. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6784) StabilityMonitors used in AS code base are leaking services

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6784?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-6784: ----------------------------- Priority: Blocker (was: Major) > StabilityMonitors used in AS code base are leaking services > ----------------------------------------------------------- > > Key: AS7-6784 > URL: https://issues.jboss.org/browse/AS7-6784 > Project: Application Server 7 > Issue Type: Bug > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Blocker > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-2616) Allow AS7 Arquillian container to pass credentials/securely authenticate

by Marco Rietveld (JIRA)

[ https://issues.jboss.org/browse/AS7-2616?page=com.atlassian.jira.plugin.s... ] Marco Rietveld commented on AS7-2616: ------------------------------------- More information on the workaround (which file should the {{<management-interfaces>}} block be placed in?) would be great. > Allow AS7 Arquillian container to pass credentials/securely authenticate > ------------------------------------------------------------------------ > > Key: AS7-2616 > URL: https://issues.jboss.org/browse/AS7-2616 > Project: Application Server 7 > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 7.1.0.Alpha1 > Reporter: Karel Piwko > Assignee: Aslak Knutsen > Priority: Critical > Labels: arq_qe_blocker > Fix For: 7.1.0.Final > > > As AS7 is going the secure way, all the tooling including Arquillian should be able to access secured management APIs. > An example how this can be implemented is present here: > https://github.com/jbossas/jboss-as-maven-plugin/commit/8dd544a51ce0bf23b... > We definitely need a way how to securely access AS7, either by user/name pair or by a more secure means. -- 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, 3 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 resolved AS7-6681. ------------------------------ Fix Version/s: 8.0.0.Alpha1 Resolution: Done > 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 > Fix For: 8.0.0.Alpha1 > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6681) ClusteredSingleSignOn ClassCastException with non-distributable apps

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6681?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6681: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 920367|https://bugzilla.redhat.com/show_bug.cgi?id=920367] from NEW to POST > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-5547) Deployment fails when Dependencies is empty in a jars manifest

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-5547?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-5547. --------------------------------- Fix Version/s: 8.0.0.Alpha1 Resolution: Done > Deployment fails when Dependencies is empty in a jars manifest > -------------------------------------------------------------- > > Key: AS7-5547 > URL: https://issues.jboss.org/browse/AS7-5547 > Project: Application Server 7 > Issue Type: Enhancement > Affects Versions: 7.1.1.Final > Reporter: Gábor Farkas > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > Attachments: empty-manifest.ear > > > I have a WAR, which produces the following error on deployment: > Caused by: java.lang.IllegalArgumentException: Empty module specification > at org.jboss.modules.ModuleIdentifier.fromString(ModuleIdentifier.java:169) [jboss-modules.jar:1.1.1.GA] > at org.jboss.as.server.deployment.module.ManifestDependencyProcessor.deploy(ManifestDependencyProcessor.java:83) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > ... 5 more > I found that my WAR contains a jar in WEB-INF/lib that has empty dependencies defined in its manifest. More exactly it's "Dependencies: ", so the colon is followed by a space character before the new line characters. The ManifestDependencyProcessor parses this as one dependency, the name of which is the empty string. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6780) Default config is not using most up to date schemas

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6780?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-6780. --------------------------------- Fix Version/s: 8.0.0.Alpha1 Resolution: Done > Default config is not using most up to date schemas > --------------------------------------------------- > > Key: AS7-6780 > URL: https://issues.jboss.org/browse/AS7-6780 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > We also need to add a test to prevent this from happening in future -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6782) JAX-RS does not work with EJB's with a non-default name

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6782?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-6782. --------------------------------- Resolution: Done > JAX-RS does not work with EJB's with a non-default name > ------------------------------------------------------- > > Key: AS7-6782 > URL: https://issues.jboss.org/browse/AS7-6782 > Project: Application Server 7 > Issue Type: Bug > Components: REST > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > 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, 3 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