admin-console fails to load when unexploded EAR containing an EJB module JAR exists in the deploy directory ----------------------------------------------------------------------------------------------------------- Key: EMBJOPR-371 URL: https://issues.jboss.org/browse/EMBJOPR-371 Project: Embedded Jopr Issue Type: Bug Affects Versions: 1.3.4.SP5 Reporter: Larry O'Leary Assignee: Stefan Negrea Fix For: 1.3.4.SP6 Attachments: Error.txt When an EAP instance has an EAR deployed to it which contains an EJB module JAR and the EAR is in an unexploded form (archived), attempting to access the admin-console results in the following exception: ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/admin-console]] (http-0.0.0.0-8080-1) Exception sending request initialized lifecycle event to listener instance of class org.jboss.on.embedded.LazyStartupListener java.lang.RuntimeException: Error handling file /opt/jboss/jboss-eap-5.1/jboss-as/server/production/deploy/exolgan-legacy-ejb.ear/exolgan-legacy-ejb.jar at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:134) at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) at org.jboss.seam.init.Initialization.create(Initialization.java:130) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) at org.jboss.on.embedded.LazyStartupListener.initialize(LazyStartupListener.java:182) at org.jboss.on.embedded.LazyStartupListener.requestInitialized(LazyStartupListener.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:180) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:599) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451) at java.lang.Thread.run(Thread.java:636) Caused by: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:131) at java.util.zip.ZipFile.<init>(ZipFile.java:148) at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) ... 21 more The issue can be resolved by adding the following files to admin-console.war/META-INF/ Empty File (seam.properties) seam-deployment.properties: org.jboss.seam.deployment.scanners=org.jboss.seam.integration.jbossas.vfs.VFSScanner