December 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7530) Port r90970 to trunk

by Brian Stansberry (JIRA)

Port r90970 to trunk -------------------- Key: JBAS-7530 URL: https://jira.jboss.org/jira/browse/JBAS-7530 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Jason T. Greene Fix For: JBossAS-6.0.0.M2 This was a commit to exclude a lot of sun javax dependencies. -- 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

15 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7519) Port JBAS-6335 to trunk

by Brian Stansberry (JIRA)

Port JBAS-6335 to trunk ----------------------- Key: JBAS-7519 URL: https://jira.jboss.org/jira/browse/JBAS-7519 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Deployers, EJB2 Reporter: Brian Stansberry Assignee: Jason T. Greene Fix For: JBossAS-6.0.0.M2 The JBAS-6335 fix needs porting to trunk. -- 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

15 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7518) Port r90280 to trunk

by Brian Stansberry (JIRA)

Port r90280 to trunk -------------------- Key: JBAS-7518 URL: https://jira.jboss.org/jira/browse/JBAS-7518 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB2 Reporter: Brian Stansberry Assignee: Jason T. Greene Fix For: JBossAS-6.0.0.M2 Attachments: r90280.diff Patch adding SFSB passivation count to container mbean needs porting to trunk. -- 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

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-7520) Port r90217, r90277 to trunk

by Brian Stansberry (JIRA)

Port r90217, r90277 to trunk ---------------------------- Key: JBAS-7520 URL: https://jira.jboss.org/jira/browse/JBAS-7520 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB2 Reporter: Brian Stansberry Assignee: Jason T. Greene Fix For: JBossAS-6.0.0.M2 Analysis of diffs of server module shows r90277 and at least some of r90217 needs porting to trunk. Following files show diffs to 6.0.0.M1: org/jboss/ejb/ContainerMBean org/jboss/ejb/Container org/jboss/invocation/InvocationStatistics r90217 touches other files in other modules as well; I haven't looked at those. -- 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

15 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7522) JBossCacheManager obtains Cache reference prematurely

by Brian Stansberry (JIRA)

JBossCacheManager obtains Cache reference prematurely ----------------------------------------------------- Key: JBAS-7522 URL: https://jira.jboss.org/jira/browse/JBAS-7522 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.M2 JBossCacheManager ends up acquiring a reference to the JBC cache during it's init method. This is done to allow throwing of ClusteringNotSupportedException by that method, allowing the behavior whereby a the deployment of a <distributable/> webapp in the default config can detect the absence of clustering classes and fall back on the non-clustered StandardManager. The problem here is JBossContextConfig can end up creating > 1 JBossCacheManager instance and calling init on it. (Need to investigate if that can be avoided.) If a 2nd instance is created, stop is not called on the first (since it's never been started). But the cache has been obtained from the CacheManager, increasing the reference count for the cache. Effect is the cache never gets fully released. This is the cause of recent failures in trunk of (AttributeBased)SessionPassivationUnitTestCase. We don't need to actually obtain the cache reference in init() to detect whether needed classes are available. Just a ref to the CacheManager is sufficient. Defer obtaining the cache reference until start(). This problem doesn't affect any released code; it's an effect of the work on JBAS-7473. -- 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

15 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-7571) out of the box shutdown fails java.lang.NoClassDefFoundError javax.management.MalformedObjectNameException

by joel schweiger (JIRA)

out of the box shutdown fails java.lang.NoClassDefFoundError javax.management.MalformedObjectNameException ---------------------------------------------------------------------------------------------------------- Key: JBAS-7571 URL: https://jira.jboss.org/jira/browse/JBAS-7571 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.1.GA Environment: Using jboss 5.0.1.GA on Redhat Linux 5.3 Reporter: joel schweiger Standard out of the box, using all configuration When I attempt to shutdown: JBOSS_CMD_STOP = java -classpath /opt/jboss/jboss-5.0.1.GA/bin/shutdown.jar:/opt/jboss/jboss-5.0.1.GA/client/jbossall-client.jar org.jboss.Shutdown --shutdown -s 10.199.74.23 Exception in thread "main" java.lang.NoClassDefFoundError: javax.management.MalformedObjectNameException at org.jboss.mx.util.ObjectNameFactory.create(ObjectNameFactory.java:52) at org.jboss.system.server.ServerImplMBean.<clinit>(ServerImplMBean.java:35) at java.lang.Class.initializeClass(libgcj.so.7rh) at org.jboss.Shutdown.main(Shutdown.java:118) Is the out of the box classpath of the shutdown command incorrect or are classes missing? It may be fixed in 5.1.0 but I need to use 5.0.1. Any suggestions? -- 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

15 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (SECURITY-450) RemoteHostTrustLoginModule third party authentication

by Anil Saldhana (JIRA)

RemoteHostTrustLoginModule third party authentication ----------------------------------------------------- Key: SECURITY-450 URL: https://jira.jboss.org/jira/browse/SECURITY-450 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: JBossSecurity_2.0.4.SP3 Reporter: Anil Saldhana Assignee: Andrew Oliver Fix For: JBossSecurity_2.0.4.SP4, JBossSecurity_2.1.0.alpha1 -- 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

15 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-449) org.jboss.security.microcontainer.beans.Util uses locale sensitive toUpperCase, causing AS boot failure in Turkish locale

by jaikiran pai (JIRA)

org.jboss.security.microcontainer.beans.Util uses locale sensitive toUpperCase, causing AS boot failure in Turkish locale ------------------------------------------------------------------------------------------------------------------------- Key: SECURITY-449 URL: https://jira.jboss.org/jira/browse/SECURITY-449 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Environment: JBoss AS 5.1.0, JBoss AS 6.0.0.M1 Reporter: jaikiran pai Assignee: Anil Saldhana A couple of users have run into issues with AS boot failure when using turkish locale. The boot fails with: 11:56:51,955 ERROR [AbstractKernelController] Error installing to Start: name=jboss-web-policy state=Create java.lang.IllegalArgumentException: Invalid control flag: REQU?RED at org.jboss.security.microcontainer.beans.Util.getControlFlag(Util.java:57) at org.jboss.security.microcontainer.beans.AuthorizationPolicyBean.getPolicyInfo(AuthorizationPolicyBean.java:49) at org.jboss.security.microcontainer.beans.ApplicationPolicyBean.getApplicationPolicy(ApplicationPolicyBean.java:459) at org.jboss.security.microcontainer.beans.ApplicationPolicyBean.start(ApplicationPolicyBean.java:420) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59) The complete details and the fix are mentioned in the comments of https://jira.jboss.org/jira/browse/JBAS-6651. I guess the Util class can just delegate the call to ControlFlag.valueOf(string), since the valueOf method does *not* have any locale specific implementation. Alternately, the Util class can be removed altogether, but it might be too much work if that class is being used in too many places. -- 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

15 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-7542) HostnameTrustLoginModule / Valve for allowing third party authentication

by Andrew Oliver (JIRA)

HostnameTrustLoginModule / Valve for allowing third party authentication ------------------------------------------------------------------------- Key: JBAS-7542 URL: https://jira.jboss.org/jira/browse/JBAS-7542 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.2.3.GA Reporter: Andrew Oliver Assignee: Anil Saldhana Presently Tested With 4.3.0. This login module is for the specific case of needing to pass credentials between instances without re-authenticating (diagram: http://dl.dropbox.com/u/1368565/redhat/patches/diagram_trust.png and http://dl.dropbox.com/u/1368565/redhat/patches/diagram_trust.odg). The valve puts the getHostName from a request object in a thread local value. The login module checks this supplied hostname (generally an IP) against a list of trusted IPs. This should only be used behind a firewall with spoofing disabled where network security has assured the getHostName call returns a valid value. No testcase is included as it requires a specific network setup and multiple instances. If there are no objections I'll commit this to the trunk with my LdapExtLoginModule patches. http://dl.dropbox.com/u/1368565/redhat/patches/HostThreadLocal.java http://dl.dropbox.com/u/1368565/redhat/patches/RemoteHostTrustLoginModule... http://dl.dropbox.com/u/1368565/redhat/patches/RemoteHostValve.java In order to use it (login-config.xml): <application-policy name = "jmx-console"> <authentication> <login-module code="org.jboss.security.auth.spi.RemoteHostTrustLoginModule" flag = "optional"> <module-option name="password-stacking">useFirstPass</module-option> <module-option name="trustedHosts">192.168.49.10</module-option> <module-option name="roles">transportAuthenticated</module-option> </login-module> .. some other login module ... </authentication> </application-policy> context.xml: <Context> <Valve className="org.jboss.web.tomcat.security.RemoteHostValve"/> </Context> -- 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

15 years, 10 months

4
11
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1978) MDB with message-destination-link declared should not require activation config properties

by Andrew Lee Rubinger (JIRA)

MDB with message-destination-link declared should not require activation config properties ------------------------------------------------------------------------------------------ Key: EJBTHREE-1978 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1978 Project: EJB 3.0 Issue Type: Bug Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Instead map to the logical name, let the container resolve the required metadata. Probably to be done in a post-processing step within jboss-metadata-ejb -- 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

15 years, 10 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2009