Re: Can't start with JavaMonitor

From: Ulrich Köster (ulric..bjectstyle.org)
Date: Wed Jul 30 2003 - 15:52:09 EDT

  • Next message: Christian Edward Gruber: "RE: Can't start with JavaMonitor"

    Hi,

    we have a some of applications running on linux. All build with
    woproject/WOLips. Our deployment expert always does some stuff with
    chmod. Maybe that's the problem? I can ask him tomorrow.

    Ulrich

    On Mittwoch, 30. Juli 2003, at 21:38 Uhr, Chuck Hill wrote:

    > A couple of things to try to get more information on the launch
    > failure...
    >
    >
    > 1. Add this to the launch arguments in Monitor and try to start the
    > instance:
    > 1>/tmp/launch.txt 2>&1
    >
    > This will record what happens while the Java process is being
    > launched
    > and will show failures due to classpath problems etc.
    >
    >
    > 2. Add logging to the public static void main(String argv[]) method to
    > log
    > interesting information. NSLog may not be functional this early in the
    > process so try using System.out.println and output redirection as in
    > the
    > previous step, or add code like this to sent logging information to a
    > file:
    >
    > FileWriter fos = null;
    > try
    > {
    > fos = new FileWriter("C:/temp/PostLaunch.txt");
    > fos.write("Starting....\n");
    >
    > fos.write(<whatever else you need to log>);
    >
    > fos.flush();
    > fos.close();
    >
    > WOApplication.main(argv, Application.class);
    > }
    > catch (Exception e)
    > {
    > System.out.println(e);
    > }
    >
    >
    > FWIW
    >
    >
    > Chuck
    >
    >
    > At 03:25 PM 30/07/2003 -0400, Christian Edward Gruber wrote:
    >> Hi Marc,
    >>
    >> I have exactly the same problem, and have had for months, but have
    >> temporarily given up on it pending more time to fix it. What is
    >> maddening, is that no matter how much I fiddle with the log settings
    >> in
    >> JavaMonitor, I can't get ANY debug output - only the file being
    >> created.
    >> It's always empty. I've taken to starting at the command-line and
    >> piping all output into a log file and using logadm to manage the file,
    >> but I won't really be able to get the whole load-balancing ecosystem
    >> to
    >> work if I can't even get JavaMonitor to start an instance.
    >>
    >> I hadn't tried building from project builder, because we're in an
    >> all-eclipse environment. That's a new and important clue.
    >>
    >> Christian.
    >>
    >>
    >>> -----Original Message-----
    >>> From: Marc Respass [mailto:mar..arcrespass.com]
    >>> Sent: Wednesday, July 30, 2003 2:09 PM
    >>> To: Ulrich Köster
    >>> Cc: woproject-de..bjectstyle.org
    >>> Subject: Re: Can't start with JavaMonitor
    >>>
    >>>
    >>> Hi Ulrich,
    >>>
    >>> This is WO 5.2.1. I don't know what resources are missing. I
    >>> can't find
    >>> any difference. I agree that the build scripts seem to be identical
    >>> which is why I wonder if anyone else has seen this problem. I
    >>> don't get
    >>> any logs written so I can't even figure out what is happening.
    >>>
    >>> Marc
    >>>
    >>> On Wednesday, July 30, 2003, at 01:08 PM, Ulrich Köster wrote:
    >>>
    >>>> Hi Marc,
    >>>>
    >>>> is this with WO 5.1 or 5.2? I've tested it with WO5.2 and the
    >>>> buildscripts seems to be identically.
    >>>>
    >>>> Of what kind is the missing resource?
    >>>>
    >>>> Ulrich
    >>>>
    >>>> On Mittwoch, 30. Juli 2003, at 17:17 Uhr, Marc Respass wrote:
    >>>>
    >>>>> Hi,
    >>>>>
    >>>>> I'm using Eclipse 2.1.1 and WOLips 1.0.4 on Mac OS X (10.2.6). I'm
    >>>>> building on Mac OS X and copying the build to Solaris to
    >>> test. When I
    >>>>> build with Eclipse, the application starts at the command
    >>> line but it
    >>>>> will not start with JavaMonitor. I tested this a lot. What
    >>> does work
    >>>>> is to import the PB.project into Project Builder and build
    >>> using PBX.
    >>>>> Then I copy the build to Solaris and it starts in JavaMonitor.
    >>>>>
    >>>>> Has anyone else experienced this? Is there something that I'm not
    >>>>> doing? I admit that I've only read enough docs to get
    >>> builds working
    >>>>> locally in Eclipse. I cannot figure out what is wrong but
    >>> I know that
    >>>>> if I build using PBX, everything works fine. If I build
    >>> with Eclipse,
    >>>>> it will not start in JavaMonitor. Also, I have not tested
    >>> enough but
    >>>>> my application would not find its resources in a framework
    >>> built with
    >>>>> Eclipse. I built it with PBX and deployed and it worked. I notice
    >>>>> that a WO framework directory is a little different if
    >>> built from PBX
    >>>>> and though it *shouldn't* matter it does seem to for me.
    >>>>>
    >>>>> Any help is greatly appreciated. We will be moving to full
    >>> ant builds
    >>>>> using woproject and building on Solaris instead of the
    >>> build and copy
    >>>>> we do now so maybe that is the real solution.
    >>>>>
    >>>>> Thanks
    >>>>> Marc
    >>>>>
    >>>>
    >>>
    >>>
    >>
    >>
    >>
    >
    > --
    >
    > Chuck Hill chil..lobal-village.net
    > Global Village Consulting Inc.
    > http://www.global-village.net



    This archive was generated by hypermail 2.0.0 : Wed Jul 30 2003 - 15:48:00 EDT