[JBoss JIRA] (ELY-116) Review getRealmName on RealmIdentity
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-116?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse resolved ELY-116.
----------------------------------
Assignee: David Lloyd (was: Darran Lofthouse)
Resolution: Done
getRealmName has been removed from the RealmIdentity
> Review getRealmName on RealmIdentity
> ------------------------------------
>
> Key: ELY-116
> URL: https://issues.jboss.org/browse/ELY-116
> Project: WildFly Elytron
> Issue Type: Task
> Components: API / SPI
> Reporter: Darran Lofthouse
> Assignee: David Lloyd
> Priority: Critical
> Labels: api_review
> Fix For: 1.0.0.Alpha1
>
>
> Within the subsystem we considering that a realm can be aliased by the time it is contained in a security domain, this then calls into question the realm name of any identity it creates.
> Need a more thorough review of how the name of the realm will be used, need to also consider how it fits with authentication mechanisms that use the realm name e.g. Digest and also credentials that incorporate the realm name.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-3174) Add view of batch jobs with ability to view, restart and stop
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3174?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-3174:
-----------------------------------
{quote}
What's best practice for executing actions on behalf of a deployment from a subsystem?
{quote}
SubsystemRegistration#registerDeploymentModel(...)
we use that for all subsystem that expose any deployment related metrics / resources
in resource tree you get this than visible in /deployment=name-of-deployment.ext/subsystem=<name-of-subsystem-that-exposes-data>/<what-ever-you-want-to-expose>
> Add view of batch jobs with ability to view, restart and stop
> -------------------------------------------------------------
>
> Key: WFLY-3174
> URL: https://issues.jboss.org/browse/WFLY-3174
> Project: WildFly
> Issue Type: Feature Request
> Components: Batch
> Reporter: James Perkins
> Assignee: James Perkins
>
> Currently there is no way to view batch jobs for a deployment with in the batch subsystem management. There should be a way to view the batch jobs that have run on various deployments.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-3839) EjbClient: No cluster node manager found for node XY during server restart
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-3839?page=com.atlassian.jira.plugin.... ]
Paul Ferraro reassigned WFLY-3839:
----------------------------------
Assignee: Richard Achmatowicz (was: Paul Ferraro)
> EjbClient: No cluster node manager found for node XY during server restart
> ---------------------------------------------------------------------------
>
> Key: WFLY-3839
> URL: https://issues.jboss.org/browse/WFLY-3839
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Affects Versions: 8.1.0.Final
> Reporter: Dominik Pospisil
> Assignee: Richard Achmatowicz
>
> Situation: 4-node cluster, one node is failed at a time, during the whole test, clients are accessing stateless clustered EJB3. The failure type in this particular case is simulating server crash: JVM is killed using kill -9.
> When the server was starting, being brought back, we saw this error:
> 16:05:29,966 ERROR [org.jboss.ejb.client.ClusterContext] (ejb-client-cluster-node-connection-creation-2-thread-17) Cannot create EJBReceiver since no cluster node manager found for node perf20 in cluster context for cluster ejb
> Here is the log output again with context, the server was starting:
> {noformat}
> 16:05:29,966 INFO [org.jboss.ejb.client.remoting.NoSuchEJBExceptionResponseHandler] (Remoting "config-based-ejb-client-endpoint" task-2) Retrying invocation which failed on node perf20 with exception:
> javax.ejb.NoSuchEJBException: No such EJB[appname=clusterbench-ee6,modulename=clusterbench-ee6-ejb,distinctname=,beanname=RemoteStatelessSBImpl]
> at org.jboss.ejb.client.remoting.NoSuchEJBExceptionResponseHandler.processMessage(NoSuchEJBExceptionResponseHandler.java:64)
> at org.jboss.ejb.client.remoting.ChannelAssociation.processResponse(ChannelAssociation.java:366)
> at org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver.handleMessage(ChannelAssociation.java:458)
> at org.jboss.remoting3.remote.RemoteConnectionChannel$4.run(RemoteConnectionChannel.java:373)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> 16:05:29,966 ERROR [org.jboss.ejb.client.ClusterContext] (ejb-client-cluster-node-connection-creation-2-thread-17) Cannot create EJBReceiver since no cluster node manager found for node perf20 in cluster context for cluster ejb
> 16:05:29,974 INFO [org.jboss.ejb.client.remoting.NoSuchEJBExceptionResponseHandler] (Remoting "config-based-ejb-client-endpoint" task-2) Retrying invocation which failed on node perf20 with exception:
> javax.ejb.NoSuchEJBException: No such EJB[appname=clusterbench-ee6,modulename=clusterbench-ee6-ejb,distinctname=,beanname=RemoteStatelessSBImpl]
> at org.jboss.ejb.client.remoting.NoSuchEJBExceptionResponseHandler.processMessage(NoSuchEJBExceptionResponseHandler.java:64)
> at org.jboss.ejb.client.remoting.ChannelAssociation.processResponse(ChannelAssociation.java:366)
> at org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver.handleMessage(ChannelAssociation.java:458)
> at org.jboss.remoting3.remote.RemoteConnectionChannel$4.run(RemoteConnectionChannel.java:373)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> 16:05:29,974 ERROR [org.jboss.ejb.client.ClusterContext] (ejb-client-cluster-node-connection-creation-2-thread-18) Cannot create EJBReceiver since no cluster node manager found for node perf20 in cluster context for cluster ejb
> 16:05:29,975 INFO [org.jboss.ejb.client.remoting.NoSuchEJBExceptionResponseHandler] (Remoting "config-based-ejb-client-endpoint" task-2) Retrying invocation which failed on node perf20 with exception:
> javax.ejb.NoSuchEJBException: No such EJB[appname=clusterbench-ee6,modulename=clusterbench-ee6-ejb,distinctname=,beanname=RemoteStatelessSBImpl]
> at org.jboss.ejb.client.remoting.NoSuchEJBExceptionResponseHandler.processMessage(NoSuchEJBExceptionResponseHandler.java:64)
> at org.jboss.ejb.client.remoting.ChannelAssociation.processResponse(ChannelAssociation.java:366)
> at org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver.handleMessage(ChannelAssociation.java:458)
> at org.jboss.remoting3.remote.RemoteConnectionChannel$4.run(RemoteConnectionChannel.java:373)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> 16:05:29,975 INFO [org.jboss.ejb.client.remoting.NoSuchEJBExceptionResponseHandler] (Remoting "config-based-ejb-client-endpoint" task-2) Retrying invocation which failed on node perf20 with exception:
> javax.ejb.NoSuchEJBException: No such EJB[appname=clusterbench-ee6,modulename=clusterbench-ee6-ejb,distinctname=,beanname=RemoteStatelessSBImpl]
> at org.jboss.ejb.client.remoting.NoSuchEJBExceptionResponseHandler.processMessage(NoSuchEJBExceptionResponseHandler.java:64)
> at org.jboss.ejb.client.remoting.ChannelAssociation.processResponse(ChannelAssociation.java:366)
> at org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver.handleMessage(ChannelAssociation.java:458)
> at org.jboss.remoting3.remote.RemoteConnectionChannel$4.run(RemoteConnectionChannel.java:373)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> {noformat}
> During the whole test, there were 4 server crashes and startups (1 for each node), but only 3 occurences of the above mentioned error. These cluster nodes are perf18, perf19, perf20, perf21, but this error was seen only for perf20 (two occurences) and perf18 (one occurence).
> I did not find anything suspicious in the server.log of perf20.
> Cache: REPL_ASYNC
> Versions: EAP 6.1.0.ER6, ejb-client 1.0.19.Final
> Link to hudson job:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-ejb-...
> Server log:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-ejb-...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-3174) Add view of batch jobs with ability to view, restart and stop
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-3174?page=com.atlassian.jira.plugin.... ]
James Perkins commented on WFLY-3174:
-------------------------------------
Thoughts:
* We need to determine if these operations should live on the batch resource or the deployment.
** If on batch it's likely a good idea to have dynamic resources for each deployment then each batch job.
* What's best practice for executing actions on behalf of a deployment from a subsystem?
* How should we limit the number of jobs displayed?
> Add view of batch jobs with ability to view, restart and stop
> -------------------------------------------------------------
>
> Key: WFLY-3174
> URL: https://issues.jboss.org/browse/WFLY-3174
> Project: WildFly
> Issue Type: Feature Request
> Components: Batch
> Reporter: James Perkins
> Assignee: James Perkins
>
> Currently there is no way to view batch jobs for a deployment with in the batch subsystem management. There should be a way to view the batch jobs that have run on various deployments.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4328) Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning)
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4328?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar edited comment on WFLY-4328 at 2/9/15 10:37 AM:
------------------------------------------------------------
Environment? Exact OS & version? Exact Java version? Maven version?
Also how did you try to build so this happen. params to maven and from where it was executed
was (Author: ctomc):
Environment? Exact OS & version? Exact Java version? Maven version?
> Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning)
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4328
> URL: https://issues.jboss.org/browse/WFLY-4328
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Reporter: Carlton Zachary
> Assignee: Eduardo Martins
>
> Getting the following error at the end of the Wildfly build.
> {noformat}
> [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning) on project wildfly-build: Execution server-provis
> ioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: java.lang.RuntimeException: Failed to process feature pack C:\WildFly9\wildfly\web-feature-pack\target\wildfly-web-feature-pack-9.0.0.Alpha2-SNAPSHOT.zip modules: C:\WildFly9\wildfly\build\target\wildfly-9.0.0.Alpha2-SNAPSHOT\modules\system\layers\base\org\picketbox\main\module.xml -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning) on project wildfly-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: java.lang.RuntimeException: Failed to process feature pack C:\WildFly9\wildfly\web-feature-pack\target\wildfly-web-feature-pack-9.0.0.Alpha2-SNAPSHOT.zip modules
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> 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:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4328) Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning)
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4328?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-4328:
------------------------------
Description:
Getting the following error at the end of the Wildfly build.
{noformat}
[ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning) on project wildfly-build: Execution server-provis
ioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: java.lang.RuntimeException: Failed to process feature pack C:\WildFly9\wildfly\web-feature-pack\target\wildfly-web-feature-pack-9.0.0.Alpha2-SNAPSHOT.zip modules: C:\WildFly9\wildfly\build\target\wildfly-9.0.0.Alpha2-SNAPSHOT\modules\system\layers\base\org\picketbox\main\module.xml -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning) on project wildfly-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: java.lang.RuntimeException: Failed to process feature pack C:\WildFly9\wildfly\web-feature-pack\target\wildfly-web-feature-pack-9.0.0.Alpha2-SNAPSHOT.zip modules
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
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:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
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)
{noformat}
was:
Getting the following error at the end of the Wildfly build.
[ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning) on project wildfly-build: Execution server-provis
ioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: java.lang.RuntimeException: Failed to process featu
re pack C:\WildFly9\wildfly\web-feature-pack\target\wildfly-web-feature-pack-9.0.0.Alpha2-SNAPSHOT.zip modules: C:\WildFly9\wildfly\build\target\wildfly-9.0.0.Alpha2-SNAPSHOT\modules\system\layers\base\org\picketbox\main\module.xml -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning) o
n project wildfly-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: jav
a.lang.RuntimeException: Failed to process feature pack C:\WildFly9\wildfly\web-feature-pack\target\wildfly-web-feature-pack-9.0.0.Alpha2-SNAPSHOT.zi
p modules
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
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:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
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)
> Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning)
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4328
> URL: https://issues.jboss.org/browse/WFLY-4328
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Reporter: Carlton Zachary
> Assignee: Eduardo Martins
>
> Getting the following error at the end of the Wildfly build.
> {noformat}
> [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning) on project wildfly-build: Execution server-provis
> ioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: java.lang.RuntimeException: Failed to process feature pack C:\WildFly9\wildfly\web-feature-pack\target\wildfly-web-feature-pack-9.0.0.Alpha2-SNAPSHOT.zip modules: C:\WildFly9\wildfly\build\target\wildfly-9.0.0.Alpha2-SNAPSHOT\modules\system\layers\base\org\picketbox\main\module.xml -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning) on project wildfly-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: java.lang.RuntimeException: Failed to process feature pack C:\WildFly9\wildfly\web-feature-pack\target\wildfly-web-feature-pack-9.0.0.Alpha2-SNAPSHOT.zip modules
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> 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:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4328) Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning)
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4328?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-4328:
---------------------------------
Assignee: Eduardo Martins (was: Jason Greene)
> Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning)
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4328
> URL: https://issues.jboss.org/browse/WFLY-4328
> Project: WildFly
> Issue Type: Bug
> Reporter: Carlton Zachary
> Assignee: Eduardo Martins
>
> Getting the following error at the end of the Wildfly build.
> [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning) on project wildfly-build: Execution server-provis
> ioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: java.lang.RuntimeException: Failed to process featu
> re pack C:\WildFly9\wildfly\web-feature-pack\target\wildfly-web-feature-pack-9.0.0.Alpha2-SNAPSHOT.zip modules: C:\WildFly9\wildfly\build\target\wildfly-9.0.0.Alpha2-SNAPSHOT\modules\system\layers\base\org\picketbox\main\module.xml -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning) o
> n project wildfly-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: jav
> a.lang.RuntimeException: Failed to process feature pack C:\WildFly9\wildfly\web-feature-pack\target\wildfly-web-feature-pack-9.0.0.Alpha2-SNAPSHOT.zi
> p modules
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> 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:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4328) Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning)
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4328?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-4328:
------------------------------
Component/s: Build System
> Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning)
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4328
> URL: https://issues.jboss.org/browse/WFLY-4328
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Reporter: Carlton Zachary
> Assignee: Eduardo Martins
>
> Getting the following error at the end of the Wildfly build.
> [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning) on project wildfly-build: Execution server-provis
> ioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: java.lang.RuntimeException: Failed to process featu
> re pack C:\WildFly9\wildfly\web-feature-pack\target\wildfly-web-feature-pack-9.0.0.Alpha2-SNAPSHOT.zip modules: C:\WildFly9\wildfly\build\target\wildfly-9.0.0.Alpha2-SNAPSHOT\modules\system\layers\base\org\picketbox\main\module.xml -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning) o
> n project wildfly-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: jav
> a.lang.RuntimeException: Failed to process feature pack C:\WildFly9\wildfly\web-feature-pack\target\wildfly-web-feature-pack-9.0.0.Alpha2-SNAPSHOT.zi
> p modules
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> 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:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4328) Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning)
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4328?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-4328:
-----------------------------------
Environment? Exact OS & version? Exact Java version? Maven version?
> Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning)
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4328
> URL: https://issues.jboss.org/browse/WFLY-4328
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Reporter: Carlton Zachary
> Assignee: Eduardo Martins
>
> Getting the following error at the end of the Wildfly build.
> [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning) on project wildfly-build: Execution server-provis
> ioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: java.lang.RuntimeException: Failed to process featu
> re pack C:\WildFly9\wildfly\web-feature-pack\target\wildfly-web-feature-pack-9.0.0.Alpha2-SNAPSHOT.zip modules: C:\WildFly9\wildfly\build\target\wildfly-9.0.0.Alpha2-SNAPSHOT\modules\system\layers\base\org\picketbox\main\module.xml -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build (server-provisioning) o
> n project wildfly-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: jav
> a.lang.RuntimeException: Failed to process feature pack C:\WildFly9\wildfly\web-feature-pack\target\wildfly-web-feature-pack-9.0.0.Alpha2-SNAPSHOT.zi
> p modules
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> 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:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-73) NPE in RootResourceIterator
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-73?page=com.atlassian.jira.plugin.sy... ]
RH Bugzilla Integration commented on WFLY-73:
---------------------------------------------
Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1185118|https://bugzilla.redhat.com/show_bug.cgi?id=1185118] from ON_QA to ASSIGNED
> NPE in RootResourceIterator
> ---------------------------
>
> Key: WFLY-73
> URL: https://issues.jboss.org/browse/WFLY-73
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JMX
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 8.0.0.Alpha1
>
>
> Intermittent testsuite failures, e.g.
> http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/684...
> Log shows this repeatedly:
> [0m[33m18:38:11,612 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-2-thread-12) Unexpected internal error: java.lang.NullPointerException
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:49)
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
> at org.jboss.as.jmx.model.RootResourceIterator.iterate(RootResourceIterator.java:39)
> at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getMBeanCount(ModelControllerMBeanHelper.java:103)
> at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.getMBeanCount(ModelControllerMBeanServerPlugin.java:116)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.getMBeanCount(PluggableMBeanServerImpl.java:220)
> at org.jboss.remotingjmx.protocol.v2.ServerProxy$GetMBeanCountHandler.handle(ServerProxy.java:618)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:152)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> RootResourceIterator.doIterate is reading the resource twice:
> {code}
> for (ResourceEntry entry : current.getChildren(type)) {
> final PathElement pathElement = entry.getPathElement();
> final Resource child = current.getChild(pathElement); // why this call since "entry" and "child" should be the same object
> final PathAddress childAddress = address.append(pathElement);
> doIterate(child, childAddress);
> }
> {code}
> The problem is "child" is null, which is possible with a dynamic resource. So, either "entry" should be used, or, if there is some reason for the 2nd read, a check for null is needed before the recursive doIterate call.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months