Bug 899236 (JBEWS-90)

Affects: Added: [Release Notes]

Documented as a known issue in the EWS 1.0.1 release notes, but more information about this issue would be appreciated.

Laura, there is "security manager" omitted in the JIRA release notes entry.
It should say something like this: "When JBoss Enterprise Web Server is run on the IBM Java Development Kit 1.6 using Java Security Manager, Tomcat 6 does not start."
 

 

Thanks, Peter! I've updated the notes to include Java Security Manager as a factor.

Rajesh to investigate for 1.0.2

Writer: Added: rebecca_newton

I would like to have this issue open. We will investigate more about this during the CR1 test cycle

Release Notes Docs Status: Added: Documented as Known Issue
Release Notes Text: Added: When JBoss Enterprise Web Server is run on the IBM Java Development Kit 1.6 using Java Security Manager, Tomcat 6 does not start.

Status for EWS 1.0.2.CR2:
- tomcat6 is not working properly with IBM JDK (IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr9-20110203_74623 (JIT enabled, AOT enabled))
- catalina.out contains following exception:
SEVERE: Error deploying configuration descriptor manager.xml
Throwable occurred: org.apache.juli.logging.LogConfigurationException: No suitable Log implementation
        at org.apache.juli.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:918)
        at org.apache.juli.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:604)
        at org.apache.juli.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:336)
        at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:704)
        at org.apache.catalina.core.ContainerBase.getLogger(ContainerBase.java:395)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4586)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
        at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:124)
        at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:146)
        at java.security.AccessController.doPrivileged(AccessController.java:202)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:777)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
        at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675)
        at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601)
        at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
        at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1315)
        at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
        at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
        at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
        at org.apache.catalina.core.StandardService.start(StandardService.java:525)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)


- with following entries added to conf/catalina.policy section grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
  tomcat works fine

permission java.util.PropertyPermission "org.apache.juli.logging.diagnostics.dest", "read";
permission java.util.PropertyPermission "org.apache.juli.logging.LogFactory.HashtableImpl", "read";
permission java.util.PropertyPermission "org.apache.juli.logging.LogFactory", "read";
permission java.util.PropertyPermission "org.apache.juli.logging.Log.allowFlawedContext", "read";
permission java.util.PropertyPermission "org.apache.juli.logging.Log.allowFlawedDiscovery", "read";
permission java.util.PropertyPermission "org.apache.juli.logging.Log.allowFlawedHierarchy", "read";
permission java.util.PropertyPermission "org.apache.juli.logging.Log", "read";
permission java.util.PropertyPermission "org.apache.juli.logging.log", "read";
permission java.lang.RuntimePermission "accessClassInPackage.sun.util.logging.resources";
permission java.lang.RuntimePermission "accessClassInPackage.org.apache.catalina.loader";

Moving this to TBD bin as this was not fixed in 1.0.2 release. Verified that this is documented in the release notes.

Release Notes Docs Status: Removed: Documented as Known Issue 
Writer: Removed: rebecca_newton 
Release Notes Text: Removed: When JBoss Enterprise Web Server is run on the IBM Java Development Kit 1.6 using Java Security Manager, Tomcat 6 does not start.