RE: Cactus with JRun 3.1

[Vincent Massol <vm...@octo.com>]

Hi Melissa,

Your problem look like a jrun configuration issue. One point though:
What is the file type of "jrun" that you execute in the <exec>? Is it a
shell script or a binary executable?

If it is a shell script, then the executable should be "cmd" or
"command" if you're on windows or "sh", "ksh", etc if you're on unix.
The name of the script should then be passed as an <arg value="jrun"/>
nested tag.

However, you mention that the container does start, which means it is
probably something else...

Unfortunately, I don't use JRun and does not know how to configure it.
Have you tried the JRun mailing-list/forum/support?

Thanks
-Vincent

> -----Original Message-----
> From: White, Melissa [mailto:mwhite@triactive.com]
> Sent: 28 February 2003 23:13
> To: 'cactus-user@jakarta.apache.org'
> Subject: Cactus with JRun 3.1
> 
> I am using JRun 3.1, and I'm having a problem with the JVM started by
my
> runservertests task. I have a local.properties file in my
> jrun31/servers/myapp directory that specifies some additional
arguments
> for
> the JVM, for example:
> 
> user.javaargs= -Dproperty=value
> 
> The behavior of my tests indicates that these properties have not been
set
> (i.e., the value is null).
> 
> The startTarget for my runservertests is very simple:
> 
> <target name="start-jrun">
>   <exec executable="jrun">
>     <arg line="-start tsm-manager" />
>   </exec>
> </target>
> 
> I have confirmed that when I execute this from the command line, JRun
does
> pick up the local.properties settings, so it seems like it should be a
> valid
> way to start the container. Has anyone else run into this problem?
> 
> Thanks! Melissa
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org