 
                                        
                                
                         
                        
                                
                                
                                        
                                                
                                        
                                        
                                        [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
                        
                        
                 
         
 
        
            
        
        
        
                
                        
                                
                                 
                                        
                                
                         
                        
                                
                                
                                        
                                                
                                        
                                        
                                        [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
                        
                        
                 
         
 
        
            
        
        
        
            
        
        
        
                
                        
                                
                                 
                                        
                                
                         
                        
                                
                                
                                        
                                                
                                        
                                        
                                        [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