Back to bug 738826
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Mike Foley | 2011-09-28 14:51:02 UTC | Priority | high | medium |
| Charles Crouch | 2011-10-19 13:15:18 UTC | Keywords | FutureFeature | |
| Environment | JON 2.4.1 EWS Plugin Pack for JBoss ON 2.4.1 SUSE Linux Enterpirse 10 Multiple Tomcat 5 and 6 instances using System V init scripts | JON 2.4.1 EWS Plugin Pack for JBoss ON 2.4.1 SUSE Linux Enterpirse 10 Multiple Tomcat 5 and 6 instances using System V init scripts |
||
| Larry O'Leary | 2012-11-19 19:21:59 UTC | Priority | medium | unspecified |
| Component | Plugins | Plugin -- Tomcat 5, Plugin -- Tomcat 6, Plugin -- Tomcat 7 | ||
| Environment | JON 2.4.1 EWS Plugin Pack for JBoss ON 2.4.1 SUSE Linux Enterpirse 10 Multiple Tomcat 5 and 6 instances using System V init scripts | JON 2.4.1 EWS Plugin Pack for JBoss ON 2.4.1 SUSE Linux Enterpirse 10 Multiple Tomcat 5 and 6 instances using System V init scripts | ||
| Version | 3.0.1 | JON 2.4.1 | ||
| Product | RHQ Project | JBoss Operations Network | ||
| Larry O'Leary | 2012-11-19 19:22:32 UTC | Type | --- | Enhancement |
| mark yarborough | 2012-11-19 20:25:18 UTC | Priority | unspecified | low |
| Target Release | --- | JON 3.1.2 | ||
| CC | myarboro | |||
| Assignee | rhq-maint | jclere | ||
| Severity | high | medium | ||
| mark yarborough | 2012-12-18 15:23:51 UTC | Target Release | JON 3.1.2 | JON 3.2.0 |
| mark yarborough | 2013-04-10 19:20:17 UTC | Target Release | JON 3.2.0 | --- |
| CC | ccrouch, jdoyle, mfoley | |||
| Component | Plugin -- Tomcat 5, Plugin -- Tomcat 6, Plugin -- Tomcat 7 | JON Plugin | ||
| Version | JON 2.4.1 | unspecified | ||
| Product | JBoss Operations Network | JBoss Enterprise Web Server 2 | ||
| Larry O'Leary | 2013-04-12 19:07:45 UTC | Version | unspecified | 2.0.0 |
| QA Contact | mfoley | lfuka | ||
| Misha H. Ali | 2013-06-14 00:34:07 UTC | CC | mhusnain | |
| Doc Text | Cause: Consequence: Workaround (if one exists): Result: | |||
| Doc Type | Enhancement | Known Issue | ||
| Mandar Joshi | 2013-06-14 07:00:57 UTC | CC | jclere, majoshi | |
| Doc Text | Cause: Consequence: Workaround (if one exists): Result: | Cause: When configuring a Tomcat server which utilizes System V Init service scripts, the service name cannot be changed. Consequence: For multiple Tomcat server installations if RPM System V Init method is specified for start/shutdown operations, the second instance of Tomcat server fails to shutdown. The following message is logged, if debug logging is enabled for the agent: DEBUG [ResourceContainer.invoker.nonDaemon-3] (jboss.on.plugins.tomcat.TomcatServerOperationsDelegate)- About to execute the following process: [ProcessExecution: executable=[service], args=[[tomcat5, stop]], env-vars=[{...}], working-dir=[null], wait=[1000], capture-output=[true], kill-on-timeout=[false], executable-is-command=[false]] DEBUG [ResourceContainer.invoker.nonDaemon-3] (jboss.on.plugins.tomcat.TomcatServerOperationsDelegate)- Exit code from process execution: 1 DEBUG [ResourceContainer.invoker.nonDaemon-3] (jboss.on.plugins.tomcat.TomcatServerOperationsDelegate)- Output from process execution: ----------------------- service: no such service tomcat5 ----------------------- DEBUG [OperationManager.invoker-1] (rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler)- Call to [org.jboss.on.plugins.tomcat.TomcatServerComponent.invokeOperation()] with args [[shutdown, Configuration[id=0]]] failed. java.util.concurrent.ExecutionException: java.lang.RuntimeException: Script returned error or non-zero exit code while shutting down the Tomcat instance. Exit code [1] at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source) at java.util.concurrent.FutureTask.get(Unknown Source) at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invokeInNewThreadWithLock(ResourceContainer.java:446) at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invoke(ResourceContainer.java:434) at $Proxy62.invokeOperation(Unknown Source) at org.rhq.core.pc.operation.OperationInvocation.run(OperationInvocation.java:217) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Workaround: There is no workaround for this problem. Result: ? | ||
| Flags | needinfo?(jclere) | |||
| Mandar Joshi | 2013-06-14 08:40:50 UTC | Doc Text | Cause: When configuring a Tomcat server which utilizes System V Init service scripts, the service name cannot be changed. Consequence: For multiple Tomcat server installations if RPM System V Init method is specified for start/shutdown operations, the second instance of Tomcat server fails to shutdown. The following message is logged, if debug logging is enabled for the agent: DEBUG [ResourceContainer.invoker.nonDaemon-3] (jboss.on.plugins.tomcat.TomcatServerOperationsDelegate)- About to execute the following process: [ProcessExecution: executable=[service], args=[[tomcat5, stop]], env-vars=[{...}], working-dir=[null], wait=[1000], capture-output=[true], kill-on-timeout=[false], executable-is-command=[false]] DEBUG [ResourceContainer.invoker.nonDaemon-3] (jboss.on.plugins.tomcat.TomcatServerOperationsDelegate)- Exit code from process execution: 1 DEBUG [ResourceContainer.invoker.nonDaemon-3] (jboss.on.plugins.tomcat.TomcatServerOperationsDelegate)- Output from process execution: ----------------------- service: no such service tomcat5 ----------------------- DEBUG [OperationManager.invoker-1] (rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler)- Call to [org.jboss.on.plugins.tomcat.TomcatServerComponent.invokeOperation()] with args [[shutdown, Configuration[id=0]]] failed. java.util.concurrent.ExecutionException: java.lang.RuntimeException: Script returned error or non-zero exit code while shutting down the Tomcat instance. Exit code [1] at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source) at java.util.concurrent.FutureTask.get(Unknown Source) at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invokeInNewThreadWithLock(ResourceContainer.java:446) at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invoke(ResourceContainer.java:434) at $Proxy62.invokeOperation(Unknown Source) at org.rhq.core.pc.operation.OperationInvocation.run(OperationInvocation.java:217) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Workaround: There is no workaround for this problem. Result: ? | Cause: When configuring a Tomcat server which utilizes System V Init service scripts, the service name cannot be changed. Consequence: Multiple Tomcat server installation which utilizes System V Init service scripts, is not supported by JBoss Operations Network. Workaround: There is no workaround for this issue since the service name is hardcoded in the plug-in. Result: ? |
| Mandar Joshi | 2013-06-14 09:17:27 UTC | Doc Text | Cause: When configuring a Tomcat server which utilizes System V Init service scripts, the service name cannot be changed. Consequence: Multiple Tomcat server installation which utilizes System V Init service scripts, is not supported by JBoss Operations Network. Workaround: There is no workaround for this issue since the service name is hardcoded in the plug-in. Result: ? | When configuring JBoss Enterprise Server's Tomcat server which utilizes System V Init service scripts, the service name cannot be changed. There is no workaround for this issue since JBoss Enterprise Server's JBoss Operations Network (JON) doesn't allow to change the service name. |
| Flags | needinfo?(jclere) | |||
| Misha H. Ali | 2013-06-19 23:39:33 UTC | Doc Text | When configuring JBoss Enterprise Server's Tomcat server which utilizes System V Init service scripts, the service name cannot be changed. There is no workaround for this issue since JBoss Enterprise Server's JBoss Operations Network (JON) doesn't allow to change the service name. | When configuring JBoss Enterprise Server's Tomcat server which utilizes System V Init service scripts, the service name cannot be changed. This is a known issue in JBoss Enterprise Web Server 2.0.1. Currently, no workaround exists for this issue because JBoss Enterprise Server's JBoss Operations Network (JON) does not allow service name changes. |
| Libor Fuka | 2013-06-28 07:53:29 UTC | Version | 2.0.0 | unspecified |
| Larry O'Leary | 2013-06-28 09:43:14 UTC | Version | unspecified | 2.0.0 |
| Jean-frederic Clere | 2014-03-08 18:53:11 UTC | Status | NEW | CLOSED |
| Resolution | --- | NOTABUG | ||
| Last Closed | 2014-03-08 13:53:11 UTC | |||
| Larry O'Leary | 2014-03-10 14:16:42 UTC | Status | CLOSED | ASSIGNED |
| Resolution | NOTABUG | --- | ||
| Keywords | Reopened | |||
| Jean-frederic Clere | 2014-03-10 15:07:27 UTC | Status | ASSIGNED | CLOSED |
| Resolution | --- | NOTABUG | ||
| Last Closed | 2014-03-08 13:53:11 UTC | 2014-03-10 11:07:27 UTC | ||
| Larry O'Leary | 2014-03-10 15:31:50 UTC | Status | CLOSED | ASSIGNED |
| CC | jawilson | |||
| Resolution | NOTABUG | --- | ||
| Flags | needinfo?(jawilson) | |||
| Thomas Segismont | 2014-06-17 07:59:45 UTC | CC | tsegismo | |
| Jean-frederic Clere | 2014-06-18 17:30:33 UTC | Status | ASSIGNED | MODIFIED |
| Larry O'Leary | 2014-06-20 23:47:31 UTC | Blocks | 1111666 | |
| Jean-frederic Clere | 2014-06-26 11:40:01 UTC | Blocks | 1113542 | |
| Larry O'Leary | 2014-07-01 23:35:29 UTC | Status | MODIFIED | ON_QA |
| Jean-frederic Clere | 2014-07-02 09:53:59 UTC | Target Release | --- | 2.1.0 |
| Target Milestone | --- | ER04 | ||
| Libor Fuka | 2014-07-18 10:11:09 UTC | Status | ON_QA | VERIFIED |
| Misha H. Ali | 2014-08-08 06:00:01 UTC | Doc Text | When configuring JBoss Enterprise Server's Tomcat server which utilizes System V Init service scripts, the service name cannot be changed. This is a known issue in JBoss Enterprise Web Server 2.0.1. Currently, no workaround exists for this issue because JBoss Enterprise Server's JBoss Operations Network (JON) does not allow service name changes. | When configuring JBoss Enterprise Server's Tomcat server which utilizes System V Init service scripts, the service name cannot be changed. This is a known issue in JBoss Enterprise Web Server 2.0.1. Currently, no workaround exists for this issue because JBoss Enterprise Server's JBoss Operations Network (JON) does not allow service name changes. What is the FIX? |
| Doc Type | Known Issue | Bug Fix | ||
| Misha H. Ali | 2014-08-09 08:15:48 UTC | Doc Text | When configuring JBoss Enterprise Server's Tomcat server which utilizes System V Init service scripts, the service name cannot be changed. This is a known issue in JBoss Enterprise Web Server 2.0.1. Currently, no workaround exists for this issue because JBoss Enterprise Server's JBoss Operations Network (JON) does not allow service name changes. What is the FIX? | Previously, when configuring JBoss Enterprise Server's Tomcat server which utilizes System V Init service scripts, the service name could not be changed. This was because JBoss Enterprise Server's JBoss Operations Network (JON) did not allow service name changes. The JBoss Operations Network interface now includes a <guilabel>Service Name</guilabel> field for users to manually specify the desired name for a service. This issue is resolved in JBoss Enterprise Web Server 2.1.0. |
| Misha H. Ali | 2014-08-12 00:54:39 UTC | Doc Text | Previously, when configuring JBoss Enterprise Server's Tomcat server which utilizes System V Init service scripts, the service name could not be changed. This was because JBoss Enterprise Server's JBoss Operations Network (JON) did not allow service name changes. The JBoss Operations Network interface now includes a <guilabel>Service Name</guilabel> field for users to manually specify the desired name for a service. This issue is resolved in JBoss Enterprise Web Server 2.1.0. | Previously, when configuring JBoss Enterprise Server's Tomcat server which utilizes System V Init service scripts, the service name could not be changed. This was because JBoss Enterprise Server's JBoss Operations Network (JON) did not allow service name changes. This is now fixed in JBoss Enterprise Web Server 2.1 and the JBoss Operations Network interface now includes a <guilabel>Service Name</guilabel> field for users to manually specify the desired name for a service. |
| Larry O'Leary | 2014-08-20 16:19:53 UTC | Blocks | 1113542 | |
| Larry O'Leary | 2014-08-21 21:40:12 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-03-10 11:07:27 UTC | 2014-08-21 17:40:12 UTC | ||
| Larry O'Leary | 2015-04-17 21:37:15 UTC | Flags | needinfo?(jawilson) |
Back to bug 738826