Works OK:
3.1.16777
Note that "jrun -version" fires up a JVM with the "user.javaargs" settings
from local.properties. If you have changed these, problems may occur. I got
problems trying to set up for remote debugging.
Roar
-----Opprinnelig melding-----
Fra: Charles Arehart [mailto:[EMAIL PROTECTED]]
Sendt: 30. august 2001 21:03
Til: JRun-Talk
Emne: RE: "jrun -version" command (was "JRun 3.1 hotfix bundle")
Sorry. The reference to a "-server" option was just a mistake. I meant to
say "-version", as I had said in the subject and went on to repeat a couple
times later in the document. :-)
As for it being a "fix", I just wondered if indeed the "jrun -version"
command should work and for some reason it's not working for me. I'll be
curious if anyone else can have it work, otherwise, sure, making the KB
clarify this other approach to running it would be good.
/charlie
-----Original Message-----
From: Matthew Horn [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 30, 2001 12:39 PM
To: JRun-Talk
Subject: RE: "jrun -version" command (was "JRun 3.1 hotfix bundle")
Charles, I forward this fix to the person responsible for fixing the KB
articles.
As for the question about the "-server" option, can you tell me where you
are reading that? As far as I know, there is no -server option.
>>-----Original Message-----
>>From: Charles Arehart [mailto:[EMAIL PROTECTED]]
>>Sent: Thursday, August 30, 2001 12:09 PM
>>To: JRun-Talk
>>Subject: "jrun -version" command (was "JRun 3.1 hotfix bundle")
>>
>>
>>Thanks for the heads up, Tormod. I've got a problem for
>>Macromedia about the
>>instructions on that hotfix page, though. Maybe someone can
>>help. The
>>"Jrun -server" command isn't responding as expected.
>>
>>The article offers instructions about how to determine the
>>current version
>>for JRun, by typing "jrun -version" at the command prompt
>>in Jrun/bin. When
>>I do that, I instead get a pop up window listing valid JRun
>>commands to
>>enter, suggesting that "version" isn't one of them. (It's
>>not that I'm not
>>in the bin directory and the JRun command's not recognized,
>>it's that the
>>JRun command isn't accepting -version as an argument.)
>>
>>After some digging, I learned from the "Advanced
>>Configuration Guide" that
>>the commands (-version and -info) could be used if *sent as
>>input to java"
>>(on a windows platform), as in:
>>
>>java JRun -version
>>
>>This is case-sensitive (JRun, not jrun).
>>
>>Also jrun.jar and servlet.jar need to be in your classpath.
>>If not, then the
>>following verbose command would work (assuming it's entered from the
>>location of your JRun installation, such as program
>>files/allaire/Jrun):
>>
>>java -cp lib/jrun.jar;lib/ext/servlet.jar JRun -version
>>
>>But why didn't the JRun.exe in /bin respond as expected?
>>
>>If there's something wrong with those instructions, I hope
>>a Macromedia
>>person can get them updated. It would seem important for
>>people to determine
>>whether to apply the hotfix.
>>
>>/charlie
>>
>>-----Original Message-----
>>From: Tormod Hystad [mailto:[EMAIL PROTECTED]]
>>Sent: Thursday, August 30, 2001 8:36 AM
>>To: JRun-Talk
>>Subject: JRun 3.1 hotfix bundle
>>
>>
>>Hey!
>>
>>There's a bugfix release of 3.1 available:
>>
>>http://www.allaire.com/Handlers/index.cfm?ID=21853&Method=Full
>>
>>This is build 16777 of JRun 3.1, the original 3.1 was build
>>15506. Lots of
>>bugs fixed.
>>
>>~ Tormod
>>
>>~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
>>Tormod Hystad
>>Senior Developer, R&D
>>CatalystOne, Inc. - Execution excellence!
>>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
