July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12276) Create a sitemap for docs.wildfly.org

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12276?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-12276: --------------------------------- Attachment: sitemap.xml > Create a sitemap for docs.wildfly.org > ------------------------------------- > > Key: WFLY-12276 > URL: https://issues.jboss.org/browse/WFLY-12276 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: Brian Stansberry > Priority: Major > Attachments: sitemap.xml > > > I've seen that google reports pages from various versions of our docs as the 'canonical' version of the page.[1] This is understandable, as google has no way know what's 'canonical', e.g. that the 17 folder is more relevant than the 14 folder and in many cases the pages themselves are identical. But I presume this will mean docs searches are more likely to direct people to older docs versions. > Of the various ways to improve this, the one that seems *possibly* practical is to add a sitemap file[2]. There are way too many pages to cover them all, but perhaps covering the root page for the version plus the root page of the various documents (Admin Guide, Developer Guide, etc) will suffice to get crawlers to focus on those pages, and then the rest will be ranked appropriately based on crawling from those roots. Or not; I'm no SEO SME. ;) > Part of the PR for adding docs for a new release would then be to update the sitemap doc, e.g. to replace '17' in URLs with '18'. > [~jamezp] FYI. > [1] https://support.google.com/webmasters/answer/139066 > [2] https://support.google.com/webmasters/answer/183668?hl=en&ref_topic=4581190 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12276) Create a sitemap for docs.wildfly.org

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12276: --------------------------------------- Summary: Create a sitemap for docs.wildfly.org Key: WFLY-12276 URL: https://issues.jboss.org/browse/WFLY-12276 Project: WildFly Issue Type: Task Components: Documentation Reporter: Brian Stansberry I've seen that google reports pages from various versions of our docs as the 'canonical' version of the page.[1] This is understandable, as google has no way know what's 'canonical', e.g. that the 17 folder is more relevant than the 14 folder and in many cases the pages themselves are identical. But I presume this will mean docs searches are more likely to direct people to older docs versions. Of the various ways to improve this, the one that seems *possibly* practical is to add a sitemap file[2]. There are way too many pages to cover them all, but perhaps covering the root page for the version plus the root page of the various documents (Admin Guide, Developer Guide, etc) will suffice to get crawlers to focus on those pages, and then the rest will be ranked appropriately based on crawling from those roots. Or not; I'm no SEO SME. ;) Part of the PR for adding docs for a new release would then be to update the sitemap doc, e.g. to replace '17' in URLs with '18'. [~jamezp] FYI. [1] https://support.google.com/webmasters/answer/139066 [2] https://support.google.com/webmasters/answer/183668?hl=en&ref_topic=4581190 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12275) Add Documentation for Enhanced Audit Logging - RFC support and reliability/speed customization

by Justin Cook (Jira)

[ https://issues.jboss.org/browse/WFLY-12275?page=com.atlassian.jira.plugin... ] Justin Cook updated WFLY-12275: ------------------------------- Summary: Add Documentation for Enhanced Audit Logging - RFC support and reliability/speed customization (was: Enhanced Audit Logging - RFC support and reliability/speed customization) > Add Documentation for Enhanced Audit Logging - RFC support and reliability/speed customization > ---------------------------------------------------------------------------------------------- > > Key: WFLY-12275 > URL: https://issues.jboss.org/browse/WFLY-12275 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Justin Cook > Assignee: Justin Cook > Priority: Major > Labels: EAP-CD18 > Fix For: 18.0.0.Beta1 > > > This RFE for Enhanced Audit Logging in WildFly Elytron is for: > * RFC5424 Support > * RFC3164 Support > * Reliability vs Speed Customization -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12275) Enhanced Audit Logging - RFC support and reliability/speed customization

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFLY-12275?page=com.atlassian.jira.plugin... ] Farah Juma updated WFLY-12275: ------------------------------ Labels: EAP-CD18 (was: EAP-CD18 affects-model) > Enhanced Audit Logging - RFC support and reliability/speed customization > ------------------------------------------------------------------------ > > Key: WFLY-12275 > URL: https://issues.jboss.org/browse/WFLY-12275 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Justin Cook > Assignee: Justin Cook > Priority: Major > Labels: EAP-CD18 > Fix For: 18.0.0.Beta1 > > > This RFE for Enhanced Audit Logging in WildFly Elytron is for: > * RFC5424 Support > * RFC3164 Support > * Reliability vs Speed Customization -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12275) Enhanced Audit Logging - RFC support and reliability/speed customization

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFLY-12275?page=com.atlassian.jira.plugin... ] Farah Juma updated WFLY-12275: ------------------------------ Labels: EAP-CD18 affects-model (was: affects-model) > Enhanced Audit Logging - RFC support and reliability/speed customization > ------------------------------------------------------------------------ > > Key: WFLY-12275 > URL: https://issues.jboss.org/browse/WFLY-12275 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Justin Cook > Assignee: Justin Cook > Priority: Major > Labels: EAP-CD18, affects-model > Fix For: 18.0.0.Beta1 > > > This RFE for Enhanced Audit Logging in WildFly Elytron is for: > * RFC5424 Support > * RFC3164 Support > * Reliability vs Speed Customization -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12275) Enhanced Audit Logging - RFC support and reliability/speed customization

by Justin Cook (Jira)

[ https://issues.jboss.org/browse/WFLY-12275?page=com.atlassian.jira.plugin... ] Justin Cook moved WFCORE-4563 to WFLY-12275: -------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-12275 (was: WFCORE-4563) Component/s: Security (was: Security) Fix Version/s: 18.0.0.Beta1 (was: 10.0.0.Beta1) > Enhanced Audit Logging - RFC support and reliability/speed customization > ------------------------------------------------------------------------ > > Key: WFLY-12275 > URL: https://issues.jboss.org/browse/WFLY-12275 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Justin Cook > Assignee: Justin Cook > Priority: Major > Labels: affects-model > Fix For: 18.0.0.Beta1 > > > This RFE for Enhanced Audit Logging in WildFly Elytron is for: > * RFC5424 Support > * RFC3164 Support > * Reliability vs Speed Customization -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4563) Enhanced Audit Logging - RFC support and reliability/speed customization

by Justin Cook (Jira)

Justin Cook created WFCORE-4563: ----------------------------------- Summary: Enhanced Audit Logging - RFC support and reliability/speed customization Key: WFCORE-4563 URL: https://issues.jboss.org/browse/WFCORE-4563 Project: WildFly Core Issue Type: Feature Request Components: Security Reporter: Justin Cook Assignee: Justin Cook Fix For: 10.0.0.Beta1 This RFE for Enhanced Audit Logging in WildFly Elytron is for: * RFC5424 Support * RFC3164 Support * Reliability vs Speed Customization -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2358) (7.2.z) TCP: connection close can block when send() block on full TCP send-window

by Brad Maxwell (Jira)

Brad Maxwell created JGRP-2358: ---------------------------------- Summary: (7.2.z) TCP: connection close can block when send() block on full TCP send-window Key: JGRP-2358 URL: https://issues.jboss.org/browse/JGRP-2358 Project: JGroups Issue Type: Bug Reporter: Brad Maxwell Assignee: Bela Ban Fix For: 4.1.1, 4.0.20 When a peer is non-responsive (without closing its socket), a TcpConnection.send() can block on a write (state is RUNNABLE!). The problem is that the TcpConnection cannout be closed either, as TcpConnection.close() tries to acquire the same lock already held by TcpConnection.send(). See the stack trace below for a sample scenario. The use case is this one: * Say we have nodes A (coord), B and C * There's heavy (clustering) traffic to all 3 nodes, from the 2 clients * B is isolated by executing 'ifdown bond0' * At this point, the messages going to B will back up at (say) A because A doesn't get any TCP acks from B * At some point, depending on the traffic and the size of the sent messages, A will acquire a lock on the send connection to B, to write data, but the write will block as the TCP send-window to B is full (note that the sender thread will still be in state RUNNABLE!) * After 40s, A suspects B and emits a new view {A,C} * This causes A's connection to B to be closed and subsequently removed. However, this _won't_ happen, as the connection close will need to acquire the connection lock, which is held by the TCP write {noformat} "main" #1 prio=5 os_prio=31 tid=0x00007fbbd3802000 nid=0x2303 runnable [0x0000700009793000] java.lang.Thread.State: RUNNABLE at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111) at java.net.SocketOutputStream.write(SocketOutputStream.java:155) at java.io.BufferedOutputStream.write(BufferedOutputStream.java:122) - locked <0x000000079e790a50> (a java.io.BufferedOutputStream) at java.io.DataOutputStream.write(DataOutputStream.java:107) - locked <0x000000079e790838> (a java.io.DataOutputStream) at org.jgroups.blocks.cs.TcpConnection.doSend(TcpConnection.java:161) at org.jgroups.blocks.cs.TcpConnection.send(TcpConnection.java:131) at org.jgroups.blocks.cs.TcpClient.send(TcpClient.java:103) at org.jgroups.tests.bla6.main(bla6.java:35) "Thread-2" #15 prio=5 os_prio=31 tid=0x00007fbbd2150800 nid=0x6503 waiting on condition [0x000070000bcf6000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x000000079e7871a8> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199) at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209) at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285) at org.jgroups.blocks.cs.TcpConnection.close(TcpConnection.java:358) at org.jgroups.util.Util.close(Util.java:422) at org.jgroups.blocks.cs.TcpClient.stop(TcpClient.java:85) at org.jgroups.blocks.cs.BaseServer.close(BaseServer.java:147) at org.jgroups.util.Util.close(Util.java:422) at org.jgroups.tests.bla6.lambda$main$0(bla6.java:27) at org.jgroups.tests.bla6$$Lambda$1/1384010761.run(Unknown Source) at java.lang.Thread.run(Thread.java:748) {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11293) Add attribute to model which will indicate that backup is synchronized with live server

by Emmanuel Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-11293?page=com.atlassian.jira.plugin... ] Emmanuel Hugonnet reopened WFLY-11293: -------------------------------------- Assignee: Emmanuel Hugonnet > Add attribute to model which will indicate that backup is synchronized with live server > ---------------------------------------------------------------------------------------- > > Key: WFLY-11293 > URL: https://issues.jboss.org/browse/WFLY-11293 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Miroslav Novak > Assignee: Emmanuel Hugonnet > Priority: Critical > > If HA is configured with replicated journal then it takes some time to backup to synchronize with live server. Once backup is in sync with live then following information appears in server.log: > {code} > 13:20:00,739 INFO [org.apache.activemq.artemis.core.server] (Thread-3 (ActiveMQ-client-netty-threads-457000966)) AMQ221024: Backup server ActiveMQServerImpl::serverUUID=bc015b34-fd73-11e5-80ca-1b35f669abb8 is synchronized with live-server. > 13:20:01,500 INFO [org.apache.activemq.artemis.core.server] (Thread-2 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@41f992ab-83559664)) AMQ221031: backup announced > {code} > Reading server logs to see whether backup is in sync is not convinient and user friendly way. Could we add this information to model so it can be detected through CLI command? > New attribute with name {{synchronized-with-live}} should be added to {{/subsystem=messaging-activemq/server=default/ha-policy=replication-slave}} > This information can be gathered by calling: {{SharedNothingBackupActivation.isRemoteBackupUpToDate()}} > Additionally we should provide this attribute also in replicated live server in: {{/subsystem=messaging-activemq/server=default/ha-policy=replication-master}} as Administrator might want to know whether live can be shutdown. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4274) Remove reference usage from xml

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4274?page=com.atlassian.jira.plugi... ] Gabriele Cardosi closed DROOLS-4274. ------------------------------------ Resolution: Done > Remove reference usage from xml > ------------------------------- > > Key: DROOLS-4274 > URL: https://issues.jboss.org/browse/DROOLS-4274 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > > Remove usage of reference from xsd and xml -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 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 July 2019