[JBoss JIRA] (SWSQE-695) Map Jira Workflows To Tablue Graphs
by Matthew Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-695?page=com.atlassian.jira.plugin.... ]
Matthew Mahoney updated SWSQE-695:
----------------------------------
Sprint: Kiali Sprint #23, Kiali Sprint #25 (was: Kiali Sprint #23, Kiali Sprint #24)
> Map Jira Workflows To Tablue Graphs
> -----------------------------------
>
> Key: SWSQE-695
> URL: https://issues.jboss.org/browse/SWSQE-695
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Matthew Mahoney
> Assignee: Prachi Yadav
> Priority: Major
> Labels: pqi
>
> Two parts to this task:
> 1) Because only a couple team members have access to Tablue, generate Kiali metric graphs in Tablue and Paste them into a team accessablel doc so that we can analyze these metrics
> 2) Map Jira Workflow queries to Tablue graphs, so that we can better understand how each of the Tablue graphs are generated.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (WFLY-12031) Memory leak in wildfly transaction client
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-12031?page=com.atlassian.jira.plugin... ]
Cheng Fang commented on WFLY-12031:
-----------------------------------
[~ochaloup]not a problem. Flavia suggested I could use the one from JBEAP-12611, and I'll give it a try.
> Memory leak in wildfly transaction client
> -----------------------------------------
>
> Key: WFLY-12031
> URL: https://issues.jboss.org/browse/WFLY-12031
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 15.0.1.Final
> Environment: wildfly-transaction-client-1.1.3.Final
> wildfly.15.0.1.Final
> Windows 10
> Reporter: Joachim Petrich
> Assignee: Cheng Fang
> Priority: Critical
>
> After a volume run of our system we recognized millions of entries in the openFilePaths Object of class FileSystemXAResourceRegistry. When enabling traces for org.wildfly.transaction it seems that for adding an entry a xid string is used
> {code:java}
> XAResourceRegistryFile(Xid xid) throws SystemException {
> xaRecoveryPath.toFile().mkdir(); // create dir if non existent
> final String xidString = SimpleXid.of(xid).toHexString('_');
> this.filePath = xaRecoveryPath.resolve(xidString);
> openFilePaths.add(*xidString*);
> {code}
> and for removing the entire file path:
> {code:java}
> protected void removeResource(XAResource resource) throws XAException {
> if (resources.remove(resource)) {
> if (resources.isEmpty()) {
> // delete file
> try {
> if (fileChannel != null) {
> fileChannel.close();
> }
> Files.delete(filePath);
> // deleting using the filepath as key caused a memory leak,
> // if xid string have been added, therefore build the xid string for removing
> openFilePaths.remove(*filePath.toString()*);
> {code}
> We didn't find any code where this xid are cleaned up.
> As workaround we additionally extract the xid String from the file path and remove the corresponding entry.
> {code:java}
> String xidString = filePath.toString().substring(filePath.toString().indexOf(
> xaRecoveryPath.toString()) + xaRecoveryPath.toString().length() + 1);
> openFilePaths.remove(xidString);
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (ELY-816) Support for masked passwords in client XML config
by Ashley Abdel-Sayed (Jira)
[ https://issues.jboss.org/browse/ELY-816?page=com.atlassian.jira.plugin.sy... ]
Ashley Abdel-Sayed edited comment on ELY-816 at 6/28/19 11:18 AM:
------------------------------------------------------------------
[~dmlloyd] It seems that there is no Sasl mechanism to support the masked password from the client side (similar to https://issues.jboss.org/browse/ELY-1252). Can you give a use case for using the masked-password in the authentication client?
[~darran] ^^FYI
was (Author: aabdelsa):
[~dmlloyd] It seems that there is no Sasl mechanism to support the masked password from the client side (similar to https://issues.jboss.org/browse/ELY-1252). Can you give a use case for using the masked-password in the authentication client?
> Support for masked passwords in client XML config
> -------------------------------------------------
>
> Key: ELY-816
> URL: https://issues.jboss.org/browse/ELY-816
> Project: WildFly Elytron
> Issue Type: Task
> Reporter: David Lloyd
> Assignee: Ashley Abdel-Sayed
> Priority: Critical
> Fix For: 1.10.0.CR3
>
>
> We need a way to support masked passwords in the auth configuration file, either as:
> * A dedicated masked-password-type XML type
> * Adding necessary fields to hashed-password-type
> * Adding a modular crypt format
> Needs to be supported anywhere passwords are allowed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (ELY-816) Support for masked passwords in client XML config
by Ashley Abdel-Sayed (Jira)
[ https://issues.jboss.org/browse/ELY-816?page=com.atlassian.jira.plugin.sy... ]
Ashley Abdel-Sayed commented on ELY-816:
----------------------------------------
[~dmlloyd] It seems that there is no Sasl mechanism to support the masked password from the client side (similar to https://issues.jboss.org/browse/ELY-1252). Can you give a use case for using the masked-password in the authentication client?
> Support for masked passwords in client XML config
> -------------------------------------------------
>
> Key: ELY-816
> URL: https://issues.jboss.org/browse/ELY-816
> Project: WildFly Elytron
> Issue Type: Task
> Reporter: David Lloyd
> Assignee: Ashley Abdel-Sayed
> Priority: Critical
> Fix For: 1.10.0.CR3
>
>
> We need a way to support masked passwords in the auth configuration file, either as:
> * A dedicated masked-password-type XML type
> * Adding necessary fields to hashed-password-type
> * Adding a modular crypt format
> Needs to be supported anywhere passwords are allowed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months