March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3378) Allow local mechanism to be enabled or disabled on a realm.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3378: ------------------------------------- Summary: Allow local mechanism to be enabled or disabled on a realm. Key: AS7-3378 URL: https://issues.jboss.org/browse/AS7-3378 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Final It should be possible to switch off the local mechanism - to achieve this it may be easier to add it to the <authentication> element so it can be omitted - i.e. the authentication element will now have multiple 'stores' defined and we will support the authentication mechanism of each of them, duplicate mechanisms will result in a WARN and the subsequent stores omitted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
6
0 / 0

[JBoss JIRA] (AS7-2548) Decide what to do with the sasl child of connector in the remoting subsystem

by Kabir Khan (Created) (JIRA)

Decide what to do with the sasl child of connector in the remoting subsystem ---------------------------------------------------------------------------- Key: AS7-2548 URL: https://issues.jboss.org/browse/AS7-2548 Project: Application Server 7 Issue Type: Feature Request Reporter: Kabir Khan Assignee: Darran Lofthouse -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
5
0 / 0

[JBoss JIRA] (AS7-3423) Handle deployments with a persistence provider and javax.persistence classes

by Scott Marlow (JIRA)

Scott Marlow created AS7-3423: --------------------------------- Summary: Handle deployments with a persistence provider and javax.persistence classes Key: AS7-3423 URL: https://issues.jboss.org/browse/AS7-3423 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.2.0.Alpha1 If an application deployment contains its own copy of a persistence provider and its own of the javax.persistence classes, deploy it as an application managed JPA application (no container managed JPA support feature are expected to be used). 1. initialize the application copy of the javax.persistence.Persistence class by setting an application deployment level PersistenceProviderResolver (via javax.persistence.spi.PersistenceProviderResolverHolder.PersistenceProviderResolver()) that would know about the persistence provider that is bundled. 2. don't inject the javax.persistence module into the deployment. 3. add a unit test that bundles a persistence provider, javax.persistence classes and uses javax.persistence.Persistence.createEntityManagerFactory(String persistenceUnitName). https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might be worth looking at when this jira is worked around. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
12
0 / 0

[JBoss JIRA] Created: (AS7-1779) Manage infinispan through console

by Heiko Braun (JIRA)

Manage infinispan through console --------------------------------- Key: AS7-1779 URL: https://issues.jboss.org/browse/AS7-1779 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
9
0 / 0

[JBoss JIRA] Created: (JGRP-1313) RELAY: bridge multiple sites

by Bela Ban (JIRA)

RELAY: bridge multiple sites ---------------------------- Key: JGRP-1313 URL: https://issues.jboss.org/browse/JGRP-1313 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.1 The current RELAY (2.12.1) bridges only 2 local clusters (sites). Think about ways to bridge multiple sites, e.g. in a star topology (all sites bridge to a central site, but not to each other), or daisy chaining (a site A bridges to site B, which bridges to site C etc) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
2
0 / 0

[JBoss JIRA] (AS7-3983) I have deployed a ejb3 in jboss7.1 server. I'm getting CommunicationException

by narendra reddy (JIRA)

narendra reddy created AS7-3983: ----------------------------------- Summary: I have deployed a ejb3 in jboss7.1 server. I'm getting CommunicationException Key: AS7-3983 URL: https://issues.jboss.org/browse/AS7-3983 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.0.Final Environment: Windows environment Reporter: narendra reddy Assignee: jaikiran pai Fix For: 7.1.1.Final Dear friends, javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1452) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:597) Please help us, would appreciated. Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] (AS7-3046) Can't pass authentication step to Web Admin console if two already created users has the same login name

by Pavel Janousek (JIRA)

[ https://issues.jboss.org/browse/AS7-3046?page=com.atlassian.jira.plugin.s... ] Pavel Janousek closed AS7-3046. ------------------------------- It isn't able to have two users in this case now, closing as verified. > Can't pass authentication step to Web Admin console if two already created users has the same login name > -------------------------------------------------------------------------------------------------------- > > Key: AS7-3046 > URL: https://issues.jboss.org/browse/AS7-3046 > Project: Application Server 7 > Issue Type: Bug > Components: Console > Affects Versions: 7.1.0.Beta1b > Reporter: Pavel Janousek > Assignee: Darran Lofthouse > Priority: Blocker > > One part of this issue is due JBPAPP-7760. There isn't any check if user already exists when new one is creating. > Next part is new - I think is it useful and meaningful if we can create two users with the same user name but each belongs to different Realm, but in this case pass authentication dialog in Web Admin console isn't possible even for user belongs to ManagementRealm realm. > Also when I've created two identical users (both under ManagementRealm, it is possible now due to JBPAPP-7760), no one can pass the same step as above even they have the same password. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3044) bin/add-user.sh allows create two identical users

by Pavel Janousek (JIRA)

[ https://issues.jboss.org/browse/AS7-3044?page=com.atlassian.jira.plugin.s... ] Pavel Janousek closed AS7-3044. ------------------------------- Verified, fixed... > bin/add-user.sh allows create two identical users > ------------------------------------------------- > > Key: AS7-3044 > URL: https://issues.jboss.org/browse/AS7-3044 > Project: Application Server 7 > Issue Type: Bug > Components: Security > Affects Versions: 7.1.0.Beta1b > Reporter: Pavel Janousek > Assignee: Darran Lofthouse > Fix For: 7.1.0.CR1 > > > bin/add-user.sh allows to create two identical users even you specify really the same input values (realm, login name and password). It created two lines in mgmt-users.properties. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3912) Unable to get Soapmessage in jboss 5.1.0 GA

by Murugan D (JIRA)

Murugan D created AS7-3912: ------------------------------ Summary: Unable to get Soapmessage in jboss 5.1.0 GA Key: AS7-3912 URL: https://issues.jboss.org/browse/AS7-3912 Project: Application Server 7 Issue Type: Bug Components: Web Services Reporter: Murugan D Assignee: Alessio Soldano When I execute context.getMessage().getSOAPBody() in jboss 5.1.0 GA AS. Then am getting the org.jboss.util.NotImplementedException exception. Code Snippet:- protected String extractOperation(SOAPMessageContext context) { SOAPBody body; try { body = context.getMessage().getSOAPBody(); } catch (SOAPException e) { logger.error("Error fetching the soap body. Exception=" + e, e); return null; } } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] (AS7-3976) EJB client sometimes does not loadbalance

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-3976: ----------------------------------- Summary: EJB client sometimes does not loadbalance Key: AS7-3976 URL: https://issues.jboss.org/browse/AS7-3976 Project: Application Server 7 Issue Type: Bug Components: Clustering, EJB Affects Versions: 7.1.0.Final Reporter: Radoslav Husar Assignee: jaikiran pai Priority: Critical Fix For: 7.1.1.Final I noticed that with a 2 node cluster, sometimes all sessions are created only on one node. Looks like cluster view is not updating properly on the client. See https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Performance-Cluste... for logs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
3
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 2012