Hi,
I upgraded my old JavaMonitor by the latest wonder one and every time I go to view a detail of one
my instances, I always have in red "No statistics for appName -A" or "No statistics
for appName-B, No statistics for appName-Z".
These messages are due to what? bad settings of the new JavaMo
Am 20.02.2014 um 14:03 schrieb David Avendasora :
>
> On Feb 20, 2014, at 6:48 AM, Johann Werner 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. I
On Feb 20, 2014, at 6:48 AM, Johann Werner 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 t
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
> 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 be
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
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/JavaApplication
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/
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
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 th
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 W
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
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 -Ddeployme
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
On Jul 20, 2011, at 2:31 PM, Klaus Berkling wrote:
> Going back to Linux and hosts with multiple IP addresses.
>
> er.extensions.WOHostUtilities.localhostips=(10.0.0.20,192.168.10.96)
>
> Having added this via command arguments or adding it the Properties file for
> my app and as it did
Going back to Linux and hosts with multiple IP addresses.
er.extensions.WOHostUtilities.localhostips=(10.0.0.20,192.168.10.96)
Having added this via command arguments or adding it the Properties file for my
app and as it did not solve my issue; how do I see if the addresses actually
got
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
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 prob
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:
>>
>> * This class replaces the WebObjects version
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 wor
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,
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 work
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. Of
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 app
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 moni
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?
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
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
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 iss
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'?
30 matches
Mail list logo
