Hi Ted,
On 26 Oct 2016, at 8:51 AM, Theodore Petrosky wrote:
> I think you are saying that JavaMonitor should only be accessed by the direct
> connect port.
>
> I never read that anywhere, and I have alway create an instance to
> JavaMonitor. Is this a bad practice?
I just don’t think you ne
I think the general thought is that you don’t want that accessible
externally. If you run it in direct connect mode and then make sure that
port isn’t accessible via your firewall you should be “safe”.
-Lon
On Tue, Oct 25, 2016 at 3:21 PM, Theodore Petrosky
wrote:
> I think you are saying that
Hi Ted,
On 26 Oct 2016, at 2:48 AM, Theodore Petrosky wrote:
> Why is it that I can only access the application scheduling or Application
> Settings sections of JavaMonitor when I access it with the direct connect
> (:56789)? these sections are not accessible if I use the running app.
> http:
