You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Neale Upstone (JIRA)" <ji...@apache.org> on 2012/07/23 18:05:34 UTC
[jira] [Created] (MTOMCAT-171) Multiple executions (i.e. sep
tomcats clash due to identical JMX naming)
Neale Upstone created MTOMCAT-171:
-------------------------------------
Summary: Multiple executions (i.e. sep tomcats clash due to identical JMX naming)
Key: MTOMCAT-171
URL: https://issues.apache.org/jira/browse/MTOMCAT-171
Project: Apache Tomcat Maven Plugin
Issue Type: Bug
Components: tomcat6
Reporter: Neale Upstone
Assignee: Olivier Lamy (*$^¨%`£)
If two executions are configured, for example to create two tomcat instances running on separate ports, these do not behave independently, as they get identified to JMX using the same names.
Some disambiguation is required, for which the httpPort might be enough (this works for me for tomcat6)
// create engine
Engine engine = container.createEngine();
- engine.setName( "localEngine" );
+ engine.setName( "localEngine-" + port);
engine.addChild( host );
engine.setDefaultHost( host.getName() );
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[jira] [Closed] (MTOMCAT-171) Multiple executions (i.e. sep tomcats
clash due to identical JMX naming)
Posted by "Olivier Lamy (*$^¨%`£ JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MTOMCAT-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy (*$^¨%`£) closed MTOMCAT-171.
------------------------------------------
Resolution: Fixed
Fix Version/s: 2.0
patch applied.
Thanks!
> Multiple executions (i.e. sep tomcats clash due to identical JMX naming)
> ------------------------------------------------------------------------
>
> Key: MTOMCAT-171
> URL: https://issues.apache.org/jira/browse/MTOMCAT-171
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat6
> Reporter: Neale Upstone
> Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.0
>
> Attachments: mtomcat-171.patch
>
>
> If two executions are configured, for example to create two tomcat instances running on separate ports, these do not behave independently, as they get identified to JMX using the same names.
> Some disambiguation is required, for which the httpPort might be enough (this works for me for tomcat6)
> // create engine
> Engine engine = container.createEngine();
> - engine.setName( "localEngine" );
> + engine.setName( "localEngine-" + port);
> engine.addChild( host );
> engine.setDefaultHost( host.getName() );
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[jira] [Commented] (MTOMCAT-171) Multiple executions (i.e. sep
tomcats clash due to identical JMX naming)
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MTOMCAT-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425118#comment-13425118 ]
Hudson commented on MTOMCAT-171:
--------------------------------
Integrated in TomcatMavenPlugin-mvn3.x #184 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/184/])
[MTOMCAT-171] Multiple executions (i.e. sep tomcats clash due to identical JMX naming)
Submitted by Neale Upstone. (Revision 1367193)
Result = FAILURE
olamy : http://svn.apache.org/viewvc/?view=rev&rev=1367193
Files :
* /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
> Multiple executions (i.e. sep tomcats clash due to identical JMX naming)
> ------------------------------------------------------------------------
>
> Key: MTOMCAT-171
> URL: https://issues.apache.org/jira/browse/MTOMCAT-171
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat6
> Reporter: Neale Upstone
> Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.0
>
> Attachments: mtomcat-171.patch
>
>
> If two executions are configured, for example to create two tomcat instances running on separate ports, these do not behave independently, as they get identified to JMX using the same names.
> Some disambiguation is required, for which the httpPort might be enough (this works for me for tomcat6)
> // create engine
> Engine engine = container.createEngine();
> - engine.setName( "localEngine" );
> + engine.setName( "localEngine-" + port);
> engine.addChild( host );
> engine.setDefaultHost( host.getName() );
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[jira] [Updated] (MTOMCAT-171) Multiple executions (i.e. sep
tomcats clash due to identical JMX naming)
Posted by "Neale Upstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MTOMCAT-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neale Upstone updated MTOMCAT-171:
----------------------------------
Attachment: mtomcat-171.patch
Attached patch for Tomcat 6.
I haven't yet verified whether this is an issue for Tomcat7 plugin
> Multiple executions (i.e. sep tomcats clash due to identical JMX naming)
> ------------------------------------------------------------------------
>
> Key: MTOMCAT-171
> URL: https://issues.apache.org/jira/browse/MTOMCAT-171
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat6
> Reporter: Neale Upstone
> Assignee: Olivier Lamy (*$^¨%`£)
> Attachments: mtomcat-171.patch
>
>
> If two executions are configured, for example to create two tomcat instances running on separate ports, these do not behave independently, as they get identified to JMX using the same names.
> Some disambiguation is required, for which the httpPort might be enough (this works for me for tomcat6)
> // create engine
> Engine engine = container.createEngine();
> - engine.setName( "localEngine" );
> + engine.setName( "localEngine-" + port);
> engine.addChild( host );
> engine.setDefaultHost( host.getName() );
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org