Well, Did you check what is the thread doing when you say the Server is hung?
Can you take a thread dump and post that here? You can take the thread dump
using Server monitor or you can refer to my post
http://coldfused.blogspot.com/2005/11/thread-dumps.html
however, I see few potential
Well, Did you check what is the thread doing when you say the Server is hung?
Can you take a thread dump and post that here? You can take the thread dump
using Server monitor or you can refer to my post
http://coldfused.blogspot.com/2005/11/thread-dumps.html
however, I see few potential
Ian,
Can anybody point out what is fundamentally wrong with this code. Such
that it has at least a 50% chance of complete failure resulting in a
non-responsive ColdFusion server that must be restarted. What gets me
is that sometimes it works completely correct and produces all the
desired
Excellent point Dan!
~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to
date
Get the Free Trial
http://ad.doubleclick.net/clk;203748912;27390454;j
Archive:
Also, Ian, how many threads are you creating here based on the query
results? 10? 10,000?
~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to
date
Get the Free Trial
Brian Kotek wrote:
Also, Ian, how many threads are you creating here based on the query
results? 10? 10,000?
For this process 1,371. That is my basic question at this time -- What
are the practical limits of the cfthread...
Here is my simplest test case to date. I seems to show that
Dan G. Switzer, II wrote:
Ian,
I wonder if the problem isn't with cfthread / but actually with heavy
usage of either cfreport / or cfpdf / tags.
Are you creating large reports? It could be a memory issue your running in
to. How much RAM is available to the JVM?
I would try simplifying
Yes the problem is probably that you are creating over 1000 threads, each of
which runs a cfreport tag to generate a PDF. You're probably killing the
server. CFThread threads are just like any normal CF web thread, and you
certainly wouldn't want to try and simultaneously process 1000 HTTP request
The memory usage of the PDF report generation is defiantly a problem.
It is what we where trying to address with the usage of the thread tag.
The idea being that by splitting the process into separate threads and
throttle them down would allow the server time to clean up memory used
in previous
Brian Kotek wrote:
Also, Ian, how many threads are you creating here based on the query
results? 10? 10,000?
For this process 1,371. That is my basic question at this time -- What
are the practical limits of the cfthread...
Here is my simplest test case to date. I seems to show that there is
He could also still use cfthread, but loop over the query and create the
threads in chunks rather than all at once. I don't know how well that will
work given the overhead of creating the PDFs, but it would be worth trying
in different chunks (2, 5, 10, etc.).
On Thu, Jul 10, 2008 at 10:57 AM,
Ian,
Here is my simplest test case to date. I seems to show that there is a
limit, but I really don't know where it might be.
cfloop from=1 to=1500 index=i
cfthread action=run name=th_#i# threadID=#i#
cfset thread.foobar = threadID
cfset thread.calc = threadID *
Dan, I already suggested this approach to IAN nearly a month ago--
twice.
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:307447
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:307626
If he thought there was merit in that he probably would have tried it
Brad Wood wrote:
Dan, I already suggested this approach to IAN nearly a month ago--
twice.
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:307447
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:307626
If he thought there was merit in that he probably
OK, then. I'll take you off my black list. :)
~Brad
-Original Message-
From: Ian Skinner [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2008 11:00 AM
To: CF-Talk
Subject: Missing Messages --- was Re: The Woes of CFThread -- going out
of my mind!
Brad Wood wrote:
Dan, I already
I'd also check if there's a spam blocker 'upstream' from you, especially if
your getting your mail through a business location. In addition, the server
is set to try and send mail for 48 hours before dropping it. A network
problem that prevents or distorts mail server connections within that time
I'd try to really limit the number of threads your creating.
I'd even look at limiting things to a fixed number of worker
threads. Try dividing the work load between like 5 or 6
threads. Have each thread process it's share of the work load
(i.e. each work load would handle 1/5 of the
Well I fail.
Can anybody point out what is fundamentally wrong with this code. Such
that it has at least a 50% chance of complete failure resulting in a
non-responsive ColdFusion server that must be restarted. What gets me
is that sometimes it works completely correct and produces all the
18 matches
Mail list logo
