Re: Wonder JavaMonitor file browser
Am 20.02.2014 um 14:03 schrieb David Avendasora webobje...@avendasora.com: On Feb 20, 2014, at 6:48 AM, Johann Werner j...@oyosys.com wrote: Hi Raymond, the file browser in JavaMonitor still works. When the listing is displayed the first time the directory to show is undefined though and thus shows no files. If you enter e.g. a '/' in Jump to: and click submit you get the correct listing of your root directory. It could choose automatically the root directory at start though. Better would be the Application Root, no? Sure, but what is the application root? This could / will be different on OS X, Linux, Windows, or your own in-house deployment structure. Perhaps adding a setting on the preference page would be the best way to go? Anything would be better than saying “Current directory:” and “Back (Up one directory level)” when you are NOT even in a directory. It is completely misleading. Better to just have the “Jump to:” field and hide the table until really, truly *is* a current directory to show the contents of. That I was just to push ;-) I’ll take a look at it. There’s plenty room to improve yet. Chuck, stop screaming. How badly could I mess it up?? Dave — WebObjects - so easy that even Dave Avendasora can do it!™ — David Avendasora Senior Software Abuser Nekesto, Inc. ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/jw%40oyosys.com This email sent to j...@oyosys.com signature.asc Description: Message signed with OpenPGP using GPGMail ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor problem
I just did a raw installation on Ubuntu 10.04 Server (only installed Java 1.6 from Oracle and wotaskd/Monitor), and I don't get the problem you have. The path to prototype.js is : http://192.168.0.48:56789/cgi-bin/WebObjects/JavaMonitor.woa/wr/wodata=/opt/Local/Library/WebObjects/JavaApplications/JavaMonitor.woa/Contents/Frameworks/Ajax.framework/WebServerResources/prototype.js Are you trying to use Monitor under Apache? Oracle jdk-6u31-linux-x64.bin Running which JDK? Ubuntu 10.04 LTS, so Yeah. :-) On May 2, 2012, at 8:19 PM, Pascal Robert wrote: Is this on Debian? Yes, I just downloaded: http://jenkins.wocommunity.org/job/WonderIntegration/lastSuccessfulBuild/artifact/Root/Roots/JavaMonitor.tar.gz That has the same behavior (or lack thereof!). :) On May 2, 2012, at 7:48 PM, Pascal Robert wrote: That sounds like a WOFrameworksBaseUrl problems… Can you try with the build on jenkins.wocommunity.org to see if you have the same problem? I've just updated my copy of wonder's integration branch, and built JavaMonitor and friends like this: ant frameworks deployment.tools -Ddeployment.standalone=true I then moved my newly-built copy of JavaMonitor.woa/ to my deployment web server (wotaskd.woa on the machine is only a couple of days old), but when I run it and go to the Site tab, clicking any of the 3 javascript actions (HTTP Adaptor Settings, Email Notifications, Backup Site Configuration) does nothing. Up in the head section, I see: script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/prototype.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/effects.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/wonder.js/script Does the Ajax.framework's WebServerResources have to be installed separately? I guess I had hoped/assumed it would use the embedded frameworks' WS resources via resource manager calls, or something. No? - Patrick ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca This email sent to prob...@macti.ca ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/pgr%40vt.edu This email sent to p...@vt.edu ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor problem
Yes, I guess I've always used it via Apache -- with a devl URL, i.e. https://hostname/cgi-bin/WebObjects/JavaMonitor.woa/-56789 and protected it via Apache config directives. Because I'm accessing w/a devl URL, there's no bizarre add JavaMonitor with JavaMonitor weirdness. I'd been looking at this all morning, and learned: (1) It's not unique to Ubuntu; it's not OS-specific at all - it happens w/OSX as well. (Of course!) (2) The wonder build of JavaMonitor doesn't set -WOFrameworksBaseURL the way an ant build of a normal project does. (3) It dawned on me that there was no corresponding JavaMonitor-WebServerResources.tar.gz. I guess I had manually copied the relevant WebServerResources dirs over to the Apache DocumentRoot at some earlier date, and forgotten about it. *sigh* I take it the usual approach is to open port 56789 to specific hosts that require access? With Apache, I can restrict access to specific hosts AND require user authentication and authorize access only to specific users. Live and learn. :-/ - Patrick On May 4, 2012, at 2:16 PM, Pascal Robert wrote: I just did a raw installation on Ubuntu 10.04 Server (only installed Java 1.6 from Oracle and wotaskd/Monitor), and I don't get the problem you have. The path to prototype.js is : http://192.168.0.48:56789/cgi-bin/WebObjects/JavaMonitor.woa/wr/wodata=/opt/Local/Library/WebObjects/JavaApplications/JavaMonitor.woa/Contents/Frameworks/Ajax.framework/WebServerResources/prototype.js Are you trying to use Monitor under Apache? Oracle jdk-6u31-linux-x64.bin Running which JDK? Ubuntu 10.04 LTS, so Yeah. :-) On May 2, 2012, at 8:19 PM, Pascal Robert wrote: Is this on Debian? Yes, I just downloaded: http://jenkins.wocommunity.org/job/WonderIntegration/lastSuccessfulBuild/artifact/Root/Roots/JavaMonitor.tar.gz That has the same behavior (or lack thereof!). :) On May 2, 2012, at 7:48 PM, Pascal Robert wrote: That sounds like a WOFrameworksBaseUrl problems… Can you try with the build on jenkins.wocommunity.org to see if you have the same problem? I've just updated my copy of wonder's integration branch, and built JavaMonitor and friends like this: ant frameworks deployment.tools -Ddeployment.standalone=true I then moved my newly-built copy of JavaMonitor.woa/ to my deployment web server (wotaskd.woa on the machine is only a couple of days old), but when I run it and go to the Site tab, clicking any of the 3 javascript actions (HTTP Adaptor Settings, Email Notifications, Backup Site Configuration) does nothing. Up in the head section, I see: script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/prototype.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/effects.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/wonder.js/script Does the Ajax.framework's WebServerResources have to be installed separately? I guess I had hoped/assumed it would use the embedded frameworks' WS resources via resource manager calls, or something. No? - Patrick ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca This email sent to prob...@macti.ca ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/pgr%40vt.edu This email sent to p...@vt.edu ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor problem
Yes, I guess I've always used it via Apache -- with a devl URL, i.e. https://hostname/cgi-bin/WebObjects/JavaMonitor.woa/-56789 and protected it via Apache config directives. Because I'm accessing w/a devl URL, there's no bizarre add JavaMonitor with JavaMonitor weirdness. I'd been looking at this all morning, and learned: (1) It's not unique to Ubuntu; it's not OS-specific at all - it happens w/OSX as well. (Of course!) (2) The wonder build of JavaMonitor doesn't set -WOFrameworksBaseURL the way an ant build of a normal project does. Exact, probably because everyone says it shouldn't run under Apache :-) (3) It dawned on me that there was no corresponding JavaMonitor-WebServerResources.tar.gz. I guess I had manually copied the relevant WebServerResources dirs over to the Apache DocumentRoot at some earlier date, and forgotten about it. *sigh* I take it the usual approach is to open port 56789 to specific hosts that require access? With Apache, I can restrict access to specific hosts AND require user authentication and authorize access only to specific users. Maybe a reverse proxy (ProxyPassReverse) and blocking port 56789 outside the box would work. Live and learn. :-/ - Patrick On May 4, 2012, at 2:16 PM, Pascal Robert wrote: I just did a raw installation on Ubuntu 10.04 Server (only installed Java 1.6 from Oracle and wotaskd/Monitor), and I don't get the problem you have. The path to prototype.js is : http://192.168.0.48:56789/cgi-bin/WebObjects/JavaMonitor.woa/wr/wodata=/opt/Local/Library/WebObjects/JavaApplications/JavaMonitor.woa/Contents/Frameworks/Ajax.framework/WebServerResources/prototype.js Are you trying to use Monitor under Apache? Oracle jdk-6u31-linux-x64.bin Running which JDK? Ubuntu 10.04 LTS, so Yeah. :-) On May 2, 2012, at 8:19 PM, Pascal Robert wrote: Is this on Debian? Yes, I just downloaded: http://jenkins.wocommunity.org/job/WonderIntegration/lastSuccessfulBuild/artifact/Root/Roots/JavaMonitor.tar.gz That has the same behavior (or lack thereof!). :) On May 2, 2012, at 7:48 PM, Pascal Robert wrote: That sounds like a WOFrameworksBaseUrl problems… Can you try with the build on jenkins.wocommunity.org to see if you have the same problem? I've just updated my copy of wonder's integration branch, and built JavaMonitor and friends like this: ant frameworks deployment.tools -Ddeployment.standalone=true I then moved my newly-built copy of JavaMonitor.woa/ to my deployment web server (wotaskd.woa on the machine is only a couple of days old), but when I run it and go to the Site tab, clicking any of the 3 javascript actions (HTTP Adaptor Settings, Email Notifications, Backup Site Configuration) does nothing. Up in the head section, I see: script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/prototype.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/effects.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/wonder.js/script Does the Ajax.framework's WebServerResources have to be installed separately? I guess I had hoped/assumed it would use the embedded frameworks' WS resources via resource manager calls, or something. No? - Patrick ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca This email sent to prob...@macti.ca ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/pgr%40vt.edu This email sent to p...@vt.edu ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor problem
Using a reverse proxy is a great idea... thanks! For you folks who access JavaMonitor directly via its port, how do you *prevent* access via Apache (i.e. via .../JavaMonitor.woa/-56789) ? On May 4, 2012, at 3:34 PM, Pascal Robert wrote: Yes, I guess I've always used it via Apache -- with a devl URL, i.e. https://hostname/cgi-bin/WebObjects/JavaMonitor.woa/-56789 and protected it via Apache config directives. Because I'm accessing w/a devl URL, there's no bizarre add JavaMonitor with JavaMonitor weirdness. I'd been looking at this all morning, and learned: (1) It's not unique to Ubuntu; it's not OS-specific at all - it happens w/OSX as well. (Of course!) (2) The wonder build of JavaMonitor doesn't set -WOFrameworksBaseURL the way an ant build of a normal project does. Exact, probably because everyone says it shouldn't run under Apache :-) (3) It dawned on me that there was no corresponding JavaMonitor-WebServerResources.tar.gz. I guess I had manually copied the relevant WebServerResources dirs over to the Apache DocumentRoot at some earlier date, and forgotten about it. *sigh* I take it the usual approach is to open port 56789 to specific hosts that require access? With Apache, I can restrict access to specific hosts AND require user authentication and authorize access only to specific users. Maybe a reverse proxy (ProxyPassReverse) and blocking port 56789 outside the box would work. Live and learn. :-/ - Patrick On May 4, 2012, at 2:16 PM, Pascal Robert wrote: I just did a raw installation on Ubuntu 10.04 Server (only installed Java 1.6 from Oracle and wotaskd/Monitor), and I don't get the problem you have. The path to prototype.js is : http://192.168.0.48:56789/cgi-bin/WebObjects/JavaMonitor.woa/wr/wodata=/opt/Local/Library/WebObjects/JavaApplications/JavaMonitor.woa/Contents/Frameworks/Ajax.framework/WebServerResources/prototype.js Are you trying to use Monitor under Apache? Oracle jdk-6u31-linux-x64.bin Running which JDK? Ubuntu 10.04 LTS, so Yeah. :-) On May 2, 2012, at 8:19 PM, Pascal Robert wrote: Is this on Debian? Yes, I just downloaded: http://jenkins.wocommunity.org/job/WonderIntegration/lastSuccessfulBuild/artifact/Root/Roots/JavaMonitor.tar.gz That has the same behavior (or lack thereof!). :) On May 2, 2012, at 7:48 PM, Pascal Robert wrote: That sounds like a WOFrameworksBaseUrl problems… Can you try with the build on jenkins.wocommunity.org to see if you have the same problem? I've just updated my copy of wonder's integration branch, and built JavaMonitor and friends like this: ant frameworks deployment.tools -Ddeployment.standalone=true I then moved my newly-built copy of JavaMonitor.woa/ to my deployment web server (wotaskd.woa on the machine is only a couple of days old), but when I run it and go to the Site tab, clicking any of the 3 javascript actions (HTTP Adaptor Settings, Email Notifications, Backup Site Configuration) does nothing. Up in the head section, I see: script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/prototype.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/effects.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/wonder.js/script Does the Ajax.framework's WebServerResources have to be installed separately? I guess I had hoped/assumed it would use the embedded frameworks' WS resources via resource manager calls, or something. No? - Patrick ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca This email sent to prob...@macti.ca ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/pgr%40vt.edu This email sent to p...@vt.edu ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor problem
That sounds like a WOFrameworksBaseUrl problems… Can you try with the build on jenkins.wocommunity.org to see if you have the same problem? I've just updated my copy of wonder's integration branch, and built JavaMonitor and friends like this: ant frameworks deployment.tools -Ddeployment.standalone=true I then moved my newly-built copy of JavaMonitor.woa/ to my deployment web server (wotaskd.woa on the machine is only a couple of days old), but when I run it and go to the Site tab, clicking any of the 3 javascript actions (HTTP Adaptor Settings, Email Notifications, Backup Site Configuration) does nothing. Up in the head section, I see: script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/prototype.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/effects.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/wonder.js/script Does the Ajax.framework's WebServerResources have to be installed separately? I guess I had hoped/assumed it would use the embedded frameworks' WS resources via resource manager calls, or something. No? - Patrick ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca This email sent to prob...@macti.ca ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor problem
Yes, I just downloaded: http://jenkins.wocommunity.org/job/WonderIntegration/lastSuccessfulBuild/artifact/Root/Roots/JavaMonitor.tar.gz That has the same behavior (or lack thereof!). :) On May 2, 2012, at 7:48 PM, Pascal Robert wrote: That sounds like a WOFrameworksBaseUrl problems… Can you try with the build on jenkins.wocommunity.org to see if you have the same problem? I've just updated my copy of wonder's integration branch, and built JavaMonitor and friends like this: ant frameworks deployment.tools -Ddeployment.standalone=true I then moved my newly-built copy of JavaMonitor.woa/ to my deployment web server (wotaskd.woa on the machine is only a couple of days old), but when I run it and go to the Site tab, clicking any of the 3 javascript actions (HTTP Adaptor Settings, Email Notifications, Backup Site Configuration) does nothing. Up in the head section, I see: script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/prototype.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/effects.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/wonder.js/script Does the Ajax.framework's WebServerResources have to be installed separately? I guess I had hoped/assumed it would use the embedded frameworks' WS resources via resource manager calls, or something. No? - Patrick ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca This email sent to prob...@macti.ca ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/pgr%40vt.edu This email sent to p...@vt.edu ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor problem
Is this on Debian? Yes, I just downloaded: http://jenkins.wocommunity.org/job/WonderIntegration/lastSuccessfulBuild/artifact/Root/Roots/JavaMonitor.tar.gz That has the same behavior (or lack thereof!). :) On May 2, 2012, at 7:48 PM, Pascal Robert wrote: That sounds like a WOFrameworksBaseUrl problems… Can you try with the build on jenkins.wocommunity.org to see if you have the same problem? I've just updated my copy of wonder's integration branch, and built JavaMonitor and friends like this: ant frameworks deployment.tools -Ddeployment.standalone=true I then moved my newly-built copy of JavaMonitor.woa/ to my deployment web server (wotaskd.woa on the machine is only a couple of days old), but when I run it and go to the Site tab, clicking any of the 3 javascript actions (HTTP Adaptor Settings, Email Notifications, Backup Site Configuration) does nothing. Up in the head section, I see: script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/prototype.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/effects.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/wonder.js/script Does the Ajax.framework's WebServerResources have to be installed separately? I guess I had hoped/assumed it would use the embedded frameworks' WS resources via resource manager calls, or something. No? - Patrick ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca This email sent to prob...@macti.ca ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/pgr%40vt.edu This email sent to p...@vt.edu ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor problem
Ubuntu 10.04 LTS, so Yeah. :-) On May 2, 2012, at 8:19 PM, Pascal Robert wrote: Is this on Debian? Yes, I just downloaded: http://jenkins.wocommunity.org/job/WonderIntegration/lastSuccessfulBuild/artifact/Root/Roots/JavaMonitor.tar.gz That has the same behavior (or lack thereof!). :) On May 2, 2012, at 7:48 PM, Pascal Robert wrote: That sounds like a WOFrameworksBaseUrl problems… Can you try with the build on jenkins.wocommunity.org to see if you have the same problem? I've just updated my copy of wonder's integration branch, and built JavaMonitor and friends like this: ant frameworks deployment.tools -Ddeployment.standalone=true I then moved my newly-built copy of JavaMonitor.woa/ to my deployment web server (wotaskd.woa on the machine is only a couple of days old), but when I run it and go to the Site tab, clicking any of the 3 javascript actions (HTTP Adaptor Settings, Email Notifications, Backup Site Configuration) does nothing. Up in the head section, I see: script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/prototype.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/effects.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/wonder.js/script Does the Ajax.framework's WebServerResources have to be installed separately? I guess I had hoped/assumed it would use the embedded frameworks' WS resources via resource manager calls, or something. No? - Patrick ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca This email sent to prob...@macti.ca ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/pgr%40vt.edu This email sent to p...@vt.edu ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor problem
Running which JDK? Ubuntu 10.04 LTS, so Yeah. :-) On May 2, 2012, at 8:19 PM, Pascal Robert wrote: Is this on Debian? Yes, I just downloaded: http://jenkins.wocommunity.org/job/WonderIntegration/lastSuccessfulBuild/artifact/Root/Roots/JavaMonitor.tar.gz That has the same behavior (or lack thereof!). :) On May 2, 2012, at 7:48 PM, Pascal Robert wrote: That sounds like a WOFrameworksBaseUrl problems… Can you try with the build on jenkins.wocommunity.org to see if you have the same problem? I've just updated my copy of wonder's integration branch, and built JavaMonitor and friends like this: ant frameworks deployment.tools -Ddeployment.standalone=true I then moved my newly-built copy of JavaMonitor.woa/ to my deployment web server (wotaskd.woa on the machine is only a couple of days old), but when I run it and go to the Site tab, clicking any of the 3 javascript actions (HTTP Adaptor Settings, Email Notifications, Backup Site Configuration) does nothing. Up in the head section, I see: script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/prototype.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/effects.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/wonder.js/script Does the Ajax.framework's WebServerResources have to be installed separately? I guess I had hoped/assumed it would use the embedded frameworks' WS resources via resource manager calls, or something. No? - Patrick ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca This email sent to prob...@macti.ca ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/pgr%40vt.edu This email sent to p...@vt.edu ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor problem
Oracle jdk-6u31-linux-x64.bin Running which JDK? Ubuntu 10.04 LTS, so Yeah. :-) On May 2, 2012, at 8:19 PM, Pascal Robert wrote: Is this on Debian? Yes, I just downloaded: http://jenkins.wocommunity.org/job/WonderIntegration/lastSuccessfulBuild/artifact/Root/Roots/JavaMonitor.tar.gz That has the same behavior (or lack thereof!). :) On May 2, 2012, at 7:48 PM, Pascal Robert wrote: That sounds like a WOFrameworksBaseUrl problems… Can you try with the build on jenkins.wocommunity.org to see if you have the same problem? I've just updated my copy of wonder's integration branch, and built JavaMonitor and friends like this: ant frameworks deployment.tools -Ddeployment.standalone=true I then moved my newly-built copy of JavaMonitor.woa/ to my deployment web server (wotaskd.woa on the machine is only a couple of days old), but when I run it and go to the Site tab, clicking any of the 3 javascript actions (HTTP Adaptor Settings, Email Notifications, Backup Site Configuration) does nothing. Up in the head section, I see: script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/prototype.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/effects.js/script script src=/WebObjects/Frameworks/Ajax.framework/WebServerResources/wonder.js/script Does the Ajax.framework's WebServerResources have to be installed separately? I guess I had hoped/assumed it would use the embedded frameworks' WS resources via resource manager calls, or something. No? - Patrick ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca This email sent to prob...@macti.ca ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/pgr%40vt.edu This email sent to p...@vt.edu ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor
On Jun 9, 2011, at 2:23 PM, Klaus Berkling wrote: Got the latest binaries. Looks like things are working a lot better (will need to look at my build setup). But it seems like 'Refuse New Sessions doesn't work. I does work on an older build of Monitor on a production server... Ok all, thanks for your responses yesterday regarding my issues. But wait, there is more. What I'm trying to do is send a bunch of REST and JSON commands to JavaMonitor to: 1) Add a bunch of instances across several nodes. Not 10 to one node, then 10 on the next, and so on; but rather one (or two) on one node, one (or two) on the next and so on. I might have five nodes. Proper load balancing, you understand. This is a pain to do in JavaMonitor. 2) Run a different number of instances for an app based on usage patterns, I might have one app serving Japan, another for the US, and yet another for Europe. e.g. I would bring up instances for Japan while I turn off instances for the US. That's the background. I have mostly completed my code, the JSON and REST calls, works nicely (thanks REST/JSON people). I can add instances and I can turn some on and turn others off. Quite neat actually. Here comes my problem. When I add the IP addresses for my nodes, just one, things break (I can't use just localhost). I'm still running only one host, but using the IP address of it's private NIC. - Turning off an instance does not work, turning on Refuse New Sessions does not work (no JSON or REST involved). - However, I can turn instances on, and I can force-quit instances (I can see this in the instance log). - Everything works if I use localhost. I have added -WOHost ip to my app, the apache.conf (WebObjectsConfig), and wotaskd. Adding the WOHost in the app will not work once I have multiple instance nodes. I have not found a thing in the logs that could shed light on this. One neat-oh site effect after adding -WOHost to wotaskd is that it resulted in an empty SiteConfig.xml file. :-) So, is it probable there a bug in wonder's JavaMonitor, should I pursue that? Or is it me and my configuration? kib Live as if you were to die tomorrow. Learn as if you were to live forever. Mahatma Gandhi Klaus Berkling Web Application Dev. Systems Analyst DynEd International, Inc. www.dyned.com | blog smime.p7s Description: S/MIME cryptographic signature ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor
Hi Klaus, On Jun 10, 2011, at 3:35 PM, Klaus Berkling wrote: On Jun 9, 2011, at 2:23 PM, Klaus Berkling wrote: Got the latest binaries. Looks like things are working a lot better (will need to look at my build setup). But it seems like 'Refuse New Sessions doesn't work. I does work on an older build of Monitor on a production server... Ok all, thanks for your responses yesterday regarding my issues. But wait, there is more. What I'm trying to do is send a bunch of REST and JSON commands to JavaMonitor to: 1) Add a bunch of instances across several nodes. Not 10 to one node, then 10 on the next, and so on; but rather one (or two) on one node, one (or two) on the next and so on. I might have five nodes. Proper load balancing, you understand. This is a pain to do in JavaMonitor. Yes. Very. Painful. 2) Run a different number of instances for an app based on usage patterns, I might have one app serving Japan, another for the US, and yet another for Europe. e.g. I would bring up instances for Japan while I turn off instances for the US. That's the background. I have mostly completed my code, the JSON and REST calls, works nicely (thanks REST/JSON people). I can add instances and I can turn some on and turn others off. Quite neat actually. Here comes my problem. When I add the IP addresses for my nodes, just one, things break (I can't use just localhost). I'm still running only one host, but using the IP address of it's private NIC. private NIC Uh oh. - Turning off an instance does not work, turning on Refuse New Sessions does not work (no JSON or REST involved). - However, I can turn instances on, and I can force-quit instances (I can see this in the instance log). - Everything works if I use localhost. There are some security checks around the IP address. See WOHostUtilities in Wonder for what is probably the fix for your problem: * pThis class replaces the WebObjects version to support loading a new IP as a local IP to the local hosts list. * This will authorize that IP to send management requests, like stopping the application, or * turning on the refuse new instance setting. This is necessary if WO does not automatically * add the needed IP to the local host list. It happens when you use private IPs and * is recognized as a problem on multi-homed linux servers./p I have added -WOHost ip to my app, the apache.conf (WebObjectsConfig), and wotaskd. Adding the WOHost in the app will not work once I have multiple instance nodes. I have not found a thing in the logs that could shed light on this. One neat-oh site effect after adding -WOHost to wotaskd is that it resulted in an empty SiteConfig.xml file. :-) That usually indicates a permissions problem (?) or a corrupt file. Wonder's version should back it up. So, is it probable there a bug in wonder's JavaMonitor, should I pursue that? Or is it me and my configuration? Private IP address is my guess for today. Chuck -- Chuck Hill Senior Consultant / VP Development Come to WOWODC this July for unparalleled WO learning opportunities and real peer to peer problem solving! Network, socialize, and enjoy a great cosmopolitan city. See you there! http://www.wocommunity.org/wowodc11/ smime.p7s Description: S/MIME cryptographic signature ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor
On Jun 10, 2011, at 7:07 PM, Klaus Berkling wrote: On Jun 10, 2011, at 5:43 PM, Chuck Hill wrote: There are some security checks around the IP address. See WOHostUtilities in Wonder for what is probably the fix for your problem: * pThis class replaces the WebObjects version to support loading a new IP as a local IP to the local hosts list. * This will authorize that IP to send management requests, like stopping the application, or * turning on the refuse new instance setting. This is necessary if WO does not automatically * add the needed IP to the local host list. It happens when you use private IPs and * is recognized as a problem on multi-homed linux servers./p Thanks. This sounds a lot like my issue (now why did I not find the thread...). I added this line: er.extensions.WOHostUtilities.localhostips=(10.0.0.20,192.168.10.96) The 10... address is private, the 192... address is 'public.' No luck. Is er.extensions.WOHostUtilities already used in wonder's JavaMonitor or do I need to add it? That property is for the app, not JavaMonitor. It tells the app that it is OK to obey admin actions from that address. Chuck -- Chuck Hill Senior Consultant / VP Development Come to WOWODC this July for unparalleled WO learning opportunities and real peer to peer problem solving! Network, socialize, and enjoy a great cosmopolitan city. See you there! http://www.wocommunity.org/wowodc11/ smime.p7s Description: S/MIME cryptographic signature ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor
On Jun 10, 2011, at 7:10 PM, Chuck Hill wrote: On Jun 10, 2011, at 7:07 PM, Klaus Berkling wrote: On Jun 10, 2011, at 5:43 PM, Chuck Hill wrote: There are some security checks around the IP address. See WOHostUtilities in Wonder for what is probably the fix for your problem: * pThis class replaces the WebObjects version to support loading a new IP as a local IP to the local hosts list. * This will authorize that IP to send management requests, like stopping the application, or * turning on the refuse new instance setting. This is necessary if WO does not automatically * add the needed IP to the local host list. It happens when you use private IPs and * is recognized as a problem on multi-homed linux servers./p Thanks. This sounds a lot like my issue (now why did I not find the thread...). I added this line: er.extensions.WOHostUtilities.localhostips=(10.0.0.20,192.168.10.96) The 10... address is private, the 192... address is 'public.' No luck. Is er.extensions.WOHostUtilities already used in wonder's JavaMonitor or do I need to add it? That property is for the app, not JavaMonitor. It tells the app that it is OK to obey admin actions from that address. Ha ha ha. I had added it to wotaskd for the same reason, wotaskd being the 'app'. I also added it to our app for good measure. I'm laughing because, if our app were a Wonder app, this would be trivial, but it's not so ... sigh. I will revisit this later then I'll (ab)use a HelloWorld app. Time to go home. Thanks Chuck!! kib We keep moving forward, opening new doors, and doing new things, because we're curious and curiosity keeps leading us down new paths. Walt Disney Klaus Berkling Web Application Dev. Systems Analyst DynEd International, Inc. www.dyned.com | blog smime.p7s Description: S/MIME cryptographic signature ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor
On Jun 10, 2011, at 7:39 PM, Klaus Berkling wrote: On Jun 10, 2011, at 7:10 PM, Chuck Hill wrote: On Jun 10, 2011, at 7:07 PM, Klaus Berkling wrote: On Jun 10, 2011, at 5:43 PM, Chuck Hill wrote: There are some security checks around the IP address. See WOHostUtilities in Wonder for what is probably the fix for your problem: * pThis class replaces the WebObjects version to support loading a new IP as a local IP to the local hosts list. * This will authorize that IP to send management requests, like stopping the application, or * turning on the refuse new instance setting. This is necessary if WO does not automatically * add the needed IP to the local host list. It happens when you use private IPs and * is recognized as a problem on multi-homed linux servers./p Thanks. This sounds a lot like my issue (now why did I not find the thread...). I added this line: er.extensions.WOHostUtilities.localhostips=(10.0.0.20,192.168.10.96) The 10... address is private, the 192... address is 'public.' No luck. Is er.extensions.WOHostUtilities already used in wonder's JavaMonitor or do I need to add it? That property is for the app, not JavaMonitor. It tells the app that it is OK to obey admin actions from that address. Ha ha ha. I had added it to wotaskd for the same reason, wotaskd being the 'app'. I also added it to our app for good measure. I'm laughing because, if our app were a Wonder app, this would be trivial, but it's not so ... sigh. I will revisit this later then I'll (ab)use a HelloWorld app. This is a patch for a WO class, so it is a class loading thing. This class needs to be in the package com.webobjects.appserver._private and the jar it is in needs to come before javawebobjects.jar in the classpath. Time to go home. Thanks Chuck!! I am home. Time to keep working! Chuck -- Chuck Hill Senior Consultant / VP Development Come to WOWODC this July for unparalleled WO learning opportunities and real peer to peer problem solving! Network, socialize, and enjoy a great cosmopolitan city. See you there! http://www.wocommunity.org/wowodc11/ smime.p7s Description: S/MIME cryptographic signature ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor
Le 2011-06-09 à 14:55, Klaus Berkling a écrit : Hi all. I'm working with wonder's JavaMonitor, sources from about last week from git. Certain basic things just aren't working, shutting down instances, clearing deaths, etc. Before I go debug things, are there currently know issues? Is there a 'oh yeah, don't use it until [this] gets fixed'? Being running the wonder version for months without issues (on CentOS Linux). But good chance that I don't have as much instances as you. ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor
On Jun 9, 2011, at 11:59 AM, Pascal Robert wrote: Le 2011-06-09 à 14:55, Klaus Berkling a écrit : I'm working with wonder's JavaMonitor, sources from about last week from git. Certain basic things just aren't working, shutting down instances, clearing deaths, etc. Before I go debug things, are there currently know issues? Is there a 'oh yeah, don't use it until [this] gets fixed'? Being running the wonder version for months without issues (on CentOS Linux). But good chance that I don't have as much instances as you. I'm testing on a small scale under Ubuntu My build is probably messed up. I'll try the build from mdimension. Thanks. kib Success is not final, failure is not fatal: it is the courage to continue that counts. Winston Churchill Klaus Berkling Web Application Dev. Systems Analyst DynEd International, Inc. www.dyned.com | blog smime.p7s Description: S/MIME cryptographic signature ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor
We also experience a lot of issues even when using just a few instances. Stopping, starting etc. via /admin can be slow. Often times, the monitor goes out of sync with a random application. We are also using Ubuntu. On 09.06.2011, at 20:59, Pascal Robert wrote: Le 2011-06-09 à 14:55, Klaus Berkling a écrit : Hi all. I'm working with wonder's JavaMonitor, sources from about last week from git. Certain basic things just aren't working, shutting down instances, clearing deaths, etc. Before I go debug things, are there currently know issues? Is there a 'oh yeah, don't use it until [this] gets fixed'? Being running the wonder version for months without issues (on CentOS Linux). But good chance that I don't have as much instances as you. ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/m.soutier%40starhealthcare.info This email sent to m.sout...@starhealthcare.info ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor
Le 2011-06-09 à 15:28, Marius Soutier a écrit : We also experience a lot of issues even when using just a few instances. Stopping, starting etc. via /admin can be slow. Often times, the monitor goes out of sync with a random application. We are also using Ubuntu. Running Sun JVM 1.6.x? On 09.06.2011, at 20:59, Pascal Robert wrote: Le 2011-06-09 à 14:55, Klaus Berkling a écrit : Hi all. I'm working with wonder's JavaMonitor, sources from about last week from git. Certain basic things just aren't working, shutting down instances, clearing deaths, etc. Before I go debug things, are there currently know issues? Is there a 'oh yeah, don't use it until [this] gets fixed'? Being running the wonder version for months without issues (on CentOS Linux). But good chance that I don't have as much instances as you. ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/m.soutier%40starhealthcare.info This email sent to m.sout...@starhealthcare.info ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor
Yup, even auto-updates to the latest release. On 09.06.2011, at 21:33, Pascal Robert wrote: Le 2011-06-09 à 15:28, Marius Soutier a écrit : We also experience a lot of issues even when using just a few instances. Stopping, starting etc. via /admin can be slow. Often times, the monitor goes out of sync with a random application. We are also using Ubuntu. Running Sun JVM 1.6.x? On 09.06.2011, at 20:59, Pascal Robert wrote: Le 2011-06-09 à 14:55, Klaus Berkling a écrit : Hi all. I'm working with wonder's JavaMonitor, sources from about last week from git. Certain basic things just aren't working, shutting down instances, clearing deaths, etc. Before I go debug things, are there currently know issues? Is there a 'oh yeah, don't use it until [this] gets fixed'? Being running the wonder version for months without issues (on CentOS Linux). But good chance that I don't have as much instances as you. ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/m.soutier%40starhealthcare.info This email sent to m.sout...@starhealthcare.info ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor
On Jun 9, 2011, at 12:33 PM, Pascal Robert wrote: Le 2011-06-09 à 15:28, Marius Soutier a écrit : We also experience a lot of issues even when using just a few instances. Stopping, starting etc. via /admin can be slow. Often times, the monitor goes out of sync with a random application. We are also using Ubuntu. Running Sun JVM 1.6.x? I'm running this: $ java -version java version 1.6.0_22 Java(TM) SE Runtime Environment (build 1.6.0_22-b04) Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode) kib Live as if you were to die tomorrow. Learn as if you were to live forever. Mahatma Gandhi Klaus Berkling Web Application Dev. Systems Analyst DynEd International, Inc. www.dyned.com | blog smime.p7s Description: S/MIME cryptographic signature ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor
Le 2011-06-09 à 16:20, Klaus Berkling a écrit : On Jun 9, 2011, at 12:33 PM, Pascal Robert wrote: Le 2011-06-09 à 15:28, Marius Soutier a écrit : We also experience a lot of issues even when using just a few instances. Stopping, starting etc. via /admin can be slow. Often times, the monitor goes out of sync with a random application. We are also using Ubuntu. Running Sun JVM 1.6.x? I'm running this: $ java -version java version 1.6.0_22 Java(TM) SE Runtime Environment (build 1.6.0_22-b04) Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode) This is what I'm running on CentOS boxes too. ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Wonder JavaMonitor
On Jun 9, 2011, at 12:25 PM, Klaus Berkling wrote: On Jun 9, 2011, at 11:59 AM, Pascal Robert wrote: Le 2011-06-09 à 14:55, Klaus Berkling a écrit : I'm working with wonder's JavaMonitor, sources from about last week from git. Certain basic things just aren't working, shutting down instances, clearing deaths, etc. Before I go debug things, are there currently know issues? Is there a 'oh yeah, don't use it until [this] gets fixed'? Being running the wonder version for months without issues (on CentOS Linux). But good chance that I don't have as much instances as you. I'm testing on a small scale under Ubuntu My build is probably messed up. I'll try the build from mdimension. Got the latest binaries. Looks like things are working a lot better (will need to look at my build setup). But it seems like 'Refuse New Sessions doesn't work. I does work on an older build of Monitor on a production server... kib Success is not final, failure is not fatal: it is the courage to continue that counts. Winston Churchill Klaus Berkling Web Application Dev. Systems Analyst DynEd International, Inc. www.dyned.com | blog smime.p7s Description: S/MIME cryptographic signature ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
