[arquillian-issues] [JBoss JIRA] (ARQ-1650) Managed container bypasses tomcat jul setup

[Thomas Diesler (JIRA)]

    [ https://issues.jboss.org/browse/ARQ-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12945844#comment-12945844 ] 

Thomas Diesler commented on ARQ-1650:
-------------------------------------

As a workaround you can add this to your arquillian.xml

{code}
            <property name="javaVmArguments">-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=${tomcat.home}/conf/logging.properties</property>
{code}
                
> Managed container bypasses tomcat jul setup
> -------------------------------------------
>
>                 Key: ARQ-1650
>                 URL: https://issues.jboss.org/browse/ARQ-1650
>             Project: Arquillian
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Tomcat Containers
>    Affects Versions: tomcat_1.0.0.CR5
>            Reporter: Thomas Diesler
>            Assignee: Thomas Diesler
>             Fix For: tomcat_1.0.0.Final
>
>
> This code from the catalina startup script is not done in the manged deployable container
> {code}
> # Set juli LogManager config file if it is present and an override has not been issued
> if [ -z "$LOGGING_CONFIG" ]; then
>   if [ -r "$CATALINA_BASE"/conf/logging.properties ]; then
>     LOGGING_CONFIG="-Djava.util.logging.config.file=$CATALINA_BASE/conf/logging.properties"
>   else
>     # Bugzilla 45585
>     LOGGING_CONFIG="-Dnop"
>   fi
> fi
> if [ -z "$LOGGING_MANAGER" ]; then
>   LOGGING_MANAGER="-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager"
> fi
> {code}
> As a result, tomcat logging does not work 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira