[JBoss JIRA] (JGRP-2485) UDP is not working after upgarde to 3_6_19 from jgroups-3.4.0.Alpha2
by Janardhan Naidu (Jira)
[ https://issues.redhat.com/browse/JGRP-2485?page=com.atlassian.jira.plugin... ]
Janardhan Naidu commented on JGRP-2485:
---------------------------------------
Attached log file also.
Please let me know if information is needed
> UDP is not working after upgarde to 3_6_19 from jgroups-3.4.0.Alpha2
> --------------------------------------------------------------------
>
> Key: JGRP-2485
> URL: https://issues.redhat.com/browse/JGRP-2485
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.19
> Reporter: Janardhan Naidu
> Assignee: Bela Ban
> Priority: Major
> Attachments: noapp.log.D20200619.T053202_NODE1
>
>
> Hi Team,
>
> we just upgraded from jgroups-3.4.0.Alpha2 to 3_6_19. post the UDP cluster communication is not working.
> after upgrade, we were hitting some warning as below and we solved those by changing property_string of UDP.
> *Warnings:*
> *WARNING: JGRP000014: Discovery.timeout has been deprecated: GMS.join_timeout should be used instead*
> [2020-06-17 14:05:49.271] ALL 000000000000 GLOBAL_SCOPE Jun 17, 2020 2:05:49 PM org.jgroups.stack.Configurator resolveAndAssignField
> *WARNING: JGRP000014: Discovery.num_initial_members has been deprecated: will be ignored*
> [2020-06-17 14:05:49.396] ALL 000000000000 GLOBAL_SCOPE Jun 17, 2020 2:05:49 PM org.jgroups.protocols.pbcast.NAKACK init
> *WARNING: use_mcast_xmit should not be used because the transport (TCP) does not support IP multicasting; setting use_mcast_xmit to false*
>
> To solve above warnings, we went through tcp.xml which was shipped using in 3_6_19 jar:
> and now our properties looks like:
> *property_string=UDP*(bind_addr=*hostIP*;bind_port=39061;mcast_addr=239.255.166.17;mcast_port=39060;ip_ttl=32;mcast_send_buf_size=150000;mcast_recv_buf_size=80000):PING:MERGE2(min_interval=5000;max_interval=10000):FD_ALL(interval=5000;timeout=20000):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=true;retransmit_timeout=300,600,1200,2400,4800;discard_delivered_msgs=true):UNICAST:pbcast.STABLE(desired_avg_gossip=20000):FRAG(frag_size=8096):pbcast.GMS(join_timeout=5000;print_local_addr=true)
>
> *distribution_property_string=TCP*(bind_port=39060;thread_pool_rejection_policy=run):TCPPING(async_discovery=true;initial_hosts=*hostIP*[39060];port_range=0;):MERGE2(min_interval=3000;max_interval=5000):FD_SOCK:FD(timeout=5000;max_tries=48):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=false;discard_delivered_msgs=true;):pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;max_bytes=0):pbcast.GMS(join_timeout=5000;print_local_addr=true)
>
> *lock.protocolStack=UDP*(bind_addr=*hostIP*;bind_port=39062;mcast_addr=239.255.166.17;mcast_port=39069;ip_ttl=32;mcast_send_buf_size=150000;mcast_recv_buf_size=80000):PING:MERGE2(min_interval=5000;max_interval=10000):FD_ALL(interval=5000;timeout=20000):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=true;retransmit_timeout=300,600,1200,2400,4800):UNICAST:pbcast.STABLE(desired_avg_gossip=20000):FRAG(frag_size=8096):pbcast.GMS(join_timeout=5000;print_local_addr=true):CENTRAL_LOCK(num_backups=2)
>
>
> With above properties, we are not seeing any warning or error. But still cluster communication is not working with UDP.
> Please help me in resolving the same
>
> Thank
> Janardhan
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (JGRP-2485) UDP is not working after upgarde to 3_6_19 from jgroups-3.4.0.Alpha2
by Janardhan Naidu (Jira)
Janardhan Naidu created JGRP-2485:
-------------------------------------
Summary: UDP is not working after upgarde to 3_6_19 from jgroups-3.4.0.Alpha2
Key: JGRP-2485
URL: https://issues.redhat.com/browse/JGRP-2485
Project: JGroups
Issue Type: Bug
Affects Versions: 3.6.19
Reporter: Janardhan Naidu
Assignee: Bela Ban
Hi Team,
we just upgraded from jgroups-3.4.0.Alpha2 to 3_6_19. post the UDP cluster communication is not working.
after upgrade, we were hitting some warning as below and we solved those by changing property_string of UDP.
*Warnings:*
*WARNING: JGRP000014: Discovery.timeout has been deprecated: GMS.join_timeout should be used instead*
[2020-06-17 14:05:49.271] ALL 000000000000 GLOBAL_SCOPE Jun 17, 2020 2:05:49 PM org.jgroups.stack.Configurator resolveAndAssignField
*WARNING: JGRP000014: Discovery.num_initial_members has been deprecated: will be ignored*
[2020-06-17 14:05:49.396] ALL 000000000000 GLOBAL_SCOPE Jun 17, 2020 2:05:49 PM org.jgroups.protocols.pbcast.NAKACK init
*WARNING: use_mcast_xmit should not be used because the transport (TCP) does not support IP multicasting; setting use_mcast_xmit to false*
To solve above warnings, we went through tcp.xml which was shipped using in 3_6_19 jar:
and now our properties looks like:
*property_string=UDP*(bind_addr=*hostIP*;bind_port=39061;mcast_addr=239.255.166.17;mcast_port=39060;ip_ttl=32;mcast_send_buf_size=150000;mcast_recv_buf_size=80000):PING:MERGE2(min_interval=5000;max_interval=10000):FD_ALL(interval=5000;timeout=20000):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=true;retransmit_timeout=300,600,1200,2400,4800;discard_delivered_msgs=true):UNICAST:pbcast.STABLE(desired_avg_gossip=20000):FRAG(frag_size=8096):pbcast.GMS(join_timeout=5000;print_local_addr=true)
*distribution_property_string=TCP*(bind_port=39060;thread_pool_rejection_policy=run):TCPPING(async_discovery=true;initial_hosts=*hostIP*[39060];port_range=0;):MERGE2(min_interval=3000;max_interval=5000):FD_SOCK:FD(timeout=5000;max_tries=48):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=false;discard_delivered_msgs=true;):pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;max_bytes=0):pbcast.GMS(join_timeout=5000;print_local_addr=true)
*lock.protocolStack=UDP*(bind_addr=*hostIP*;bind_port=39062;mcast_addr=239.255.166.17;mcast_port=39069;ip_ttl=32;mcast_send_buf_size=150000;mcast_recv_buf_size=80000):PING:MERGE2(min_interval=5000;max_interval=10000):FD_ALL(interval=5000;timeout=20000):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=true;retransmit_timeout=300,600,1200,2400,4800):UNICAST:pbcast.STABLE(desired_avg_gossip=20000):FRAG(frag_size=8096):pbcast.GMS(join_timeout=5000;print_local_addr=true):CENTRAL_LOCK(num_backups=2)
With above properties, we are not seeing any warning or error. But still cluster communication is not working with UDP.
Please help me in resolving the same
Thank
Janardhan
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFLY-13603) Cache associated with default module throws NPE on start
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-13603:
-----------------------------------
Summary: Cache associated with default module throws NPE on start
Key: WFLY-13603
URL: https://issues.redhat.com/browse/WFLY-13603
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 20.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
{noformat}
2020-06-11 13:57:16,198 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 90) MSC000001: Failed to start service org.wildfly.clustering.infinispan.cache.security.MyApplicationRealm: org.jboss.msc.service.StartException in service org.wildfly.clustering.infinispan.cache.security.MyApplicationRealm: org.infinispan.commons.CacheConfigurationException: Failed to construct component org.infinispan.container.impl.InternalDataContainer, path org.infinispan.container.impl.InternalDataContainer
<< org.infinispan.stats.impl.StatsCollector
<< org.infinispan.AdvancedCache
at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:66)
at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:485)
Caused by: org.infinispan.commons.CacheConfigurationException: Failed to construct component org.infinispan.container.impl.InternalDataContainer, path org.infinispan.container.impl.InternalDataContainer
<< org.infinispan.stats.impl.StatsCollector
<< org.infinispan.AdvancedCache
at org.infinispan.factories.impl.BasicComponentRegistryImpl.doInstantiateWrapper(BasicComponentRegistryImpl.java:189)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.instantiateWrapper(BasicComponentRegistryImpl.java:176)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.getComponent0(BasicComponentRegistryImpl.java:141)
at org.infinispan.factories.impl.WireContext.get(WireContext.java:20)
at org.infinispan.stats.impl.CorePackageImpl$2.wire(CorePackageImpl.java:43)
at org.infinispan.stats.impl.CorePackageImpl$2.wire(CorePackageImpl.java:39)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.invokeInjection(BasicComponentRegistryImpl.java:334)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.doWireWrapper(BasicComponentRegistryImpl.java:231)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.wireWrapper(BasicComponentRegistryImpl.java:212)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.getComponent0(BasicComponentRegistryImpl.java:147)
at org.infinispan.factories.impl.WireContext.get(WireContext.java:20)
at org.infinispan.cache.impl.CorePackageImpl$3.wire(CorePackageImpl.java:75)
at org.infinispan.cache.impl.CorePackageImpl$3.wire(CorePackageImpl.java:73)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.invokeInjection(BasicComponentRegistryImpl.java:334)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.wireDependencies(BasicComponentRegistryImpl.java:242)
at org.infinispan.cache.impl.EncoderCache.wireRealCache(EncoderCache.java:125)
at org.infinispan.cache.impl.CorePackageImpl$4.wire(CorePackageImpl.java:94)
at org.infinispan.cache.impl.CorePackageImpl$4.wire(CorePackageImpl.java:90)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.invokeInjection(BasicComponentRegistryImpl.java:334)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.doWireWrapper(BasicComponentRegistryImpl.java:231)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.wireWrapper(BasicComponentRegistryImpl.java:212)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.registerComponent(BasicComponentRegistryImpl.java:371)
at org.infinispan.factories.impl.BasicComponentRegistry.registerComponent(BasicComponentRegistry.java:100)
at org.infinispan.factories.InternalCacheFactory.createSimpleCache(InternalCacheFactory.java:151)
at org.infinispan.factories.InternalCacheFactory.createCache(InternalCacheFactory.java:81)
at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:696)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:645)
at org.infinispan.manager.DefaultCacheManager.internalGetCache(DefaultCacheManager.java:530)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:511)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:504)
at org.jboss.as.clustering.infinispan.DefaultCacheContainer.getCache(DefaultCacheContainer.java:92)
at org.wildfly.clustering.infinispan.spi.service.CacheServiceConfigurator.get(CacheServiceConfigurator.java:77)
at org.wildfly.clustering.infinispan.spi.service.CacheServiceConfigurator.get(CacheServiceConfigurator.java:55)
at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:63)
... 7 more
Caused by: java.lang.NullPointerException
at org.wildfly.clustering.infinispan.spi.DataContainerFactory.createBoundedDataContainer(DataContainerFactory.java:113)
at org.wildfly.clustering.infinispan.spi.DataContainerFactory.construct(DataContainerFactory.java:72)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.doInstantiateWrapper(BasicComponentRegistryImpl.java:186)
... 40 more
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz edited comment on WFLY-13433 at 6/18/20 4:08 PM:
---------------------------------------------------------------------
Added more resources, changed the branch: [https://github.com/rachmatowicz/wildfly/tree/WFLY-13433]
Resources now completed:
{noformat}
ApplicationSecurityDomainDefinition
CacheFactoryResourceDefinition
PassivationStoreResourceDefinition
EJB3RemoteResourceDefinition
EJB3SubsystemRootResourceDefintion
IdentityResourceDefinition{noformat}
PassivationStoreResoureDefinition integrates with Capability classes from org.wildfly.clustering.controller.
was (Author: rachmato):
Added more resources, changes the branch: [https://github.com/rachmatowicz/wildfly/tree/WFLY-13433]
Resources now completed:
{noformat}
ApplicationSecurityDomainDefinition
CacheFactoryResourceDefinition
PassivationStoreResourceDefinition
EJB3RemoteResourceDefinition
EJB3SubsystemRootResourceDefintion
IdentityResourceDefinition{noformat}
PassivationStoreResoureDefinition integrates with Capability classes from org.wildfly.clustering.controller.
> Improve capability support in EJB3 subsystem
> --------------------------------------------
>
> Key: WFLY-13433
> URL: https://issues.redhat.com/browse/WFLY-13433
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Affects Versions: 20.0.0.Beta1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
>
> Survey all external subsystem dependencies and introduce capability based dependencies where required.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz edited comment on WFLY-13433 at 6/18/20 4:07 PM:
---------------------------------------------------------------------
Added more resources, changes the branch: [https://github.com/rachmatowicz/wildfly/tree/WFLY-13433]
Resources now completed:
{noformat}
ApplicationSecurityDomainDefinition
CacheFactoryResourceDefinition
PassivationStoreResourceDefinition
EJB3RemoteResourceDefinition
EJB3SubsystemRootResourceDefintion
IdentityResourceDefinition{noformat}
PassivationStoreResoureDefinition integrates with Capability classes from org.wildfly.clustering.controller.
was (Author: rachmato):
Added more resources, changes the branch: [https://github.com/rachmatowicz/wildfly/tree/WFLY-13433]
Resources now completed:
<noformat>
ApplicationSecurityDomainDefinition
CacheFactoryResourceDefinition
PassivationStoreResourceDefinition
EJB3RemoteResourceDefinition
EJB3SubsystemRootResourceDefintion
IdentityResourceDefinition
<noformat>
> Improve capability support in EJB3 subsystem
> --------------------------------------------
>
> Key: WFLY-13433
> URL: https://issues.redhat.com/browse/WFLY-13433
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Affects Versions: 20.0.0.Beta1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
>
> Survey all external subsystem dependencies and introduce capability based dependencies where required.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFCORE-5013) Remove the wildfly-openssl i386 bindings
by Farah Juma (Jira)
Farah Juma created WFCORE-5013:
----------------------------------
Summary: Remove the wildfly-openssl i386 bindings
Key: WFCORE-5013
URL: https://issues.redhat.com/browse/WFCORE-5013
Project: WildFly Core
Issue Type: Task
Components: Security
Reporter: Farah Juma
Assignee: Farah Juma
We should remove the wildfly-openssl-linux-i386 and the wildfly-openssl-windows-i386 bindings for WildFly Core 13.0.0.Final (i.e., WildFly 21 Final).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFLY-13601) JACC Not Correctly Activated Without Legacy Security
by Darran Lofthouse (Jira)
Darran Lofthouse created WFLY-13601:
---------------------------------------
Summary: JACC Not Correctly Activated Without Legacy Security
Key: WFLY-13601
URL: https://issues.redhat.com/browse/WFLY-13601
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 21.0.0.Beta1
The legacy security subsystem contains a deployment unit processor which establishes the JACC Policy for a deployment as it is deployed, once this subsystem is removed the policy is no longer established.
We need an equivalent within the WildFly Elytron subsystem, at the same time we need to avoid duplication. Ideally if one subsystem can detect the other it can skip installing it's own DUPs but failing that the DUP will need to check if the other is present. As we are looking at the required steps to remove legacy security by default we may want to consider the Elytron approach having a higher priority.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFLY-13598) Hard coded dependencies from resource adapters to legacy security sercvies.
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFLY-13598?page=com.atlassian.jira.plugi... ]
Darran Lofthouse reassigned WFLY-13598:
---------------------------------------
Assignee: (was: Darran Lofthouse)
> Hard coded dependencies from resource adapters to legacy security sercvies.
> ---------------------------------------------------------------------------
>
> Key: WFLY-13598
> URL: https://issues.redhat.com/browse/WFLY-13598
> Project: WildFly
> Issue Type: Enhancement
> Components: JCA, Security
> Affects Versions: 20.0.0.Final
> Reporter: Darran Lofthouse
> Priority: Major
> Labels: legacy_security_removal
>
> A resource adapter defined similar to:
>
> {code:xml}
> <resource-adapters>
> <resource-adapter id="myrar.rar">
> <archive>
> myrar.rar
> </archive>
> <connection-definitions>
> <connection-definition class-name="org.wildfly.test.MyRar" pool-name="connection-definition"/>
> </connection-definitions>
> </resource-adapter>
> </resource-adapters>
> {code}
> Leads to an error:
> {code}
> 13:48:11,932 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "resource-adapters"),
> ("resource-adapter" => "myrar.rar"),
> ("connection-definitions" => "connection-definition")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.security.subject-factory",
> "jboss.security.simple-security-manager"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.resourceadapters.ra.\"myrar.rar\".connection-definition is missing [jboss.security.simple-security-manager, jboss.security.subject-factory]"]
> }
> {code}
> Resources should not depend on legacy security by default as it may not be there.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months