FusionReactor Google Group

Re: Changing the log file directory

dapyw...@googlemail.com (Darren Pywell) — Tue, 05 Jan 2010 16:25:55 UT

Hi Randy,
Yes it's possible to change the directories (and filenames even) of
the FusionReactor log files. The log filenames (and paths) are
controlled via properties in the reactor.conf configuration file. Its
possible to change these properties by hand in the file but you have
to shut FusionReactor down (i.e stop the monitored server) to do it

Changing the log file directory

rjohnso...@gmail.com (Randy Johnson) — Wed, 30 Dec 2009 17:30:33 UT

Hello,
Is there a way for me to change the directory where fusion reactor
stores it's log files?
Thanks!
Randy

Re: FusionReactor Group: Re: Multiple Instances - Fusion Reactor Not Working

dapyw...@googlemail.com (Darren Pywell) — Fri, 18 Dec 2009 07:54:12 UT

Hi Rod,
Sure thing. Glad it's working :-)
Was the path in your web.xml or your default-web.xml file?
The config path definition is and isn't needed :-) and I'd better
explain that...
If you specify the path FusionReactor knows exactly where to find it's
configuration file. If you leave it out FusionReactor looks for it's

Re: FusionReactor Group: Re: Multiple Instances - Fusion Reactor Not Working

rod.buc...@gmail.com (Yendor) — Fri, 18 Dec 2009 00:46:06 UT

Hi
We found the problem, it was a bad path but it was in the web.xml
file. It looks like it was part of the original Fusion Reactor 1.x
install - so maybe it's not needed anymore?
<filter>
<filter-name>FusionReactor</fi lter-name>
<filter-class>com.intergral.fu sionreactor.filter.FusionReact orFilter</

Re: FusionReactor Group: Re: Multiple Instances - Fusion Reactor Not Working

rod.buc...@gmail.com (Yendor) — Thu, 17 Dec 2009 23:16:09 UT

Hi Darren
Thanks, I didn't know where to look to change the path. I'll give that
a shot as soon as I can get permission to take a server out of the
cluster.
Cheers,
Rod

Re: FusionReactor Group: Re: Multiple Instances - Fusion Reactor Not Working

dapyw...@googlemail.com (Darren Pywell) — Thu, 17 Dec 2009 21:13:52 UT

Hi Rod,
Thanks for the info. The error tells us that FusionReactor is looking
in the wrong location it configuration file. It would be looking in
the instance folder as you point out. The instance folders were
introduced in FusionReactor 2, it seems like the instance manager that
was used created FR version 1 style entries.

Re: FusionReactor Group: Re: Multiple Instances - Fusion Reactor Not Working

rod.buc...@gmail.com (Yendor) — Thu, 17 Dec 2009 07:28:18 UT

Hi
Thankyou for the responses.
As for the support request, I wasn't the person who lodged it so I
cannot be sure that it was done properly. The person who did it said
that they followed the links on the website to the contact support
form here: [link]
To address your suggestions:

Re: FusionReactor Group: Re: 3.01 - not stopping at breakpoints

dan.oke...@gmail.com (Dan O'Keefe) — Wed, 16 Dec 2009 18:05:24 UT

Thanks Charlie, I did not realize there were 2 separate groups.

Chris, I had 2 issues. The first was my CF files are on the server in
the VMWare instance and I have a mapped drive letter on my client
which I was using in the source code lookup. I corrected that to be
the server path to the files. But even after correcting that I could

RE: FusionReactor Group: Re: Multiple Instances - Fusion Reactor Not Working

charlie_li...@carehart.org (charlie arehart) — Wed, 16 Dec 2009 17:15:31 UT

Besides what Darren offered, another possible problem is a firewall blocking
you from accessing the port, if you're using FR's built-in web server.

I could see a situation where your primary instance may have been opened by
you using your external web server, but then the links in the Dashboard are

RE: FusionReactor Group: Re: 3.01 - not stopping at breakpoints

charlie_li...@carehart.org (charlie arehart) — Wed, 16 Dec 2009 16:41:59 UT

Besides Christopher's excellent tip, it seems to have slipped notice that
you've asked this on the FusionReactor, rather than the FusionDebug, list.

Just sharing this for future reference: if one is already a member of that
group, they can just change the email address for sending notes to
fusiondebug@googlegroups.com. And to join that group, see

Re: Multiple Instances - Fusion Reactor Not Working

dapyw...@googlemail.com (Darren Pywell) — Wed, 16 Dec 2009 11:20:20 UT

Hi Yendor,

Just to touch on the support point first. The support is usually super-
responsive so I've checked the support-inbox and I don't see a request
pending on this topic. Can you let me know when you sent the request,
thx.

Using the Instance Manager or Installer, usually it's difficult to

Re: 3.01 - not stopping at breakpoints

chris_w...@intergral.com (Christopher) — Wed, 16 Dec 2009 08:20:35 UT

Hi Dan,

One important thing to note about remote debugging is that the source
lookup entries must be absolute pathnames on the server (e.g. C:
\ColdFusion8\wwwroot). It is important to note that the files on your
local machine must be in sync with the server files.

Here is a technote about remote debugging:

Multiple Instances - Fusion Reactor Not Working

rod.buc...@gmail.com (Yendor) — Wed, 16 Dec 2009 00:31:58 UT

We have Coldfusion 7 installed in multiserver mode (Windows 2003, IIS
6). We have three instances of Coldfusion running on it - the default
instance and two extra instances.

We have FusionReactor 3.5 enterprise and it installs ok on the default
CF instance. We used the "Instance Manager" to add the other two CF

3.01 - not stopping at breakpoints

dan.oke...@gmail.com (Dan O'Keefe) — Tue, 15 Dec 2009 23:36:44 UT

Hello,

We purchased 5 licenses of FusionDebug and I will be training on it
for our developers, and our environments are all pretty similar:

Windows XP - Service Pack 3 - Security Update 20,955 :) - Current
Eclipse is Flash Builder 4 Beta 2 - FD 3.01 perspective
VMWare Workstation 6.5.3 185404 - Windows Server 2003 - IIS -

CP setting for running requests: set it to one less than max that can run, to be notified when all running

charlie_li...@carehart.org (charlie arehart) — Tue, 15 Dec 2009 17:54:53 UT

I just noticed something that tripped up some expected crash protection
notification for someone I'm working with. I wanted to share it with others
here.

You may know that the FR Crash Protection offers 3 choices, detecting when a
request takes too long, memory is too low, or too many requests are running.