While we may see some response to that tracker ticket, I have some other thoughts.
BTW, I was torn whether to offer them there or here. I've opted for here because currently the tracker system fails to send email notifications (something I've written a separate bug report for).
1) So first, Rocker, this is something I've not heard of before. Of course it should not hang. And indeed cfsetup itself does no network calls, unless the path you give it for the cfusion location is elsewhere, and yours clearly was not.
So, good on you for experimenting to find that it was somehow processing the web.xml file. I would not have expected that, but it may have its reasons. But now that you know that's where your hangup is, now we can focus on what in there is causing it for you.
2) I notice there are multiple references in your log's stack trace to "mobile.MobileServlet". Some may recognize that as being related to the little-used mobile feature set (added in cf11 and due to be removed in cf2025).
I wonder if you were to comment out those references, might that remove the problem (it may not). You'd want to be very careful. First, save a copy of the file. Second, use html/xml comments (2 dashes) not cfml (3 dashes), or cf won't start. Finally, note there are more than one sort of xml line there referring to that mobileservlet.
But again that may not solve things. If it happens again, it may move on to some other mapping you have there. There are several. But try it and if it doesn't work then share (or study) the next error to see if points to another.
3) Or you could share your web.xml here, and maybe we'll spot something amiss. I don't think there's anything of a privacy nsture6innitz but check to be sure.
4) And if you do share that or even another long stack trace, please use the feature here to attach a file to your reply, rather than dump such large text into your reply. That makes it cumbersome to distinguish one reply from another, and all the more if folks may read this on a phone--and I can attest that writing replies here on a phone, especially long ones like this has its own challenges! 🙂
5) Finally, I put a comment into the tracker ticket to point to this post of yours, to help folks there see this additional discussion here (first from you and BKBK, and now me). And I do hope you and others will find this new reply. I opted to not offer it as a reply to the others, as again on a phone the indentation of nested replies starts to get especially clumsy. First world problems and "difficult choices". 🙂
/Charlie (troubleshooter, carehart.org)
1 Correct answer
17
Replies
AdChoices