Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-12-12T13:24:05Z

Elien Vergne:
Firstly thanks a lot for helping me, I appreciate. I have update my database succesfuly and now, I'm trying to import an old theme. It look like half finish...

For themes, my recommendation would be to just create a new theme, based on the look&feel of your old theme. Frontend technology moves even faster, and coming from Version 4.4, you'll probably want to take advantage of the whole mobile-optimized and other device-dependent features that are already built-in.

As you already have the full layout, it's probably quicker to create a new theme than to make sure the old one is pixel-perfect and works with the latest features. And this is just based on my expectation of work: I'd assume that it's less work to create a new one than to migrate an ancient theme.

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-12-12T10:18:52Z

Olaf Kock:

"Unsupported Major Minor Version" is a great message to google. It basically means that you're trying to execute newer Java Bytecode (e.g. Java 8, what Liferay 7.x is targeted to) on an older Java VM (e.g. Java 6, as you state). More thorough explanation of this message is easily available everywhere.

TL;DR: Any code that you got with Liferay 7.x (including the upgrade routines) need Java 8, no older Java version is sufficient.

For future error messages, please consider to post textual error messages as text, rather than as screenshots

Hello,

Firstly thanks a lot for helping me, I appreciate. I have update my database succesfuly and now, I'm trying to import an old theme. It look like half finish...

I've got some issue like this: " {code="404", msg="ProxyServlet: /o/liferay_theme_sdm/css/sdm/sdm_base", uri=/o/liferay_theme_sdm/css/sdm/sdm_base} ".

Can you explain to me, how to fix it ?

Because, i do have this files in my "module project liferay" added to my server. And some time when i modify there names, this error disapear, But it never applied my theme completly.

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-12-06T08:46:16Z

Elien Vergne:

David H Nebinger:

Everything before 7 was targeting Java 6, although Java 7 would also work.

7.x and beyond targets Java 8.

When you get that message, it typically means that some piece was compiled against a newer version of Java than what you are currently using.

So, should i use Java 6 or 7, could i execute the "com.liferay.portal.tools.db.upgrade.client.jar" from LR 7 ? Because here I'm using Java 8 and i try on jdk 1.6.0_14 too but got this message ... Something going wrong here

"Unsupported Major Minor Version" is a great message to google. It basically means that you're trying to execute newer Java Bytecode (e.g. Java 8, what Liferay 7.x is targeted to) on an older Java VM (e.g. Java 6, as you state). More thorough explanation of this message is easily available everywhere.

TL;DR: Any code that you got with Liferay 7.x (including the upgrade routines) need Java 8, no older Java version is sufficient.

For future error messages, please consider to post textual error messages as text, rather than as screenshots

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-30T08:55:55Z

David H Nebinger:

Everything before 7 was targeting Java 6, although Java 7 would also work.

7.x and beyond targets Java 8.

When you get that message, it typically means that some piece was compiled against a newer version of Java than what you are currently using.

So, should i use Java 6 or 7, could i execute the "com.liferay.portal.tools.db.upgrade.client.jar" from LR 7 ? Because here I'm using Java 8 and i try on jdk 1.6.0_14 too but got this message ... Something going wrong here

The "communication channel is about to be closed" issue I don't understand; it's a filesystem issue, so it makes me wonder what database you're actually using?

I'm using MySQL 5.6.42 and jdk 1.8.0_192. Also i have jdk 1.6.0_14 and 1.8.0_45.

Thank for taking your time,

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-29T16:20:01Z

Elien Vergne:

I'm arrived to the upgrade of my database with upgrade tools but I facing e new error : Unsupported minor major version 51...

Everything before 7 was targeting Java 6, although Java 7 would also work.

7.x and beyond targets Java 8.

When you get that message, it typically means that some piece was compiled against a newer version of Java than what you are currently using.

The "communication channel is about to be closed" issue I don't understand; it's a filesystem issue, so it makes me wonder what database you're actually using?

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-29T16:01:50Z

Richard Sezov:

Liferay 7.0:

https://dev.liferay.com/discover/deployment/-/knowledge_base/7-0/upgrading-to-liferay-7

Liferay 7.1:

https://dev.liferay.com/discover/deployment/-/knowledge_base/7-1/upgrading-to-liferay-71

Hello I'm following the liferay 7.0 upgrading process

https://dev.liferay.com/discover/deployment/-/knowledge_base/7-0/upgrading-to-liferay-7

I'm arrived to the upgrade of my database with upgrade tools but I facing e new error : Unsupported minor major version 51...

I know it's a different between the version of the compiler and the runtime of the jar, but i don't uunderstand why here ? I've got this error message.

Secondly, a little bit earlier on this week , I was facing to a new error : " The communication channel is about to be closed ". How can i fix it?

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-23T10:21:31Z

Hi ! I'm back because i'm facing an new error on my DB upgrade process... I'm on 6.1.2, when i launch the portal, it's works! but when i try to accept the Term of utilisation i getting a blank charging page and an error "java.lang.IndexOutOfBoundsExecption".

How can i fix it ?

best regard

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-15T08:49:13Z

Richard Sezov:

Hey Elien,

You don't have to guess about the procedure for upgrades. It's documented for every version you need to upgrade from. Please follow the documented upgrade instructions for each version of Liferay up to the latest version.

Liferay 5.1:

https://dev.liferay.com/documents/10184/307080/liferay-administrator-guide-5.1.pdf/9157da13-6b85-4fc0-af7d-969137da9935

Liferay 5.2:

https://dev.liferay.com/documents/10184/307080/liferay-administrator-guide-5.2.pdf/aec4dcfe-07b0-4d96-b603-71b2fe98dd34

Liferay 6.0:

https://dev.liferay.com/documents/10184/307080/liferay-administrator-guide-6.0.pdf/340b0adc-5575-49f6-8acf-a9d24ece68d9

Liferay 6.1:

https://dev.liferay.com/discover/portal/-/knowledge_base/6-1/upgrading-liferay

Liferay 6.2:

https://dev.liferay.com/discover/deployment/-/knowledge_base/6-2/upgrading-liferay

Liferay 7.0:

https://dev.liferay.com/discover/deployment/-/knowledge_base/7-0/upgrading-to-liferay-7

Liferay 7.1:

https://dev.liferay.com/discover/deployment/-/knowledge_base/7-1/upgrading-to-liferay-71

Hi, thanks a lot I appreciate , I will follow them.

David H Nebinger:

The upgrade tool cannot process upgrades before 6.1, so you need to manually do the upgrades...

First 4.4 to 5.2.

Then 5.2 to 6.0.

Then 6.0 to 6.1.

Lastly you can do 6.1 to 7.x using the DB upgrade

And for each upgrade, you need the latest bundle at that version, configure to point to your DB, then start the environ and the DB will upgrade. If you get failures during these steps, roll back the database, clean up the data issue, then restart the upgrade.

Yes, that was I was thinking about, but never have the fully information to do it .

So thank you to All of you, for your precious help!

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-14T16:39:32Z

Elien Vergne:

Ok, I've got 2 or 3 question more :

- To Launch any version i need to DL only Tomcat bundle Vx.x.x from Sourcforge and configure into my Ecplise application ?

- I've got the Liferay plugin server but I can't install any lower version than running on Tomcat 7,how can i run liferay portal into basic apache server ?

Hey Elien,

You don't have to guess about the procedure for upgrades. It's documented for every version you need to upgrade from. Please follow the documented upgrade instructions for each version of Liferay up to the latest version.

Liferay 5.1:

https://dev.liferay.com/documents/10184/307080/liferay-administrator-guide-5.1.pdf/9157da13-6b85-4fc0-af7d-969137da9935

Liferay 5.2:

https://dev.liferay.com/documents/10184/307080/liferay-administrator-guide-5.2.pdf/aec4dcfe-07b0-4d96-b603-71b2fe98dd34

Liferay 6.0:

https://dev.liferay.com/documents/10184/307080/liferay-administrator-guide-6.0.pdf/340b0adc-5575-49f6-8acf-a9d24ece68d9

Liferay 6.1:

https://dev.liferay.com/discover/portal/-/knowledge_base/6-1/upgrading-liferay

Liferay 6.2:

https://dev.liferay.com/discover/deployment/-/knowledge_base/6-2/upgrading-liferay

Liferay 7.0:

https://dev.liferay.com/discover/deployment/-/knowledge_base/7-0/upgrading-to-liferay-7

Liferay 7.1:

https://dev.liferay.com/discover/deployment/-/knowledge_base/7-1/upgrading-to-liferay-71

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-14T16:35:55Z

Elien Vergne:

So i try to launch the db_upgrade_client tools (from liferay 7.0.5 Tomcat bundle) but it shutdown with "you must upgrade yur portal to 5203"

The upgrade tool cannot process upgrades before 6.1, so you need to manually do the upgrades...

First 4.4 to 5.2.

Then 5.2 to 6.0.

Then 6.0 to 6.1.

Lastly you can do 6.1 to 7.x using the DB upgrade

And for each upgrade, you need the latest bundle at that version, configure to point to your DB, then start the environ and the DB will upgrade. If you get failures during these steps, roll back the database, clean up the data issue, then restart the upgrade.

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-14T15:24:38Z

David H Nebinger:

Wait, so upgrades are not done by executing a SQL script. If you've done it that way, you should roll back and start over.

In Liferay, an upgrade is always processed by pointing the newer version of Liferay at the old database and starting it up.

Oww ok, my bad!

This error come back when I'm trying to launch my Liferay portal 7.0.5.

I've got firstly: you must upgrade your liferay portal to 7005.

So i try to launch the db_upgrade_client tools (from liferay 7.0.5 Tomcat bundle) but it shutdown with "you must upgrade yur portal to 5203"

So I need to launch 5.2.x before 7.0.5 and surely more like (6.0.6 and 6.1 + 6.2) .

So, for example, to get to 5.2 you are going to download Liferay 5.2.x, point it at your 4.4.2 database, and then start it. It will perform a DB upgrade, changing not just the schema, but it will also update the data per necessary upgrade requirements.

Ok, I've got 2 or 3 question more :

- To Launch any version i need to DL only Tomcat bundle Vx.x.x from Sourcforge and configure into my Ecplise application ?

- I've got the Liferay plugin server but I can't install any lower version than running on Tomcat 7,how can i run liferay portal into basic apache server ?

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-14T14:21:45Z

Elien Vergne:

So, I already need your knowledge again : I'm trying to upgrade my dB manually with upgrade x.x.x-x.x.x.sql until 6.2.

Wait, so upgrades are not done by executing a SQL script. If you've done it that way, you should roll back and start over.

In Liferay, an upgrade is always processed by pointing the newer version of Liferay at the old database and starting it up.

So, for example, to get to 5.2 you are going to download Liferay 5.2.x, point it at your 4.4.2 database, and then start it. It will perform a DB upgrade, changing not just the schema, but it will also update the data per necessary upgrade requirements.

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-14T09:14:16Z

Alberto Chaparro:

Hi Elien,

Regarding the database upgrade try to follow this approach to reduce the steps and to use newer versions:

Upgrade from 4.4.2 to 6.0.6

Upgrade from 6.0.6 to 6.2

Upgrade from 6.2 to 7.0

Please, google for information about every upgrade in the forums/documentation since you will need it.

Let us know about the results.

Best regards.

Hi,

Yes, my internship mission has change a little: I've got to install Liferay 7.0 directly, migrate my dB up to 7.0 (normal) , create a new special thema for my compagny ,and try to implement 1 or 2 portlets .

So, I already need your knowledge again : I'm trying to upgrade my dB manually with upgrade x.x.x-x.x.x.sql until 6.2. And after I try to execute the upgrading tools in the V7.0 bundle.

But when I launch com.liferay.portal.tools.db.upgrade.client.jar with java -jar com.liferay.portal.tools.db.upgrade.client.jar -j "-Duser.country=US -Duser.language=en -Duser.timezone=GMT -Xmx4096m" after modifcation of the properties files to my config. I've got an error message like this :

" You must first upgrade to Liferay Portal 5203" I think it's because my dB has not move to any newest version ? Is it right ? What should i do ?

Best regards.

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-13T12:06:58Z

Hi Elien,

I already agree with Olaf and David answers in realtion to the complexity of the project taking into account the experience and deadline, the possibility of discard current developments could be a good option to reduce the time and try to adapt the future version of Liferay instead.

Regarding the database upgrade try to follow this approach to reduce the steps and to use newer versions:

Upgrade from 4.4.2 to 6.0.6
Upgrade from 6.0.6 to 6.2
Upgrade from 6.2 to 7.0

Please, google for information about every upgrade in the forums/documentation since you will need it.

Let us know about the results.

Best regards.

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-12T15:18:37Z

Elien Vergne:

Olaf Kock:

I guess this doesn't sound too compelling. However, in the beginning you stated that you're new to Liferay. And we don't know the amount of custom code that you have in your installation.

Yes, I've got 97 specifiques portlets to rewrite and I don't know if it's a lot but yes like i said I'm new on liferay framework. And i don't have any notion of how many time this work can take for me ^^. But I'm limited

97 portlets in 1 1/2 months? That's 30 working days, e.g. more than 3 portlets per day. If they're not all trivial, I'd call this impossible - especially given that you have no experience and should strive to not just "dump the code" but rather go for creating a maintainable system, at least with minimal documentation.

Plus, it doesn't include upgrading the database (or re-creating the content side of things) and learning OSGi or porting any of the non-mentioned modifications to Liferay's core.

Elien Vergne:

I'm pretty sure I can't finish on time with a stable, and filled portal.
I'll try to do my best. But thank you for your answer and your instructions .

I'd recommend to ring the alarm earlier (e.g. now) rather than later. It's an impossible task that you have in front of you. A good project manager will rather value a raised flag early in the process, rather than the empty promise "I'll do what I can", only for the inevitable event of the project status turning red on the day of planned completion.

All the best, and let us know of the problems you're running into.

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-12T13:18:07Z

Olaf Kock:

I guess this doesn't sound too compelling. However, in the beginning you stated that you're new to Liferay. And we don't know the amount of custom code that you have in your installation.

Yes, I've got 97 specifiques portlets to rewrite and I don't know if it's a lot but yes like i said I'm new on liferay framework. And i don't have any notion of how many time this work can take for me ^^. But I'm limited

To be honest, I expect it to be simpler to start over new, if only because almost nobody here will be able to help you on any code-related problems in the 4.x or 5.x series, and only few people will be able to do so on 6.x. It's just too big of a task for someone new to the framework. It's even too big of a task for someone very experienced, especially if the result should be a well documented and maintainable portal, not a quickly cobbled-together fragile thing.

Yeah, I didn't expect that when I chose this mission. Unfortunately, I'm pretty sure I can't finish on time with a stable, and filled portal.

I'll try to do my best. But thank you for your answer and your instructions .

Best regard

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-12T11:06:56Z

Elien Vergne:

So,I "just" need to upgrade my database to LR7 and rewrite all my custom code for 7.x with LR7 source and documentation code ..Nice !

I guess this doesn't sound too compelling. However, in the beginning you stated that you're new to Liferay. And we don't know the amount of custom code that you have in your installation.

Being new to Liferay - and it seems you're alone, without a team - means that you'll have to get "into the groove". And Liferay 4.x is more than 10 years old, with probably only very few people remembering it these days. As far as I remember, it was the last version based on EJB, which was discontinued in 5.x - There have been numerous changes within the past 10 years, last to the adoption of OSGi. If you have to learn about your existing code, the architectural changes in the last 10 years, and OSGi (that all on top of being new to Liferay), it seems like this is a quite big task - and even without knowing the amount of custom code that you have, most likely it's too big.

After all, your tasks will be:

identify all the customizations that have been made
identify the reason for the customizations (to judge if they're now superfluous, or if they're no longer necessary for business reasons)
identify how to port the existing and necessary customizations through the versions, into the latest version
adapt all custom portlets to latest API (in case they use any API)
adapt all custom portlets to current library versions (you don't want to bring forward the ancient libraries that someone has used in 2008, right?
implement a new theme to make the portal look like your organization's
Make sure the new portal has the same content as the old one (by upgrading the database, or by creating a portal with the same content)

To be honest, I expect it to be simpler to start over new, if only because almost nobody here will be able to help you on any code-related problems in the 4.x or 5.x series, and only few people will be able to do so on 6.x. It's just too big of a task for someone new to the framework. It's even too big of a task for someone very experienced, especially if the result should be a well documented and maintainable portal, not a quickly cobbled-together fragile thing.

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-12T10:32:00Z

Wow, I never would have guessed that anyone was still using 4.4.2...

Well, yes, me too I guess my compagny don't really appreciate changement... (This version have 10 year)

You might as well forget the code upgrade...

Liferay 4 used Prototype as the JS framework. While it may still exist, no one uses it at all AFAIK.

Your JS is no longer valid, the JSP tag libraries, locations, etc. have changed, the portal code has undergone numerous rewrites, theming has changed many times over...

There will simply be no way for you to upgrade this code.

Your only option is to completely rewrite your custom code for 7.x. Use the current documentation and source code as your specifications and requirements. Use LR7 clean development aspects and build the code correctly, themes and all.

So,I "just" need to upgrade my database to LR7 and rewrite all my custom code for 7.x with LR7 source and documentation code ..Nice !

Certainly discard all of the bad practices from 4.x such as the use of the EXT plugin (especially the ext-service) while you are rewriting code.

I will !

Thanks a lot for your quick response ,

I need to rush now (my internship end next month)

RE: Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-11T14:24:49Z

Elien Vergne:

I've got the mission for my internship to update an old liferay portal (V.4.4.2) to V7.0.

Wow, I never would have guessed that anyone was still using 4.4.2...

Caused by: java.lang.NoClassDefFoundError: javax/jms/Destination
   at java.lang.ClassLoader.defineClass1(Native Method)
   at java.lang.ClassLoader.defineClass(ClassLoader.java:621)


GRAVE: Exception au démarrage du filtre Layout Cache Filter - Layout
java.lang.NoClassDefFoundError: Could not initialize class com.liferay.portal.util.PropsUtil
   at com.liferay.portal.servlet.filters.layoutcache.LayoutCacheFilter.<clinit>(LayoutCacheFilter.java:83)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)


GRAVE: Exception au démarrage du filtre Layout Cache Filter - Friendly
java.lang.NoClassDefFoundError: Could not initialize class com.liferay.portal.servlet.filters.layoutcache.LayoutCacheFilter
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

So this kind of tells me that your environment is not quite updated correctly. Normally I wouldn't recommend trying to overlay 5.x on top of the existing 4.x; instead you just use the 5.x bundle and copy in your portal-ext.properties and other configuration elements, effectively pointing 5.x at your 4.x database. Then, when you start up, the 5.x environment should update the database when you start the environment.

I know i have a lot of work to do and i know i have to upgrade step by step the different version (4.4->5.0->5.1->5.2->6.0->6.1->etc).

Well, not really. I mean, the only thing you're really updating is the database. For this scenario, you're pointing each successive version of Liferay at your database and letting Liferay do the work when starting up.

Continue using Liferay 6 all the way through to 6.1; you won't need Java 8 until you're at the last step in the upgrade to LR7.

and we are using ext plugin (ext-impl,ext-lib,ext-service...)

You might as well forget the code upgrade...

Liferay 4 used Prototype as the JS framework. While it may still exist, no one uses it at all AFAIK.

Your JS is no longer valid, the JSP tag libraries, locations, etc. have changed, the portal code has undergone numerous rewrites, theming has changed many times over...

There will simply be no way for you to upgrade this code.

Certainly discard all of the bad practices from 4.x such as the use of the EXT plugin (especially the ext-service) while you are rewriting code.

Upgrade process 4.4.2 -> 7.0 difficulties (NEED HELP)

2018-11-09T10:53:52Z

Hello I'm student and new on liferay framework. (sorry for my verry bad english level you will understand why under ^^)

I've got the mission for my internship to update an old liferay portal (V.4.4.2) to V7.0.

I have 1 month 1/2 to realize this upgrade and I need you're help guys... I follow a lot of upgrade process but i'm always stun at the beginning... I try https://web.liferay.com/fr/community/wiki/-/wiki/Main/Upgrade+Instructions+from+4.4+to+5.0 methode but I do wrong because nothing change. I undeploy like they said my Root folder in <Tomcat Home>/webapps, Copy the new versions of the dependency .jars and try to deploy "liferay-portal-5.0.1.war" downloaded on https://sourceforge.net/projects/lportal/files/Liferay%20Portal/5.0.1%20RC . But when i restart my server this error appears :

INFO: Déploiement de l'archive liferay-portal-5.0.1.war de l'application web
Loading jar:file:/C:/PACKDEV/tomcat-6.0.36/webapps/liferay-portal-5.0.1/WEB-INF/lib/portal-impl.jar!/system.properties
Loading jar:file:/C:/PACKDEV/tomcat-6.0.36/webapps/liferay-portal-5.0.1/WEB-INF/lib/portal-impl.jar!/portal.properties
9 nov. 2018 11:39:10 org.apache.catalina.core.StandardContext filterStart
GRAVE: Exception au démarrage du filtre Secure MainServlet Filter
java.lang.ExceptionInInitializerError
   at com.liferay.portal.velocity.LiferayResourceCache.get(LiferayResourceCache.java:43)
   at org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:288)
   at org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1102)
   at org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1077)
   at org.apache.velocity.runtime.VelocimacroFactory.initVelocimacro(VelocimacroFactory.java:196)
   at org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:251)
   at org.apache.velocity.runtime.RuntimeSingleton.init(RuntimeSingleton.java:113)
   at org.apache.velocity.app.Velocity.init(Velocity.java:83)
   at com.liferay.portal.events.InitAction.run(InitAction.java:224)
   at com.liferay.portal.util.InitUtil.init(InitUtil.java:40)
   at com.liferay.portal.util.PropsUtil.<clinit>(PropsUtil.java:41)
   at com.liferay.portal.servlet.filters.secure.SecureFilter.init(SecureFilter.java:88)
   at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:295)
   at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
   at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:115)
   at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4072)
   at org.apache.catalina.core.StandardContext.start(StandardContext.java:4726)
   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
   at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)
   at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)
   at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
   at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
   at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
   at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
   at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
   at org.apache.catalina.core.StandardService.start(StandardService.java:525)
   at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
   at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.activemq.Broker' defined in class path resource [META-INF/activemq-spring-jms.xml]: Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from class path resource [META-INF/activemq.xml]; nested exception is java.lang.NoClassDefFoundError: javax/jms/Destination
   at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1260)
   at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:438)
   at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383)
   at java.security.AccessController.doPrivileged(Native Method)
   at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353)
   at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
   at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169)
   at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
   at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
   at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:394)
   at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:736)
   at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369)
   at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:123)
   at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:76)
   at com.liferay.util.spring.context.LazyClassPathApplicationContext.<init>(LazyClassPathApplicationContext.java:42)
   at com.liferay.portal.spring.util.SpringUtil.getContext(SpringUtil.java:40)
   at com.liferay.portal.bean.BeanLocatorImpl.locate(BeanLocatorImpl.java:62)
   at com.liferay.portal.bean.BeanLocatorImpl.locate(BeanLocatorImpl.java:46)
   at com.liferay.portal.kernel.bean.BeanLocatorUtil.locate(BeanLocatorUtil.java:51)
   at com.liferay.portal.kernel.cache.SingleVMPoolUtil._getUtil(SingleVMPoolUtil.java:94)
   at com.liferay.portal.kernel.cache.SingleVMPoolUtil.getSingleVMPool(SingleVMPoolUtil.java:59)
   at com.liferay.portal.kernel.cache.SingleVMPoolUtil.getCache(SingleVMPoolUtil.java:55)
   at com.liferay.portal.velocity.LiferayResourceCacheUtil.<clinit>(LiferayResourceCacheUtil.java:57)
   ... 39 more
Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from class path resource [META-INF/activemq.xml]; nested exception is java.lang.NoClassDefFoundError: javax/jms/Destination
   at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:405)
   at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:327)
   at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:295)
   at org.apache.xbean.spring.context.ResourceXmlApplicationContext.loadBeanDefinitions(ResourceXmlApplicationContext.java:111)
   at org.apache.xbean.spring.context.ResourceXmlApplicationContext.loadBeanDefinitions(ResourceXmlApplicationContext.java:104)
   at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:97)
   at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:411)
   at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:338)
   at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:88)
   at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:76)
   at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:72)
   at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:68)
   at org.apache.activemq.xbean.BrokerFactoryBean.afterPropertiesSet(BrokerFactoryBean.java:82)
   at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1288)
   at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1257)
   ... 61 more
Caused by: java.lang.NoClassDefFoundError: javax/jms/Destination
   at java.lang.ClassLoader.defineClass1(Native Method)
   at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
   at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
   at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:2854)
   at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1159)
   at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1647)
   at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526)
   at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
   at java.lang.Class.getDeclaredMethods0(Native Method)
   at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
   at java.lang.Class.getDeclaredMethods(Class.java:1791)
   at java.beans.Introspector$1.run(Introspector.java:1272)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.beans.Introspector.getPublicDeclaredMethods(Introspector.java:1270)
   at java.beans.Introspector.getTargetMethodInfo(Introspector.java:1136)
   at java.beans.Introspector.getBeanInfo(Introspector.java:387)
   at java.beans.Introspector.getBeanInfo(Introspector.java:159)
   at java.beans.Introspector.getBeanInfo(Introspector.java:220)
   at java.beans.Introspector.<init>(Introspector.java:368)
   at java.beans.Introspector.getBeanInfo(Introspector.java:159)
   at org.apache.xbean.spring.context.v2c.XBeanQNameHelper.getBeanInfo(XBeanQNameHelper.java:78)
   at org.apache.xbean.spring.context.v2c.XBeanQNameHelper.coerceNamespaceAwarePropertyValues(XBeanQNameHelper.java:54)
   at org.apache.xbean.spring.context.v2c.XBeanBeanDefinitionParserDelegate.parseBeanDefinitionElement(XBeanBeanDefinitionParserDelegate.java:63)
   at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:383)
   at org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.parseBeanFromExtensionElement(XBeanNamespaceHandler.java:208)
   at org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.parseBeanFromExtensionElement(XBeanNamespaceHandler.java:256)
   at org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.parse(XBeanNamespaceHandler.java:152)
   at org.apache.xbean.spring.context.v2.XBeanNamespaceHandler.parse(XBeanNamespaceHandler.java:49)
   at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1246)
   at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1236)
   at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:135)
   at org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.parseBeanDefinitions(XBeanBeanDefinitionDocumentReader.java:63)
   at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:92)
   at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:488)
   at org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionReader.registerBeanDefinitions(XBeanXmlBeanDefinitionReader.java:79)
   at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:383)
   ... 75 more
Caused by: java.lang.ClassNotFoundException: javax.jms.Destination
   at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1680)
   at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526)
   at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
   ... 111 more
9 nov. 2018 11:39:10 org.apache.catalina.core.StandardContext filterStart
GRAVE: Exception au démarrage du filtre Layout Cache Filter - Layout
java.lang.NoClassDefFoundError: Could not initialize class com.liferay.portal.util.PropsUtil
   at com.liferay.portal.servlet.filters.layoutcache.LayoutCacheFilter.<clinit>(LayoutCacheFilter.java:83)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
   at java.lang.Class.newInstance0(Class.java:355)
   at java.lang.Class.newInstance(Class.java:308)
   at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
   at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
   at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:115)
   at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4072)
   at org.apache.catalina.core.StandardContext.start(StandardContext.java:4726)
   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
   at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)
   at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)
   at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
   at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
   at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
   at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
   at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
   at org.apache.catalina.core.StandardService.start(StandardService.java:525)
   at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
   at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
9 nov. 2018 11:39:10 org.apache.catalina.core.StandardContext filterStart
GRAVE: Exception au démarrage du filtre Session Id Filter
java.lang.NoClassDefFoundError: Could not initialize class com.liferay.portal.util.PropsUtil
   at com.liferay.portal.servlet.filters.sessionid.SessionIdFilter.<clinit>(SessionIdFilter.java:53)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
   at java.lang.Class.newInstance0(Class.java:355)
   at java.lang.Class.newInstance(Class.java:308)
   at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
   at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
   at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:115)
   at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4072)
   at org.apache.catalina.core.StandardContext.start(StandardContext.java:4726)
   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
   at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)
   at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)
   at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
   at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
   at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
   at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
   at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
   at org.apache.catalina.core.StandardService.start(StandardService.java:525)
   at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
   at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
9 nov. 2018 11:39:10 org.apache.catalina.core.StandardContext filterStart
GRAVE: Exception au démarrage du filtre Compression Filter
java.lang.NoClassDefFoundError: Could not initialize class com.liferay.portal.util.PropsUtil
   at com.liferay.portal.servlet.filters.compression.CompressionFilter.<clinit>(CompressionFilter.java:56)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
   at java.lang.Class.newInstance0(Class.java:355)
   at java.lang.Class.newInstance(Class.java:308)
   at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
   at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
   at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:115)
   at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4072)
   at org.apache.catalina.core.StandardContext.start(StandardContext.java:4726)
   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
   at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)
   at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)
   at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
   at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
   at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
   at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
   at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
   at org.apache.catalina.core.StandardService.start(StandardService.java:525)
   at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
   at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
9 nov. 2018 11:39:10 org.apache.catalina.core.StandardContext filterStart
GRAVE: Exception au démarrage du filtre Velocity Filter
java.lang.NoClassDefFoundError: Could not initialize class com.liferay.portal.util.PropsUtil
   at com.liferay.portal.servlet.filters.velocity.VelocityFilter.<clinit>(VelocityFilter.java:78)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
   at java.lang.Class.newInstance0(Class.java:355)
   at java.lang.Class.newInstance(Class.java:308)
   at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
   at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
   at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:115)
   at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4072)
   at org.apache.catalina.core.StandardContext.start(StandardContext.java:4726)
   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
   at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)
   at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)
   at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
   at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
   at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
   at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
   at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
   at org.apache.catalina.core.StandardService.start(StandardService.java:525)
   at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
   at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
9 nov. 2018 11:39:10 org.apache.catalina.core.StandardContext filterStart
GRAVE: Exception au démarrage du filtre Virtual Host Filter
java.lang.NoClassDefFoundError: Could not initialize class com.liferay.portal.util.PropsUtil
   at com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.<clinit>(VirtualHostFilter.java:76)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
   at java.lang.Class.newInstance0(Class.java:355)
   at java.lang.Class.newInstance(Class.java:308)
   at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
   at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
   at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:115)
   at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4072)
   at org.apache.catalina.core.StandardContext.start(StandardContext.java:4726)
   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
   at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)
   at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)
   at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
   at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
   at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
   at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
   at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
   at org.apache.catalina.core.StandardService.start(StandardService.java:525)
   at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
   at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
9 nov. 2018 11:39:10 org.apache.catalina.core.StandardContext filterStart
GRAVE: Exception au démarrage du filtre Double Click Filter
java.lang.NoClassDefFoundError: Could not initialize class com.liferay.portal.util.PropsUtil
   at com.liferay.portal.servlet.filters.doubleclick.DoubleClickFilter.<clinit>(DoubleClickFilter.java:56)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
   at java.lang.Class.newInstance0(Class.java:355)
   at java.lang.Class.newInstance(Class.java:308)
   at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
   at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
   at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:115)
   at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4072)
   at org.apache.catalina.core.StandardContext.start(StandardContext.java:4726)
   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
   at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)
   at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)
   at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
   at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
   at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
   at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
   at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
   at org.apache.catalina.core.StandardService.start(StandardService.java:525)
   at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
   at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
9 nov. 2018 11:39:10 org.apache.catalina.core.StandardContext filterStart
GRAVE: Exception au démarrage du filtre Layout Cache Filter - Friendly
java.lang.NoClassDefFoundError: Could not initialize class com.liferay.portal.servlet.filters.layoutcache.LayoutCacheFilter
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
   at java.lang.Class.newInstance0(Class.java:355)
   at java.lang.Class.newInstance(Class.java:308)
   at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
   at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
   at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:115)
   at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4072)
   at org.apache.catalina.core.StandardContext.start(StandardContext.java:4726)
   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
   at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)
   at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)
   at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
   at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
   at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
   at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
   at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
   at org.apache.catalina.core.StandardService.start(StandardService.java:525)
   at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
   at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
9 nov. 2018 11:39:10 org.apache.catalina.core.StandardContext filterStart
GRAVE: Exception au démarrage du filtre Layout Cache Filter - Resource
java.lang.NoClassDefFoundError: Could not initialize class com.liferay.portal.servlet.filters.layoutcache.LayoutCacheFilter
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
   at java.lang.Class.newInstance0(Class.java:355)
   at java.lang.Class.newInstance(Class.java:308)
   at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
   at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
   at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:115)
   at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4072)
   at org.apache.catalina.core.StandardContext.start(StandardContext.java:4726)
   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
   at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)
   at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)
   at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
   at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
   at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
   at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
   at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
   at org.apache.catalina.core.StandardService.start(StandardService.java:525)
   at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
   at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
9 nov. 2018 11:39:10 org.apache.catalina.core.StandardContext filterStart
GRAVE: Exception au démarrage du filtre Strip Filter
java.lang.NoClassDefFoundError: Could not initialize class com.liferay.portal.util.PropsUtil
   at com.liferay.portal.servlet.filters.strip.StripFilter.<clinit>(StripFilter.java:56)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
   at java.lang.Class.newInstance0(Class.java:355)
   at java.lang.Class.newInstance(Class.java:308)
   at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
   at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
   at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:115)
   at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4072)
   at org.apache.catalina.core.StandardContext.start(StandardContext.java:4726)
   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
   at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)
   at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)
   at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
   at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
   at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
   at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
   at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
   at org.apache.catalina.core.StandardService.start(StandardService.java:525)
   at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
   at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

I know i have a lot of work to do and i know i have to upgrade step by step the different version (4.4->5.0->5.1->5.2->6.0->6.1->etc).

I have MySQL 5.6.42 ,

jdk 1.6.0_14 but need to move to 1.8.0_45 for the final result

Tomcat 6.0.36 , Tomcat 8.0.21

I'm using ecplise Luna

and we are using ext plugin (ext-impl,ext-lib,ext-service...)

Do you have any solution ? I'll be greatful \o/

Best regard

And sorry again for my english level