Hi Andrew,
With the startup you can see that cranking up the Message Broker Servlet (ie
Livecycle/Blaze) is taking almost a minute, which I find is usually due to some
network ports used by LCDS still being open from the last time ColdFusion was
run. However CF is usually available to take forwarded requests from the web
server when you see:
27/03 11:06:03 user ColdFusionStartUpServlet: ColdFusion: application
services are now available
Which in your log is only seven seconds after the first startup log message.
What happens on line 67 of index.cfm (or is it Application.cfc)? The logs are
trying to tell you something there, check it out. As an earlier,
ahead-of-its-time draft of the song goes:
"How many logs must a developer tail, before you can call them a developer?" ;-)
Cheers,
Robin
ROBIN HILLIARD
Chief Technology Officer
[email protected]
RocketBoots Pty Ltd
Level 11
189 Kent Street
Sydney NSW 2001
Australia
Phone +61 2 9323 2507
Facsimile +61 2 9323 2501
Mobile +61 418 414 341
www.rocketboots.com.au
On 28/03/2010, at 10:07 AM, Andrew wrote:
> Just to add to that, after the initial timeout on index.cfm, if you
> hit the page again instantly it is fine, and the app works fine and
> seems to perform as expected.
>
> It's just the initial load that are extremely slugging (both starting
> the server, and initialising the app).
>
> --
> You received this message because you are subscribed to the Google Groups
> "cfaussie" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/cfaussie?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"cfaussie" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/cfaussie?hl=en.
