January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6092) Upgrade Narayana to 5.2.13.Final

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-6092?page=com.atlassian.jira.plugin.... ] Tom Jenkinson edited comment on WFLY-6092 at 1/29/16 9:19 AM: -------------------------------------------------------------- Step 3: http://albany.eng.hst.ams2.redhat.com/job/release-btny-narayana-quickstar... was (Author: tomjenkinson): Step 3: http://albany.eng.hst.ams2.redhat.com/job/release-btny-narayana-quickstar... > Upgrade Narayana to 5.2.13.Final > -------------------------------- > > Key: WFLY-6092 > URL: https://issues.jboss.org/browse/WFLY-6092 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > https://issues.jboss.org/browse/JBTM/fixforversion/12329358/?selectedTab=... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6092) Upgrade Narayana to 5.2.13.Final

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-6092?page=com.atlassian.jira.plugin.... ] Tom Jenkinson edited comment on WFLY-6092 at 1/29/16 9:13 AM: -------------------------------------------------------------- Step 3: http://albany.eng.hst.ams2.redhat.com/job/release-btny-narayana-quickstar... was (Author: tomjenkinson): Step 3: http://albany.eng.hst.ams2.redhat.com/job/release-btny-narayana-quickstar... > Upgrade Narayana to 5.2.13.Final > -------------------------------- > > Key: WFLY-6092 > URL: https://issues.jboss.org/browse/WFLY-6092 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > https://issues.jboss.org/browse/JBTM/fixforversion/12329358/?selectedTab=... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6090) Problems with passivation listener ordering cause CoarseSessionPassivationTestCase to fail intermittently with Undertow 1.3.16.Final

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-6090?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-6090: ------------------------------------ Actually - it's not the ordering of the events that is wrong (locking of the session ensures that events are not triggered out of order), but rather the assumptions made by the test that are no longer true. Effectively, the test should not assume that the sessionWillPassivate event was fired until the subsequent request. The test should also be changed to validate event order, e.g. that the subsequent request saw a sessionWillPassivate followed by a sessionDidActivate event. > Problems with passivation listener ordering cause CoarseSessionPassivationTestCase to fail intermittently with Undertow 1.3.16.Final > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-6090 > URL: https://issues.jboss.org/browse/WFLY-6090 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Stuart Douglas > Assignee: Paul Ferraro > > The upgrade to Undertow 1.3.16.Final causes this test to fail frequently (but not every time). > The change that makes this more frequent was the change to send the response before closing the session. If you are having trouble reproducing this you can add the following code to the bottom of the SessionOperationServlet doGet method to make it 100% reproducible (this should work with any version of Undertow): > {code} > resp.getOutputStream().close(); > try { > Thread.sleep(100); > } catch (InterruptedException e) { > throw new RuntimeException(e); > } > {code} > The underlying problem here is the way the passivation/activation listeners are called. > Previously if you did not close the response in the Servlet the session would be closed before the response would be sent, which guaranteed that prePassivate would be called. This also had the side effect that the test would only ever require a single request to see the first session passivating. > This is no longer the case, which means the following: > - Sometimes session1 has not had its passivation listener called before the session2 request is made > - The second session2 request can result in a call to sessionActivated (which makes the test fail). This is especially bogus as there is a chance session2 has not had sessionWillPassivate called yet. > The underlying cause of all this is the way listeners are handled in InfinispanSessionManager when persistent is true. Basically: > - Requests can cause a session to activate before the passivation listener has been called, resulting in out of order invocations > - Multiple concurrent requests to a session will result in multiple activation callbacks, followed by multiple passivation callbacks. > Basically at the moment the ordering these events is completely broken. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2009) TCP/TCP_NIO: make SO_REUSEADDR configurable

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2009?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2009. ---------------------------- Resolution: Done > TCP/TCP_NIO: make SO_REUSEADDR configurable > ------------------------------------------- > > Key: JGRP-2009 > URL: https://issues.jboss.org/browse/JGRP-2009 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.6.8, 4.0 > > > Before binding a {{ServerSocket}} or {{ServerSocketChannel}}, let the user configure whether of not to reuse addresses by setting option {{SO_REUSEADDR}} (and possibly {{SO_REUSEPORT}}?). > See https://issues.jboss.org/browse/ISPN-6099 for details -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2009) TCP/TCP_NIO: make SO_REUSEADDR configurable

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2009?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-2009 at 1/29/16 9:06 AM: --------------------------------------------------------- * Added a new attribute {{reuse_addr}} to {{TCP}} and {{TCP_NIO}}. The default is {{false}}, which is different from the previous default. * * Fixed on master * Fixed on 3.6 branch (3.6.8-SNAPSHOT) was (Author: belaban): * Fixed on master * Fixed on 3.6 branch (3.6.8-SNAPSHOT) > TCP/TCP_NIO: make SO_REUSEADDR configurable > ------------------------------------------- > > Key: JGRP-2009 > URL: https://issues.jboss.org/browse/JGRP-2009 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.6.8, 4.0 > > > Before binding a {{ServerSocket}} or {{ServerSocketChannel}}, let the user configure whether of not to reuse addresses by setting option {{SO_REUSEADDR}} (and possibly {{SO_REUSEPORT}}?). > See https://issues.jboss.org/browse/ISPN-6099 for details -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5519) Some clustering tests fail with security manager

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5519?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5519: --------------------------------- Priority: Major (was: Minor) > Some clustering tests fail with security manager > ------------------------------------------------ > > Key: WFLY-5519 > URL: https://issues.jboss.org/browse/WFLY-5519 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 10.0.0.CR2 > Reporter: Marek Kopecký > Assignee: Radoslav Husar > Attachments: clustering.secman.zip > > > *Description of problem:* > Some clustering tests fails with security manager. Affected testcases: > {noformat}org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover > org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover > org.jboss.as.test.clustering.cluster.dispatcher.CommandDispatcherTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).failoverOnStop > org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).nestedBeanFailover > org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).connectionFactoryFailover > org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).jmsConnectionFactoryFailover > org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).noFailover > org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).simpleFailover > org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulTimeoutTestCase(SYNC-tcp).timeout > org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testBasicXPC > org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testSecondLevelCache > org.jboss.as.test.clustering.cluster.provider.ServiceProviderRegistrationTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.registry.RegistryTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.singleton.SingletonServiceTestCase(SYNC-tcp).testSingletonService > org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase(SYNC-tcp).testFormAuthSingleSignOn > org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testSerialized > org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testSessionReplication > org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testGracefulServeOnUndeploy > org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testGracefulServeOnShutdown > org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.web.ReplicationForNegotiationAuthenticatorTestCase(SYNC-tcp).testOneRequestSimpleFailover > org.jboss.as.test.clustering.cluster.web.async.AsyncServletTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.web.context.InvalidateConversationTestCase(SYNC-tcp).testInvalidate > org.jboss.as.test.clustering.cluster.web.expiration.CoarseSessionExpirationTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.web.expiration.FineSessionExpirationTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.web.passivation.CoarseSessionPassivationTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.web.passivation.FineSessionPassivationTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.web.shared.SharedSessionFailoverTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.single.registry.RegistryTestCase.org.jboss.as.test.clustering.single.registry.RegistryTestCase > org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase.org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase{noformat} > *How reproducible:* > Always > *Steps to Reproduce:* > # ./integration-tests.sh -Dmaven.repo.local=$MAVEN_REPO_LOCAL -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -Dmcast=$MCAST_ADDR -Djboss.dist=$JBOSS_DIST -Dsecurity.manager -Dts.clustering -Dts.noSmoke > *Actual results:* > See attached logs > *Expected results:* > No errors -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2009) TCP/TCP_NIO: make SO_REUSEADDR configurable

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2009?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2009: -------------------------------- * Fixed on master * Fixed on 3.6 branch (3.6.8-SNAPSHOT) > TCP/TCP_NIO: make SO_REUSEADDR configurable > ------------------------------------------- > > Key: JGRP-2009 > URL: https://issues.jboss.org/browse/JGRP-2009 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.6.8, 4.0 > > > Before binding a {{ServerSocket}} or {{ServerSocketChannel}}, let the user configure whether of not to reuse addresses by setting option {{SO_REUSEADDR}} (and possibly {{SO_REUSEPORT}}?). > See https://issues.jboss.org/browse/ISPN-6099 for details -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4786) Clustering integration tests fails once -Dnode0 and -Dnode1 are used

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4786?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-4786: ------------------------------------ Assignee: Romain Pelisse (was: Radoslav Husar) Romain, want to look into this as we talked over in Berlin? It needs a bit of careful investigation. > Clustering integration tests fails once -Dnode0 and -Dnode1 are used > -------------------------------------------------------------------- > > Key: WFLY-4786 > URL: https://issues.jboss.org/browse/WFLY-4786 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 10.0.0.Alpha3 > Reporter: Petr Kremensky > Assignee: Romain Pelisse > Priority: Minor > Attachments: maven.logs, results.zip, testsuite.clustering.logs.zip > > > Tests from wildfly-ts-integ-clustering module fails once we change default binding interfaces by -Dnode0 and -Dnode1 properties. > See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-as-testsuite-... > * build 5 binds to localhost (no -Dnode*) > * build 6 uses -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 > Similar failures were addressed for EAP 6 by https://bugzilla.redhat.com/show_bug.cgi?id=1076015 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5519) Some clustering tests fail with security manager

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5519?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5519: --------------------------------- Priority: Minor (was: Major) > Some clustering tests fail with security manager > ------------------------------------------------ > > Key: WFLY-5519 > URL: https://issues.jboss.org/browse/WFLY-5519 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 10.0.0.CR2 > Reporter: Marek Kopecký > Assignee: Radoslav Husar > Priority: Minor > Attachments: clustering.secman.zip > > > *Description of problem:* > Some clustering tests fails with security manager. Affected testcases: > {noformat}org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover > org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover > org.jboss.as.test.clustering.cluster.dispatcher.CommandDispatcherTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).failoverOnStop > org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).nestedBeanFailover > org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).connectionFactoryFailover > org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).jmsConnectionFactoryFailover > org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).noFailover > org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).simpleFailover > org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulTimeoutTestCase(SYNC-tcp).timeout > org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testBasicXPC > org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testSecondLevelCache > org.jboss.as.test.clustering.cluster.provider.ServiceProviderRegistrationTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.registry.RegistryTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.singleton.SingletonServiceTestCase(SYNC-tcp).testSingletonService > org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase(SYNC-tcp).testFormAuthSingleSignOn > org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testSerialized > org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testSessionReplication > org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testGracefulServeOnUndeploy > org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testGracefulServeOnShutdown > org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.web.ReplicationForNegotiationAuthenticatorTestCase(SYNC-tcp).testOneRequestSimpleFailover > org.jboss.as.test.clustering.cluster.web.async.AsyncServletTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.web.context.InvalidateConversationTestCase(SYNC-tcp).testInvalidate > org.jboss.as.test.clustering.cluster.web.expiration.CoarseSessionExpirationTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.web.expiration.FineSessionExpirationTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.web.passivation.CoarseSessionPassivationTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.web.passivation.FineSessionPassivationTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.cluster.web.shared.SharedSessionFailoverTestCase(SYNC-tcp).test > org.jboss.as.test.clustering.single.registry.RegistryTestCase.org.jboss.as.test.clustering.single.registry.RegistryTestCase > org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase.org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase{noformat} > *How reproducible:* > Always > *Steps to Reproduce:* > # ./integration-tests.sh -Dmaven.repo.local=$MAVEN_REPO_LOCAL -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -Dmcast=$MCAST_ADDR -Djboss.dist=$JBOSS_DIST -Dsecurity.manager -Dts.clustering -Dts.noSmoke > *Actual results:* > See attached logs > *Expected results:* > No errors -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6092) Upgrade Narayana to 5.2.13.Final

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-6092?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-6092: ------------------------------------- Step 3: http://albany.eng.hst.ams2.redhat.com/job/release-btny-narayana-quickstar... > Upgrade Narayana to 5.2.13.Final > -------------------------------- > > Key: WFLY-6092 > URL: https://issues.jboss.org/browse/WFLY-6092 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > https://issues.jboss.org/browse/JBTM/fixforversion/12329358/?selectedTab=... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2016