Bug reccurent

Ricardo Djoumessi · le 30/10/18 à 17:39

En effet, j'ai constamment cette erreur. s'il vous plait ce serait dû à quoi concrètement.

 

17:33:24,459 FATAL [JCMS 9] [ChannelInitServlet] - An exception occured while initializing JCMS. The site is not available.
java.lang.Error: Unresolved compilation problems:
The method add(Data, Map, String) in the type AbstractLinkIndexListener is not applicable for the arguments (ConversationSpace, Group, String)
The method add(Data, Map, String) in the type AbstractLinkIndexListener is not applicable for the arguments (ConversationSpace, Group, String)
The method add(Data, Map, String) in the type AbstractLinkIndexListener is not applicable for the arguments (ConversationSpaceCommunity, SocialFAQ, String)
The method add(Data, Map, String) in the type AbstractLinkIndexListener is not applicable for the arguments (ConversationSpaceCommunity, SocialSuggestionBox, String)
The method add(Data, Map, String) in the type AbstractLinkIndexListener is not applicable for the arguments (ConversationSpaceCommunity, SocialForum, String)
The method add(Data, Map, String) in the type AbstractLinkIndexListener is not applicable for the arguments (PortletConversationSpace, ConversationSpace, String)
The method add(Data, Map, String) in the type AbstractLinkIndexListener is not applicable for the arguments (SocialFAQ, Group, String)
The method add(Data, Map, String) in the type AbstractLinkIndexListener is not applicable for the arguments (SocialFAQ, Group, String)
The method add(Data, Map, String) in the type AbstractLinkIndexListener is not applicable for the arguments (SocialForum, Group, String)
The method add(Data, Map, String) in the type AbstractLinkIndexListener is not applicable for the arguments (SocialForum, Group, String)
The method add(Data, Map, String) in the type AbstractLinkIndexListener is not applicable for the arguments (SocialSuggestionBox, Group, String)
The method add(Data, Map, String) in the type AbstractLinkIndexListener is not applicable for the arguments (SocialSuggestionBox, Group, String)
The method add(Data, Map, String) in the type AbstractLinkIndexListener is not applicable for the arguments (CalendarEvent, Group[], String)
The method add(Data, Map, String) in the type AbstractLinkIndexListener is not applicable for the arguments (CalendarEvent, Member[], String)
The method add(Data, Map, String) in the type AbstractLinkIndexListener is not applicable for the arguments (CalendarEvent, AbstractEventResource[], String)
The method add(Data, Map, String) in the type AbstractLinkIndexListener is not applicable for the arguments (CalendarEvent, FileDocument[], String)
The method getNewsletter() from the type NewsletterContent refers to the missing type AbstractNewsletter
The method getNewsletter() from the type AbstractNewsletterContentCustom refers to the missing type AbstractNewsletter
The method getNewsletter() from the type AbstractNewsletterContentCustom refers to the missing type AbstractNewsletter

at generated.LinkIndexListener.handleCreate(LinkIndexListener.java:93)
at com.jalios.jstore.Store.notifyCreate(Store.java:1664)
at com.jalios.jstore.Store.processStorableLogEntry(Store.java:752)
at com.jalios.jstore.LogManagerLoadHandler.processStorableLogEntry(LogManagerLoadHandler.java:129)
at com.jalios.jstore.LogManagerHandler.startElement(LogManagerHandler.java:95)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at com.jalios.jstore.LogManager.parseLog(LogManager.java:364)
at com.jalios.jstore.LogManager.parseLog(LogManager.java:324)
at com.jalios.jstore.LogManager.load(LogManager.java:145)
at com.jalios.jstore.Store.load(Store.java:554)
at com.jalios.jstore.Store.load(Store.java:539)
at com.jalios.jcms.Channel.loadStore(Channel.java:1325)
at com.jalios.jcms.ChannelInitServlet.init(ChannelInitServlet.java:127)
at com.jalios.jcms.ChannelInitServlet.init(ChannelInitServlet.java:81)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1284)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1197)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5231)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5518)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1575)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1565)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
oct. 30, 2018 5:33:24 PM org.apache.catalina.core.StandardContext loadOnStartup
GRAVE: La servlet /jcms a généré une exception "load()"
javax.servlet.ServletException: An exception occured while initializing JCMS. The site is not available.
at com.jalios.jcms.ChannelInitServlet.init(ChannelInitServlet.java:187)
at com.jalios.jcms.ChannelInitServlet.init(ChannelInitServlet.java:81)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1284)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1197)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5231)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5518)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1575)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1565)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

oct. 30, 2018 5:33:24 PM org.apache.catalina.startup.HostConfig deployDirectory
INFOS: Déploiement du répertoire C:\JALIOS\DevPack-JCMS-9.0.4\tomcat\bin de l'application web
oct. 30, 2018 5:33:24 PM org.apache.catalina.startup.HostConfig deployDirectory
INFOS: Deployment of web application directory C:\JALIOS\DevPack-JCMS-9.0.4\tomcat\bin has finished in 31 ms
oct. 30, 2018 5:33:24 PM org.apache.catalina.startup.HostConfig deployDirectory
INFOS: Déploiement du répertoire C:\JALIOS\DevPack-JCMS-9.0.4\tomcat\conf de l'application web
oct. 30, 2018 5:33:24 PM org.apache.catalina.startup.HostConfig deployDirectory
INFOS: Deployment of web application directory C:\JALIOS\DevPack-JCMS-9.0.4\tomcat\conf has finished in 24 ms
oct. 30, 2018 5:33:24 PM org.apache.catalina.startup.HostConfig deployDirectory
INFOS: Déploiement du répertoire C:\JALIOS\DevPack-JCMS-9.0.4\tomcat\lib de l'application web
oct. 30, 2018 5:33:24 PM org.apache.catalina.startup.HostConfig deployDirectory
INFOS: Deployment of web application directory C:\JALIOS\DevPack-JCMS-9.0.4\tomcat\lib has finished in 38 ms
oct. 30, 2018 5:33:24 PM org.apache.catalina.startup.HostConfig deployDirectory
INFOS: Déploiement du répertoire C:\JALIOS\DevPack-JCMS-9.0.4\tomcat\logs de l'application web
oct. 30, 2018 5:33:24 PM org.apache.catalina.startup.HostConfig deployDirectory
INFOS: Deployment of web application directory C:\JALIOS\DevPack-JCMS-9.0.4\tomcat\logs has finished in 33 ms
oct. 30, 2018 5:33:24 PM org.apache.catalina.startup.HostConfig deployDirectory
INFOS: Déploiement du répertoire C:\JALIOS\DevPack-JCMS-9.0.4\tomcat\temp de l'application web
oct. 30, 2018 5:33:24 PM org.apache.catalina.startup.HostConfig deployDirectory
INFOS: Deployment of web application directory C:\JALIOS\DevPack-JCMS-9.0.4\tomcat\temp has finished in 30 ms
oct. 30, 2018 5:33:24 PM org.apache.catalina.startup.HostConfig deployDirectory
INFOS: Déploiement du répertoire C:\JALIOS\DevPack-JCMS-9.0.4\tomcat\webapps de l'application web
oct. 30, 2018 5:33:24 PM org.apache.catalina.startup.HostConfig deployDirectory
INFOS: Deployment of web application directory C:\JALIOS\DevPack-JCMS-9.0.4\tomcat\webapps has finished in 27 ms
oct. 30, 2018 5:33:24 PM org.apache.catalina.startup.HostConfig deployDirectory
INFOS: Déploiement du répertoire C:\JALIOS\DevPack-JCMS-9.0.4\tomcat\work de l'application web
oct. 30, 2018 5:33:24 PM org.apache.catalina.startup.HostConfig deployDirectory
INFOS: Deployment of web application directory C:\JALIOS\DevPack-JCMS-9.0.4\tomcat\work has finished in 28 ms
oct. 30, 2018 5:33:24 PM org.apache.coyote.AbstractProtocol start
INFOS: Starting ProtocolHandler ["http-bio-8080"]
oct. 30, 2018 5:33:24 PM org.apache.coyote.AbstractProtocol start
INFOS: Starting ProtocolHandler ["ajp-bio-8009"]
oct. 30, 2018 5:33:24 PM org.apache.catalina.startup.Catalina start
INFOS: Server startup in 5882 ms

#1

Bonjour,

Utilisez-vous le dev-pack?

Quelle est la version du Jalios utilisée?

Seifallah Bellassoued · le 02/11/18 à 17:32
#2

Si vous utiliser le dev-pack je pense que vous avez ajouté un module mais vous n'avez pas ajouté son jar au build path du projet

Seifallah Bellassoued · le 02/11/18 à 17:37
#3

Merci pour cette nouvelle conversation.

En cas de nécessité, vous pouvez créer un ticket dans votre espace support en référençant cette conversation.

Cordialement.

Support Jalios · le 07/11/18 à 00:30
4 pts
Aline Taguet · le 28/12/18 à 15:00

Boonjour,

Merci pour cette demande, comme l'a indiqué  @Seifallah Bellassoued , il semblerait que le jar du dev pack n'est pas configuré correctement sur votre serveur d'applications.

Si vous avez besoin d'un accompagnement, vous pouvez contacter nos services professionnels ( @Nicolas Dupont ) ou, si vous avez un contrat de support, contacter le support technique ( @Alain D'heygère )

Cordialement,

0 pt