[JBoss JIRA] (WFLY-10491) Fix wildfly-capabilities repository representation on GitHub
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10491?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-10491:
----------------------------------
Priority: Trivial (was: Major)
> Fix wildfly-capabilities repository representation on GitHub
> ------------------------------------------------------------
>
> Key: WFLY-10491
> URL: https://issues.jboss.org/browse/WFLY-10491
> Project: WildFly
> Issue Type: Task
> Components: Documentation
> Reporter: Radoslav Husar
> Assignee: Brian Stansberry
> Priority: Trivial
>
> Currently, the https://github.com/wildfly/wildfly-capabilities repository says its "forked from bstansberry/wildfly-capabilities". The common practice and understanding in community is that the upstream repository is the one that is not forked from any other repository. Thus having the upstream repository not represented as upstream is confusing.
> The repo should have been *moved* to wildfly organization and not *forked*.
> To remedy this, with a method we used in the past, is to delete the bstansberry/wildfly-capabilities repository (and then fork from wildfly of course).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (WFLY-9933) Nodes can not join the cluster if there are sessions which can not initial transfered
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-9933?page=com.atlassian.jira.plugin.... ]
Paul Ferraro closed WFLY-9933.
------------------------------
Fix Version/s: 13.0.0.Final
Resolution: Done
> Nodes can not join the cluster if there are sessions which can not initial transfered
> -------------------------------------------------------------------------------------
>
> Key: WFLY-9933
> URL: https://issues.jboss.org/browse/WFLY-9933
> Project: WildFly
> Issue Type: Enhancement
> Components: Clustering
> Reporter: Wolf-Dieter Fink
> Assignee: Paul Ferraro
> Fix For: 13.0.0.Final
>
>
> The current configuration for the infinispan cache for web session replication is waiting on the initial state transfer. If this goes wrong for some reason, i.e. an existing session which can not serialized, the complete start will fail.
> This can affect all applications which are correctly working.
> As this can be a configuration issue, like the timeout for the initial-state-transfer, or a bug in the application code because the session must be serializable, it should be possible to start the server even if threre are some sessions failing.
> With the current configuration options there is no way to configure the cache in a way that the cache is not waiting for the ST or to have the ST asynchronous that the server starts and 'only' the session replication will not be fully loaded.
> As an enhancement such configuration should be possible.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months