Bug 786082
Summary: | tomcat as a service is not properly detected | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Web Server 2 | Reporter: | Tom Fonteyne <tfonteyn> |
Component: | JON Plugin | Assignee: | Jean-frederic Clere <jclere> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Libor Fuka <lfuka> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.0.0 | CC: | bkramer, ccrouch, loleary, majoshi, mfoley, mhusnain, myarboro |
Target Milestone: | ER04 | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Windows | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously in JBoss Enterprise Web Server, the JON Tomcat plugin was not able to discover Tomcat installed as a Microsoft Windows service.
In JBoss Enterprise Web Server 2.1, the JON Tomcat plugin is now fixed so that Tomcat is discovered as expected.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-08-21 21:40:15 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1111666 |
Description
Tom Fonteyne
2012-01-31 11:43:00 UTC
Also tested on 2.4.2rc4, also failing as expected. Per 3.1.2 triage with loleary, mfoley, ccrouch, asantos: Okay to move to JON 3.2. In fact it works with EWS so just tell the customers to use EWS. I verified with EWS2 Tomcat6,7 installed as Windows service + JON 3.1.2.GA + updated Tomcat plugin (brew build [1]) [1] https://brewweb.devel.redhat.com//buildinfo?buildID=269954 Cross referencing: https://bugzilla.redhat.com/show_bug.cgi?id=963264 Where i add steps how to properly install EWS Tomcat as windows service with JON Tomcat plugin and get it all works. Moving this back to NEW as this doesn't appear to be fixed. It only works if the user creates hacks together a new script to get around this failure. There should be no "special steps" to install EWS as a service when using it with JBoss ON. Instead, the managed plug-in should handle this situation within its discovery code. Asking the user to hack the startup scripts and officially supported startup process doesn't seem like an acceptable solution. Yes, perhaps a workaround, but doesn't warrant this bug to be VERIFIED. VERIFIED on MS Windows Server 2008 (32bit) + JON 3.2.0.GA (update02) + JON Tomcat plugin (update01) + OracleJDK 1.6 + EWS ER4 Tomcat6/7 This fix, change, or update was tested and released in Web Server Plugin Pack Update-01 for JBoss ON 3.2 -- https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=32543 |