Re: Wonder's JavaMonitor, is it ready for prime time ?

[Lachlan Deck]

Hi Gavin,

quite a post :-)

On 27/07/2008, at 6:20 AM, Gavin Eadie wrote:

On Jul 26, 2008, at 12:31 AM, Lachlan Deck wrote:

I've been trying to get Wonder's JavaMonitor to work for me without success. Before I delve into its guts, I should know if I'm being too eager to use it. Is

it working for anyone else? ... Gav

We're using it on a test server.

Thanks, Lachlan, I'll return to the battle with more confidence. I wonder if any of the following rings unpleasant bells for anyone, it all looks pretty good to me (but I've been staring at it for hours!) ...

Which adaptor are you using? Apple's, Wonder's?

To be clear - we're not using the most recent nightly. So I'm not sure if that makes any difference or not. Q recently updated the Wonder one, syncing changes between the Wonder one and Apple's. On my laptop, however, I've just got the standard 5.4.x installed. So what steps have you taken to install things?

First, WebObject's deployment infrastructure:


  with jar file frameworks.

     so, wotaskd's classpath.txt:

<.. looks fine ...>
     and, JavaMonitor's classpath.txt:

<... looks fine ...>

  change /Library/WebObjects/Configuration/ to be owned by _appserver

  add launchd files for wotaskd and womonitor, eg:

My ultimate goal is to have a tidy deployment on RHEL 5, but I'm starting on my laptop with Leopard (WO 5.4.2) so that I can figure out the various steps to success. Since Leopard (not Server) doesn't come with deployment capability, this seemed like a good (re)learning strategy. latest Wonder sources for wotaskd and womonitor, build them in embedded form

Mine attached.

let launchd do its thing and wotaskd and JavaMonitor are running. Happiness!!

Next, Apache:

  build the latest (post-Q changes) Adaptor from Wonder


     are same size (104KB), so I'm less nervous.


  'apache.conf' file.  This file starts:

lots of warning messages. I'm nervous, so I build the Apple one and it behaves the same. They both build mod_WebObjects.so files that take a look at '/etc/apache2/httpd.conf' and see that it ends by reading in any *.conf files in '/etc/apache2/other/' -- read through the Wonder

$ ls -lah /etc/apache2/other/
total 24
drwxr-xr-x  5 root  wheel   170B 14 May 12:40 .
drwxr-xr-x  9 root  wheel   306B 22 Feb 03:19 ..
-r--r--r--  1 root  wheel    73B 25 Nov  2007 bonjour.conf
-r--r--r--  1 root  wheel   194B 25 Nov  2007 php5.conf

ALl you need do is create a symlink to the conf file you want to include. e.g., lrwxr-xr-x 1 root wheel 57B 14 May 12:40 webobjects.conf -> / System/Library/WebObjects/Adaptors/Apache2.2/apache.conf

  type 'sudo /usr/sbin/apxs -i -a -n WebObjects \

/System/Library/WebObjects/Adaptors/Apache2.2/ mod_WebObjects.la'

Not needed if doing the above.

my first concerns arise when the application status never goes ON (green).

for uri:
jar:file:///Library/WebObjects/Applications/JavaMonitor.woa/Contents/Library/Ajax.jar!/WebServerResources/wonder.js

the console log shows JavaMonitor unable to load static assets, for example: Jul 26 14:40:06 Gavins-Mobile com.apple.womonitor[48]: 77429367 [WorkerThread4] INFO er.extensions.appserver.ERXStaticResourceRequestHandler - Unable to get contents of file 'jar:file:/Library/WebObjects/ Applications/JavaMonitor.woa/Contents/Library/Ajax.jar!/ WebServerResources/wonder.js' this might be trouble, but since my application is running on port 2001 ('http://localhost:2001/' works), I assume JavaMonitor and wotaskd have done their job.

  However, http://localhost/cgi-bin/WebObjects/VersionDisplay



Diagnosis so far

  uncomment last line of 'apache.conf'
  'sudo touch /tmp/logWebObjects'
  tail -f /Library/WebObjects/Logs/WebObjects.log






     "Cannot load /usr/libexec/apache2/mod_WebObjects.so into server:





     ?

returns "The requested application was not found on this server." and, in the Apache log: ::1 - - [26/Jul/2008:14:48:06 -0400] "GET /cgi-bin/WebObjects/ VersionDisplay HTTP/1.1" 404 99 looks generally OK as far as adapter initialization but no sign of application requests etc. Question: Am I using the right adapter? Apple's one is 4 times bigger than the one I built. Answer: Stay with Apple's -- Wonder's causes Apache to report (as does my build of Apple's): dlopen(/usr/libexec/apache2/mod_WebObjects.so, 10): no suitable image found. Did find: /usr/libexec/apache2/mod_WebObjects.so: mach-o, but wrong architecture Question: It looks like Apache isn't passing '.../cgi-bin/ WebObjects/...' through the adaptor, why not? ? loading 'mod_WebObjects' before 'mod_rewrite' -- no difference

Have you specifically turned on mod_rewrite?

Try just using the stock conf file and simply doing the symlink thing. Just get the basic config working first with the standard WO stuff ... then try updating the adaptor etc. Bit by bit until it breaks.

I'm horribly aware that I've likely done something simply stupid. Stupid or not, I'll write this up in the wiki (more likely, I'll enhance an existing page), for those who travel behind us. I'm also aware that within moments of clicking "Send", the answer will be beamed into my head my magic .. Gav

with regards,
--

Lachlan Deck

com.apple.webobjects.womonitor.plist
Description: Binary data

com.apple.webobjects.wotaskd.plist
Description: Binary data

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list      (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]