[JBoss JIRA] (WFLY-3558) Wildfly throws misleading exception for EJB misimplementation
by Randahl Fink Isaksen (JIRA)
Randahl Fink Isaksen created WFLY-3558:
------------------------------------------
Summary: Wildfly throws misleading exception for EJB misimplementation
Key: WFLY-3558
URL: https://issues.jboss.org/browse/WFLY-3558
Project: WildFly
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 8.0.0.Final
Reporter: Randahl Fink Isaksen
Assignee: Jason Greene
I invoked a method on one of my EJBs and got the exception below on the client side. The problem is, this exception is quite misleading. I found out, that the problem went away after I corrected my EJB's method – It had a parameter which was not Serializable.
I suggest throwing a more meaningful AParameterDidNotImplementSerializableException in this situation – that would have saved me hours of debugging.
java.lang.IllegalStateException: EJBCLIENT000051: Cannot proceed with invocation since the locator StatefulEJBLocator{appName='wefend-server', moduleName='wefend-ejb', distinctName='', beanName='InstallBean', view='interface com.wefend.services.install.InstallService', sessionId='{[-71, -73, -47, 40, -82, 13, 67, -49, -112, -55, 33, 50, 42, -94, -102, -104]}'} has an affinity on node zirconium which has been excluded from current invocation context org.jboss.ejb.client.EJBClientInvocationContext@33c102c9
at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:66)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at org.jboss.ejb.client.EJBClientInvocationContext.retryRequest(EJBClientInvocationContext.java:208)
at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:256)
at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:265)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:198)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144)
at com.sun.proxy.$Proxy4.install(Unknown Source)
at com.wefend.observatory.install.task.InstallTask.call(InstallTask.java:91)
at javafx.concurrent.Task$TaskCallable.call(Task.java:1426)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (WFLY-3557) Sever level MBean hasn't been initialized yet when a web app starts up, causing javax.management.InstanceNotFoundException
by Osamu Nagano (JIRA)
[ https://issues.jboss.org/browse/WFLY-3557?page=com.atlassian.jira.plugin.... ]
Osamu Nagano commented on WFLY-3557:
------------------------------------
Sample stack trace:
{code}
09:46:06,302 INFO [stdout] (ServerService Thread Pool -- 53) --- TestValve2 : start
09:46:06,303 INFO [stdout] (ServerService Thread Pool -- 53) --- TestValve2 : getGlobalConfiguration
09:46:06,304 INFO [stdout] (ServerService Thread Pool -- 53) --- TestValve2 : getGlobalConfiguration error
09:46:06,306 ERROR [stderr] (ServerService Thread Pool -- 53) javax.management.InstanceNotFoundException: jboss.web:name=TestValve,type=Valve
09:46:06,306 ERROR [stderr] (ServerService Thread Pool -- 53) at org.jboss.as.jmx.PluggableMBeanServerImpl.findDelegate(PluggableMBeanServerImpl.java:94)
09:46:06,307 ERROR [stderr] (ServerService Thread Pool -- 53) at org.jboss.as.jmx.PluggableMBeanServerImpl.getAttribute(PluggableMBeanServerImpl.java:171)
09:46:06,307 ERROR [stderr] (ServerService Thread Pool -- 53) at test.valve.TestValve2.getGlobalConfiguration(TestValve2.java:100)
09:46:06,307 ERROR [stderr] (ServerService Thread Pool -- 53) at test.valve.TestValve2.start(TestValve2.java:68)
09:46:06,308 ERROR [stderr] (ServerService Thread Pool -- 53) at org.apache.catalina.core.StandardPipeline.start(StandardPipeline.java:223)
09:46:06,309 ERROR [stderr] (ServerService Thread Pool -- 53) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3713)
09:46:06,310 ERROR [stderr] (ServerService Thread Pool -- 53) at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156)
09:46:06,310 ERROR [stderr] (ServerService Thread Pool -- 53) at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60)
09:46:06,311 ERROR [stderr] (ServerService Thread Pool -- 53) at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93)
09:46:06,311 ERROR [stderr] (ServerService Thread Pool -- 53) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
09:46:06,311 ERROR [stderr] (ServerService Thread Pool -- 53) at java.util.concurrent.FutureTask.run(FutureTask.java:262)
09:46:06,312 ERROR [stderr] (ServerService Thread Pool -- 53) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
09:46:06,312 ERROR [stderr] (ServerService Thread Pool -- 53) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
09:46:06,312 ERROR [stderr] (ServerService Thread Pool -- 53) at java.lang.Thread.run(Thread.java:744)
09:46:06,313 ERROR [stderr] (ServerService Thread Pool -- 53) at org.jboss.threads.JBossThread.run(JBossThread.java:122)
{code}
> Sever level MBean hasn't been initialized yet when a web app starts up, causing javax.management.InstanceNotFoundException
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3557
> URL: https://issues.jboss.org/browse/WFLY-3557
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (JBoss Web)
> Affects Versions: JBoss AS7 7.2.0.Final
> Reporter: Osamu Nagano
> Assignee: Remy Maucherat
> Attachments: module.xml, TestWAR.war, test_valve.jar
>
>
> With "-Dorg.apache.tomcat.util.ENABLE_MODELER=true", server level MBeans like a global valve become available. Those should be visible from start phase of a web app, though sometimes those are missing and javax.management.InstanceNotFoundException is thrown. This sporadically happens due to the parallel nature of WildFly start up. It is reproducible by using a debugger (Eclipse is better than JDB, because JDB stops all threads).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (WFLY-3557) Sever level MBean hasn't been initialized yet when a web app starts up, causing javax.management.InstanceNotFoundException
by Osamu Nagano (JIRA)
[ https://issues.jboss.org/browse/WFLY-3557?page=com.atlassian.jira.plugin.... ]
Osamu Nagano updated WFLY-3557:
-------------------------------
Description: With "-Dorg.apache.tomcat.util.ENABLE_MODELER=true", server level MBeans like a global valve become available. Those should be visible from start phase of a web app, though sometimes those are missing and javax.management.InstanceNotFoundException is thrown. This sporadically happens due to the parallel nature of WildFly start up. It is reproducible by using a debugger (Eclipse is better than JDB, because JDB stops all threads). (was: With "-Dorg.apache.tomcat.util.ENABLE_MODELER=true", server level MBeans like a global valve become available. Those should be visible from start phase of a web app, though sometimes those are missing and javax.management.InstanceNotFoundException is thrown. This sporadically happens due to the parallel nature of WildFly start up.)
> Sever level MBean hasn't been initialized yet when a web app starts up, causing javax.management.InstanceNotFoundException
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3557
> URL: https://issues.jboss.org/browse/WFLY-3557
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (JBoss Web)
> Affects Versions: JBoss AS7 7.2.0.Final
> Reporter: Osamu Nagano
> Assignee: Remy Maucherat
> Attachments: module.xml, TestWAR.war, test_valve.jar
>
>
> With "-Dorg.apache.tomcat.util.ENABLE_MODELER=true", server level MBeans like a global valve become available. Those should be visible from start phase of a web app, though sometimes those are missing and javax.management.InstanceNotFoundException is thrown. This sporadically happens due to the parallel nature of WildFly start up. It is reproducible by using a debugger (Eclipse is better than JDB, because JDB stops all threads).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (WFLY-3557) Sever level MBean hasn't been initialized yet when a web app starts up, causing javax.management.InstanceNotFoundException
by Osamu Nagano (JIRA)
[ https://issues.jboss.org/browse/WFLY-3557?page=com.atlassian.jira.plugin.... ]
Osamu Nagano updated WFLY-3557:
-------------------------------
Attachment: module.xml
test_valve.jar
TestWAR.war
> Sever level MBean hasn't been initialized yet when a web app starts up, causing javax.management.InstanceNotFoundException
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3557
> URL: https://issues.jboss.org/browse/WFLY-3557
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (JBoss Web)
> Affects Versions: JBoss AS7 7.2.0.Final
> Reporter: Osamu Nagano
> Assignee: Remy Maucherat
> Attachments: module.xml, TestWAR.war, test_valve.jar
>
>
> With "-Dorg.apache.tomcat.util.ENABLE_MODELER=true", server level MBeans like a global valve become available. Those should be visible from start phase of a web app, though sometimes those are missing and javax.management.InstanceNotFoundException is thrown. This sporadically happens due to the parallel nature of WildFly start up. It is reproducible by using a debugger (Eclipse is better than JDB, because JDB stops all threads).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (WFLY-3557) Sever level MBean hasn't been initialized yet when a web app starts up, causing javax.management.InstanceNotFoundException
by Osamu Nagano (JIRA)
Osamu Nagano created WFLY-3557:
----------------------------------
Summary: Sever level MBean hasn't been initialized yet when a web app starts up, causing javax.management.InstanceNotFoundException
Key: WFLY-3557
URL: https://issues.jboss.org/browse/WFLY-3557
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (JBoss Web)
Affects Versions: JBoss AS7 7.2.0.Final
Reporter: Osamu Nagano
Assignee: Remy Maucherat
With "-Dorg.apache.tomcat.util.ENABLE_MODELER=true", server level MBeans like a global valve become available. Those should be visible from start phase of a web app, though sometimes those are missing and javax.management.InstanceNotFoundException is thrown. This sporadically happens due to the parallel nature of WildFly start up.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (WFLY-3548) JTA synchronization for a distributed transaction called with incorrect TCCL
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-3548?page=com.atlassian.jira.plugin.... ]
Martin Kouba commented on WFLY-3548:
------------------------------------
One way is described in the referenced [bugzilla issue|https://bugzilla.redhat.com/show_bug.cgi?id=1098127 ].
The other way is a bit simpler:
# Enable JTS
# Run CDI TCK test: {{org.jboss.cdi.tck.tests.event.observer.transactional.TransactionalObserverTest}} - note that this test is currently missing some assertions (CDITCK-427) and does not fail, however you should see exceptions in the log
## git clone git@github.com:weld/core.git
## cd core/jboss-tck-runner/1.1/
## mvn clean test -Dincontainer -DtckTest=TransactionalObserverTest#testSucessfullTransaction
> JTA synchronization for a distributed transaction called with incorrect TCCL
> ----------------------------------------------------------------------------
>
> Key: WFLY-3548
> URL: https://issues.jboss.org/browse/WFLY-3548
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Transactions
> Affects Versions: 8.1.0.Final
> Reporter: Martin Kouba
> Assignee: Gytis Trikleris
>
> It seems the RequestProcessor which is processing JTA synchronizations
> does not have the right TCCL set.
> As a result, during synchronization invocation:
> * {{NameNotFoundException}} is thrown for a JNDI lookup of "java:comp/UserTransaction"
> * if we try to acccess {{org.jboss.weld.Container}} by means of {{org.jboss.as.weld.services.ModuleGroupSingletonProvider.TCCLSingleton}}, we get ISE: "Singleton not set....This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment."
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (DROOLS-354) Can't load pom.properties when jar not on default drive on Windows
by Vijay Dharap (JIRA)
[ https://issues.jboss.org/browse/DROOLS-354?page=com.atlassian.jira.plugin... ]
Vijay Dharap commented on DROOLS-354:
-------------------------------------
To give my scneario details;
1. drools rules kjar project built and installed from D drive. (got installed on C:\ in M2_REPO) - mvn install
2. java jar project is trying to utilize the installed kjar module for exec:java maven goal to run a commandline java program.
Following is the error log:
[INFO] --- exec-maven-plugin:1.2.1:java (default-cli) @ yyyy-web ---
[com.xxxx.yyyy.util.ReportCalculator.main()] INFO org.drools.compiler.kie.builder.impl.ClasspathKieProject - Found kmodule: jar:file:/C:/Users/vijay_dharap/.m2/repository/com/xxxx/yyyy-rules/0.0.1-SNAPSHOT/yyyy-rules-0.0.1-SNAPSHOT.jar!/META-INF/kmodule.xml
[com.xxxx.yyyy.util.ReportCalculator.main()] ERROR org.drools.compiler.kie.builder.impl.ClasspathKieProject - Unable to load pom.properties from/C:/Users/vijay_dharap/.m2/repository/com/xxxx/yyyy-rules/0.0.1-SNAPSHOT/yyyy-rules-0.0.1-SNAPSHOT.jar as jarPath cannot be found
/Users/vijay_dharap/.m2/repository/com/xxxx/yyyy-rules/0.0.1-SNAPSHOT/yyyy-rules-0.0.1-SNAPSHOT.jar
[com.xxxx.yyyy.util.ReportCalculator.main()] ERROR org.drools.compiler.kie.builder.impl.ClasspathKieProject - Unable to load pom.properties from/C:/Users/vijay_dharap/.m2/repository/com/xxxx/yyyy-rules/0.0.1-SNAPSHOT/yyyy-rules-0.0.1-SNAPSHOT.jar
\Users\vijay_dharap\.m2\repository\com\xxxx\yyyy-rules\0.0.1-SNAPSHOT\yyyy-rules-0.0.1-SNAPSHOT.jar (The system cannot find the path specified)
[com.xxxx.yyyy.util.ReportCalculator.main()] ERROR org.drools.compiler.kie.builder.impl.ClasspathKieProject - Unable to build index of kmodule.xml url=jar:file:/C:/Users/vijay_dharap/.m2/repository/com/xxxx/yyyy-rules/0.0.1-SNAPSHOT/yyyy-rules-0.0.1-SNAPSHOT.jar!/META-INF/kmodule.xml
null
> Can't load pom.properties when jar not on default drive on Windows
> ------------------------------------------------------------------
>
> Key: DROOLS-354
> URL: https://issues.jboss.org/browse/DROOLS-354
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 6.0.0.Final
> Environment: Windows
> Reporter: Peter Cooper
> Assignee: Mark Proctor
>
> I'm using Apache Tomcat to run my web application, which includes Drools 6.0.0.Final and getting rules files out of the classpath. However, the webapps directory (the appBase in Tomcat's server.xml) is on a different drive than the main Tomcat installation. When Drools is trying to get its pom properties (ClasspathKieProject's getPomProperties method, starting on line 167) it looks like it first strips off the Windows drive letter. It then tries to find the path, but on the drive of the Windows current directory (in this case, the drive where Tomcat is installed) instead of the drive where the file actually is. This means that it can't find the jar file, so I get the "Unable to load pom.properties" "as jarPath cannot be found" error. I'm not sure why it's trying to strip off the drive letter, since I think it would be able to find the file correctly if that weren't the case.
> Thank you.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (JBASMP-58) jboss-as-maven-plugin freezes on authentication
by Bryan Galvin (JIRA)
[ https://issues.jboss.org/browse/JBASMP-58?page=com.atlassian.jira.plugin.... ]
Bryan Galvin commented on JBASMP-58:
------------------------------------
Jarkko - The history of this issue does not only apply to 7.5 Final .... read this
https://github.com/jbossas/jboss-as-maven-plugin/issues/18
I posted my experience with this issue here and the actions we took to resolve it.
When Judah posted, I responded to help with those things that worked for us; and I am glad to see the issue is resolved for Judah.
I am not "talking about" downgrading to anyone.
> jboss-as-maven-plugin freezes on authentication
> -----------------------------------------------
>
> Key: JBASMP-58
> URL: https://issues.jboss.org/browse/JBASMP-58
> Project: JBoss AS Maven Plugins
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: deploy
> Affects Versions: 7.5.Final
> Environment: mac os x 10.8.5 & mac os x 10.9
> mvn 3.1.1
> Reporter: Julien Derveeuw
> Assignee: James Perkins
> Priority: Critical
>
> I have jboss 7.1.1 in standalone mode running on machine A (linux).
> I want to deploy remotely to it using client machine B @ mac os X 10.8.5 / JDK 1.7.0_45-b18.
> If I connect from B to A using {{jboss-cli}}, everything works fine, I am able to login.
> If I try to deploy from maven with this :
> {code:xml}
> <groupId>org.jboss.as.plugins</groupId>
> <artifactId>jboss-as-maven-plugin</artifactId>
> <version>7.5.Final</version>
> <configuration>
> <hostname>${deploy.jboss.host}</hostname>
> <port>${deploy.jboss.port}</port>
> <username>${deploy.jboss.user}</username>
> <password>${deploy.jboss.password}</password>
> </configuration>
> <executions>
> <execution>
> <phase>install</phase>
> <goals>
> <goal>deploy</goal>
> </goals>
> </execution>
> </executions>
> {code}
> plugin freezes indefinitely on
> {{Authenticating against security realm: ManagementRealm}}
> No more details are available with {{mvn -X}}
> If I remove the password or username from pom, it fails correctly with :
> {{The connection failed: Authentication failed: all available authentication mechanisms failed}}
> so it seems that the plugin somehow manages to connect to machine A.
> After digging on google, I ended up adding {{-Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.KQueueSelectorProvider}} to mvn runner options because NIOs on jdk7@macosx is said to be buggy but it didn't help.
> More details :
> {code:title=mvn 3.1.1 output|borderStyle=solid}Nov 7, 2013 10:40:09 PM org.xnio.Xnio <clinit>
> INFO: XNIO Version 3.0.3.GA
> Nov 7, 2013 10:40:09 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.0.3.GA
> Nov 7, 2013 10:40:09 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 3.2.3.GA
> Authenticating against security realm: ManagementRealm
> {code}
> {code:title=jstack 7.1.1.Final|borderStyle=solid}
> "main" prio=5 tid=7f86d6800800 nid=0x1060f0000 in Object.wait() [1060ee000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <7f4102a20> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl)
> at java.lang.Object.wait(Object.java:485)
> at org.jboss.threads.AsyncFutureTask.await(AsyncFutureTask.java:192)
> - locked <7f4102a20> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl)
> at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:266)
> - locked <7f4102a20> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient$DelegatingCancellableAsyncFuture.get(AbstractModelControllerClient.java:363)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient$DelegatingCancellableAsyncFuture.get(AbstractModelControllerClient.java:317)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:137)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:81)
> at org.jboss.as.plugin.deployment.standalone.StandaloneDeployment.exists(StandaloneDeployment.java:175)
> at org.jboss.as.plugin.deployment.standalone.StandaloneDeployment.createPlan(StandaloneDeployment.java:108)
> at org.jboss.as.plugin.deployment.standalone.StandaloneDeployment.execute(StandaloneDeployment.java:133)
> at org.jboss.as.plugin.deployment.AbstractDeployment.execute(AbstractDeployment.java:138)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {code}
> {code:title=jstack 7.5.Final|borderStyle=solid}
> "main" prio=5 tid=7fceea001000 nid=0x10d4d0000 in Object.wait() [10d4ce000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <7f42f2150> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl)
> at java.lang.Object.wait(Object.java:485)
> at org.jboss.threads.AsyncFutureTask.await(AsyncFutureTask.java:192)
> - locked <7f42f2150> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl)
> at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:266)
> - locked <7f42f2150> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl)
> at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:100)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.as.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:234)
> at org.jboss.as.plugin.common.AbstractServerConnection.getClient(AbstractServerConnection.java:156)
> - locked <7f42f2230> (a java.lang.Object)
> at org.jboss.as.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:133)
> - locked <7f42f2230> (a java.lang.Object)
> at org.jboss.as.plugin.deployment.AbstractDeployment.validate(AbstractDeployment.java:192)
> at org.jboss.as.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:136)
> - locked <7f42f2230> (a java.lang.Object)
> at org.jboss.as.plugin.deployment.AbstractAppDeployment.doExecute(AbstractAppDeployment.java:70)
> at org.jboss.as.plugin.deployment.AbstractDeployment.execute(AbstractDeployment.java:111)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months