With my changes to your startup script I get the following results:
-- The CFMX admin shows that the JVM 1.4.2-34 is being used for CFMX
(this is the correct version)
-- The JMC console shows that JVM 1.3.1is being used for JRun (this is
not the correct version)
In the past, I have been able to accomplish the above with info from
Christian Cantrell's blog
But I am concerned that the use of 2 different JVMs may cause problems.
In response to an earlier thread, I tested some versions of a JRun
updater that tried to address this issue. We were able to get JRun to
use the latest JVM, but:
-- we could not get CFMX to use the latest JVM with the JRun Updater
-- there were other problems with the JMC with the JRun Updater
installed
Your script is probably adequate for development.
I am trying to decide what to recommend to a client who wants to
install CFMX (or possibly BD) on an XServe for production in a
multi-homed environment. Each of the client's customers will use a
unique domain to manage his private web and multimedia files (created
by my client)
The big issue is that CFMX is not supported for production on the OS X
platform.
Steven Erat clarified Macromedia's policy, quoted below.
To minimize problems and maximize the potential for vendor support, it
seems to make sense to run both JRun and CFMX on JVM 1.3.1 until
Macromedia provides a solution that allows both to run on the latest
JVM.
Thanks for your help
Start quote
To the specific support question regarding CFMX on Mac OSX, while it
continues to be policy that Macromedia doesn't support that
configuration
for production systems at this time, I believe that the spirit of the
policy
can be interpreted to mean that problems that are specific to Mac OSX
and
cannot be reproduced on other platforms will not qualify for escalated
status or bug fixes, although I think it would be fair to say that
Macromedia will in fact support such customers to the extent that the
reported problem or question is not restricted to the Mac OSX
platform.��In
fact, the support staff maintains a cohort of Mac OSX systems that are
configured with CFMX and JRun to be used for this very
scenario.��Should
anyone have an experience to the contrary when officially logging a
support
ticket, then I invite you to contact me so that I can help rectify the
situation and perhaps even assist in providing the technical support
myself.
-Steven Erat
Macromedia Server Product Support
End Quote
On May 8, 2004, at 10:25 AM, Matt Liotta wrote:
> My start script is as follows, which correctly uses Java 1.4.2. There��
> is some stuff in this script that you obviously won't need, but I��
> thought I would share it as is.
>
> cd /Applications/JRun4/bin
> PATH=$PATH:/Applications/JRun4/bin
> export PATH
>
> CLASSPATH=/Applications/JRun4/lib/jrun.jar:/Applications/JRun4/
> servers/
> lib/alchemy-jaas.jar:/Applica
> tions/JRun4/servers/lib/cfmx-j2ee.jar:/Applications/JRun4/servers/lib/
> cfmx-ssl.jar
> export CLASSPATH
> java -cp $CLASSPATH jrunx.kernel.JRun -start admin >��
> /Applications/JRun4/logs/default.out.log &
> java -cp $CLASSPATH jrunx.kernel.JRun -start default >��
> /Applications/JRun4/logs/default.out.log &
> java -cp $CLASSPATH jrunx.kernel.JRun -start bluedragon >��
> /Applications/JRun4/logs/default.out.log &
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
