We've recently updated from 6.1.1 to 6.4.1. We never used the AMC in 6.1.1...but in the configuration page in the TAC it was always green.
Now we've upgraded to 6.4.1 and the configuration is always red - no error message like 'invalid URL' - just a big red dot. I can connect to the DB fine in the 'Activity Monitoring Center' connection page - but I get an "AMC is not valid. Message is: null"
In PROD - which is still 6.1.1 - we get a green light on config, but a different error when using the AMC. This looks to me like possibly the same issue - so we've never had it setup correctly I'm assuming.
We've grown a lot with Talend over the last year; and now with 6.4.1 we'd like to start using the AMC so any assistance would be appreciated.
Update - I opened a ticket and after trying numerous configurations we were able to resolve the issue finally by deleting the Tomcat "Work" and 'Temp" folder contents, and re-deploying the AMC. The Talend engineer indicated he has seen very strange issues with Tomcat and by removing all folder content we were basically flushing the cache - and that eliminated the issue on our end.
We installed the AMC along with the TAC war files - same location. Webapps has the Admin(TAC) and AMC apps.
When I change the URL on the config setting to an invalid URL I get the proper message in the TAC that the URL is invalid or the AMC is not running. When i then set it to the correct URL I get the red exclamation mark - but no message letting me know what the issue is. I checked the logs and found this in the localhost log:
Sep 07, 2017 9:02:52 AM org.apache.catalina.core.StandardWrapperValve invoke SEVERE: Servlet.service() for servlet [equinoxbridgeservlet] in context with path [/amc] threw exception java.lang.IllegalArgumentException: Entry point not found: amc at org.eclipse.rwt.internal.lifecycle.EntryPointUtil.getEntryPointByName(EntryPointUtil.java:94) at org.eclipse.rwt.internal.lifecycle.EntryPointUtil.findByStartupParameter(EntryPointUtil.java:64) at org.eclipse.rwt.internal.lifecycle.EntryPointUtil.findCurrentEntryPointRegistration(EntryPointUtil.java:46) at org.eclipse.rwt.internal.lifecycle.EntryPointUtil.getCurrentEntryPointProperties(EntryPointUtil.java:40) at org.eclipse.rwt.internal.service.StartupPageConfigurer.applyEntryPointProperties(StartupPageConfigurer.java:190) at org.eclipse.rwt.internal.service.StartupPageConfigurer.getTemplate(StartupPageConfigurer.java:77) at org.eclipse.rwt.internal.service.StartupPage.send(StartupPage.java:44) at org.eclipse.rwt.internal.service.LifeCycleServiceHandler.handleGetRequest(LifeCycleServiceHandler.java:77) at org.eclipse.rwt.internal.service.LifeCycleServiceHandler.synchronizedService(LifeCycleServiceHandler.java:64) at org.eclipse.rwt.internal.service.LifeCycleServiceHandler.service(LifeCycleServiceHandler.java:58) at org.eclipse.rwt.engine.RWTServlet.handleValidRequest(RWTServlet.java:101) at org.eclipse.rwt.engine.RWTServlet.doPost(RWTServlet.java:80) at org.eclipse.rwt.engine.RWTServlet.doGet(RWTServlet.java:72) at javax.servlet.http.HttpServlet.service(HttpServlet.java:621) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.eclipse.rap.rwt.osgi.internal.CutOffContextPathWrapper.service(CutOffContextPathWrapper.java:106) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:60) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:152) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:200) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310) 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)
With your 6.4.1 Big Data Platform, could you please create a case on talend support portal so that we can give you a remote assistance(webex) through support cycle with priority?
Update - I opened a ticket and after trying numerous configurations we were able to resolve the issue finally by deleting the Tomcat "Work" and 'Temp" folder contents, and re-deploying the AMC. The Talend engineer indicated he has seen very strange issues with Tomcat and by removing all folder content we were basically flushing the cache - and that eliminated the issue on our end.
