Project

General

Profile

Actions

Incident #5589

closed

The tagme webapp doesn't work anymore after the smartgears ugprade

Added by Andrea Dell'Amico over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Urgent
Category:
System Application
Target version:
Start date:
Oct 27, 2016
Due date:
% Done:

100%

Estimated time:
1.00 h
Infrastructure:
Production

Description

Tagme is not working after the upgrade to the new smartegears 2. On the smartgears front all is working correctly, but tagme fails with the following exception:

2016-10-27 18:27:45,332 [catalina-exec-5] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/tagme].[TAGME]- Allocate exception for servlet TAGME
it.acubelab.tagme.config.ConfigurationException: The path of TAGME config file is empty and the JVM System Property tagme.config is not set
        at it.acubelab.tagme.config.TagmeConfig.init(TagmeConfig.java:104)
        at it.acubelab.tagme.config.TagmeConfig.init(TagmeConfig.java:89)
        at it.acubelab.tagme.config.TagmeConfig.init(TagmeConfig.java:153)
        at it.acubelab.tagme.web.TagmeServlet.init(TagmeServlet.java:68)
        at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1279)
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1192)
        at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:864)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:134)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
        at it.acubelab.tagme.web.SetCharEncodingValve.invoke(SetCharEncodingValve.java:18)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
        at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
        at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:683)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
        at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1041)
        at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
        at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313)
        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)

Can you investigate? I don't know how to intervene.


Related issues

Related to D4Science Infrastructure - Incident #5591: The new authorization service stops respondingClosedLucio LeliiOct 28, 2016

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)