Re: WOLips and jMechanic

From: Brendan Duddridge (brenda..lickspace.com)
Date: Wed Sep 08 2004 - 10:19:08 EDT

  • Next message: Andrus Adamchik: "Re: WOLips hangs on "create Resources/Java/...""

    Hi Ulrich,

    I just checked and both my run configurations have the default workspace
    check box selected. My DriveItAdmin run configuration ends up with
    ${working_dir_loc_WOLips:DriveItAdmin} and my DriveItAdmin (Profiled) run
    configuration has ${workspace_loc:DriveItAdmin}. However, I changed my
    DriveItAdmin (Profiled) run configuration to also use
    ${working_dir_loc_WOLips:DriveItAdmin}, but it didn't help. The same error
    occurred.

    Is it possible that jMechanic doesn't work anymore with Eclipse 3 in debug
    mode? There was something about that on the web site, but then it said the
    latest version supported Eclipse 3, so that's a bit confusing.

    Thanks,

    ___________________________

    Brendan Duddridge

    ClickSpace Interactive Inc.
    Suite L100
    239 - 10th Ave SE
    Calgary, AB T2G 0V9
    Canada
    (403) 277-5591
    http://www.clickspace.com/

    > From: Ulrich Köster <ulric..bjectstyle.org>
    > Date: Wed, 8 Sep 2004 09:43:21 +0200
    > To: "WOLips <woproject-de..bjectstyle.org>" <woproject-dev@objectstyle.org>
    > Subject: Re: WOLips and jMechanic
    >
    > Hi Brendan,
    >
    >
    > Am 07.09.2004 um 20:30 schrieb Brendan Duddridge:
    >
    >> Hi,
    >>
    >> Has anyone managed to get WOLips working with jMechanic? I installed
    >> jMechanic and WOLips Profiling, but when I run my profiled WO
    >> application, I
    >> get the following in my output:
    >>
    >> HPROF ERROR: unable to resolve a method id
    >> HPROF ERROR : got a NULL trace in class_load
    >> HPROF ERROR: unable to map JVMPI obj ID to hprof obj ID in
    >> globalref_alloc
    >> HPROF ERROR: unable to map JVMPI obj ID to hprof obj ID in
    >> globalref_alloc
    >> HPROF ERROR: class ID already in use
    >>
    >> [2004-09-07 12:24:05 MDT] <main> Created adaptor of class
    >> WODefaultAdaptor
    >> on port 63965 and address voyager.local/192.168.5.172 with
    >> WOWorkerThread
    >> minimum of 16 and maximum of 256
    >> [2004-09-07 12:24:08 MDT] <main> Application project found: Will locate
    >> resources in '/Users/brendan/Projects/DriveIt/DriveItAdmin' rather than
    >> '/Users/brendan/Projects/DriveIt/DriveItAdmin/build/DriveItAdmin.woa' .
    >> [2004-09-07 12:24:09 MDT] <main> Creating LifebeatThread now with:
    >> DriveItAdmin 63965 voyager.local/192.168.5.172 1085 30000
    >> *** DIApplication: WOSMTPHost: mail.clickspace.com
    >> *** DIApplication: SPAM_SMTP_HOST: saturn.clickspace.com
    >> *** DIApplication: NO_SPAM_SMTP_HOST: krypton.clickspace.com
    >> In developer mode: true
    >> Welcome to DriveItAdmin !
    >>
    >> [2004-09-07 12:24:11 MDT] <main> Opening application's URL in browser:
    >> http://voyager.local:63965/cgi-bin/WebObjects/DriveItAdmin.woa
    >> [2004-09-07 12:24:11 MDT] <main> Waiting for requests...
    >> [2004-09-07 12:24:17 MDT] <WorkerThread0>
    >> WOBundle.lookForClassInAllBundles(CSLogin) failed!
    >> [2004-09-07 12:24:17 MDT] <WorkerThread0>
    >> <com.webobjects.appserver._private.WOComponentRequestHandler>:
    >> Exception
    >> occurred while handling request:
    >> com.webobjects.foundation.NSKeyValueCoding$UnknownKeyException:
    >> <com.webobjects.appserver.WOSession 0xa980fa> valueForKey(): lookup of
    >> unknown key: 'isLoggedIn'.
    >> This class does not have an instance variable of the name isLoggedIn or
    >> _isLoggedIn, nor a method of the name isLoggedIn, _isLoggedIn,
    >> getIsLoggedIn, or _getIsLoggedIn
    >>
    >>
    >> The first suspect information is at the top with all those HPROF
    >> ERRORs. The
    >> second suspect part is the fact that it can't find my isLoggedIn
    >> method,
    >> which does exist. It works fine if I run the application normally or
    >> even in
    >> the debugger. But when I run it with a Profiled WO App configuration,
    >> I get
    >> the above errors.
    >>
    >
    > The HPROF Errors are okay. Are the working directories equal for both
    > launch configs?
    >
    > Ulrich
    >
    >

    This archive was generated by hypermail 2.0.0 : Wed Sep 08 2004 - 10:19:13 EDT