[
https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16441542#comment-16441542
]
ASF subversion and git services commented on LOG4J2-548:
--------------------------------------------------------
Commit 35f4ed5f7817305a12d3badc311cce810324ecf9 in logging-log4j2's branch
refs/heads/release-2.x from [~bananetomate]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=35f4ed5 ]
[LOG4J2-548] Log4j 2.0 ERROR "Could not search jar" with JBoss EAP 6.2.
> Log4j 2.0 ERROR "Could not search jar" 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
> Priority: Major
> Attachments: LOG4J2-548 - evictors.patch, 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
(v7.6.3#76005)
