May 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBAS-9493) Unable to read the logging configuration "logging.properties" when the charater "#" is included in the JBoss home path

by Frederic Hornain (JIRA)

Frederic Hornain created JBAS-9493: -------------------------------------- Summary: Unable to read the logging configuration "logging.properties" when the charater "#" is included in the JBoss home path Key: JBAS-9493 URL: https://issues.jboss.org/browse/JBAS-9493 Project: Application Server 3 4 5 and 6 Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.M5, 6.0.0.M4, 6.0.0.M3, 6.0.0.M2, 6.0.0.M1 Environment: Fedora 16, JBoss EAP 6.0.0 Beta 1 Reporter: Frederic Hornain Priority: Minor Unable to read the logging configuration from 'file:/Lab#2/eap6/standalone/configuration/logging.properties' (java.io.FileNotFoundException: /Lab (No such file or directory)) -- 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

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] (JBRULES-3494) Accumulate with vars having a different order than the one imposed by Declaration's hashCode causes a ClassCastException

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3494: ------------------------------------ Summary: Accumulate with vars having a different order than the one imposed by Declaration's hashCode causes a ClassCastException Key: JBRULES-3494 URL: https://issues.jboss.org/browse/JBRULES-3494 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Running the following drl causes a ClassCastException: import java.util.List declare MessageHolder id : String msg: String end query getResults( String $mId, List $holders ) accumulate( $holder : MessageHolder( id == $mId, $ans : msg ), $holders : collectList( $holder ) ) end rule "Init" when then insert( new MessageHolder( "1", "x" ) ); end -- 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

13 years, 12 months

1
1
0 / 0

[JBoss JIRA] (AS7-4736) CurrentServiceContainer does not have a permission check

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-4736: ----------------------------------- Summary: CurrentServiceContainer does not have a permission check Key: AS7-4736 URL: https://issues.jboss.org/browse/AS7-4736 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.1.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.1.2.Final (EAP) CurrentServiceContainer.getServiceContainer() does not have a permission check, which means untrusted code could potentially disrupt the operation of the server -- 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

13 years, 12 months

1
1
0 / 0

[JBoss JIRA] (AS7-3464) add-user.sh - possibility of setting another Realms should be considered again

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-3464?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-3464: ---------------------------------- Fix Version/s: 7.2.0.Alpha1 (was: Open To Community) Assignee: Darran Lofthouse Scheduling for AS 7.2 as I want us to move from having a pre-defined realm name to encouraging the admin to choose a realm name on entering the first user - after that all subsequent users will use the same realm. > add-user.sh - possibility of setting another Realms should be considered again > ------------------------------------------------------------------------------ > > Key: AS7-3464 > URL: https://issues.jboss.org/browse/AS7-3464 > Project: Application Server 7 > Issue Type: Bug > Components: Security > Affects Versions: 7.1.0.CR1b > Reporter: Pavel Janousek > Assignee: Darran Lofthouse > Priority: Minor > Fix For: 7.2.0.Alpha1 > > > I'm aware of add-user.sh isn't general tool for managing an user/groups/roles credential store at all. Is it supposed only as shorthand for quick definition of users access to admin console out of the box. Well.. > According previous paragraph it isn't to much meaningful for me to bring possibility of specify another realm during the invocation of this tool. I think already - Admin console can use another realm than ManagementRealm by change default configuration. I think already too - property file can't contain users definition belong multiple realms. As is stated in comment in the begin of file mgmt-users.properties, this file is for "declaration of users for the realm 'ManagementRealm'". > I think we should avoid to insert new user with different realm there (it is possible now). add-user.sh doesn't manage any other file and other property file(s) can't be specified during invocation. > I think this present situation/behavior should confuse hard our end-users - especially users with their own experiences with other JEE servers (Apache Geronimo, Sun/Oracle GlassFish etc.). > Because we don't provide/support any tool for general CRUD managing of credential store of type like property file(s) - like other JEE app. servers do, we really should use this script/tool only as way to simple very basic user creation in default AS7 environment, because we can't support this tool in any other situation with present behavior and in a such changed environments behavior or final state is hardly understandable (if we create property file (by other way) with the same username, but in different realms, we can't log to admin console never more; if we have users in one realm, switch AS7 instance to use other "admin" realm, we can't add any from existing user to this new realm; we don't know which user belongs to which realm later etc.) > So conclusion - I think we should remove specification of Realm from input process of add-user.sh script at all and use this script only to define users belongs to ManagementRealm realm and manages only properly mgmt-users.properties files (standalone and domain configuration) -- 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

13 years, 12 months

1
0
0 / 0

[JBoss JIRA] (AS7-4408) CLONE - Enable JAAS support for the SASL Realms

by Jan Lanik (JIRA)

Jan Lanik created AS7-4408: ------------------------------ Summary: CLONE - Enable JAAS support for the SASL Realms Key: AS7-4408 URL: https://issues.jboss.org/browse/AS7-4408 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management, Security Reporter: Jan Lanik Assignee: Darran Lofthouse Fix For: 7.1.0.Final -- 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

13 years, 12 months

3
2
0 / 0

[JBoss JIRA] (AS7-4676) Support Password Stacking for Domain HTTP Server

by Jess Sightler (JIRA)

Jess Sightler created AS7-4676: ---------------------------------- Summary: Support Password Stacking for Domain HTTP Server Key: AS7-4676 URL: https://issues.jboss.org/browse/AS7-4676 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management, Security Reporter: Jess Sightler Assignee: Brian Stansberry Priority: Minor Our clients need the ability to restrict logins by client certificate, and by a role stored within an LDAP server. Ideally, the system would support some form of password-stacking feature to allow access based upon a combination of authentication systems. Cf, http://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/Usin... for how this is implemented in existing EAP5 installations. -- 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

13 years, 12 months

2
3
0 / 0

[JBoss JIRA] (AS7-4737) Boot time flag not visible when creating system properties

by Heiko Braun (JIRA)

Heiko Braun created AS7-4737: -------------------------------- Summary: Boot time flag not visible when creating system properties Key: AS7-4737 URL: https://issues.jboss.org/browse/AS7-4737 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.Alpha1 -- 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

13 years, 12 months

1
1
0 / 0

[JBoss JIRA] (AS7-4738) Cannot remove system property from serve group

by Heiko Braun (JIRA)

Heiko Braun created AS7-4738: -------------------------------- Summary: Cannot remove system property from serve group Key: AS7-4738 URL: https://issues.jboss.org/browse/AS7-4738 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.Alpha1 -- 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

13 years, 12 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJPA-26) Implement the clarified rules for resource discovery

by Hardy Ferentschik (JIRA)

Implement the clarified rules for resource discovery ---------------------------------------------------- Key: JBJPA-26 URL: https://jira.jboss.org/jira/browse/JBJPA-26 Project: JBoss JPA Issue Type: Task Reporter: Hardy Ferentschik Assignee: Carlo de Wolf The JPA 2 specs clarifies the usage of the <jar-file> element of persistence.xml. See section 8.2.1.6 of the spec. Section 8.2.1.6.3 gives a hole range of examples for different ear file configurations. I am opening this issue as a replacement for http://opensource.atlassian.com/projects/hibernate/browse/HHH-4666, since it is really the responsibility of the container to parse the ear file and create the right PersistenceUnitInfo instance to be passed to Hibernate. Hibernate's Ejb3Configuration already makes use of the information passed via PersistenceUnitInfo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

2
1
0 / 0

[JBoss JIRA] (AS7-3492) Server side invocations on a clustered stateful bean end up being handled on the same local node

by jaikiran pai (JIRA)

jaikiran pai created AS7-3492: --------------------------------- Summary: Server side invocations on a clustered stateful bean end up being handled on the same local node Key: AS7-3492 URL: https://issues.jboss.org/browse/AS7-3492 Project: Application Server 7 Issue Type: Bug Components: Clustering, EJB Affects Versions: 7.1.0.CR1b Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 7.1.0.Final Currently, if a stateful bean is @Cluster(ed) and an invocation on it is done from within the same server, invocations on that bean are always handled by the LocalEJBReceiver even if the cluster has multiple others nodes hosting that stateful bean. The LocalEjbReceiver currently receives the cluster topology but doesn't create (remote) EJB receviers out of it for the client context. The missing piece is configurations that need to be passed for creating the remote EJB receivers. -- 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

13 years, 12 months

4
14
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 May 2012