Back to bug 803093
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Mike Foley | 2012-03-19 16:19:00 UTC | Priority | unspecified | medium |
| Larry O'Leary | 2012-11-19 19:19:02 UTC | Priority | medium | unspecified |
| Component | Plugins | Plugin -- Tomcat 6, Plugin -- Tomcat 7 | ||
| Version | 4.2 | JON 3.0.0 | ||
| Product | RHQ Project | JBoss Operations Network | ||
| Larry O'Leary | 2012-11-19 19:19:28 UTC | Type | --- | Bug |
| mark yarborough | 2012-11-19 20:21:20 UTC | Target Release | --- | JON 3.1.2 |
| CC | myarboro | |||
| Assignee | rhq-maint | jclere | ||
| mark yarborough | 2012-11-20 21:23:03 UTC | Flags | needinfo?(jclere) | |
| Jean-frederic Clere | 2012-11-21 07:51:42 UTC | Flags | needinfo?(jclere) | |
| mark yarborough | 2012-12-18 15:23:49 UTC | Target Release | JON 3.1.2 | JON 3.2.0 |
| Larry O'Leary | 2013-02-21 03:56:14 UTC | Severity | medium | high |
| Link ID | Red Hat Knowledge Base (Solution) 81653 | |||
| mark yarborough | 2013-04-10 19:21:15 UTC | Target Release | JON 3.2.0 | --- |
| CC | ccrouch, jdoyle, mfoley | |||
| Component | Plugin -- Tomcat 6, Plugin -- Tomcat 7 | JON Plugin | ||
| Version | JON 3.0.0 | unspecified | ||
| Product | JBoss Operations Network | JBoss Enterprise Web Server 2 | ||
| Larry O'Leary | 2013-04-12 19:03:53 UTC | QA Contact | mfoley | lfuka |
| Larry O'Leary | 2013-04-12 19:08:50 UTC | Version | unspecified | 2.0.0 |
| Misha H. Ali | 2013-06-13 23:06:22 UTC | CC | mhusnain | |
| Doc Text | Cause: Consequence: Workaround (if one exists): Result: | |||
| Doc Type | Bug Fix | Known Issue | ||
| Mandar Joshi | 2013-06-14 06:36:07 UTC | CC | majoshi | |
| Doc Text | Cause: Consequence: Workaround (if one exists): Result: | Cause: Attempts to change the existing connector fail. Consequence: When existing Tomcat connector is changed by modifying the Tomcatsever.xml file, the new connector is not discovered and the old connector is also not valid. Workaround: Remove the old connector resource from the JBoss Operations Network inventory and force service discovery to discover the new connector. Result: The new connector is discovered by removing the old connector from the JBoss Operations Network inventory. |
||
| Mandar Joshi | 2013-06-14 06:37:26 UTC | CC | jclere | |
| Flags | needinfo?(jclere) | |||
| Mandar Joshi | 2013-06-14 06:43:05 UTC | Doc Text | Cause: Attempts to change the existing connector fail. Consequence: When existing Tomcat connector is changed by modifying the Tomcatsever.xml file, the new connector is not discovered and the old connector is also not valid. Workaround: Remove the old connector resource from the JBoss Operations Network inventory and force service discovery to discover the new connector. Result: The new connector is discovered by removing the old connector from the JBoss Operations Network inventory. | Cause: When existing Tomcat connector is changed by modifying the Tomcatsever.xml file, the new connector is not discovered and the old connector is also not valid. Consequence: Attempts to change the existing connector fail. Workaround: Remove the old connector resource from the JBoss Operations Network inventory and force service discovery to discover the new connector. Result: The new connector is discovered by removing the old connector from the JBoss Operations Network inventory. |
| Jean-frederic Clere | 2013-06-14 08:58:47 UTC | Flags | needinfo?(jclere) | |
| Mandar Joshi | 2013-06-14 09:27:13 UTC | Doc Text | Cause: When existing Tomcat connector is changed by modifying the Tomcatsever.xml file, the new connector is not discovered and the old connector is also not valid. Consequence: Attempts to change the existing connector fail. Workaround: Remove the old connector resource from the JBoss Operations Network inventory and force service discovery to discover the new connector. Result: The new connector is discovered by removing the old connector from the JBoss Operations Network inventory. | In JBoss Enterprise Web Server, when an existing Tomcat connector is changed by modifying the <filename>Tomcat server.xml</filename> file, JBoss Operations Network (JON) does not discover the new connector. The old connector is kept in the inventory and it is not valid. This is a known issue in JBoss Enterprise Web Server 2.0.1. As a workaround for this issue, remove the old connector resource from the JBoss Operations Network (JON) inventory and force service discovery to discover the new connector. |
| Misha H. Ali | 2013-06-19 23:40:36 UTC | Doc Text | In JBoss Enterprise Web Server, when an existing Tomcat connector is changed by modifying the <filename>Tomcat server.xml</filename> file, JBoss Operations Network (JON) does not discover the new connector. The old connector is kept in the inventory and it is not valid. This is a known issue in JBoss Enterprise Web Server 2.0.1. As a workaround for this issue, remove the old connector resource from the JBoss Operations Network (JON) inventory and force service discovery to discover the new connector. | In JBoss Enterprise Web Server, when an existing Tomcat connector is changed by modifying the <filename>Tomcat server.xml</filename> file, JBoss Operations Network (JON) does not discover the new connector. The old connector is kept in the inventory and it is not valid. This is a known issue in JBoss Enterprise Web Server 2.0.1. As a workaround for this issue, remove the old connector resource from the JBoss Operations Network (JON) inventory and force service discovery to discover the new connector. |
| mark yarborough | 2014-02-14 13:47:31 UTC | Status | NEW | CLOSED |
| Resolution | --- | WONTFIX | ||
| Last Closed | 2014-02-14 08:47:31 UTC | |||
| John Doyle | 2014-02-14 14:18:13 UTC | CC | jdoyle | |
| Larry O'Leary | 2014-02-14 14:47:11 UTC | Status | CLOSED | ASSIGNED |
| Resolution | WONTFIX | --- | ||
| Keywords | Reopened | |||
| Jimmy Wilson | 2014-02-14 20:50:16 UTC | CC | jawilson | |
| Misha H. Ali | 2014-08-08 05:50:58 UTC | Doc Text | In JBoss Enterprise Web Server, when an existing Tomcat connector is changed by modifying the <filename>Tomcat server.xml</filename> file, JBoss Operations Network (JON) does not discover the new connector. The old connector is kept in the inventory and it is not valid. This is a known issue in JBoss Enterprise Web Server 2.0.1. As a workaround for this issue, remove the old connector resource from the JBoss Operations Network (JON) inventory and force service discovery to discover the new connector. | In JBoss Enterprise Web Server, when an existing Tomcat connector is changed by modifying the <filename>Tomcat server.xml</filename> file, JBoss Operations Network (JON) does not discover the new connector. The old connector is kept in the inventory and it is not valid. This is a known issue in JBoss Enterprise Web Server 2.1.0. As a workaround for this issue, remove the old connector resource from the JBoss Operations Network (JON) inventory and force service discovery to discover the new connector. |
| Misha H. Ali | 2014-08-12 06:29:50 UTC | Doc Text | In JBoss Enterprise Web Server, when an existing Tomcat connector is changed by modifying the <filename>Tomcat server.xml</filename> file, JBoss Operations Network (JON) does not discover the new connector. The old connector is kept in the inventory and it is not valid. This is a known issue in JBoss Enterprise Web Server 2.1.0. As a workaround for this issue, remove the old connector resource from the JBoss Operations Network (JON) inventory and force service discovery to discover the new connector. | In JBoss Enterprise Web Server, when an existing Tomcat connector was changed by modifying Tomcat's <filename>server.xml</filename> file, JBoss Operations Network (JON) did not discover the new connector. The old connector remains in the inventory and is invalid. This is a known issue in JBoss Enterprise Web Server 2.1. As a workaround for this issue, remove the old connector resource from the JBoss Operations Network (JON) inventory and force service discovery to discover the new connector. |
| John Skeoch | 2015-02-01 23:29:30 UTC | CC | ccrouch | hbrock |
| Scott Mumford | 2015-03-18 04:10:46 UTC | CC | smumford | |
| Doc Text | In JBoss Enterprise Web Server, when an existing Tomcat connector was changed by modifying Tomcat's <filename>server.xml</filename> file, JBoss Operations Network (JON) did not discover the new connector. The old connector remains in the inventory and is invalid. This is a known issue in JBoss Enterprise Web Server 2.1. As a workaround for this issue, remove the old connector resource from the JBoss Operations Network (JON) inventory and force service discovery to discover the new connector. | In JBoss Enterprise Web Server, when an existing Tomcat connector was changed by modifying Tomcat's <filename>server.xml</filename> file, JBoss Operations Network (JON) did not discover the new connector. The old connector remains in the inventory and is invalid. This is a known issue in JBoss Enterprise Web Server 3.0. As a workaround for this issue, remove the old connector resource from the JBoss Operations Network (JON) inventory and force service discovery to discover the new connector. |
||
| Libor Fuka | 2015-06-11 06:34:07 UTC | QA Contact | lfuka | mbabacek |
| Michal Karm Babacek | 2015-06-16 12:52:09 UTC | QA Contact | mbabacek | fgoldefu |
| John Skeoch | 2015-09-01 03:00:02 UTC | CC | majoshi | pyaduvan |
| Richa | 2017-10-10 15:38:08 UTC | QA Contact | fgoldefu | rhatlapa |
| CC | fgoldefu | |||
| QA Contact | rhatlapa | fgoldefu | ||
| QA Contact | fgoldefu | jstefl | ||
| Status | ASSIGNED | CLOSED | ||
| CC | rmarwaha | |||
| Resolution | --- | WONTFIX | ||
| Last Closed | 2014-02-14 08:47:31 UTC | 2017-10-10 11:38:08 UTC |
Back to bug 803093