January 2016 - jboss-jira - Jboss List Archives

[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)

8 years, 11 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)

8 years, 11 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)

8 years, 11 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)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5640) RemoteStatelessFailoverTestCase fails with "No EJB receiver available for handling"

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5640?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5640: --------------------------------- Summary: RemoteStatelessFailoverTestCase fails with "No EJB receiver available for handling" (was: No EJB receiver available for handling) > RemoteStatelessFailoverTestCase fails with "No EJB receiver available for handling" > ----------------------------------------------------------------------------------- > > Key: WFLY-5640 > URL: https://issues.jboss.org/browse/WFLY-5640 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB, Test Suite > Affects Versions: 10.0.0.CR4 > Environment: hp-ux 11v3 - hpjdk1.8 > solaris 10,11 - x86 and x86_64, rhel 6 - x86 and x86_64, rhel 7 x86_64 - openjdk1.8, ibmjdk1.8, oraclejdk1.8 > Reporter: Ivan Straka > Assignee: Richard Achmatowicz > Fix For: 10.0.0.CR5 > > Attachments: logs > > > There are two tests failing in exteded tests in clusteringejb2 package in AS TS. > org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase(SYNC-tcp-extended)#testLoadbalanceSpecifiedByDescriptor > org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase(SYNC-tcp-extended)#testLoadbalanceAnnotatedBean > both with exception > {code} > Error Message > EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:stateless-ejb2-failover-test, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@54acff7d > Stacktrace > java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:stateless-ejb2-failover-test, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@54acff7d > at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798) > at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:112) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146) > at com.sun.proxy.$Proxy28.create(Unknown Source) > at org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase.loadbalance(RemoteStatelessFailoverTestCase.java:262) > at org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase.testLoadbalanceAnnotatedBean(RemoteStatelessFailoverTestCase.java:224) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6093) /console/App.html#standalone-runtime/ds-metrics is not bookmarkable; forwards to /console/App.html#home

by The Alchemist (JIRA)

The Alchemist created WFLY-6093: ----------------------------------- Summary: /console/App.html#standalone-runtime/ds-metrics is not bookmarkable; forwards to /console/App.html#home Key: WFLY-6093 URL: https://issues.jboss.org/browse/WFLY-6093 Project: WildFly Issue Type: Feature Request Components: Web Console Reporter: The Alchemist Assignee: Heiko Braun Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6083) Removing of non-existent login-module finishes with outcome success

by Dmitrii Tikhomirov (JIRA)

[ https://issues.jboss.org/browse/WFLY-6083?page=com.atlassian.jira.plugin.... ] Dmitrii Tikhomirov reassigned WFLY-6083: ---------------------------------------- Assignee: Dmitrii Tikhomirov (was: Alexey Loubyansky) > Removing of non-existent login-module finishes with outcome success > ------------------------------------------------------------------- > > Key: WFLY-6083 > URL: https://issues.jboss.org/browse/WFLY-6083 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: Ondrej Lukas > Assignee: Dmitrii Tikhomirov > Priority: Minor > > In case when non-existent login-module is removed through Management CLI, opertation should finish with failure. However it finishes with outcome success and nothing is changed. It can be confusing since wrong command seems same as correct command. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1045) kie-ci 6.3.0.Final conflicts with newer versions of Guava

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1045?page=com.atlassian.jira.plugi... ] Petr Široký resolved DROOLS-1045. --------------------------------- Fix Version/s: 6.4.0.Beta1 Resolution: Done The issues was fixed as part of upgrade of Maven from 3.2.2 to 3.2.5 (done after 6.3.0.Final). [~abaxter] would you be able to test with 6.4.0.Beta1/6.4.0-SNAPSHOT just to make sure your use case works? Thanks! > kie-ci 6.3.0.Final conflicts with newer versions of Guava > --------------------------------------------------------- > > Key: DROOLS-1045 > URL: https://issues.jboss.org/browse/DROOLS-1045 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Adam Baxter > Assignee: Petr Široký > Fix For: 6.4.0.Beta1 > > > When using kie-ci with Google's Guava library (v19), we hit the following error: http://stackoverflow.com/questions/32528042/maven-java-lang-illegalaccess... > We solved this by excluding kie-ci's sisu-guice transitive dependency and including the 3.1.7 version released in 2014. > Please update kie-ci's dependencies such that this is no longer an issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 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: ------------------------------------- Following: https://developer.jboss.org/wiki/NarayanaReleaseProcess push upstream step 2 complete > 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)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-963) Guava Version too old required by KIE-CI

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-963?page=com.atlassian.jira.plugin... ] Petr Široký resolved DROOLS-963. -------------------------------- Fix Version/s: 6.4.0.CR1 Assignee: Petr Široký (was: Mario Fusco) Resolution: Done This will be fixed in 6.4.0.Final. It got resolved as part of Maven upgrade from 3.2.2 to 3.2.5. > Guava Version too old required by KIE-CI > ---------------------------------------- > > Key: DROOLS-963 > URL: https://issues.jboss.org/browse/DROOLS-963 > Project: Drools > Issue Type: Enhancement > Affects Versions: 6.3.0.Final > Reporter: Mauricio Salatino > Assignee: Petr Široký > Fix For: 6.4.0.CR1 > > > This might not be fixable, but testing drools (6.3.0.Final) with Arquillian and KIE-CI I found that KIE-CI is using a very very old version of Guava (version 10.x). In order to get it working with Arquillian and Weld I needed to go to middle ground between Weld requirement (version 18) and KIE-CI to get it working. I ended up adding Guava 14 as a direct dependency and that gets the project working. > I link the pom.xml file that I've used with all the versions: https://github.com/Salaboy/drools-workshop/blob/master/drools-kie-ci-exam... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2016