|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
[jira] Created: (MJBOSS-34) Add a wait period between retries of the JMX Connection when using startAndWaitGoalAdd a wait period between retries of the JMX Connection when using startAndWaitGoal
----------------------------------------------------------------------------------- Key: MJBOSS-34 URL: http://jira.codehaus.org/browse/MJBOSS-34 Project: Maven 2.x JBoss Plugin Issue Type: Improvement Reporter: Fuzail Attachments: StartAndWaitMojo.java.patch When using the startAndWait goal I keep hitting the retry timeout since the plugin doesnt wait for Jboss to initialize before attempting to make a JMX connection I resolved this by simply adding a retryWait period in the execute code. Attached is the patch for it if it seems usefull -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Updated: (MJBOSS-34) Add a wait period between retries of the JMX Connection when using startAndWaitGoal[ http://jira.codehaus.org/browse/MJBOSS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier updated MJBOSS-34: ---------------------------- Fix Version/s: 1.4.0 Assignee: Paul Gier > Add a wait period between retries of the JMX Connection when using startAndWaitGoal > ----------------------------------------------------------------------------------- > > Key: MJBOSS-34 > URL: http://jira.codehaus.org/browse/MJBOSS-34 > Project: Maven 2.x JBoss Plugin > Issue Type: Improvement > Reporter: Fuzail > Assignee: Paul Gier > Fix For: 1.4.0 > > Attachments: StartAndWaitMojo.java.patch > > > When using the startAndWait goal I keep hitting the retry timeout since the plugin doesnt wait for Jboss to initialize before attempting to make a JMX connection > I resolved this by simply adding a retryWait period in the execute code. Attached is the patch for it if it seems usefull -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (MJBOSS-34) Add a wait period between retries of the JMX Connection when using startAndWaitGoal[ http://jira.codehaus.org/browse/MJBOSS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196463#action_196463 ] Fuzail commented on MJBOSS-34: ------------------------------ Hi I tried the latest snapshot and checked the code from trunk, but I still have the problem. What happens is that the JBoss instance is starting up and the lookup for the RMIAdaptor occurs before the RMI Server on JBoss has started. Even if i push up my retries to 100 I still get the "Unable to get JBoss jmx MBean connection: jmx not bound." This is on JBoss 4.2.2.GA release. > Add a wait period between retries of the JMX Connection when using startAndWaitGoal > ----------------------------------------------------------------------------------- > > Key: MJBOSS-34 > URL: http://jira.codehaus.org/browse/MJBOSS-34 > Project: Maven 2.x JBoss Plugin > Issue Type: Improvement > Reporter: Fuzail > Assignee: Paul Gier > Fix For: 1.4.0 > > Attachments: StartAndWaitMojo.java.patch > > > When using the startAndWait goal I keep hitting the retry timeout since the plugin doesnt wait for Jboss to initialize before attempting to make a JMX connection > I resolved this by simply adding a retryWait period in the execute code. Attached is the patch for it if it seems usefull -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Closed: (MJBOSS-34) Add a wait period between retries of the JMX Connection when using startAndWaitGoal[ http://jira.codehaus.org/browse/MJBOSS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier closed MJBOSS-34. --------------------------- Resolution: Fixed I was able to reproduce the problem and see what you are talking about. I applied the patcht with some modifications in [r10988|http://fisheye.codehaus.org/changelog/mojo/trunk/mojo?cs=10988]. I also noticed that the mojo is not working correctly because of lacking configuration of an RMI security manager. So I created MJBOSS-35 to address this issue separately. Thanks for finding this! > Add a wait period between retries of the JMX Connection when using startAndWaitGoal > ----------------------------------------------------------------------------------- > > Key: MJBOSS-34 > URL: http://jira.codehaus.org/browse/MJBOSS-34 > Project: Maven 2.x JBoss Plugin > Issue Type: Improvement > Reporter: Fuzail > Assignee: Paul Gier > Fix For: 1.4.0 > > Attachments: StartAndWaitMojo.java.patch > > > When using the startAndWait goal I keep hitting the retry timeout since the plugin doesnt wait for Jboss to initialize before attempting to make a JMX connection > I resolved this by simply adding a retryWait period in the execute code. Attached is the patch for it if it seems usefull -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |