Sirex, I think your only remaining problem is that the pdf service reports it can't be started, right? If so, try this one last step (mentioned by bkbk  previously above, but the order of doing it is important).   On the pdf services page, edit your localhost service, but without any need of change, click the "update" button.  Then try starting it. Then test your pdf.   And if your ORIGINAL problem remains, that's a different matter.  ... View more

But we don't need to see a comparison of the dump when things fail vs when you add tostring to get it to work. We need to see the dump of the manager variable when the data causes the split to fail vs when the data lets it work.   And please don't use the text format but the traditional html one, with the extra info that may convey regarding the contents of that object. Feel free to take a screenshot of the dumps.  ... View more

I'll try to create a cf2023 update of that specific compose file, and will confirm it works then will post it in the repo.   As for yo/down vs stop/start, I hear you feeling the latter is more common. I've not experienced that, but we can have differing opinion. I'll also try to test doing that, in case I might learn anything to help you with. Or perhaps someone else already will know.   Finally, it's not new that the pdfg has been in a separate service. It's always been since it (and cfhtmltopdf) came out in cf11. More important to your concern here, it's been a separate process launched within the container setup since Adobe created the docket images originally with CF2016.  ... View more

V, you've focused incorrectly on the second point in my reply, without regard to my far more important first point (these are STILL your cf startup logs from 6 months ago) and last point (how to get you the right uodate log). Please reconsider those two points.  ... View more

First, those log lines are from 6 months ago. Besides getting correct ones, it could help if you'd put them in a code block to help separate them from your own words. We're having to scroll now thousands of lines in this thread.    As for your not finding an update install log in the instance's hf-updates folder, you may have applied the update using the cfusion instance, in which case the log lines for the update of this instance are in the hf-updates folder for that cfusion instance.  ... View more

Because you have some code that's creating objects that can't be gc'ed. Changing gc algorithms is not the solution.   And your move to cf2023 is no more likely the cause for you than it was for Dave, who originally opened this discussion.   Perhaps like him you might simply be suffering from unexpected new rates of bot traffic. Your first screenshot shows you getting about 30 cf requests per second. Is that to be expected? If you still have your cf2018 available, and was it running fr, within the past 30 days? If so, then you could view the fr archived metrics to see its depiction of requests per second when traffic was going through that cf2018 instance.   You could also look at your daily, weekly, and monthly fr reports (if you configured fr to send you email), which also track the count of requests against cf. Did those counts change over time?   If none of those prove helpful, have you read all the discussions in these 4 pages of messages, offering various diagnostic ideas? ... View more

Can you please consider what I wrote last night, in another thread here.  ... View more

You have not succeeded in that desire, otherwise I wouldn't be asking. Anyway, my question was for Patrick. If he opts not to reply, then I leave what I said for the sake of others. ... View more

My focus is on how some of his cfldap query results would work but not others, as well as the asserted change being due to the recent cf update.   I don't see how your conclusion closes those considerations. ... View more

While everyone seems happy to declare totring as the winning answer (with the two responses about that being marked as the "answers"), I'd contend this issue still begs unanswered questions.   First Patrick, I'd asked you just above to do a dump of the variable when it fails. It would be very interesting to know what that shows vs when it works. Then we may be able to get to the root cause problem.   One other thing: this could even be one of those sort of problems solved by clearing the felix-cache (as discussed in the update technote) vs making code changes. That affects the underlying Java objects and methods in a way that could well be where your issue arise.   I appreciate you may be happy to have found "any solution", but l would lament if future readers saw those two currently marked answers about tostring if that proved ultimately to be an unnecessary workaround. Sadly most won't read the rest to hear if this might be the alternative root cause solution.  ... View more

Until you solve the problem of the second instance failing on startup, take it out of the cluster so that your requests don't fail when the load balancer sends traffic to it.    As for the instance failing on startup, I don't think that will be related at all to it being in a cluster. (You can confirm that once it's been removed and you restart it.) What changed since it last ran? Did you perhaps update cf? If so, perhaps you had a failure then (see the update's install log in the hf-updates folder) --or on the first startup after that, which is when package updates happen (see the coldfusion-out.log for the instance, at the time of the update).  ... View more

freeman, I think your problem is not what you presume--but I still hope I can offer a couple of things to help.   First, the screenshots do not match your assertions: the heap does not show being "full" (top right corner of first graph, top left corner of second). And while the oldgen (second column/third row in second graph) is indeed growing, it's barely half its max.   Second, you say these screenshots are what you see when CF "becomes unresponsive". The first screenshot shows being taken at your 16:53:30 CET. As FR was able to show you this screen, then it would seem CF was responsive (as this FR on-prem UI runs WITHIN the JVM along with CF).    Perhaps as important, the right side of the top left 4 graphs (of that first screenshot) show there is NO activity (no running or incoming requests or queries) in the 15 seconds before this point in time--though the top right heap graph and bottom right CPU graphs show they are being populated right up to the time of the screenshot.    If that inactivity is what you're referring to (perhaps you or customers are making requests which "hang"), I would contend that your problem is not "in CF" nor "in the jvm" (and not related to the heap or the GCs). Instead, it seems CF is no longer being GIVEN requests to run...and for that I would suggest a possible culprit is that web server connector (or the web server, whether IIS or Apache), or perhaps something in front of those.   I'll repeat: if FR was RESPONSIVE and these graphs were updating during this time, then CF was "fine".  If instead you may say "oh, no. once I took the screenshot I then found that FR was itself no longer updating", that would be very different.   But then I would ask then whether you are accessing FR through its builtin web server port (like 8088) or using FR's capability to use a modified url without a port (yourdomain/fusionreactor.cfm/findex.htm) to respond by way of your web server (like IIS or Apache). If the latter case, then if the web server or connector stopped letting traffic into CF it would also stop letting that modified URL through as well.   FWIW I'll note that your second graph DOES show that the "code heap" graph is approaching its max. That is controlled (indirectly) by a JVM arg called ReservedCodeCacheSize, which defaults to 240m on most modern OS's and JVM versions...and your max of 116 is consistent with that default (which is split inobviously among the 3 codeheap memory spaces). In any case, hitting that max won't make CF hang: it would just prevent JIT compilation in the JVM--which might have some impact, but not what you're seeing.   You should take look as well at your coldfusion-error.log file, to see if it contains any sort of outofmemory error. just before this hangup That WOULD indicate if CF was indeed hitting any such heap or other memory error. My sense is you'll find none.   Finally, if indeed this issue you're having proves to be unrelated to the original post's contention of a "memory leak in cf2023" (which turned out instead to be an impact of excessive automated traffic), you may want to consider creating a new discussion. This one's few dozen replies are now split over 4 "pages" in this forum's UI...and that will make it ever harder for you to get casual readers to see (let alone, reply) to your issue. Not a command, just a suggestion. ... View more

You can have what you want, and the resolution may well be a simple one. But I'm afraid there's just too much to consider (for your various issues) such that it seems it will not be readily solved via back and forth here. Perhaps someone else will help that way.   But I will say that if you "just want it solved" (working with either apache or iis, whether locally or via your public IP, and without any delay difference between those), I feel confident that we can achieve that via a remote screenshare consulting session. I don't think it would take even a hour--though I can't promise that.   But I can promise that you won't pay for any time you don't find valuable, so if you do really want it solved and are in a position to pay for such help, you can learn more about my rates, approach, satisfaction guarantee, online calendar, and more. Otherwise again perhaps others here (including Adobe) may work to draw out the cause and solution. BTW, I do help daily here with problems suited to such back and forth, so I hope you'll not conclude that I'm withholding help "to get paid". ... View more

Ok, let's see if Pete agrees.   (He may see/reply only to the thread where you first offered this. If it doesn't help in his special case, I'll hope he notices this other thread.)  ... View more

Bkbk, while your dump is looking at the variable in your sample code, my focus was focused on Pete's original code...to help him given that his reply to you earlier said his AD query was returning different info.   Are you trying to assert in your code that you've found the exact cause and solution? Or was yours just some more code to help Pete try to figure things out? That's how I read it, so mine was indeed added as SEPERATE from what you wrote--which is in fact why I created it as a new thread (though I acknowledged what you and Pete F had written). As you often like to point out, we're all here trying to help. I didn't feel my suggestion was stepping on or dismissing yours.   And either way, my question to him about his update level still stands.  ... View more

I realize this is a few days after your original question, but assuming the problem remains (and beyond the ideas shared so far by Yorik, Patrick, bkbk and Pete), I have a different question, especially since you say the problem happens only on SOME of your AD query results.    I think a simple change will help better diagnose what's amiss. First, it's not clear whether your error is happening on line 2, 4, or 5 of your code. There error refers to line 17. Assuming that's line 2 above, what do you see if you change that line:   <cfset mgr = manager.split(",")[1]/>   to:   <cftry> <cfset mgr = manager.split(",")[1]/> <cfcatch> <cfdump var="#manager#" > <cfabort> </cfcatch> </cftry>     The point here is to see just what is in that manager scope. Or if you want to, you could put all the code in the cftry and dump both the manager and mgr variables, since again we can't know from the error which is the one that has your issue.   Finally, you've not said what cf update you were on BEFORE applying cf2021 update 17. Was it before update 13? If so, there may be a connection to its change of default behavior regarding implicit scope searching. See the technote for that update for more on that change, as well as options for reverting the behavior change at the app or jvm level.  If somehow the dump doesn't help, and you were on update 12 or earlier, let us know if changing that default behavior might help.  ... View more

I realize this is a few days after your original question, but assuming the problem remains (and beyond the ideas shared so far by bkbk and Dave), I want to turn our attention to your presumption that this a "cf2023" problem. Until you can offer a test case that allows us to prove that ourselves (between our own cf2018 and cf2023), I have a different question.   You say your cf2023 is on docker on aws. What's your cf2018 setup? Is it also a docker image? (Adobe did offer docker images for cf2018 originally.) Either way, it at least also on aws? (There could be some facet unique to that which would not happen otherwise.) Is the OS st least the same between the two cf instances (I don't expect that should change how the features work. I'm just helping consider possibilities.)    Indeed, are both cf instances talking to exactly the same database, and using the same driver type in cf? And what are your update levels for cf2023 and 2018? In particular, are you testing cf2023 update 11, since that has dozens of bug fixes. (And yes, Adobe has released a container image with update 11 pre-installed which should make it easy for you to try.)    I realize you may not want to "play 20 questions ". As I said, if you could offer some small example code (that is standalone and allows us to recreate your results) that could let us skip most of those considerations, if we could confirm it was SOLELY about cf2018 vs cf2023. Until then, perhaps these will help you find the cause of your different behavior.  ... View more

Mary, you say "I have made all the necessary changes and I have not been able to get the website to be seen through a public IP with Apache, with IIS it is done automatically".   This seems to be a very different problem than what you raised here originally...and especially since that first issue has a marked "answer" above, you should probably create a new discussion.   If you do that, indicate whether this new challenge is limited to cf pages or not (as you indicated originally). I suspect it's about any request.   And if so, this would seem to have nothing to do with CF. As such, there are many things that could be amiss/need to be changed. It may be about a firewall on the box or in your network, or it may be about apache or even OS/networking configuration.    Indeed, when you refer to iis working "automatically" I'm not sure what you mean, but are you saying one fact that iis IS running on this machine? (Your previous comments suggested that was on another machine.) Assuming it's not, you might find that even if iis WAS on this machine, it would fail to be reachable also--which would reassert my last point.    Finally, if you feel you could create a new discussion that would address all these questions, doing that might be helpful. But if it feels unwieldy to try that, then just go ahead and answer here if you like.   Hope we can get to your resolution.  ... View more

Dwayne, did you clear the felix-cache? The steps are in the update technote, to help with other issues related to the htmltopdf package. It may help with yours. I've confirmed landscape does work after the update, a bug fix it specifically addressed as you may know.   Let us know if it helps or not.  ... View more

Freeman, while you may await further direct help from Adobe support folks, if you look at the coldfusion-out.log and especially the first startup after that update to 11, I suspect you'll find the explanation for both the admin not working and the "ClientScope service is not available" error. If you would share just the errors within that, we may see something if you don't. Same if there are errors after the uninstall.  ... View more

Great to hear and glad to help. Thanks also for marking the "answer". That helps in many ways. 🙂 ... View more

I appreciate how frustrating such a situation can be, but I think the root cause can be determined to be an unintended mistake in your processes there: The reboot of the box restarted cf, which would not run. Was it the reboot that caused the problem? The windows updates? I think not.  You restarted cf after that, and it would not start.  I'm willing to bet money that if you'd tried that Cf restart BEFORE the box restart, it would have failed then, too.  So what was the root cause? My money would be that this is what had happened: You or anyone there ran a Java 11 update on the machine... WHILE CF was running  As such, the jvm installer tried to lay down the new version in that jdk-11 folder... which cf was pointing to. (You'd referred to, "the jvm.config which had been pointing to the jdk-11 install".) But with CF running, the jvm installer couldn't modify the files pointed to by cf.  So on restart of cf (before or after the box reboot amd/or windows updates), cf would fail to start because of the mix of old and new jvm files in that jdk-11 folder  And this is what I said above last August in my point 4.   And I warn of it toward the bottom of each blog post I do on new Java updates, like I did on Tuesday: https://www.carehart.org/blog/2024/10/15/java_updates_oct_2024   And in the original post I did about this change with the jvm installer in Jan 2023, I suggest that the "solution" is either to stop cf while installing the jvm update, or use the zip extraction approach to installing the new Java version. I also lament there that the problem would plague people for years to come. 😞   Hope that's helpful.    ... View more

Thanks for the updates, Madhab. On this last one, sure, raising the heap MIGHT solve the problem temporarily--or it might even solve it permanently. It could be that you "just needed a bit more" heap than you had. It could be that some combination of factors has contributed to it, whether only recurrently (as you've indicated) or perhaps it's been some recent increase in traffic that's pushed you closer to that limit over time.   If you hit the new limit, it will be time to consider either what the objects are which are piling up, or the traffic causing it, or something else.  ... View more

I'll add a different perspective: I won't be surprised if you find zero info in the logs to explain this. I've seen that many times before, as Carl and BKBK may have.   But my first suspicion (based on your initial evidence) is that Cf may be running out of memory (heap). And while you MAY see outofmemory errors (likely in the coldfusion-error.log), sometimes you won't. Or well before your restart, it may well complain of gc overhead limit reached. That would be a warning that the jvm (underlying cf) is doing excessive Gc's (garbage collection, to remove any old unused objects)--but there is not much it can gc, so heap use remains high and Gc's continue, clogging the cpu and making requests hang.    And in that case, the new challenge is finding WHAT is holding on to memory. And thus will begin a possibly very long series of posts here as we toss out possible causes and possible tools. 🙂    But let's not get ahead of ourselves. Maybe you'll find a simpler explanation. A boy can have dreams.  ... View more

Thanks. First, glad you were able to recover with the uninstall. Second, as for point 5, that's the same info you'd offered before. I asked if there was OTHER info--before that.   But now I'd turn our attention to what info you see also in the update log. That, too, is in the hf-updates folder for the update you applied. I suspect you had errors DURING the install of the update. There can be many causes of that. I discuss it more in a blog post of some years ago, still relevant (How to solve common problems with applying ColdFusion updates), but I don't know if it will be necessary for you to read it.    One key point I make there, and another question for you: when you applied the update manually, did you use "run as admin" when opening the command line?   Finally, there's one more question I should have asked: what Java version does your cf admin now show that you have running under cf? (Don't judge from the command line. That could be different from what cf uses. See the "settings summary" page in the admin, which is the last link at the top of the "server settings" section. Then see about 10 lines down.)    Since you're on cf2023, it should be some Java 17. But (since applying the update 10 you're on) did you perhaps change the jvm cf uses to use Java 17.0.8 or later? If so, you may be hitting an issue I discuss in a blog post from a year ago (this week, in fact) https://www.carehart.org/blog/2023/10/10/solving_problems_applying_latest_cf_updates   The tldr at the top of the post maybe all you need. In fact Adobe mentions it in the technotes for yesterday's update: you may need to add another jvm arg to the manual command line update you did. You'd want to add:   -Djdk.util.zip.disableZip64ExtraFieldValidation=true   on the "java -jar " command, with that placed BEFORE the -jar arg).  I elaborate in the post on HOW to do it if the technote's suggestion isn't enough. I also mention this in my own blog post from last night about yesterday's update, FWIW: https://www.carehart.org/blog/2024/10/16/ColdFusion_updates_released_Oct_15_2024   Let us know if any of this gets you going.   I'll add that as I also mention in those posts, I can certainly help folks directly, via remote screenshare, often solving such things quite quickly (consider how readily all this info on share comes to mind for me). Of course, different people have different problems. I try in these online resources to guide you based on what info you offer. I also write to benefit ANYONE who may be following along. In a session together, we'd obviously be targeted to your specific needs and what you know/don't know. More at carehart.org/consulting.   But I hope I've given you (and others here) enough to hopefully get you going on your own.  ... View more

While you await a reply from Adobe, I'll report that I did not get that error in applying the update. You could help us help you by answering a few questions: Was this cf2023 or 2021? What update were you on before this? What OS? Are you saying cf now won't start? Is there perhaps more info in the cf logs, before that one, during startup? Have you tried uninstalling the update?   Even if you "can't access the cf admin to do that", note that you can do it from the command line--like the manual install you attempted.  See the cfusion/hf-updates folder whose name includes the number of the update you did. That has an uninstall folder in it, and that has an uninstall .bat or .sh to run.   Or again, perhaps Adobe or someone else may chime in with news that they've seen this before and/or have different info to suggest. ... View more

Sorry this is a couple of years late, but I was searching for pages where people discussed this "No Service manager is available" error. I want to share that in some situations the solution turns out to be very simple: you need to make sure the PDF service (listed in the CF Admin "PDF Services" page) is indeed "enabled", by clicking the "play" button.   Sadly, there are no "words" to the right of the service to indicate if it's enabled, and the play/stop icons are fairly small and so easy to mis/misconstrue. What's more, it can be confusing that the service can VERIFY fine even if not ENABLED.  🙂 ... View more

I realize this is a couple of years on, but in case it may help anyone, I had an instance where I got this error ("No Service manager is available"), and the solution was actually rather simple: on the "PDF service" page of the CF admin, make sure that the "enable" (or "play") button is on (and the "stop" button is not).   In other words, in at least one case I helped with today, the problem was simply that the PDF service was indeed NOT enabled. But there's no words to convey that (in the table to the right of the service). There are only these tiny UI elements, and it can be easy to miss whether the service is enabled or not. And what's also confusing is that the service will "verify" if you try it (reporting "ok"), but that's NOT checking whether the service is ENABLED in CF, only if the service it points to (the add-on service) is running.   Now, if instead you try to run the cfhtmltopdf and get instead the error, "Error occurred while generating PDF", that's a DIFFERENT problem. Often the solution is one I offered in a couple of other places, such as https://stackoverflow.com/a/77327211/90802. ... View more

I understand that you offered screenshots of what fails for your ap.p. I'd asked if instead you could to take a few mins to create a simple demo that allows us and Adobe to see if we can experience it.   But short of that, yes, checking the dev tool results may help you solve it yourself. If not, try to share it here, sure. That may not be trivial, as those are often multiple screens of info to consider.  ... View more