[JBoss JIRA] (WFLY-5511) DomainDeploymentOverlayTestCase fails on pure IPv6 if proxy is used
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFLY-5511?page=com.atlassian.jira.plugin.... ]
ehsavoie Hugonnet commented on WFLY-5511:
-----------------------------------------
Removing the zone part from the address when creating the URL "fixes" the test. This looks like some misconfiguration issue.
> DomainDeploymentOverlayTestCase fails on pure IPv6 if proxy is used
> -------------------------------------------------------------------
>
> Key: WFLY-5511
> URL: https://issues.jboss.org/browse/WFLY-5511
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.0.CR2
> Reporter: Marek Kopecký
> Assignee: Alexey Loubyansky
>
> *Description of problem:*
> DomainDeploymentOverlayTestCase fails on pure IPv6 machine with {{Unable to determine IP address from host name "2620:52:0:105f::ffff:8%eth0"}}
> *How reproducible:*
> Always on pure IPv6 machine if proxy is used
> *Steps to Reproduce:*
> # export PROXY_PARAMS="-DproxySet=true -DproxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -DproxyPort=3128 -Dhttp.proxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -Dhttp.proxyPort=3128 -Dhttps.proxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -Dhttps.proxyPort=3128"
> # ./integration-tests.sh -Dmaven.repo.local=$MAVEN_REPO_LOCAL -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIPV6_1 -Dnode1=$MYTESTIPV6_2 -Dmcast=$MCAST_ADDRV6 -Dipv6 -Djboss.dist=$JBOSS_DIST -Dtest=DomainDeploymentOverlayTestCase -Dts.domain -DfailIfNoTests=false $PROXY_PARAMS
> *Actual results:*
> MYTESTIPV6_1=2620:52:0:105f::ffff:8
> {noformat}
> The following error was encountered while trying to retrieve the URL: http://2620:52:0:105f::ffff:8%eth0:8080/deployment0/SimpleServlet?
> Unable to determine IP address from host name "2620:52:0:105f::ffff:8%eth0"
> The DNS server returned:
> Name Error: The domain name does not exist.
> This means that the cache was not able to resolve the hostname presented in the URL. Check if the address is correct.
> Your cache administrator is sysadmin-engops-jbossqe(a)redhat.com.
> {noformat}
> *Expected results:*
> No error
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JGRP-1620) RpcDispatcher/MessageDispatcher changes
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1620?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1620:
---------------------------
Description:
* In MessageDispatcher.castMessageXXX() and send(), we pass a Message as argument. Change this to only ship the byte[] buffer and options.
** This prevents a unicast RPC from having a message with a null dest, or a multicast RPC having a message with a non-null dest (JGRP-1617).
* Return null from castMessage() if the call is async, instead of a null {{RspList}}
* Investigate whether non-blocking RPCs need to create Request instances at all
* Return a {{CompletableFuture}} instead of a {{NotifyingFuture}}
* Remove {{NotifyingFuture}} and {{FutureListener}}: requires changing {{ExecutionService}}
** Perhaps: https://github.com/wburns/infinispan/blob/ISPN-6074/core/src/main/java/or...
was:
* In MessageDispatcher.castMessageXXX() and send(), we pass a Message as argument. Change this to only ship the byte[] buffer and options.
** This prevents a unicast RPC from having a message with a null dest, or a multicast RPC having a message with a non-null dest (JGRP-1617).
* Return null from castMessage() if the call is async, instead of a null {{RspList}}
* Investigate whether non-blocking RPCs need to create Request instances at all
* Return a {{CompletableFuture}} instead of a {{NotifyingFuture}}
* Remove {{NotifyingFuture}} and {{FutureListener}}: requires changing {{ExecutionService}}
> RpcDispatcher/MessageDispatcher changes
> ---------------------------------------
>
> Key: JGRP-1620
> URL: https://issues.jboss.org/browse/JGRP-1620
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.0
>
>
> * In MessageDispatcher.castMessageXXX() and send(), we pass a Message as argument. Change this to only ship the byte[] buffer and options.
> ** This prevents a unicast RPC from having a message with a null dest, or a multicast RPC having a message with a non-null dest (JGRP-1617).
> * Return null from castMessage() if the call is async, instead of a null {{RspList}}
> * Investigate whether non-blocking RPCs need to create Request instances at all
> * Return a {{CompletableFuture}} instead of a {{NotifyingFuture}}
> * Remove {{NotifyingFuture}} and {{FutureListener}}: requires changing {{ExecutionService}}
> ** Perhaps: https://github.com/wburns/infinispan/blob/ISPN-6074/core/src/main/java/or...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6180) X: failed submitting DONT_BUNDLE message to thread pool: java.util.concurrent.RejectedExecutionException: Task org.jgroups.protocols.TP$SingleMessageHandler@Y rejected from java.util.concurrent.ThreadPoolExecutor@Z
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-6180:
------------------------------------
Summary: X: failed submitting DONT_BUNDLE message to thread pool: java.util.concurrent.RejectedExecutionException: Task org.jgroups.protocols.TP$SingleMessageHandler@Y rejected from java.util.concurrent.ThreadPoolExecutor@Z
Key: WFLY-6180
URL: https://issues.jboss.org/browse/WFLY-6180
Project: WildFly
Issue Type: Bug
Components: Clustering
Reporter: Radoslav Husar
Assignee: Radoslav Husar
[JBossINF] [0m[31m00:03:59,091 ERROR [org.jgroups.protocols.UDP] (unicast receiver,ee,perf20) perf20: failed submitting DONT_BUNDLE message to thread pool: java.util.concurrent.RejectedExecutionException: Task org.jgroups.protocols.TP$SingleMessageHandler@cf4fccc rejected from java.util.concurrent.ThreadPoolExecutor@122a91ad[Running, pool size = 300, active threads = 3, queued tasks = 0, completed tasks = 57909800]. Msg: RequestCorrelator: id=200, type=REQ, id=39088476, rsp_expected=true, FORK: ee:web, UNICAST3: DATA, seqno=21476211, conn_id=2, UDP: [cluster_name=ee]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6179) X: failed submitting DONT_BUNDLE message to thread pool: java.util.concurrent.RejectedExecutionException: Task org.jgroups.protocols.TP$SingleMessageHandler@Y rejected from java.util.concurrent.ThreadPoolExecutor@Z
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6179?page=com.atlassian.jira.plugin.... ]
Radoslav Husar reassigned WFLY-6179:
------------------------------------
Assignee: Radoslav Husar (was: Jason Greene)
> X: failed submitting DONT_BUNDLE message to thread pool: java.util.concurrent.RejectedExecutionException: Task org.jgroups.protocols.TP$SingleMessageHandler@Y rejected from java.util.concurrent.ThreadPoolExecutor@Z
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6179
> URL: https://issues.jboss.org/browse/WFLY-6179
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> [JBossINF] [0m[31m00:03:59,091 ERROR [org.jgroups.protocols.UDP] (unicast receiver,ee,perf20) perf20: failed submitting DONT_BUNDLE message to thread pool: java.util.concurrent.RejectedExecutionException: Task org.jgroups.protocols.TP$SingleMessageHandler@cf4fccc rejected from java.util.concurrent.ThreadPoolExecutor@122a91ad[Running, pool size = 300, active threads = 3, queued tasks = 0, completed tasks = 57909800]. Msg: RequestCorrelator: id=200, type=REQ, id=39088476, rsp_expected=true, FORK: ee:web, UNICAST3: DATA, seqno=21476211, conn_id=2, UDP: [cluster_name=ee]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JGRP-1620) RpcDispatcher/MessageDispatcher changes
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1620?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1620:
---------------------------
Description:
* In MessageDispatcher.castMessageXXX() and send(), we pass a Message as argument. Change this to only ship the byte[] buffer and options.
** This prevents a unicast RPC from having a message with a null dest, or a multicast RPC having a message with a non-null dest (JGRP-1617).
* Return null from castMessage() if the call is async, instead of a null {{RspList}}
* Investigate whether non-blocking RPCs need to create Request instances at all
* Return a {{CompletableFuture}} instead of a {{NotifyingFuture}}
* Remove {{NotifyingFuture}} and {{FutureListener}}: requires changing {{ExecutionService}}
was:
* In MessageDispatcher.castMessageXXX() and send(), we pass a Message as argument. Change this to only ship the byte[] buffer and options.
** This prevents a unicast RPC from having a message with a null dest, or a multicast RPC having a message with a non-null dest (JGRP-1617).
* Return null from castMessage() if the call is async, instead of a null {{RspList}}
* Investigate whether non-blocking RPCs need to create Request instances at all
* Return a {{CompletableFuture}} instead of a {{NotifyingFuture}}
> RpcDispatcher/MessageDispatcher changes
> ---------------------------------------
>
> Key: JGRP-1620
> URL: https://issues.jboss.org/browse/JGRP-1620
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.0
>
>
> * In MessageDispatcher.castMessageXXX() and send(), we pass a Message as argument. Change this to only ship the byte[] buffer and options.
> ** This prevents a unicast RPC from having a message with a null dest, or a multicast RPC having a message with a non-null dest (JGRP-1617).
> * Return null from castMessage() if the call is async, instead of a null {{RspList}}
> * Investigate whether non-blocking RPCs need to create Request instances at all
> * Return a {{CompletableFuture}} instead of a {{NotifyingFuture}}
> * Remove {{NotifyingFuture}} and {{FutureListener}}: requires changing {{ExecutionService}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6152) EJB timer scheduler log an Exception for an already canceled timer
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-6152?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-6152:
-----------------------------------------------
Brad Maxwell <bmaxwell(a)redhat.com> changed the Status of [bug 1305960|https://bugzilla.redhat.com/show_bug.cgi?id=1305960] from MODIFIED to POST
> EJB timer scheduler log an Exception for an already canceled timer
> ------------------------------------------------------------------
>
> Key: WFLY-6152
> URL: https://issues.jboss.org/browse/WFLY-6152
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.0.0.Final
> Reporter: Wolf-Dieter Fink
> Assignee: Wolf-Dieter Fink
> Priority: Minor
> Labels: timer, timers, timerservice
>
> If a timer is canceled inside of the @timeout method the scheduler will log an ERROR if the timer duration is longer than the intervall and an overlapping execution should be fired.
> This is due to internal validatons.
> This will not happen if the timer is canceled by an external process, here the scheduler is removed.
> The log message is like this:
> ERROR [org.jboss.as.ejb3] (EJB default - 3) WFLYEJB0164: Exception running timer task for timer [id=0bd9870b-568b-42f5-9bda-e1525c3500aa timedObjectId=ejb30-timer.ejb30-timer.SimpleTimerBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@53ba1a7f initialExpiration=Tue Feb 09 17:19:32 CET 2016 intervalDuration(in milli sec)=5000 nextExpiration=Tue Feb 09 17:19:37 CET 2016 timerState=CANCELED info=SimpleTimerInfo description=A timer started every 5 seconds] on EJB ejb30-timer.ejb30-timer.SimpleTimerBean: javax.ejb.NoSuchObjectLocalException: WFLYEJB0331: Timer was canceled
> at org.jboss.as.ejb3.timerservice.TimerImpl.assertTimerState(TimerImpl.java:459)
> at org.jboss.as.ejb3.timerservice.TimerImpl.isPersistent(TimerImpl.java:215)
> at org.jboss.as.ejb3.timerservice.TimerServiceImpl.shouldRun(TimerServiceImpl.java:1117)
> at org.jboss.as.ejb3.timerservice.TimerTask.run(TimerTask.java:124)
> at org.jboss.as.ejb3.timerservice.TimerServiceImpl$Task$1.run(TimerServiceImpl.java:1221)
> at org.wildfly.extension.requestcontroller.RequestController$QueuedTask$1.run(RequestController.java:497)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-5511) DomainDeploymentOverlayTestCase fails on pure IPv6 if proxy is used
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5511?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-5511:
-----------------------------------
Are we 101% sure that proxy server works fine with ipv6?
> DomainDeploymentOverlayTestCase fails on pure IPv6 if proxy is used
> -------------------------------------------------------------------
>
> Key: WFLY-5511
> URL: https://issues.jboss.org/browse/WFLY-5511
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.0.CR2
> Reporter: Marek Kopecký
> Assignee: Alexey Loubyansky
>
> *Description of problem:*
> DomainDeploymentOverlayTestCase fails on pure IPv6 machine with {{Unable to determine IP address from host name "2620:52:0:105f::ffff:8%eth0"}}
> *How reproducible:*
> Always on pure IPv6 machine if proxy is used
> *Steps to Reproduce:*
> # export PROXY_PARAMS="-DproxySet=true -DproxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -DproxyPort=3128 -Dhttp.proxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -Dhttp.proxyPort=3128 -Dhttps.proxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -Dhttps.proxyPort=3128"
> # ./integration-tests.sh -Dmaven.repo.local=$MAVEN_REPO_LOCAL -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIPV6_1 -Dnode1=$MYTESTIPV6_2 -Dmcast=$MCAST_ADDRV6 -Dipv6 -Djboss.dist=$JBOSS_DIST -Dtest=DomainDeploymentOverlayTestCase -Dts.domain -DfailIfNoTests=false $PROXY_PARAMS
> *Actual results:*
> MYTESTIPV6_1=2620:52:0:105f::ffff:8
> {noformat}
> The following error was encountered while trying to retrieve the URL: http://2620:52:0:105f::ffff:8%eth0:8080/deployment0/SimpleServlet?
> Unable to determine IP address from host name "2620:52:0:105f::ffff:8%eth0"
> The DNS server returned:
> Name Error: The domain name does not exist.
> This means that the cache was not able to resolve the hostname presented in the URL. Check if the address is correct.
> Your cache administrator is sysadmin-engops-jbossqe(a)redhat.com.
> {noformat}
> *Expected results:*
> No error
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6179) X: failed submitting DONT_BUNDLE message to thread pool: java.util.concurrent.RejectedExecutionException: Task org.jgroups.protocols.TP$SingleMessageHandler@Y rejected from java.util.concurrent.ThreadPoolExecutor@Z
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6179?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-6179:
------------------------------
Component/s: Clustering
> X: failed submitting DONT_BUNDLE message to thread pool: java.util.concurrent.RejectedExecutionException: Task org.jgroups.protocols.TP$SingleMessageHandler@Y rejected from java.util.concurrent.ThreadPoolExecutor@Z
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6179
> URL: https://issues.jboss.org/browse/WFLY-6179
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Radoslav Husar
> Assignee: Jason Greene
>
> [JBossINF] [0m[31m00:03:59,091 ERROR [org.jgroups.protocols.UDP] (unicast receiver,ee,perf20) perf20: failed submitting DONT_BUNDLE message to thread pool: java.util.concurrent.RejectedExecutionException: Task org.jgroups.protocols.TP$SingleMessageHandler@cf4fccc rejected from java.util.concurrent.ThreadPoolExecutor@122a91ad[Running, pool size = 300, active threads = 3, queued tasks = 0, completed tasks = 57909800]. Msg: RequestCorrelator: id=200, type=REQ, id=39088476, rsp_expected=true, FORK: ee:web, UNICAST3: DATA, seqno=21476211, conn_id=2, UDP: [cluster_name=ee]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6179) X: failed submitting DONT_BUNDLE message to thread pool: java.util.concurrent.RejectedExecutionException: Task org.jgroups.protocols.TP$SingleMessageHandler@Y rejected from java.util.concurrent.ThreadPoolExecutor@Z
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-6179:
------------------------------------
Summary: X: failed submitting DONT_BUNDLE message to thread pool: java.util.concurrent.RejectedExecutionException: Task org.jgroups.protocols.TP$SingleMessageHandler@Y rejected from java.util.concurrent.ThreadPoolExecutor@Z
Key: WFLY-6179
URL: https://issues.jboss.org/browse/WFLY-6179
Project: WildFly
Issue Type: Bug
Reporter: Radoslav Husar
Assignee: Jason Greene
[JBossINF] [0m[31m00:03:59,091 ERROR [org.jgroups.protocols.UDP] (unicast receiver,ee,perf20) perf20: failed submitting DONT_BUNDLE message to thread pool: java.util.concurrent.RejectedExecutionException: Task org.jgroups.protocols.TP$SingleMessageHandler@cf4fccc rejected from java.util.concurrent.ThreadPoolExecutor@122a91ad[Running, pool size = 300, active threads = 3, queued tasks = 0, completed tasks = 57909800]. Msg: RequestCorrelator: id=200, type=REQ, id=39088476, rsp_expected=true, FORK: ee:web, UNICAST3: DATA, seqno=21476211, conn_id=2, UDP: [cluster_name=ee]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JASSIST-259) Concurrency issue in ProxyFactory
by Shigeru Chiba (JIRA)
[ https://issues.jboss.org/browse/JASSIST-259?page=com.atlassian.jira.plugi... ]
Shigeru Chiba resolved JASSIST-259.
-----------------------------------
Fix Version/s: 3.21.0-GA
Resolution: Done
> Concurrency issue in ProxyFactory
> ---------------------------------
>
> Key: JASSIST-259
> URL: https://issues.jboss.org/browse/JASSIST-259
> Project: Javassist
> Issue Type: Bug
> Affects Versions: 3.12.0.GA
> Environment: AIX, IBM J9 VM (build 2.8, JRE 1.8.0 AIX ppc64-64 Compressed References 20150722_258693 (JIT enabled, AOT enabled)
> Reporter: Christian Beikov
> Assignee: Shigeru Chiba
> Priority: Critical
> Fix For: 3.21.0-GA
>
>
> Look at the following line to understand the issue
> https://github.com/jboss-javassist/javassist/blob/master/src/main/javassi...
> If there are 2 threads T1 and T2 at this line, T1 pauses and T2 runs through, on some systems T1 may encounter thisClass to be null after it wakes up again.
> This leads to Hibernate getting a null class in JavassistProxyFactory and trying to create an instance of that which fails with a NPE.
> Can anyone please confirm this issue? Maybe there is something in the JMM that I am not aware of that makes this code safe, but as far as I can tell, this looks like a real bug that just happens to uncover itself on an environment like J9 on AIX.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months