jruby 1.6.4 causes "SEVERE: Unable to process Jar entry [org/jruby/RubyRegexp.class] from Jar [jar:file:${liferay.home}/tomcat-7.0.56/webapps/ROOT/WEB-INF/lib/jruby.jar!/] for annotations java.io.EOFException" on Tomcat 7.0.56

• Type: Technical Task
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 6.1.30 EE GA3, 6.1.X EE
• Fix Version/s: 6.1.X EE, 6.2.0 CE M2
• Component/s: Environments, Environments > App Servers, Frontend Infrastructure, Themes Infrastructure
• Labels:
  • ee-ts
  • liferay-fixpack-platform-29-6130
  • liferay-fixpack-portal-55-6130
• Branch Version/s:
  6.1.x
• Backported to Branch:
  Committed
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal-ee/pull/7609

1- Facts

• https://issues.liferay.com/browse/LPS-29837 upgraded jruby from 1.6.4 to 1.6.5
• For some unknown reasons, the first commit (the one that replaces the jruby.jar) has not been backported to ee-6.1.x:
• 6.1.30 is marked as a fixed version on LPS-29837

commits - master/62x/6210:
1-https://github.com/liferay/liferay-portal-ee/commit/125b7ac095a61712db53f35adeff38d32b51c91d

2- https://github.com/liferay/liferay-portal-ee/commit/f6b196f85f82d5a29e17e31584837a74a5411dcf

3- https://github.com/liferay/liferay-portal-ee/commit/d06a3ddc693c38d1d54cf9b134baf9bdd5762138

4- https://github.com/liferay/liferay-portal-ee/commit/570a48e28dc8738396df57adaec8a86bd5a46a74

commits - ee-6.1.x:

1- https://github.com/liferay/liferay-portal-ee/commit/f5add5a7f13a077c88d19c3f28dcd7848f5931bb

2- https://github.com/liferay/liferay-portal-ee/commit/6c6e370e98d605b058b92d747741736ef5886d66

3- https://github.com/liferay/liferay-portal-ee/commit/3f1719f2d9f210bb30d54f5cfb405d9839fbbdf1

2- Problem
6.1.30 is unable to start on latest Tomcat (tomcat-7.0.56) due to the following error:

2014.10.24. 8:59:56 org.apache.catalina.startup.ContextConfig processAnnotationsJar
SEVERE: Unable to process Jar entry [org/jruby/RubyRegexp.class] from Jar [jar:file:/c:/liferay/apache-tomcat-7.0.56/webapps/ROOT/WEB-INF/lib/jruby.jar!/] for annotations
java.io.EOFException
at org.apache.tomcat.util.bcel.classfile.FastDataInputStream.readUnsignedShort(FastDataInputStream.java:120)
at org.apache.tomcat.util.bcel.classfile.Utility.swallowFieldOrMethod(Utility.java:75)
at org.apache.tomcat.util.bcel.classfile.ClassParser.readMethods(ClassParser.java:235)
at org.apache.tomcat.util.bcel.classfile.ClassParser.parse(ClassParser.java:92)
at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2071)
at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1947)
at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1913)
at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1898)
at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1330)
at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:889)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:386)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5380)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:672)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1861)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)

• Replacing the jruby.jar included in 6.1.30 (v.1.6.4) with v.1.6.5 solves this issue.