[
https://jira.codehaus.org/browse/MJBOSS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276864#comment-276864
]
Scott Marlow commented on MJBOSS-61:
------------------------------------
This does sound similar to
https://issues.jboss.org/browse/JBAS-7818?focusedCommentId=12523915&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12523915
(as mentioned above), but please point me to the code that is experiencing the
failure and we can go from there. Having the exception call stack might also
be helpful.
> start-and-wait typecast exception on JBoss 6 AS Final during Container Test
> ---------------------------------------------------------------------------
>
> Key: MJBOSS-61
> URL: https://jira.codehaus.org/browse/MJBOSS-61
> Project: Maven 2.x JBoss Plugin
> Issue Type: Bug
> Affects Versions: 1.5.0
> Environment: OSX, Ubuntu Maverick Meerkat
> Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800)
> Jboss AS 6.0.0.Final
> Reporter: Todd Morrison
>
> *Problem*
> Attempting container dependent tests using
> {quote}
> mvn jboss:start-and-wait clean test jboss:stop
> {quote}
> Results in
> {quote}
> [INFO] --- jboss-maven-plugin:1.5.0:start-and-wait (default-cli) @
> xxxxx.xxxxx ---
> [INFO] Starting JBoss...
> [INFO] Waiting to retrieve JBoss JMX MBean connection...
> [INFO] Waiting to retrieve JBoss JMX MBean connection...
> {quote}
> ...
> {quote}
> [ERROR] Failed to execute goal
> org.codehaus.mojo:jboss-maven-plugin:1.5.0:start-and-wait (default-cli) on
> project xxxxx.xxxx: A type incompatibility occured while executing
> org.codehaus.mojo:jboss-maven-plugin:1.5.0:start-and-wait:
> javax.naming.Reference cannot be cast to
> javax.management.MBeanServerConnection
> {quote}
> *Temp Solution that is not the best for build servers*
> Running
> {quote}
> mvn jboss:start-and-wait clean test jboss:stop
> {quote}
> And then letting the build fail, followed by
> {quote}
> mvn clean test jboss:stop
> {quote}
> Actually works. I am guessing this is because the thread is created, just not
> monitored from the first call. Then, the second attaches, runs, and shuts the
> server process down just fine.
> Guidance anyone?
--
This message is automatically generated by JIRA.
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
