[
https://jira.codehaus.org/browse/MJBOSS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276862#comment-276862
]
Scott Marlow commented on MJBOSS-61:
------------------------------------
JBAS-7818 was about using JSR-160 rather than JBoss proprietary classes.
https://issues.jboss.org/browse/JBAS-7889 contains some documentation links
that were updated for the change in AS 6.
Could you give the error exception call stack and either a code example or a
link to the code that experiences the failure.
> 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
