Bug 756098 - Basic Admin Guide: Update/add section about configuring EWS
Summary: Basic Admin Guide: Update/add section about configuring EWS
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Documentation
Version: 4.2
Hardware: Unspecified
OS: Windows
medium
medium
Target Milestone: ---
: ---
Assignee: Deon Ballard
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-22 17:10 UTC by Libor Zoubek
Modified: 2015-11-02 00:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-29 15:13:45 UTC
Embargoed:


Attachments (Terms of Use)

Description Libor Zoubek 2011-11-22 17:10:52 UTC
Description of problem:
I was trying to setup EWS (tomcat 5/6) on windows 7. I've successfully installed tomcats to run as windows services. I was following http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/2.4/html-single/Basic_Admin_Guide/index.html#configuring-tomcat-for-discovery

Especially Chapter 8.7.1. I tried to do similar steps in windows startup.bat and setenv.bat but without access. Tomcat was not affected by any change in these  files. After few hours spend I found a solution:

I had to run regedit, navigate to 
HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun 2.0\Tomcat<VERSION>\Parameters\Java 
and edit Options attribute and add:

-Dcom.sun.management.jmxremote.port=9876
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false

Since that, I've restarted Tomcat service and it started to listen on desired JMX port without requiring authorization.

I am not aware of any other/better way to configure startup tomcat aguments when it runs as a service.

Please add this in to Chapter 8.7.1 it can save few hours of madness for some people.


Note You need to log in before you can comment on or make changes to this bug.