[JBoss JIRA] (WFLY-6356) Error while processing a prepare in a single-phase transaction due to replication timeout
by Michal Vinkler (JIRA)
Michal Vinkler created WFLY-6356:
------------------------------------
Summary: Error while processing a prepare in a single-phase transaction due to replication timeout
Key: WFLY-6356
URL: https://issues.jboss.org/browse/WFLY-6356
Project: WildFly
Issue Type: Bug
Components: Clustering
Reporter: Michal Vinkler
Assignee: Paul Ferraro
This is a separate issue originally logged as part of JBEAP-794 (#4 in this [comment|https://issues.jboss.org/browse/JBEAP-794?focusedCommentId=131706...]).
Seen in ejb-remote, ejb-ejbservlet and http-session scenarios with *REPL* cache and *SYNC* replication.
TimeoutException occured after perf18 (or any other node) rejoined a cluster (after graceful shutdown, jvmkill or undeploy - it doesn't matter), but it does not seem to affect client:
{code}
[JBossINF] [0m[31m03:23:38,458 ERROR [org.infinispan.transaction.impl.TransactionCoordinator] (default task-24) ISPN000097: Error while processing a prepare in a single-phase transaction: org.infinispan.util.concurrent.TimeoutException: Replication timeout for perf19
[JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:765)
[JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$175(JGroupsTransport.java:612)
[JBossINF] at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602)
[JBossINF] at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
[JBossINF] at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
[JBossINF] at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962)
[JBossINF] at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:47)
[JBossINF] at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:16)
[JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
[JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
[JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[JBossINF] at java.lang.Thread.run(Thread.java:745)
{code}
Also, JBEAP-3779 an JBEAP-3781 (and partially also JBEAP-3782) accompany this issue, see [occurrences report|http://download.eng.brq.redhat.com/scratch/mvinkler/reports/occurr...]
Server link:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6328) TimeoutException: Replication timeout when handling request
by Michal Vinkler (JIRA)
[ https://issues.jboss.org/browse/WFLY-6328?page=com.atlassian.jira.plugin.... ]
Michal Vinkler updated WFLY-6328:
---------------------------------
Description:
Seen in ejb-ejbservlet and http-session scenarios with *REPL* cache.
TimeoutException occured after perf19 (or any other node) rejoined a cluster (after graceful shutdown, jvmkill or undeploy - it doesn't matter) and definitely results in client getting 500:
{code}
[JBossINF] [0m[31m03:23:38,793 ERROR [io.undertow.request] (default task-92) UT005023: Exception handling request to /clusterbench/session: org.infinispan.util.concurrent.TimeoutException: Replication timeout for perf19
[JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:765)
[JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$175(JGroupsTransport.java:612)
[JBossINF] at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602)
[JBossINF] at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
[JBossINF] at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
[JBossINF] at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962)
[JBossINF] at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:47)
[JBossINF] at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:16)
[JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
[JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
[JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[JBossINF] at java.lang.Thread.run(Thread.java:745)
{code}
Client:
{code}
2016/02/26 03:23:38:806 EST [WARN ][Runner - 1620] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>>
org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>
at org.jboss.smartfrog.loaddriver.http.HttpRequestProcessorFactoryImpl$HttpRequestProcessor.processRequest(HttpRequestProcessorFactoryImpl.java:163)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
at java.lang.Thread.run(Thread.java:745)
{code}
Also, JBEAP-3779 accompanies this issue, see [occurrences report|http://download.eng.brq.redhat.com/scratch/mvinkler/reports/occurr...]
Server link:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
Client link:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
This is a separate Jira for issue #3 from https://issues.jboss.org/browse/JBEAP-794?focusedCommentId=13170628&page=...
was:
Seen in ejb-ejbservlet and http-session scenarios with *REPL* cache.
TimeoutException occured after perf19 rejoined a cluster (after graceful shutdown) and definitely results in client getting 500:
{code}
[JBossINF] [0m[31m03:23:38,793 ERROR [io.undertow.request] (default task-92) UT005023: Exception handling request to /clusterbench/session: org.infinispan.util.concurrent.TimeoutException: Replication timeout for perf19
[JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:765)
[JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$175(JGroupsTransport.java:612)
[JBossINF] at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602)
[JBossINF] at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
[JBossINF] at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
[JBossINF] at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962)
[JBossINF] at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:47)
[JBossINF] at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:16)
[JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
[JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
[JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[JBossINF] at java.lang.Thread.run(Thread.java:745)
{code}
Client:
{code}
2016/02/26 03:23:38:806 EST [WARN ][Runner - 1620] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>>
org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>
at org.jboss.smartfrog.loaddriver.http.HttpRequestProcessorFactoryImpl$HttpRequestProcessor.processRequest(HttpRequestProcessorFactoryImpl.java:163)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
at java.lang.Thread.run(Thread.java:745)
{code}
Also, JBEAP-3779 accompanies this issue, see [occurrences report|http://download.eng.brq.redhat.com/scratch/mvinkler/reports/occurr...]
Server link:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
Client link:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
This is a separate Jira for issue #3 from https://issues.jboss.org/browse/JBEAP-794?focusedCommentId=13170628&page=...
> TimeoutException: Replication timeout when handling request
> -----------------------------------------------------------
>
> Key: WFLY-6328
> URL: https://issues.jboss.org/browse/WFLY-6328
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.Final
> Reporter: Michal Vinkler
> Assignee: Paul Ferraro
> Priority: Critical
>
> Seen in ejb-ejbservlet and http-session scenarios with *REPL* cache.
> TimeoutException occured after perf19 (or any other node) rejoined a cluster (after graceful shutdown, jvmkill or undeploy - it doesn't matter) and definitely results in client getting 500:
> {code}
> [JBossINF] [0m[31m03:23:38,793 ERROR [io.undertow.request] (default task-92) UT005023: Exception handling request to /clusterbench/session: org.infinispan.util.concurrent.TimeoutException: Replication timeout for perf19
> [JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:765)
> [JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$175(JGroupsTransport.java:612)
> [JBossINF] at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602)
> [JBossINF] at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
> [JBossINF] at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
> [JBossINF] at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962)
> [JBossINF] at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:47)
> [JBossINF] at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:16)
> [JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [JBossINF] at java.lang.Thread.run(Thread.java:745)
> {code}
> Client:
> {code}
> 2016/02/26 03:23:38:806 EST [WARN ][Runner - 1620] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>>
> org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>
> at org.jboss.smartfrog.loaddriver.http.HttpRequestProcessorFactoryImpl$HttpRequestProcessor.processRequest(HttpRequestProcessorFactoryImpl.java:163)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Also, JBEAP-3779 accompanies this issue, see [occurrences report|http://download.eng.brq.redhat.com/scratch/mvinkler/reports/occurr...]
> Server link:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
> Client link:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
> This is a separate Jira for issue #3 from https://issues.jboss.org/browse/JBEAP-794?focusedCommentId=13170628&page=...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6328) TimeoutException: Replication timeout when handling request
by Michal Vinkler (JIRA)
[ https://issues.jboss.org/browse/WFLY-6328?page=com.atlassian.jira.plugin.... ]
Michal Vinkler updated WFLY-6328:
---------------------------------
Description:
Seen in ejb-ejbservlet and http-session scenarios with *REPL* cache.
TimeoutException occured after perf19 rejoined a cluster (after graceful shutdown) and definitely results in client getting 500:
{code}
[JBossINF] [0m[31m03:23:38,793 ERROR [io.undertow.request] (default task-92) UT005023: Exception handling request to /clusterbench/session: org.infinispan.util.concurrent.TimeoutException: Replication timeout for perf19
[JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:765)
[JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$175(JGroupsTransport.java:612)
[JBossINF] at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602)
[JBossINF] at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
[JBossINF] at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
[JBossINF] at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962)
[JBossINF] at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:47)
[JBossINF] at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:16)
[JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
[JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
[JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[JBossINF] at java.lang.Thread.run(Thread.java:745)
{code}
Client:
{code}
2016/02/26 03:23:38:806 EST [WARN ][Runner - 1620] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>>
org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>
at org.jboss.smartfrog.loaddriver.http.HttpRequestProcessorFactoryImpl$HttpRequestProcessor.processRequest(HttpRequestProcessorFactoryImpl.java:163)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
at java.lang.Thread.run(Thread.java:745)
{code}
Also, JBEAP-3779 accompanies this issue, see [occurrences report|http://download.eng.brq.redhat.com/scratch/mvinkler/reports/occurr...]
Server link:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
Client link:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
This is a separate Jira for issue #3 from https://issues.jboss.org/browse/JBEAP-794?focusedCommentId=13170628&page=...
was:
Seen in ejb-ejbservlet and http-session scenarios with *REPL* cache.
TimeoutException occured after perf19 rejoined a cluster (after graceful shutdown) and definitely results in client getting 500:
{code}
[JBossINF] [0m[31m03:23:38,793 ERROR [io.undertow.request] (default task-92) UT005023: Exception handling request to /clusterbench/session: org.infinispan.util.concurrent.TimeoutException: Replication timeout for perf19
[JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:765)
[JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$175(JGroupsTransport.java:612)
[JBossINF] at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602)
[JBossINF] at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
[JBossINF] at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
[JBossINF] at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962)
[JBossINF] at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:47)
[JBossINF] at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:16)
[JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
[JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
[JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[JBossINF] at java.lang.Thread.run(Thread.java:745)
{code}
Client:
{code}
2016/02/26 03:23:38:806 EST [WARN ][Runner - 1620] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>>
org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>
at org.jboss.smartfrog.loaddriver.http.HttpRequestProcessorFactoryImpl$HttpRequestProcessor.processRequest(HttpRequestProcessorFactoryImpl.java:163)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
at java.lang.Thread.run(Thread.java:745)
{code}
Server link:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
Client link:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
This is a separate Jira for issue #3 from https://issues.jboss.org/browse/JBEAP-794?focusedCommentId=13170628&page=...
> TimeoutException: Replication timeout when handling request
> -----------------------------------------------------------
>
> Key: WFLY-6328
> URL: https://issues.jboss.org/browse/WFLY-6328
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.Final
> Reporter: Michal Vinkler
> Assignee: Paul Ferraro
> Priority: Critical
>
> Seen in ejb-ejbservlet and http-session scenarios with *REPL* cache.
> TimeoutException occured after perf19 rejoined a cluster (after graceful shutdown) and definitely results in client getting 500:
> {code}
> [JBossINF] [0m[31m03:23:38,793 ERROR [io.undertow.request] (default task-92) UT005023: Exception handling request to /clusterbench/session: org.infinispan.util.concurrent.TimeoutException: Replication timeout for perf19
> [JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:765)
> [JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$175(JGroupsTransport.java:612)
> [JBossINF] at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602)
> [JBossINF] at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
> [JBossINF] at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
> [JBossINF] at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962)
> [JBossINF] at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:47)
> [JBossINF] at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:16)
> [JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [JBossINF] at java.lang.Thread.run(Thread.java:745)
> {code}
> Client:
> {code}
> 2016/02/26 03:23:38:806 EST [WARN ][Runner - 1620] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>>
> org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>
> at org.jboss.smartfrog.loaddriver.http.HttpRequestProcessorFactoryImpl$HttpRequestProcessor.processRequest(HttpRequestProcessorFactoryImpl.java:163)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Also, JBEAP-3779 accompanies this issue, see [occurrences report|http://download.eng.brq.redhat.com/scratch/mvinkler/reports/occurr...]
> Server link:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
> Client link:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
> This is a separate Jira for issue #3 from https://issues.jboss.org/browse/JBEAP-794?focusedCommentId=13170628&page=...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6353) Provide support for "slot" property with "resource-adapter" creation CLI
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/WFLY-6353?page=com.atlassian.jira.plugin.... ]
Ramesh Reddy updated WFLY-6353:
-------------------------------
Summary: Provide support for "slot" property with "resource-adapter" creation CLI (was: Provide support for adding "slot" property with "resource-adapter" creation CLI script)
> Provide support for "slot" property with "resource-adapter" creation CLI
> ------------------------------------------------------------------------
>
> Key: WFLY-6353
> URL: https://issues.jboss.org/browse/WFLY-6353
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 9.0.2.Final
> Reporter: Ramesh Reddy
> Assignee: Alexey Loubyansky
>
> Currently when one adds a resource-adapter using the CLI using the module the "slot" property is allowed in the standalone.xml file. For ex:
> {code}
> <subsystem xmlns="urn:jboss:domain:resource-adapters:3.0">
> <resource-adapters>
> <resource-adapter id="file">
> <module slot="34" id="org.jboss.teiid.resource-adapter.file"/>
> </resource-adapter>
> </resource-adapters>
> </subsystem>
> {code}
> However the same is added through CLI like
> {code}
> /subsystem=resource-adapters/resource-adapter=file:add(module=org.jboss.teiid.resource-adapter.file, slot=34)
> {code}
> it will fail, this should be corrected.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6353) Provide support for adding "slot" property with "resource-adapter" creation CLI script
by Ramesh Reddy (JIRA)
Ramesh Reddy created WFLY-6353:
----------------------------------
Summary: Provide support for adding "slot" property with "resource-adapter" creation CLI script
Key: WFLY-6353
URL: https://issues.jboss.org/browse/WFLY-6353
Project: WildFly
Issue Type: Bug
Components: CLI
Affects Versions: 9.0.2.Final
Reporter: Ramesh Reddy
Assignee: Alexey Loubyansky
Currently when one adds a resource-adapter using the CLI using the module the "slot" property is allowed in the standalone.xml file. For ex:
{code}
<subsystem xmlns="urn:jboss:domain:resource-adapters:3.0">
<resource-adapters>
<resource-adapter id="file">
<module slot="34" id="org.jboss.teiid.resource-adapter.file"/>
</resource-adapter>
</resource-adapters>
</subsystem>
{code}
However the same is added through CLI like
{code}
/subsystem=resource-adapters/resource-adapter=file:add(module=org.jboss.teiid.resource-adapter.file, slot=34)
{code}
it will fail, this should be corrected.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6352) Build Fails with maven 3.3.9 Oracle JDK 8
by Eric Lemesre (JIRA)
[ https://issues.jboss.org/browse/WFLY-6352?page=com.atlassian.jira.plugin.... ]
Eric Lemesre updated WFLY-6352:
-------------------------------
Description:
When trying to build 10.0.0.Final with Maven 3.3.9 I get the following error from maven-enforcer plugin (at wildfly-feature-pack module).
{code}
$ mvn --version
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
Apache Maven 3.3.9
Maven home: /usr/share/maven
Java version: 1.8.0_72, vendor: Oracle Corporation
Java home: /usr/lib/jvm/jdk-8-oracle-x64/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: "linux", version: "4.2.0-1-amd64", arch: "amd64", family: "unix"
{code}
{code}
$ mvn clean install -PRelease
....
[INFO] ------------------------------------------------------------------------
[INFO] Building WildFly: Full Feature Pack 10.0.0.Final
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (ban-bad-dependencies) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-java-version) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-maven-version) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (ban-transitive-deps) @ wildfly-feature-pack ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message:
org.wildfly:wildfly-feature-pack:pom:10.0.0.Final
dom4j:dom4j:jar:1.6.1:compile has transitive dependencies:
jaxme:jaxme-api:jar:0.3:compile
msv:xsdlib:jar:20030807:compile
msv:relaxngDatatype:jar:20030807:compile
pull-parser:pull-parser:jar:2:compile
xpp3:xpp3:jar:1.1.3.3:compile
{code}
was:
When trying to build 10.0.0.Final with Maven 3.3.9 I get the following error from maven-enforcer plugin (at wildfly-feature-pack module).
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
Apache Maven 3.3.9
Maven home: /usr/share/maven
Java version: 1.8.0_72, vendor: Oracle Corporation
Java home: /usr/lib/jvm/jdk-8-oracle-x64/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: "linux", version: "4.2.0-1-amd64", arch: "amd64", family: "unix"
{code}
$ mvn clean install -PRelease
....
[INFO] ------------------------------------------------------------------------
[INFO] Building WildFly: Full Feature Pack 10.0.0.Final
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (ban-bad-dependencies) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-java-version) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-maven-version) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (ban-transitive-deps) @ wildfly-feature-pack ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message:
org.wildfly:wildfly-feature-pack:pom:10.0.0.Final
dom4j:dom4j:jar:1.6.1:compile has transitive dependencies:
jaxme:jaxme-api:jar:0.3:compile
msv:xsdlib:jar:20030807:compile
msv:relaxngDatatype:jar:20030807:compile
pull-parser:pull-parser:jar:2:compile
xpp3:xpp3:jar:1.1.3.3:compile
{code}
> Build Fails with maven 3.3.9 Oracle JDK 8
> ------------------------------------------
>
> Key: WFLY-6352
> URL: https://issues.jboss.org/browse/WFLY-6352
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Affects Versions: 10.0.0.Final
> Environment:
> Reporter: Eric Lemesre
> Assignee: Paul Gier
>
> When trying to build 10.0.0.Final with Maven 3.3.9 I get the following error from maven-enforcer plugin (at wildfly-feature-pack module).
> {code}
> $ mvn --version
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
> Apache Maven 3.3.9
> Maven home: /usr/share/maven
> Java version: 1.8.0_72, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/jdk-8-oracle-x64/jre
> Default locale: fr_FR, platform encoding: UTF-8
> OS name: "linux", version: "4.2.0-1-amd64", arch: "amd64", family: "unix"
> {code}
> {code}
> $ mvn clean install -PRelease
> ....
> [INFO] ------------------------------------------------------------------------
> [INFO] Building WildFly: Full Feature Pack 10.0.0.Final
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ wildfly-feature-pack ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4:enforce (ban-bad-dependencies) @ wildfly-feature-pack ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-java-version) @ wildfly-feature-pack ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-maven-version) @ wildfly-feature-pack ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4:enforce (ban-transitive-deps) @ wildfly-feature-pack ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message:
> org.wildfly:wildfly-feature-pack:pom:10.0.0.Final
> dom4j:dom4j:jar:1.6.1:compile has transitive dependencies:
> jaxme:jaxme-api:jar:0.3:compile
> msv:xsdlib:jar:20030807:compile
> msv:relaxngDatatype:jar:20030807:compile
> pull-parser:pull-parser:jar:2:compile
> xpp3:xpp3:jar:1.1.3.3:compile
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6352) Build Fails with maven 3.3.9 Oracle JDK 8
by Eric Lemesre (JIRA)
[ https://issues.jboss.org/browse/WFLY-6352?page=com.atlassian.jira.plugin.... ]
Eric Lemesre updated WFLY-6352:
-------------------------------
Description:
When trying to build 10.0.0.Final with Maven 3.3.9 I get the following error from maven-enforcer plugin (at wildfly-feature-pack module).
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
Apache Maven 3.3.9
Maven home: /usr/share/maven
Java version: 1.8.0_72, vendor: Oracle Corporation
Java home: /usr/lib/jvm/jdk-8-oracle-x64/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: "linux", version: "4.2.0-1-amd64", arch: "amd64", family: "unix"
{code}
$ mvn clean install -PRelease
....
[INFO] ------------------------------------------------------------------------
[INFO] Building WildFly: Full Feature Pack 10.0.0.Final
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (ban-bad-dependencies) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-java-version) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-maven-version) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (ban-transitive-deps) @ wildfly-feature-pack ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message:
org.wildfly:wildfly-feature-pack:pom:10.0.0.Final
dom4j:dom4j:jar:1.6.1:compile has transitive dependencies:
jaxme:jaxme-api:jar:0.3:compile
msv:xsdlib:jar:20030807:compile
msv:relaxngDatatype:jar:20030807:compile
pull-parser:pull-parser:jar:2:compile
xpp3:xpp3:jar:1.1.3.3:compile
{code}
was:
When trying to build 10.0.0.Final with Maven 3.3.9 I get the following error from maven-enforcer plugin (at wildfly-feature-pack module).
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
Apache Maven 3.3.9
Maven home: /usr/share/maven
Java version: 1.8.0_72, vendor: Oracle Corporation
Java home: /usr/lib/jvm/jdk-8-oracle-x64/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: "linux", version: "4.2.0-1-amd64", arch: "amd64", family: "unix"
```
$ mvn clean install -PRelease
....
[INFO] ------------------------------------------------------------------------
[INFO] Building WildFly: Full Feature Pack 10.0.0.Final
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (ban-bad-dependencies) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-java-version) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-maven-version) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (ban-transitive-deps) @ wildfly-feature-pack ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message:
org.wildfly:wildfly-feature-pack:pom:10.0.0.Final
dom4j:dom4j:jar:1.6.1:compile has transitive dependencies:
jaxme:jaxme-api:jar:0.3:compile
msv:xsdlib:jar:20030807:compile
msv:relaxngDatatype:jar:20030807:compile
pull-parser:pull-parser:jar:2:compile
xpp3:xpp3:jar:1.1.3.3:compile
```
> Build Fails with maven 3.3.9 Oracle JDK 8
> ------------------------------------------
>
> Key: WFLY-6352
> URL: https://issues.jboss.org/browse/WFLY-6352
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Affects Versions: 10.0.0.Final
> Environment:
> Reporter: Eric Lemesre
> Assignee: Paul Gier
>
> When trying to build 10.0.0.Final with Maven 3.3.9 I get the following error from maven-enforcer plugin (at wildfly-feature-pack module).
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
> Apache Maven 3.3.9
> Maven home: /usr/share/maven
> Java version: 1.8.0_72, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/jdk-8-oracle-x64/jre
> Default locale: fr_FR, platform encoding: UTF-8
> OS name: "linux", version: "4.2.0-1-amd64", arch: "amd64", family: "unix"
> {code}
> $ mvn clean install -PRelease
> ....
> [INFO] ------------------------------------------------------------------------
> [INFO] Building WildFly: Full Feature Pack 10.0.0.Final
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ wildfly-feature-pack ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4:enforce (ban-bad-dependencies) @ wildfly-feature-pack ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-java-version) @ wildfly-feature-pack ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-maven-version) @ wildfly-feature-pack ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4:enforce (ban-transitive-deps) @ wildfly-feature-pack ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message:
> org.wildfly:wildfly-feature-pack:pom:10.0.0.Final
> dom4j:dom4j:jar:1.6.1:compile has transitive dependencies:
> jaxme:jaxme-api:jar:0.3:compile
> msv:xsdlib:jar:20030807:compile
> msv:relaxngDatatype:jar:20030807:compile
> pull-parser:pull-parser:jar:2:compile
> xpp3:xpp3:jar:1.1.3.3:compile
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6352) Build Fails with maven 3.3.9 Oracle JDK 8
by Eric Lemesre (JIRA)
[ https://issues.jboss.org/browse/WFLY-6352?page=com.atlassian.jira.plugin.... ]
Eric Lemesre updated WFLY-6352:
-------------------------------
Description:
When trying to build 10.0.0.Final with Maven 3.3.9 I get the following error from maven-enforcer plugin (at wildfly-feature-pack module).
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
Apache Maven 3.3.9
Maven home: /usr/share/maven
Java version: 1.8.0_72, vendor: Oracle Corporation
Java home: /usr/lib/jvm/jdk-8-oracle-x64/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: "linux", version: "4.2.0-1-amd64", arch: "amd64", family: "unix"
```
$ mvn clean install -PRelease
....
[INFO] ------------------------------------------------------------------------
[INFO] Building WildFly: Full Feature Pack 10.0.0.Final
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (ban-bad-dependencies) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-java-version) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-maven-version) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (ban-transitive-deps) @ wildfly-feature-pack ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message:
org.wildfly:wildfly-feature-pack:pom:10.0.0.Final
dom4j:dom4j:jar:1.6.1:compile has transitive dependencies:
jaxme:jaxme-api:jar:0.3:compile
msv:xsdlib:jar:20030807:compile
msv:relaxngDatatype:jar:20030807:compile
pull-parser:pull-parser:jar:2:compile
xpp3:xpp3:jar:1.1.3.3:compile
```
was:
When trying to build 10.0.0.Final with Maven 3.3.9 I get the following error from maven-enforcer plugin (at wildfly-feature-pack module).
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
Apache Maven 3.3.9
Maven home: /usr/share/maven
Java version: 1.8.0_72, vendor: Oracle Corporation
Java home: /usr/lib/jvm/jdk-8-oracle-x64/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: "linux", version: "4.2.0-1-amd64", arch: "amd64", family: "unix"
$ mvn clean install -PRelease
....
[INFO] ------------------------------------------------------------------------
[INFO] Building WildFly: Full Feature Pack 10.0.0.Final
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (ban-bad-dependencies) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-java-version) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-maven-version) @ wildfly-feature-pack ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (ban-transitive-deps) @ wildfly-feature-pack ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message:
org.wildfly:wildfly-feature-pack:pom:10.0.0.Final
dom4j:dom4j:jar:1.6.1:compile has transitive dependencies:
jaxme:jaxme-api:jar:0.3:compile
msv:xsdlib:jar:20030807:compile
msv:relaxngDatatype:jar:20030807:compile
pull-parser:pull-parser:jar:2:compile
xpp3:xpp3:jar:1.1.3.3:compile
> Build Fails with maven 3.3.9 Oracle JDK 8
> ------------------------------------------
>
> Key: WFLY-6352
> URL: https://issues.jboss.org/browse/WFLY-6352
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Affects Versions: 10.0.0.Final
> Environment:
> Reporter: Eric Lemesre
> Assignee: Paul Gier
>
> When trying to build 10.0.0.Final with Maven 3.3.9 I get the following error from maven-enforcer plugin (at wildfly-feature-pack module).
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
> Apache Maven 3.3.9
> Maven home: /usr/share/maven
> Java version: 1.8.0_72, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/jdk-8-oracle-x64/jre
> Default locale: fr_FR, platform encoding: UTF-8
> OS name: "linux", version: "4.2.0-1-amd64", arch: "amd64", family: "unix"
> ```
> $ mvn clean install -PRelease
> ....
> [INFO] ------------------------------------------------------------------------
> [INFO] Building WildFly: Full Feature Pack 10.0.0.Final
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ wildfly-feature-pack ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4:enforce (ban-bad-dependencies) @ wildfly-feature-pack ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-java-version) @ wildfly-feature-pack ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-maven-version) @ wildfly-feature-pack ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4:enforce (ban-transitive-deps) @ wildfly-feature-pack ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message:
> org.wildfly:wildfly-feature-pack:pom:10.0.0.Final
> dom4j:dom4j:jar:1.6.1:compile has transitive dependencies:
> jaxme:jaxme-api:jar:0.3:compile
> msv:xsdlib:jar:20030807:compile
> msv:relaxngDatatype:jar:20030807:compile
> pull-parser:pull-parser:jar:2:compile
> xpp3:xpp3:jar:1.1.3.3:compile
> ```
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month