[ 
http://jira.codehaus.org/browse/MJBOSS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263816#action_263816
 ] 

Todd Morrison commented on MJBOSS-61:
-------------------------------------

This is the relevant comment: 
https://issues.jboss.org/browse/JBAS-7818?focusedCommentId=12523915&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12523915

So, I am guessing that this is just a AS 5 vs. 6 support issue.

> start-and-wait typecast exception on JBoss 6 AS Final during Container Test
> ---------------------------------------------------------------------------
>
>                 Key: MJBOSS-61
>                 URL: http://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.
-
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


Reply via email to