tracker issue : CF-4204036

select a category, or use search below
(searches all categories and all time range)
Title:

Enterprise Manager page link appears in the Administrator Console of a ColdFusion instance. Clicking on it results in an error.

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): A. B. / ()

Created: 02/20/2019

Components: Administrator, Administrator Console

Versions: 2018

Failure Type: Incorrectly functioning

Found In Build/Fixed In Build: 2018.0.01.311402 / 2018.0.04.314203

Priority/Frequency: Normal / Some users will encounter

Locale/System: / Win 2016

Vote Count: 0

Problem Description: When I create a new instance in the usual way in ColdFusion 2018, the instance's Administrator console contains the Enterprise Manager page link. When I click on the link I get an error. See attached printscreens. 

Steps to Reproduce:
1) Create a new ColdFusion instance in the usual way (in the ColdFusion Administrator).
2) Open the new instance's ColdFusion Administrator.
3) click on the link to the Enterprise Manager page.

Actual Result:
You will see in the leftmost column a link to the Enterprise Manager page. 
When you click on it, you get the following error (in the instance's exception.log):

"Error","http-nio-8602-exec-10","02/20/19","11:51:22","cfadmin","Variable PROCESSSERVER is undefined. The specific sequence of files included or processed is: D:\Coldfusion2018\t1studiestaging2018\wwwroot\CFIDE\administrator\entman\index.cfm, line: 13 "
coldfusion.runtime.UndefinedVariableException: Variable PROCESSSERVER is undefined.
	at coldfusion.runtime.CfJspPage._get(CfJspPage.java:455)
	at coldfusion.runtime.CfJspPage._get(CfJspPage.java:421)
	at coldfusion.runtime.CfJspPage._get(CfJspPage.java:400)
	at cfserverlist2ecfm1422983201._factor9(D:\Coldfusion2018\t1studiestaging2018\wwwroot\CFIDE\administrator\entman\serverlist.cfm:13)
	at cfserverlist2ecfm1422983201.runPage(D:\Coldfusion2018\t1studiestaging2018\wwwroot\CFIDE\administrator\entman\serverlist.cfm:1)
	at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:262)
	at coldfusion.tagext.lang.IncludeTag.handlePageInvoke(IncludeTag.java:729)
	at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:565)
	at coldfusion.runtime.CfJspPage._emptyTcfTag(CfJspPage.java:4082)
	at cfindex2ecfm1803757194.runPage(D:\Coldfusion2018\t1studiestaging2018\wwwroot\CFIDE\administrator\entman\index.cfm:327)
	at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:262)
	at coldfusion.tagext.lang.IncludeTag.handlePageInvoke(IncludeTag.java:729)
	at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:565)
	at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65)
	at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:597)
	at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:43)
	at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40)
	at coldfusion.filter.PathFilter.invoke(PathFilter.java:162)
	at coldfusion.filter.IpFilter.invoke(IpFilter.java:45)
	at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:96)
	at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28)
	at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38)
	at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:60)
	at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
	at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
	at coldfusion.filter.CachingFilter.invoke(CachingFilter.java:62)
	at coldfusion.CfmServlet.service(CfmServlet.java:226)
	at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:311)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
	at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:46)
	at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:47)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
	at coldfusion.filter.ClickjackingProtectionFilter.doFilter(ClickjackingProtectionFilter.java:75)
	at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:47)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:491)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:357)
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:408)
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:764)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1388)
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.base/java.lang.Thread.run(Thread.java:844)

Expected Result:
No link to the Enterprise Manager page.
Consequently no error.

Any Workarounds:
No relevant.

Attachments:

Comments:

Hi , I couldn't able to reproduce the issue in ColdFusion 2018 update1 in windows machine. Can you clear browser cache and let us know if it issue persist? Also, please check in other browser for the issue.  Did created the instance before the update or after the update ?   Thanks, Mukesh
Comment by Mukesh K.
30388 | February 25, 2019 08:11:43 AM GMT
Hi Mukesh, Thank you for your reply. I duly opened a different browser window (Firefox, whereas I had previously used Chrome) and cleared the cache. Then I opened the CFAdmin page of an instance different from the main instance, cfusion. It contains a link to the Enterprise Manager: the issue. See latest printscreen. The ColdFusion build number is 2018.0.02.313961
Comment by A. B.
30393 | February 26, 2019 11:47:38 AM GMT
latest printscreen: Enterprise_Manager_link_in_instance_CFAdmin.png
Comment by A. B.
30395 | February 26, 2019 12:29:41 PM GMT
A.B, you say you are running on update 2. I am unable to reproduce this problem on u2. I do NOT see a link to the Enterprise Manager within a created instance. Now, Mukesh had asked if you created the instance BEFORE that. Can you please confirm? To be clear, I created the instance WHILE ON update 2, and again am NOT seeing the EM on the left in the instance. (And what we're getting at is that if you may have created the instance BEFORE updating TO update 2, the problem could have been created at instance creation time.) And to be clear, for readers who may wonder: we should NOT see the Enterprise Manager menu (the ability to list and/or create new instances and clusters) within any by the main CFUSION instance. If you DO see it in any other instance, that is a bug, not expected behavior. And as such, the error at the top is not the REAL bug. It would seem that error is happening BECAUSE you are (by some mistake) seeing the EM in an instance other than the cfusion one.
Comment by Charlie A.
30807 | May 22, 2019 06:20:08 PM GMT
Ah, an update to my last comment. I see the problem DOES happen on update 3 (not 2), which is unfortunate. But some very good news is that I notice now that this bug is now listed here (on the top right) as "fixed" in update 4, which is to come. FWIW, I had tested update 2 (creating an instance on it, looking for the ent man in that instance) because A.B. had referred to being on that update (reporting in a comment above on 2/29 that "The ColdFusion build number is 2018.0.02.313961"). Then I went ahead and updated to update 3 and tried again, and I DO see the behavior. That's really odd (that I experienced it on u3 and NOT u2), as A.B. first reported it happening on update 1 (see the "found in build" on the top right, when this was opened on 2/20), then in u2 (per that comment), and now it's indicated to be fixed in 4. To be clear, I not only confirmed I could not SEE the Ent Man link on the left, but I also could not RUN the entman url (CFIDE/administrator/entman/index.cfm) on that instance I created, while on update 2. But now after applying u3 (to both my cfusion and that new instance), not only do I see that entman menu item on the left within the new instance, but also that entman URL *DOES WORK * in the instance. More important, I can confirm that in the hotfix_filelist.log (in hf-updates within the instance) I can literally SEE that the update IS *adding* the entman folder and files to the instance, which again is clearly a mistake. instances should not have that. So again, the fact that Adobe says they are fixing this in u4 is great news. (I hope they will not only prevent new instances from having those entman folder/files but also remove them from already-created instances other than the cfusion one.)
Comment by Charlie A.
30808 | May 22, 2019 06:43:34 PM GMT
The Enterprise Manager created a bug. The Adobe team has dealt with it. All's well that ends well. :)
Comment by A. B.
30815 | May 23, 2019 06:22:39 PM GMT