[JBoss JIRA] (ISPN-11626) CLI diagnostics tool
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11626?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11626:
-----------------------------------
Status: Open (was: New)
> CLI diagnostics tool
> --------------------
>
> Key: ISPN-11626
> URL: https://issues.redhat.com/browse/ISPN-11626
> Project: Infinispan
> Issue Type: Feature Request
> Components: CLI, Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Labels: supportability
> Fix For: 11.0.0.Final
>
>
> Enhance the CLI to be able to obtain a combined dump of the following information
> * current server.log
> * current gc.log
> * configuration
> * data/caches.xml
> * thread dump
> * lsof
> * general machine information like OS, memory, cpu
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (ISPN-11703) JGroups Stacks should be initialized lazily
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11703?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-11703:
------------------------------
Summary: JGroups Stacks should be initialized lazily (was: JGroups Stacks should be initailized lazily)
> JGroups Stacks should be initialized lazily
> -------------------------------------------
>
> Key: ISPN-11703
> URL: https://issues.redhat.com/browse/ISPN-11703
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Reporter: Will Burns
> Priority: Major
> Fix For: 11.0.0.Dev05
>
>
> When we initialize the Parser we always read in the default jgroups stacks. This is done even if the global configuration doesn't have clustering. The parser is also started whenever a new cache is configured and started at runtime. These should be done only if the parser requires the jgroups stacks.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months