Coldfusion in J2EE configuration

Question

hi,
i m trying to deploy CF7 as a war in JBoss4.0.3 SP1 on Fedora
Core 4.
But the commons-logging.jar and log4j.jar in both JBoss and
CF seem to break the flow.
During JBoss startup, a message that might need attention is
14:16:42,842 INFO [TomcatDeployer] deploy, ctxPath=/cfusion,
warUrl=.../deploy/cfusion.war/
14:16:48,420 INFO [STDOUT] log4j:ERROR A
"org.jboss.logging.appender.FileAppender" object is not assignable
to a "org.apache.log4j.Appender" variable.
14:16:48,423 INFO [STDOUT] log4j:ERROR Could not instantiate
appender named "FILE".
After the startup, on accessing any cfm the error I get is :
14:19:12,166 ERROR [[CfmServlet]] Servlet.service() for
servlet CfmServlet threw exception
java.lang.ExceptionInInitializerError
Caused by:
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JLogger does not implement Log
I have tried some of these but with no success:
1. removing the commons-logging.jar and log4j.jar from
cfusion.war.
2. upgrading the above jars in cfusion.war with the ones in
JBoss.
Any help would be appreciated.
Regards,
Zara

Answer 1

Ian Skinner wrote:
>And that in multi-server, ColdFusion is placed in a
controlling
>position. I.E. you can easily go the lifetime of a server
never
>working with the JRun Console. At least I have never had
to use it.
>I've done all my administration with the ColdFusion
administration
>console and|or JVM config files.
Since we have used the full JRun 2 CPU license since 2003, we
have kept it separate from the CF deployment, i.e. deploying CF as
an expanded WAR file on 50+ server instances. We are doing a proof
of concept on moving up to 64-bit, so I just need to confirm that
multi-server configuration is indeed host within the built-in JRun
app server at 64-bits.
>That may be where some of this is coming from. I believe
I read
>somewhere that Adobe is no longer developing JRun as a
separate >product from ColdFusion. It is my understanding that
the ColdFusion >team has incorporated the JRun team into their
organization.
Yes, that makes sense. Starting with CF8, I think, is when
JRun was no longer sold as a separate application server.
>If this is true, I would say that 'Yes' you can not buy a
64 bit version
>of JRun on it's own. Rather you get the 64 bit JRun when
you install
>the 64 bit ColdFusion in a JRun based configuration, i.e.
stand-alone or
>multi-home. Thus you would never again use the j2ee
installation option
>to install ColdFusion to an 'existing' JRun because you
can no longer
>get a separate JRun.
That does make sense re. the 64-bit version of JRun being
bundled with CF 8.0.1 for multi-server configuration deployment,
but that a separate 64-bit version of JRun application is _not_
available.
Thanks!