Multiple Instances - Fusion Reactor Not Working

[Yendor]

Hi

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
instances.

However we cannot see the CF admin console for the two extra CF
instances. It opens up a browser on and cannot find the site. It seems
that there is no web server configured for that url/port. We have
tried manually installing FR for the other two instances and we have
tried re-running the FR install to add the extra instances. We have
also tried installing FR onto one of the extra instances rather than
the default.

We have logged a support request but have had no response so far.

Does anyone have any advice? What web server does FR use? IIS? It's
own? JRun? If we knew that it might help to diagnose why we cannot
browse to the admin console. Or maybe we just installed it
incorrectly?

Thanks

[Darren Pywell]

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
install it incorrectly :-), it should be the job of this software to
get the installation done correctly. Typically the only issues that
come up are file permissions (can't write to the directories) or the
port that is selected for FusionReactor to use is in use by another
application, although both of these are checked.

One thing I should mention right away is that you must restart your
ColdFusion instances before FusionReactor can be used. I thought I
better mention that just in case.

FusionReactor has a lightweight built in webserver (typically running
on port 8088) and (by default) also maps itself onto your external
webserver such as IIS or Apache. Typically you can access
FusionReactor's internal webserver like this:

http://<server>:8088/fusionreactor

and the external one like this:

http://<server>/fusionreactor/fhtml.cfm

Just replace the <server> with the name of the server or the IP
address of the server.

When you install and new FusionReactor into a instance then
FusionReactor creates a folder under it's <FR installation directory>/
instance/ with the name of the instance that you create.

For example:

C:\FusionReactor\instance\coldfusion.cfmx8.INT000B

You should see a folder for each one. Inside this folder is a log
folder and inside there a log file called reactor-0.log usually should
be created when FR starts. If there are any errors then you can look
into this log file to see if you have problems.

Another good thing way to find problems is to look into the JRun logs
for the instances that are having problems. You will find these
typically under :

C:\ColdFusion8\runtime\logs\ for a standalone style installation

or

C:\JRun4\logs for a Multi-Server style installation (like yours).

Look for -out.log and -err.log files with the name of the server where
the problems are occuring. You want to look in the log files the point
where ColdFusion was started. Alternatively you can try stopping the
ColdFusion service and then starting in from the command line, for
example:

> cd \ColdFusion\bin
> cfstart.bat

or

> cd \JRun4\bin
> jrun.exe start cfusion


Look for errors during the startup.

If you can post any errors that you find here, I can take a look at
what to do next.

Thanks,
Darren

[charlie arehart]

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
trying to use the built-in web server port. Or if you did get into the first
instance on the 8088 port, perhaps that was opened in your firewall in the
past for some other app (it's fairly common, such as for tomcat). If that
wasn't running when FR was installed, that's why FR would have acquired it
for the first instance.

Finally, note as well that your firewall may allow access to these ports
from inside your network but not from outside, so consider that as you're
testing things. Hope you can get it resolved. You'll find this list (and the
FR support team) to be very interested in helping.

/charlie

> -----Original Message-----
> From: fusion...@googlegroups.com
> [mailto:fusion...@googlegroups.com] On Behalf Of Darren Pywell
> Sent: Wednesday, December 16, 2009 6:20 AM
> To: FusionReactor
> Subject: FusionReactor Group: Re: Multiple Instances - Fusion Reactor
> Not Working
>
> 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
> install it incorrectly :-), it should be the job of this software to
> get the installation done correctly. Typically the only issues that
> come up are file permissions (can't write to the directories) or the
> port that is selected for FusionReactor to use is in use by another
> application, although both of these are checked.

<snip>

[Yendor]

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: http://www.fusion-reactor.com/contact/?type=services

To address your suggestions:

Restarts - we restarted the CF instances multiple times and also
restarted the server mutliple times during and after installation.

Ports - we have checked using netstat and telnet that the ports we are
using are free. The default instance (where FR works ok) is on 8088.
The other two non-working instances are on 8090 and 8091.

FR Logs - these folders exist (names changed):

C:\FusionReactor\instance\coldfusion-default
C:\FusionReactor\instance\coldfusion-instance1
C:\FusionReactor\instance\coldfusion-instance2

However the logs in instance1 and instance2 are empty. The
reactor-0.log in the default instance only has one warning:

2009-12-17 17:17:56.917 WARNING Retrieving metrics from
http://127.0.0.1:8088/fusionreactor/fService.cfm?command=remoting&subcommand=transfer&data=metrics:
Couldn't find a FusionReactor Enterprise service at
http://127.0.0.1:8088/fusionreactor/fService.cfm?command=remoting&subcommand=transfer&data=metrics

The installation was an upgrade from version 1.x standard to 3.5
enterprise... if that helps.

The "-out" log for the instances where FR isn't working have this
error:

17/12 17:20:42 user FusionReactor: FusionReactor Rev. 3.5.1, Build:
FusionReactor.78.14986
17/12 17:20:42 user FusionReactor: Initializing configuration
17/12 17:20:42 user FusionReactor: Loading configuration from C:
\FusionReactor\conf\reactor.conf...
17/12 17:20:42 user FusionReactor Exception: C:\FusionReactor\conf
\reactor.conf (The system cannot find the path specified)
java.io.FileNotFoundException: C:\FusionReactor\conf\reactor.conf (The
system cannot find the path specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:
106)
at com.intergral.fusionreactor.config.d.d
(ConfigurationHandler.java:44)
at com.intergral.fusionreactor.core.u.vc
(FusionReactor.java:533)
at
com.intergral.fusionreactor.filter.FusionReactorFilter.init
(FusionReactorFilter.java:640)
at jrun.servlet.FilterObject.init(FilterObject.java:
63)
at jrun.servlet.FilterManager.loadFilter
(FilterManager.java:195)
at jrun.servlet.FilterManager.init(FilterManager.java:
155)
at jrun.servlet.FilterManager.create
(FilterManager.java:74)
at jrun.servlet.WebApplicationService.start
(WebApplicationService.java:223)
at jrun.ea.EnterpriseApplication.start
(EnterpriseApplication.java:194)
at jrun.deployment.DeployerService.initModules
(DeployerService.java:710)
at
jrun.deployment.DeployerService.createWatchedDeployment
(DeployerService.java:242)
at jrun.deployment.DeployerService.deploy
(DeployerService.java:430)
at
jrun.deployment.DeployerService.checkWatchedDirectories
(DeployerService.java:179)
at jrun.deployment.DeployerService.run
(DeployerService.java:891)
at jrunx.scheduler.SchedulerService.invokeRunnable
(SchedulerService.java:223)
at jrunx.scheduler.ThreadPool
$ThreadThrottle.invokeRunnable(ThreadPool.java:426)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:
66)

The path "C:\FusionReactor\conf\reactor.conf" doesn't exist. The
reactor.conf file is in the "C:\FusionReactor\instance\[server-name]
\conf" folder.

We can totally uninstall FR and try again if you think that will fix
it. We tried this once but maybe we missed something? Or perhaps there
is a setting somewhere to fix the location of this file?

Thankyou again for the help.
Rod
(yendor = rodney backwards)

[Darren Pywell]

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.

You can fix the problem by editing the default-web.xml file which you
should find in a JRun4 installation under C:\JRun4\servers
\<nameofinstance>\SERVER-INF for each server.

I've included mine below from my JRun4 installation. The important
line is the one that states where to find the config file. This will
need correcting C:/FusionReactor/instance/[server-name]/conf/
reactor.conf (notice the /'s :-) )

Example FR filter definition part my default-web.xml file:

<!--FusionReactor filter - created Fri Jan 25 00:24:33 CET 2008-->
<filter>
<filter-name>FusionReactor</filter-name>
<filter-
class>com.intergral.fusionreactor.filter.FusionReactorFilter</filter-
class>
<init-param>
<param-name>config</param-name>
<param-value>C:/FusionReactor/instance/
cfusion.jrun4.INT000B/conf/reactor.conf</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>FusionReactor</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>

Cheers,
Darren

On Dec 17, 8:28 am, Yendor <rod.buc...@gmail.com> wrote:
> 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:http://www.fusion-reactor.com/contact/?type=services
>
> To address your suggestions:
>
> Restarts - we restarted the CF instances multiple times and also
> restarted the server mutliple times during and after installation.
>
> Ports - we have checked using netstat and telnet that the ports we are
> using are free. The default instance (where FR works ok) is on 8088.
> The other two non-working instances are on 8090 and 8091.
>
> FR Logs - these folders exist (names changed):
>
> C:\FusionReactor\instance\coldfusion-default
> C:\FusionReactor\instance\coldfusion-instance1
> C:\FusionReactor\instance\coldfusion-instance2
>
> However the logs in instance1 and instance2 are empty. The
> reactor-0.log in the default instance only has one warning:
>

> 2009-12-17 17:17:56.917 WARNING Retrieving metrics fromhttp://127.0.0.1:8088/fusionreactor/fService.cfm?command=remoting&sub...
> Couldn't find a FusionReactor Enterprise service  athttp://127.0.0.1:8088/fusionreactor/fService.cfm?command=remoting&sub...

[Yendor]

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

[Yendor]

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</filter-name>
<filter-class>com.intergral.fusionreactor.filter.FusionReactorFilter</

filter-class>
<init-param>
<param-name>config</param-name>

<param-value>C:/FusionReactor/instance/Instance Name/conf/
reactor.conf</param-value>
</init-param>
</filter>

We fixed the path and it is all working properly now.

Thankyou very much for the help Darren. Your advice told us what to
look for.

Cheers,
Rod

[Darren Pywell]

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
configuration file in the class path. I don't recommend letting FR
look for it on the classpath because it means that FR will take the
first reactor.conf file it finds (on the classpath). So if there were
two reactor.conf files and the classpath changed then the FR
configuration could also change. So always specify the config param,
which is what the installer and instance manager do.

Cheers,
Darren