>From the time that I sent the message below, I've been debugging and the >problem can be solved by removing libraries in portal-app image that overlap >with classes inside epsdk-music-2.2.0-SNAPSHOT-jar-with-dependencies.jar. The following Dockerfile gives a workaround image that allows me to work:
FROM onap/portal-app:2.5.0 MAINTAINER Juan Postlbauer <[email protected]> RUN rm -v /opt/apache-tomcat-8.0.37/webapps/ONAPPORTAL/WEB-INF/lib/bcprov-jdk14-138.jar RUN rm -v /opt/apache-tomcat-8.0.37/webapps/ONAPPORTAL/WEB-INF/lib/logback-c* RUN rm -v /opt/apache-tomcat-8.0.37/webapps/ONAPPORTAL/WEB-INF/lib/spring-web-4.2.3.RELEASE.jar RUN rm -v /opt/apache-tomcat-8.0.37/webapps/ONAPPORTAL/WEB-INF/lib/spring-webmvc-4.2.3.RELEASE.jar RUN rm -v /opt/apache-tomcat-8.0.37/webapps/ONAPPORTAL/WEB-INF/lib/spring-session-core-2.0.1.RELEASE.jar I still get the error about class org.openecomp.portalapp.portal.utils.CustomLoggingFilter not found, but it doesn't prevent startup BR, Juan From: [email protected] [mailto:[email protected]] On Behalf Of Postlbauer, Juan Sent: Thursday, 27 June, 2019 11:11 To: [email protected] Cc: Popokh, Leo (HPE DT) <[email protected]> Subject: [onap-discuss] #portal (Dublin) portal-app startup failure due to conflict in logback versions? I'm trying to run the master branch of integration. If manually run (with docker run) the image onap/portal-app:2.5.0 (sha256:1bbd2d4f18a49de7d2ec4f63367c69d3531a301622b5cea33c1b5e36464e5c1c), then I get the following: SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/opt/apache-tomcat-8.0.37/webapps/ONAPPORTAL/WEB-INF/lib/epsdk-music-2.2.0-SNAPSHOT-jar-with-dependencies.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/opt/apache-tomcat-8.0.37/webapps/ONAPPORTAL/WEB-INF/lib/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class] But after that warning everything runs fine. However, when the portal-app runs this image with the injected files from configmap dev-portal-portal-app-onapportal, then I get a severe error: 27-Jun-2019 07:37:44.064 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /opt/apache-tomcat-8.0.37/webapps/ONAPPORTAL SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/opt/apache-tomcat-8.0.37/webapps/ONAPPORTAL/WEB-INF/lib/epsdk-music-2.2.0-SNAPSHOT-jar-with-dependencies.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/opt/apache-tomcat-8.0.37/webapps/ONAPPORTAL/WEB-INF/lib/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class] Failed to instantiate [ch.qos.logback.classic.LoggerContext] Reported exception: java.lang.NoSuchMethodError: ch.qos.logback.core.util.Loader.getResourceOccurrenceCount(Ljava/lang/String;Ljava/lang/ClassLoader;)Ljava/util/Set; 27-Jun-2019 07:38:30.140 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/ONAPPORTAL] startup failed due to previous errors And as a result the portal is not available (If you want to reproduce it, my git clone of oom master points to commit df7fba01e18132103b9ddd6e4d64a4777323340d) Additionally, after you fix the logback version conflict you get an extra error caused by the following line in logback.xml <filter class="org.openecomp.portalapp.portal.utils.CustomLoggingFilter" /> By changing openecomp back to onap (which is what appears in the docker image) the problem goes away Am I the only one experiencing these problems? TIA, Juan -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#17876): https://lists.onap.org/g/onap-discuss/message/17876 Mute This Topic: https://lists.onap.org/mt/32315223/21656 Mute #portal: https://lists.onap.org/mk?hashtag=portal&subid=2740164 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
