February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBASMP-58) jboss-as-maven-plugin freezes on authentication

by Jarkko Rantavuori (JIRA)

[ https://issues.jboss.org/browse/JBASMP-58?page=com.atlassian.jira.plugin.... ] Jarkko Rantavuori commented on JBASMP-58: ----------------------------------------- I am encountering this on Windows 7, Maven 3.0.4, Maven-plugin 7.5.Final, deploying to EAP 6.1.1 in local VM that is using CentOS 6.4. It doesn't seem to be Mac-only issue. > 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 > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2996) Remove need for native-interface on the Host Controller

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-2996: -------------------------------------- Summary: Remove need for native-interface on the Host Controller Key: WFLY-2996 URL: https://issues.jboss.org/browse/WFLY-2996 Project: WildFly Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 9.0.0.CR1 The HC requires a native-interface becomes the intra-domain comms (slave->master and server->HC) are hard coded to the "remote" protocol. Make this configurable for slave->master and dynamically determine what to use for server->HC. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2996) Remove need for native-interface on the Host Controller

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2996?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-2996: ----------------------------------- Description: The HC requires a native-interface because the intra-domain comms (slave->master and server->HC) are hard coded to the "remote" protocol. Make this configurable for slave->master and dynamically determine what to use for server->HC. (was: The HC requires a native-interface becomes the intra-domain comms (slave->master and server->HC) are hard coded to the "remote" protocol. Make this configurable for slave->master and dynamically determine what to use for server->HC.) > Remove need for native-interface on the Host Controller > ------------------------------------------------------- > > Key: WFLY-2996 > URL: https://issues.jboss.org/browse/WFLY-2996 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 9.0.0.CR1 > > > The HC requires a native-interface because the intra-domain comms (slave->master and server->HC) are hard coded to the "remote" protocol. Make this configurable for slave->master and dynamically determine what to use for server->HC. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2908) The formatter attribute is changed every time it's processed

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2908?page=com.atlassian.jira.plugin.... ] James Perkins edited comment on WFLY-2908 at 2/21/14 1:38 PM: -------------------------------------------------------------- WFLY-2995 was hidden because of this bug. was (Author: jamezp): WFLY-2909 was hidden because of this bug. > The formatter attribute is changed every time it's processed > ------------------------------------------------------------ > > Key: WFLY-2908 > URL: https://issues.jboss.org/browse/WFLY-2908 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 8.0.1.Final > > > The {{HandlerOperations.equalValue()}} method uses the incorrect property name when comparing values resulting in the method always returning {{false}}. > This does not harm anything, but just changes the format pattern each time a resource is processed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2995) Using a log4j appender as a custom-handler should invoke the activateOptions if required

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2995?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2995: ----------------------------------------------- James Perkins <jperkins(a)redhat.com> changed the Status of [bug 1066606|https://bugzilla.redhat.com/show_bug.cgi?id=1066606] from NEW to ASSIGNED > Using a log4j appender as a custom-handler should invoke the activateOptions if required > ---------------------------------------------------------------------------------------- > > Key: WFLY-2995 > URL: https://issues.jboss.org/browse/WFLY-2995 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > > Currently the {{OptionHandler.activateOptions}} is only invoked during construction of a log4j appender. This invocation should happen if any property is updated or added. The invocation of this method should also only happen once. Multiple invocation could result in errors or leave the appender in an invalid state. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2995) Using a log4j appender as a custom-handler should invoke the activateOptions if required

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2995?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2995: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1066606, https://bugzilla.redhat.com/show_bug.cgi?id=1066607 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1066607) > Using a log4j appender as a custom-handler should invoke the activateOptions if required > ---------------------------------------------------------------------------------------- > > Key: WFLY-2995 > URL: https://issues.jboss.org/browse/WFLY-2995 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > > Currently the {{OptionHandler.activateOptions}} is only invoked during construction of a log4j appender. This invocation should happen if any property is updated or added. The invocation of this method should also only happen once. Multiple invocation could result in errors or leave the appender in an invalid state. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2995) Using a log4j appender as a custom-handler should invoke the activateOptions if required

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2995?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2995: ----------------------------------------------- James Perkins <jperkins(a)redhat.com> changed the Status of [bug 1066607|https://bugzilla.redhat.com/show_bug.cgi?id=1066607] from NEW to ASSIGNED > Using a log4j appender as a custom-handler should invoke the activateOptions if required > ---------------------------------------------------------------------------------------- > > Key: WFLY-2995 > URL: https://issues.jboss.org/browse/WFLY-2995 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > > Currently the {{OptionHandler.activateOptions}} is only invoked during construction of a log4j appender. This invocation should happen if any property is updated or added. The invocation of this method should also only happen once. Multiple invocation could result in errors or leave the appender in an invalid state. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2995) Using a log4j appender as a custom-handler should invoke the activateOptions if required

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2995?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2995: ----------------------------------------------- James Perkins <jperkins(a)redhat.com> changed the Status of [bug 1066607|https://bugzilla.redhat.com/show_bug.cgi?id=1066607] from NEW to ASSIGNED > Using a log4j appender as a custom-handler should invoke the activateOptions if required > ---------------------------------------------------------------------------------------- > > Key: WFLY-2995 > URL: https://issues.jboss.org/browse/WFLY-2995 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > > Currently the {{OptionHandler.activateOptions}} is only invoked during construction of a log4j appender. This invocation should happen if any property is updated or added. The invocation of this method should also only happen once. Multiple invocation could result in errors or leave the appender in an invalid state. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2995) Using a log4j appender as a custom-handler should invoke the activateOptions if required

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2995?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2995: ------------------------------------------ Bugzilla Update: (was: Perform) Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=1066606, https://bugzilla.redhat.com/show_bug.cgi?id=1066607) > Using a log4j appender as a custom-handler should invoke the activateOptions if required > ---------------------------------------------------------------------------------------- > > Key: WFLY-2995 > URL: https://issues.jboss.org/browse/WFLY-2995 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > > Currently the {{OptionHandler.activateOptions}} is only invoked during construction of a log4j appender. This invocation should happen if any property is updated or added. The invocation of this method should also only happen once. Multiple invocation could result in errors or leave the appender in an invalid state. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2995) Using a log4j appender as a custom-handler should invoke the activateOptions if required

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2995?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2995: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1066606 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1066606, https://bugzilla.redhat.com/show_bug.cgi?id=1066607) > Using a log4j appender as a custom-handler should invoke the activateOptions if required > ---------------------------------------------------------------------------------------- > > Key: WFLY-2995 > URL: https://issues.jboss.org/browse/WFLY-2995 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > > Currently the {{OptionHandler.activateOptions}} is only invoked during construction of a log4j appender. This invocation should happen if any property is updated or added. The invocation of this method should also only happen once. Multiple invocation could result in errors or leave the appender in an invalid state. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2014