[ https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435497#comment-16435497 ]
Martin edited comment on LOG4J2-548 at 4/12/18 12:54 PM: --------------------------------------------------------- We have that specific problem in production here and the patch works as a workaround. It's been more than a year since the patch was suggested, may I ask when that could be integrated in a build? was (Author: laforet): It's been more than a year since the patch was suggested. We have that specific problem in production here and the patch works as a workaround. May I ask when that could be integrated in a build? > 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 > Priority: Major > 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 (v7.6.3#76005)