February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-1833) CLI usability: operations that shutdown the server-side management interface result in "Communication error"

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-1833?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-1833: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> made a comment on [bug 914817|https://bugzilla.redhat.com/show_bug.cgi?id=914817] Addition of high-level "reload" and "shutdown" commands to the CLI that better deal with the fact that these commands result in a break in communication with the server process. > CLI usability: operations that shutdown the server-side management interface result in "Communication error" > ------------------------------------------------------------------------------------------------------------ > > Key: AS7-1833 > URL: https://issues.jboss.org/browse/AS7-1833 > Project: Application Server 7 > Issue Type: Enhancement > Components: CLI > Affects Versions: 7.0.0.Final, 7.0.1.Final > Reporter: Radoslav Husar > Assignee: Alexey Loubyansky > Priority: Critical > Labels: eap6-ux > Fix For: 7.2.0.Alpha1 > > > If you shutdown the server, you get an error: > {code} > [standalone@localhost:9999 /] :shutdown > Communication error: Channel closed > Closed connection to localhost:9999 > {code} > Even though its considered by this comment clean - https://issues.jboss.org/browse/AS7-689?focusedCommentId=12614756&page=co... - I is not really clean as you get an error but termination of the channel can be anticipated. Users might be confused now knowing if its an actual error or not. For example take a look at SSH. > The same basic issue exists for the :reload operation. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBBUILD-726) org.apache.maven:maven-plugin-api:jar:2.1.0-M2-SNAPSHOT has a snapshot parent org.apache.maven:maven-parent:pom:11-SNAPSHOT that doesn't exist anymore

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/JBBUILD-726?page=com.atlassian.jira.plugi... ] Paul Gier commented on JBBUILD-726: ----------------------------------- It looks like the maven pom (maven-2.1.0-M2-20090213.232933-1.pom), is proxied from the apache snapshots repository (http://repository.apache.org/snapshots/). You can check that by adding "?describe" to the end of the URL and check the "originatingRepositoryId" field. https://repository.jboss.org/nexus/content/groups/public/org/apache/maven... I could purge the proxied artifacts from the jboss repository, but the problem would re-appear with the next request. The artifacts probably need to be cleaned up in the Apache snapshots repository. Can these artifacts be updated in the build so that released versions are used? > org.apache.maven:maven-plugin-api:jar:2.1.0-M2-SNAPSHOT has a snapshot parent org.apache.maven:maven-parent:pom:11-SNAPSHOT that doesn't exist anymore > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBBUILD-726 > URL: https://issues.jboss.org/browse/JBBUILD-726 > Project: JBoss Build System > Issue Type: Bug > Components: Artifact Repositories > Reporter: Marek Schmidt > Assignee: Paul Gier > Fix For: Build Support 2013 > > > Hello, > I am getting this error in weld examples, with the jboss-public repository enabled: > mvn glassfish:start-domain > ... > {noformat} > [ERROR] Failed to execute goal org.glassfish.maven.plugin:maven-glassfish-plugin:2.1:start-domain (default-cli) on project weld-jsf-numberguess: Execution default-cli of goal org.glassfish.maven.plugin:maven-glassfish-plugin:2.1:start-domain failed: Plugin org.glassfish.maven.plugin:maven-glassfish-plugin:2.1 or one of its dependencies could not be resolved: Failed to collect dependencies for org.glassfish.maven.plugin:maven-glassfish-plugin:jar:2.1 (): Failed to read artifact descriptor for org.apache.maven:maven-plugin-api:jar:2.1.0-M2-SNAPSHOT: Failure to find org.apache.maven:maven-parent:pom:11-SNAPSHOT in http://repository.jboss.org/nexus/content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced -> [Help 1] > {noformat} > The problem seems to be that > https://repository.jboss.org/nexus/content/groups/public/org/apache/maven... > has a parent > https://repository.jboss.org/nexus/content/groups/public/org/apache/maven... > which doesn't exist anymore in the jboss public repo. > Snapshots which depends on snapshots that have already been removed, should probably be removed also. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBBUILD-726) org.apache.maven:maven-plugin-api:jar:2.1.0-M2-SNAPSHOT has a snapshot parent org.apache.maven:maven-parent:pom:11-SNAPSHOT that doesn't exist anymore

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/JBBUILD-726?page=com.atlassian.jira.plugi... ] Paul Gier updated JBBUILD-726: ------------------------------ Fix Version/s: Build Support 2013 > org.apache.maven:maven-plugin-api:jar:2.1.0-M2-SNAPSHOT has a snapshot parent org.apache.maven:maven-parent:pom:11-SNAPSHOT that doesn't exist anymore > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBBUILD-726 > URL: https://issues.jboss.org/browse/JBBUILD-726 > Project: JBoss Build System > Issue Type: Bug > Components: Artifact Repositories > Reporter: Marek Schmidt > Assignee: Paul Gier > Fix For: Build Support 2013 > > > Hello, > I am getting this error in weld examples, with the jboss-public repository enabled: > mvn glassfish:start-domain > ... > {noformat} > [ERROR] Failed to execute goal org.glassfish.maven.plugin:maven-glassfish-plugin:2.1:start-domain (default-cli) on project weld-jsf-numberguess: Execution default-cli of goal org.glassfish.maven.plugin:maven-glassfish-plugin:2.1:start-domain failed: Plugin org.glassfish.maven.plugin:maven-glassfish-plugin:2.1 or one of its dependencies could not be resolved: Failed to collect dependencies for org.glassfish.maven.plugin:maven-glassfish-plugin:jar:2.1 (): Failed to read artifact descriptor for org.apache.maven:maven-plugin-api:jar:2.1.0-M2-SNAPSHOT: Failure to find org.apache.maven:maven-parent:pom:11-SNAPSHOT in http://repository.jboss.org/nexus/content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced -> [Help 1] > {noformat} > The problem seems to be that > https://repository.jboss.org/nexus/content/groups/public/org/apache/maven... > has a parent > https://repository.jboss.org/nexus/content/groups/public/org/apache/maven... > which doesn't exist anymore in the jboss public repo. > Snapshots which depends on snapshots that have already been removed, should probably be removed also. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-93) Create document that correlates versions of the jboss-javaee-6.0 and jboss-javaee-web-6.0 to JBAS 6 and AS 7 releases

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-93?page=com.atlassian.jira.plugin.sy... ] Shelly McGowan resolved JBEE-93. -------------------------------- Fix Version/s: JavaEE 6 Spec APIs 3.0.2.Final (was: No Release) Resolution: Done Considering this issue Resolved. The JDF site, noted above, shows this information. With the upcoming EE 7 work, early access versions of the APIs (and EE7 BOMs) will be provided when possible. > Create document that correlates versions of the jboss-javaee-6.0 and jboss-javaee-web-6.0 to JBAS 6 and AS 7 releases > --------------------------------------------------------------------------------------------------------------------- > > Key: JBEE-93 > URL: https://issues.jboss.org/browse/JBEE-93 > Project: JBoss JavaEE Spec APIs > Issue Type: Enhancement > Components: general > Reporter: Shelly McGowan > Assignee: Shelly McGowan > Fix For: JavaEE 6 Spec APIs 3.0.2.Final > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-105) Create a JBoss version of the JavaBeans activation framework (javax.activation) API

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-105?page=com.atlassian.jira.plugin.s... ] Shelly McGowan reassigned JBEE-105: ----------------------------------- Assignee: Shelly McGowan > Create a JBoss version of the JavaBeans activation framework (javax.activation) API > ----------------------------------------------------------------------------------- > > Key: JBEE-105 > URL: https://issues.jboss.org/browse/JBEE-105 > Project: JBoss JavaEE Spec APIs > Issue Type: Feature Request > Components: general > Reporter: Paul Gier > Assignee: Shelly McGowan > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > > The JBoss jaxr-api jar current depends on the javax.activation package. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4807) Add LDAP authorization for security realms.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4807?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4807: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Add LDAP authorization for security realms. > ------------------------------------------- > > Key: AS7-4807 > URL: https://issues.jboss.org/browse/AS7-4807 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Flemming Harms > Fix For: 8.0.0.Alpha1 > > > Add support for loading roles from LDAP in security 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6453) ejb-security-interceptors quickstart has several issues

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6453?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6453: --------------------------------------- This is merged so it looks like it should be resolved. I'm not sure about the Fix Version. > ejb-security-interceptors quickstart has several issues > ------------------------------------------------------- > > Key: AS7-6453 > URL: https://issues.jboss.org/browse/AS7-6453 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Reporter: Josef Cacek > Assignee: Darran Lofthouse > > The ejb-security-interceptors quickstarts should be improved a little bit: > * root element of the {{jboss-ejb3.xml}} deployment descriptor should be {{<ejb-jar>}} (c.f. AS7-6452) > * DelegationLoginModule doesn't need the callbackHandler member variable, the parrent class holds it ({{AbstractServerLoginModule}}) > * possible {{EJBException}} from the {{invocationContext.proceed()}} call is not correctly propagated in the {{ServerSecurityInterceptor}} > The correct part of ServerSecurityInterceptor code should look like: > {code} > try { > if (desiredUser != null && connectionUser != null > && (desiredUser.getName().equals(connectionUser.getName()) == false)) { > // The final part of this check is to verify that the change does actually indicate a change in user. > try { > // We have been requested to switch user and have successfully identified the user from the connection > // so now we attempt the switch. > cachedSecurityContext = SecurityActions.securityContextSetPrincipalInfo(desiredUser, > new OuterUserCredential(connectionUser)); > // keep track that we switched the security context > contextSet = true; > SecurityActions.remotingContextClear(); > } catch (Exception e) { > logger.error("Failed to switch security context for user", e); > // Don't propagate the exception stacktrace back to the client for security reasons > throw new EJBAccessException("Unable to attempt switching of user."); > } > } > return invocationContext.proceed(); > } finally { > // switch back to original security context > if (contextSet) { > SecurityActions.securityContextSet(cachedSecurityContext); > } > } > {code} -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6232) DefaultAuthenticationCacheFactory should not use internal Infinispan classes

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/AS7-6232?page=com.atlassian.jira.plugin.s... ] Paul Ferraro commented on AS7-6232: ----------------------------------- A "correct" implemention of DefaultAuthenticationCacheFactory would use a cache defined by the infinispan subsystem itself and injection via the CacheService (which returns an ConcurrentMap implementation). The DefaultAuthenticationCacheFactory would register a cache listener that listens to the relevant eviction events. That way we also correctly handle the lifecycle of the cache and its cache manager. I'm going to reassign this to the clustering team. > DefaultAuthenticationCacheFactory should not use internal Infinispan classes > ---------------------------------------------------------------------------- > > Key: AS7-6232 > URL: https://issues.jboss.org/browse/AS7-6232 > Project: Application Server 7 > Issue Type: Bug > Components: Security > Affects Versions: 7.1.3.Final (EAP) > Reporter: Tristan Tarrant > Assignee: Anil Saldhana > > The DefaultAuthenticationCacheFactory class (and the AuthenticationCacheEvictionListener class) use internal Infinispan classes which are subject to change without API stability guarantees. The code should be rewritten to use an Infinispan cache instead. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6232) DefaultAuthenticationCacheFactory should not use internal Infinispan classes

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/AS7-6232?page=com.atlassian.jira.plugin.s... ] Paul Ferraro reassigned AS7-6232: --------------------------------- Assignee: Paul Ferraro (was: Anil Saldhana) > DefaultAuthenticationCacheFactory should not use internal Infinispan classes > ---------------------------------------------------------------------------- > > Key: AS7-6232 > URL: https://issues.jboss.org/browse/AS7-6232 > Project: Application Server 7 > Issue Type: Bug > Components: Security > Affects Versions: 7.1.3.Final (EAP) > Reporter: Tristan Tarrant > Assignee: Paul Ferraro > > The DefaultAuthenticationCacheFactory class (and the AuthenticationCacheEvictionListener class) use internal Infinispan classes which are subject to change without API stability guarantees. The code should be rewritten to use an Infinispan cache instead. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6612) Remove JAXR support

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-6612?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on AS7-6612: ---------------------------------- This was just okayed. > Remove JAXR support > ------------------- > > Key: AS7-6612 > URL: https://issues.jboss.org/browse/AS7-6612 > Project: Application Server 7 > Issue Type: Sub-task > Components: JAXR > Reporter: David Lloyd > Fix For: 8.0.0.Alpha1 > > > ...Just as soon as [~jason.greene] verifies that we should. -- 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, 2 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 February 2013