June 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10295) Upgrade to JGroups 4.0.20.Final

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10295?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10295: -------------------------------- Status: Open (was: New) > Upgrade to JGroups 4.0.20.Final > ------------------------------- > > Key: ISPN-10295 > URL: https://issues.jboss.org/browse/ISPN-10295 > Project: Infinispan > Issue Type: Component Upgrade > Components: Dependency > Affects Versions: 9.4.14.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.15.Final > > > Includes fixes for JGRP-2350 (TCP: connection close can block when send() block on full TCP send-window) and for JGRP-2354 (ForkChannel does not receive SITE_UNREACHABLE events). -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10295) Upgrade to JGroups 4.0.20.Final

by Dan Berindei (Jira)

Dan Berindei created ISPN-10295: ----------------------------------- Summary: Upgrade to JGroups 4.0.20.Final Key: ISPN-10295 URL: https://issues.jboss.org/browse/ISPN-10295 Project: Infinispan Issue Type: Component Upgrade Components: Dependency Affects Versions: 9.4.14.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 9.4.15.Final Includes fixes for JGRP-2350 (TCP: connection close can block when send() block on full TCP send-window) and for JGRP-2354 (ForkChannel does not receive SITE_UNREACHABLE events). -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10294) Customizable splash resource

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10294?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10294: ------------------------------------- Description: The server should accept custom splash instead of the index.html and banner.png that are in the rest module resources. Ideally the resources should be "brandable" to distinguish community and product. The resources to be server could come from another jar was:The server should accept custom splash instead of the index.html and banner.png that are in the rest module resources. Ideally the resources should be "brandable" to distinguish community and product > Customizable splash resource > ---------------------------- > > Key: ISPN-10294 > URL: https://issues.jboss.org/browse/ISPN-10294 > Project: Infinispan > Issue Type: Enhancement > Components: REST > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > The server should accept custom splash instead of the index.html and banner.png that are in the rest module resources. Ideally the resources should be "brandable" to distinguish community and product. > The resources to be server could come from another jar -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10294) Customizable splash resource

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-10294: ---------------------------------------- Summary: Customizable splash resource Key: ISPN-10294 URL: https://issues.jboss.org/browse/ISPN-10294 Project: Infinispan Issue Type: Enhancement Components: REST Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes The server should accept custom splash instead of the index.html and banner.png that are in the rest module resources. Ideally the resources should be "brandable" to distinguish community and product -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10293) It should be possible to add protobuf files directly to the server installation

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-10293: --------------------------------------- Summary: It should be possible to add protobuf files directly to the server installation Key: ISPN-10293 URL: https://issues.jboss.org/browse/ISPN-10293 Project: Infinispan Issue Type: Feature Request Components: Server Reporter: Wolf-Dieter Fink Definition files (protobuf) for queries and indexing need to be added with client requests during runtime. It will be stored in an internal cache and there is a persistence with a filestore to ensure it will survive restarts. But this is not always ensured as there might be catastropic failures or unclean shutdown which can cause inconsistence or complete loss. The behaviour in such cases is not deterministic and heavy to track or solve. For this reason it should be possible to add the protobuf definitions directly to the server installation which is picked up during startup. It might be a local cache as the expectation is that all nodes will have the same, but a repl cache might be possible as well. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10292) It should be possible to add protobuf files directly to the server installation

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-10292: --------------------------------------- Summary: It should be possible to add protobuf files directly to the server installation Key: ISPN-10292 URL: https://issues.jboss.org/browse/ISPN-10292 Project: Infinispan Issue Type: Feature Request Components: Server Reporter: Wolf-Dieter Fink Definition files (protobuf) for queries and indexing need to be added with client requests during runtime. It will be stored in an internal cache and there is a persistence with a filestore to ensure it will survive restarts. But this is not always ensured as there might be catastropic failures or unclean shutdown which can cause inconsistence or complete loss. The behaviour in such cases is not deterministic and heavy to track or solve. For this reason it should be possible to add the protobuf definitions directly to the server installation which is picked up during startup. It might be a local cache as the expectation is that all nodes will have the same, but a repl cache might be possible as well. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10291) Upgrade to JGroups 4.1.1.Final

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10291?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10291: -------------------------------- Status: Open (was: New) > Upgrade to JGroups 4.1.1.Final > ------------------------------ > > Key: ISPN-10291 > URL: https://issues.jboss.org/browse/ISPN-10291 > Project: Infinispan > Issue Type: Component Upgrade > Components: Dependency > Affects Versions: 10.0.0.Beta3, 9.4.14.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.15.Final > > > JGroups 4.1.0.Final has several improvements for running under Quarkus, plus should be better at using the same kind of IP address everywhere when not running with {{-Djava.net.preferIPv4Stack=true}}: > http://belaban.blogspot.com/2019/05/410-released.html > 4.1.1.Final adds a fix for JGRP-2350 (TCP: connection close can block when send() block on full TCP send-window) and for JGRP-2354 (ForkChannel does not receive SITE_UNREACHABLE events) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10291) Upgrade to JGroups 4.1.1.Final

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10291?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10291: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7029 > Upgrade to JGroups 4.1.1.Final > ------------------------------ > > Key: ISPN-10291 > URL: https://issues.jboss.org/browse/ISPN-10291 > Project: Infinispan > Issue Type: Component Upgrade > Components: Dependency > Affects Versions: 10.0.0.Beta3, 9.4.14.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.15.Final > > > JGroups 4.1.0.Final has several improvements for running under Quarkus, plus should be better at using the same kind of IP address everywhere when not running with {{-Djava.net.preferIPv4Stack=true}}: > http://belaban.blogspot.com/2019/05/410-released.html > 4.1.1.Final adds a fix for JGRP-2350 (TCP: connection close can block when send() block on full TCP send-window) and for JGRP-2354 (ForkChannel does not receive SITE_UNREACHABLE events) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10291) Upgrade to JGroups 4.1.1.Final

by Dan Berindei (Jira)

Dan Berindei created ISPN-10291: ----------------------------------- Summary: Upgrade to JGroups 4.1.1.Final Key: ISPN-10291 URL: https://issues.jboss.org/browse/ISPN-10291 Project: Infinispan Issue Type: Component Upgrade Components: Dependency Affects Versions: 9.4.14.Final, 10.0.0.Beta3 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 10.0.0.Beta4, 9.4.15.Final JGroups 4.1.0.Final has several improvements for running under Quarkus, plus should be better at using the same kind of IP address everywhere when not running with {{-Djava.net.preferIPv4Stack=true}}: http://belaban.blogspot.com/2019/05/410-released.html 4.1.1.Final adds a fix for JGRP-2350 (TCP: connection close can block when send() block on full TCP send-window) and for JGRP-2354 (ForkChannel does not receive SITE_UNREACHABLE events) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10290) JGroupsTransport.invokeCommandStaggered allocates too much

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10290?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10290: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7028 > JGroupsTransport.invokeCommandStaggered allocates too much > ---------------------------------------------------------- > > Key: ISPN-10290 > URL: https://issues.jboss.org/browse/ISPN-10290 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Beta3, 9.4.14.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 10.0.0.Beta4 > > > I assumed the {{logRequest(requestId, command, "staggered " + targets)}} call would be inlined and the JIT would eliminate the allocation when trace logging is disabled, but apparently that doesn't always happen, and a {{StringBuilder}} instance is always created. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2019