You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2017/02/17 23:24:44 UTC

[jira] [Commented] (LOG4J2-548) Log4j 2.0 with JBoss EAP 6.2

    [ https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872725#comment-15872725 ] 

Gary Gregory commented on LOG4J2-548:
-------------------------------------

Thank you for your patch Eric. 

Did you try a full build to make sure all the unit tests pass? 'mvn clean install'

Thank you,
Gary

> Log4j 2.0 with  JBoss EAP 6.2
> -----------------------------
>
>                 Key: LOG4J2-548
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-548
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0-rc1, 2.1
>         Environment: EJB 3.1 , JBoss EAP 6.2 , Windows 7 , Eclipse Kepler 
>            Reporter: Shehata
>            Assignee: Ralph Goers
>         Attachments: LOG4J2-548 - evictors.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> When trying to use log4j 2.0-rc1 with EJB3.1 i got Error Message:
> "ERROR StatusLogger Could not search jar file 'jboss-eap-6.2\standalone\deployments\Log4J2Ear.ear\lib\log4j-core-2.0-rc1.jar\org\apache\logging\log4j\core' for classes matching criteria: annotated with @Plugin file not found"
> after debugging the application found that the problem is located in :
> org.apache.logging.log4j.core.config.plugins.ResolverUtil
> method: findInPackage --> line number 247
> the protocol used in the jar is vfs not vfszip



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org