7 Replies Latest reply on Mar 28, 2011 3:58 PM by andrew.geery

jbossas 6 + seam 2.2.1 + error in opening zip file

andrew.geery Mar 28, 2011 11:04 AM

I'm trying to migrate my Seam application from JBoss AS 4.2.3 to 6.0. However, when I deploy the WAR, I get an error about not being able to unzip one of my jar files. I've manually verified that I can, indeed, un'jar the file in question just fine and I've restarted the server to make sure the issue isn't an incomplete deployment.

A couple of things that are a little different about this app: (1) JSF is not used for the view [Flex is used instead]; and (2) the WEB-INF/classes directory is empty -- all of the classes are in jar files. I've found lots of posts from last summer about this issue. However, I never found a solution; it was listed as fixed in M4. Does this ring any bells?

Thanks

Andrew

2011-03-24 00:02:13,759 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) deploy, ctxPath=/app-webapp

2011-03-24 00:02:13,860 INFO [javax.servlet.ServletContextListener] (HDScanner) Welcome to Seam 2.2.1.Final

2011-03-24 00:02:13,922 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/app-webapp]] (HDScanner) Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener: java.lang.RuntimeException: Error handling file /usr/local/jboss/jboss-6.0.0.Final/server/default/deploy/app-webapp.war/WEB-INF/lib/app-seam-0.0.1-SNAPSHOT.jar

at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:134) [:2.2.1.Final]

at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) [:2.2.1.Final]

at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) [:2.2.1.Final]

at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [:2.2.1.Final]

at org.jboss.seam.init.Initialization.create(Initialization.java:130) [:2.2.1.Final]

at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [:2.2.1.Final]

at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3369) [:6.0.0.Final]

at org.apache.catalina.core.StandardContext.start(StandardContext.java:3828) [:6.0.0.Final]

at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:294) [:6.0.0.Final]

at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146) [:6.0.0.Final]

at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:477) [:6.0.0.Final]

at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) [:6.0.0.Final]

at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.0.Final]

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_23]

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_23]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_23]

at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_23]

at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.GA]

at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.GA]

at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.GA]

at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.GA]

at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.GA]

at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) [:2.2.0.GA]

at $Proxy41.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:53) [:2.2.0.GA]

at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:41) [:2.2.0.GA]

at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:301) [:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:894) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:641) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:182) [:2.2.0.GA]

at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:58) [:2.2.0.GA]

at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) [:2.2.0.GA]

at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.GA]

at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.GA]

at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [:2.2.0.GA]

at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550) [:2.2.0.GA]

at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1571) [:2.2.0.GA]

at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491) [:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA]

at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.GA]

at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.GA]

at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.GA]

at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.Final]

at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2]

at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.2.2]

at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.2.2]

at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) [:0.2.2]

at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.2.2]

at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95) [:0.2.2]

at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2]

at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2]

at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2]

at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2]

at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.2.2]

at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2]

at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2]

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_23]

at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_23]

at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_23]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_23]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [:1.6.0_23]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [:1.6.0_23]

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23]

at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]

Caused by: java.util.zip.ZipException: error in opening zip file

at java.util.zip.ZipFile.open(Native Method) [:1.6.0_23]

at java.util.zip.ZipFile.<init>(ZipFile.java:127) [:1.6.0_23]

at java.util.zip.ZipFile.<init>(ZipFile.java:144) [:1.6.0_23]

at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) [:2.2.1.Final]

... 80 more

1. jbossas 6 + seam 2.2.1 + error in opening zip file

alesj Mar 28, 2011 11:10 AM (in response to andrew.geery)

You need this lib in your classpath, so Seam will understand VFS.
* http://anonsvn.jboss.org/repos/jbossas/projects/jboss-seam-int/trunk/jbossas/

But I need to check why Seam.deployer integration is not kicking in ...
Actions
2. jbossas 6 + seam 2.2.1 + error in opening zip file

andrew.geery Mar 28, 2011 11:36 AM (in response to alesj)

It looks like I have them in the app server installation (this is AS 6):

# find . -name '*seam-int-j*.jar' -ls
7203528   12 -rw-rw-r--   1 root     root        11468 Dec 28 08:31 ./server/default/deployers/seam.deployer/lib-int/jboss-seam-int-jbossas.jar
7203263   12 -rw-rw-r--   1 root     root        11468 Dec 28 08:31 ./server/all/deployers/seam.deployer/lib-int/jboss-seam-int-jbossas.jar
7202878   12 -rw-rw-r--   1 root     root        11468 Dec 28 08:30 ./server/standard/deployers/seam.deployer/lib-int/jboss-seam-int-jbossas.jar

Do I need to copy them somewhere so they're used properly?

Thanks
Andrew
Actions
3. jbossas 6 + seam 2.2.1 + error in opening zip file

alesj Mar 28, 2011 11:49 AM (in response to andrew.geery)

They should kick-in by itself, via seam.deployer.
Dunno why it doesn't ...

For now you can manually add them to your app,
and meanwhile I'll try to re-create this example and see why it doesn't kick in.
Actions
4. jbossas 6 + seam 2.2.1 + error in opening zip file

alesj Mar 28, 2011 11:50 AM (in response to alesj)

For now you can manually add them to your app,
I mean, add *it*, not them. :-)
* anyone of those 3 will do, as they are all the same
Actions
5. jbossas 6 + seam 2.2.1 + error in opening zip file

andrew.geery Mar 28, 2011 1:14 PM (in response to alesj)

Thanks, Ales! Adding jboss-seam-int-jbossas.jar to WEB-INF/lib directory did allow me to successfully deploy the application.

Looking at the code for SeamUrlIntegrationDeployer [I couldn't find the official repository, but I found this]: http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/releases/org.jboss.seam.integration/jboss-seam-int-microcontainer/5.0.0.CR5/org/jboss/seam/integration/microcontainer/deployers/SeamUrlIntegrationDeployer.java

My issue was that I didn't have any of the triggers that would tell the server that the application was a Seam app:

seam.properties
META-INF/seam.properties
WEB-INF/classes/seam.properties
META-INF/components.xml
WEB-INF/classes/META-INF/components.xml

My problem was there is a components.xml and a seam.properties file *BUT* they are contained in a jar in WEB-INF/lib directory, so the server didn't pick them up. I simply added an empty seam.properties at the top-level and the app deployed correctly.

Thanks again for your help!
Andrew
Actions
6. jbossas 6 + seam 2.2.1 + error in opening zip file

alesj Mar 28, 2011 3:32 PM (in response to andrew.geery)

Looking at the code for SeamUrlIntegrationDeployer [I couldn't find the official repository, but I found this]: http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/releases/org.jboss.seam.integration/jboss-seam-int-microcontainer/5.0.0.CR5/org/jboss/seam/integration/microcontainer/deployers/SeamUrlIntegrationDeployer.java
It's actually the same as I posted before. :-)
My issue was that I didn't have any of the triggers that would tell the server that the application was a Seam app:

seam.properties
META-INF/seam.properties
WEB-INF/classes/seam.properties
META-INF/components.xml
WEB-INF/classes/META-INF/components.xml

My problem was there is a components.xml and a seam.properties file *BUT* they are contained in a jar in WEB-INF/lib directory, so the server didn't pick them up. I simply added an empty seam.properties at the top-level and the app deployed correctly.
Ah, yes, that explains it then. :-)
Nice workaround.

Can you create a wiki page from this use case?
Actions
7. jbossas 6 + seam 2.2.1 + error in opening zip file

andrew.geery Mar 28, 2011 3:58 PM (in response to alesj)

Done! http://community.jboss.org/wiki/SeamapplicationjavautilzipZipExceptionerrorinopeningzipfile

Thanks again for the help!
Actions

Go to original post