portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sean Taylor (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] [Commented] (JS2-1365) Old Version of Tomcat packaged with JetSpeed
Date Wed, 03 Oct 2018 22:49:00 GMT

    [ https://issues.apache.org/jira/browse/JS2-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637585#comment-16637585
] 

David Sean Taylor commented on JS2-1365:
----------------------------------------

Sounds like we'd have to package with Tomcat9 

> Old Version of Tomcat packaged with JetSpeed
> --------------------------------------------
>
>                 Key: JS2-1365
>                 URL: https://issues.apache.org/jira/browse/JS2-1365
>             Project: Jetspeed 2
>          Issue Type: Bug
>    Affects Versions: 2.3.1
>            Reporter: Peter_Lenahan@ibi.com
>            Priority: Critical
>         Attachments: jetspeed-crashing.png
>
>
> The older version of Tomcat currently packaged with Jetspeed, does not support The Java
9 feature of Multi Release Jar files.
> As a result, the log4j-api-2.11.0.jar which is packaged with Java 9 support causes an
> error when trying to parse the Java 9 classes.
> This error can be seen in the attached image, and the trace below.
> Editing the log4j-api-2.11.0.jar jar file and removing the Java 9 files allows the portlet
to start.
> This is not a problem in the JetSpeed code, just the packaging of older tomcat in the 
jetspeed release 2.3.1
>  
> Here is the stack trace which shows the problem is in tomcat.
>  
> Creating war C:\Apache\Jetspeed-2.3.1\webapps\ops286.war ...
> War C:\Apache\Jetspeed-2.3.1\webapps\ops286.war created
> Oct 03, 2018 3:33:06 PM org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive C:\Apache\Jetspeed-2.3.1\webapps\ops286.war
> Oct 03, 2018 3:33:07 PM org.apache.catalina.deploy.WebXml setVersion
> WARNING: Unknown version string [3.1]. Default version will be used.
> Oct 03, 2018 3:33:09 PM org.apache.catalina.startup.ContextConfig processAnnotationsJar
> SEVERE: Unable to process Jar entry [META-INF/versions/9/module-info.class] from Jar
[jar:file:/C:/Apache/Jetspeed-2.3.1/webapps/ops286/WEB-INF/lib/log4j-api-2.11.0.jar!/] for
annotations
> org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid byte tag in constant
pool: 19
>  at org.apache.tomcat.util.bcel.classfile.Constant.readConstant(Constant.java:97)
>  at org.apache.tomcat.util.bcel.classfile.ConstantPool.<init>(ConstantPool.java:55)
>  at org.apache.tomcat.util.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:176)
>  at org.apache.tomcat.util.bcel.classfile.ClassParser.parse(ClassParser.java:85)
>  at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2121)
>  at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1983)
>  at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1944)
>  at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1929)
>  at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1328)
>  at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:887)
>  at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:387)
>  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:5472)
>  at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
>  at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:899)
>  at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:875)
>  at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
>  at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1092)
>  at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1984)
>  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  at java.lang.Thread.run(Thread.java:748)
> Oct 03, 2018 3:33:09 PM org.apache.catalina.startup.TldConfig execute
> INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging
for this logger for a complete list of JARs that were scanned but no TLDs were found in them.
Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
> JetspeedContainerServlet: starting initialization of Portlet Application at: ops286
> JetspeedContainerServlet: initialization done for Portlet Application at: ops286
> Oct 03, 2018 3:33:09 PM org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deployment of web application archive C:\Apache\Jetspeed-2.3.1\webapps\ops286.war
has finished in 2,624 ms



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message