Bug 751506 - [admin-console] Fails to load if unexploded EAR is deployed with a EJB JAR inside it
Summary: [admin-console] Fails to load if unexploded EAR is deployed with a EJB JAR in...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: RHQ Project
Classification: Other
Component: No Component
Version: unspecified
Hardware: All
OS: All
high
high
Target Milestone: ---
: ---
Assignee: Stefan Negrea
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-04 23:17 UTC by Larry O'Leary
Modified: 2012-07-19 14:51 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
EAP 5.1.1 running on Fedora 14 (Linux 2.6.35.14-97.fc14.x86_64)
Last Closed: 2012-07-09 18:31:11 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EMBJOPR-371 0 Major Resolved admin-console fails to load when unexploded EAR containing an EJB module JAR exists in the deploy directory 2017-07-08 15:34:48 UTC
Red Hat Knowledge Base (Legacy) 65588 0 None None None Never

Description Larry O'Leary 2011-11-04 23:17:30 UTC
Description of problem:
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





Version-Release number of selected component (if applicable):
JBoss EAP 5.1.1 with admin-console 1.3.4.SP4

How reproducible:
Always

Additional info:
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

Comment 1 Larry O'Leary 2012-07-09 18:31:11 UTC
This affects the upstream EMBJOPR project only and does not reference/reflect any code in RHQ.

Comment 2 JBoss JIRA Server 2012-07-17 17:56:22 UTC
Stefan Negrea <snegrea> updated the status of jira EMBJOPR-371 to Resolved

Comment 3 JBoss JIRA Server 2012-07-17 17:56:22 UTC
Stefan Negrea <snegrea> made a comment on jira EMBJOPR-371

I attempted to reproduce the problem with EAP 5.1.1, EAP 5.1.2, and various other builds using many different permutations of ear files but was not able to reproduce the problem. 

Closing this bug  with 'cannot reproduce'. If the problem reappears please attach test data and reopen this ticket.


Note You need to log in before you can comment on or make changes to this bug.