[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 edited comment on WFLY-12031 at 6/26/19 10:42 AM:
-------------------------------------------------------------
[~petrjoac] could you try running with the latest wildfly-transaction-client [1.1.4.Final|https://github.com/wildfly/wildfly-transaction-client/release...], and see if that fixes the issue? If not, then we will need to apply the proposed fix on [2019-04-30|https://issues.jboss.org/browse/WFLY-12031?focusedCommentId=13...] in next release (maybe 1.1.5.Final). So either way, I think it's helpful to try out wildfly-transaction-client 1.1.4.Final
was (Author: cfang):
[~petrjoac] could you try running with the latest wildfly-transaction-client [1.1.4.Final|https://github.com/wildfly/wildfly-transaction-client/release...], and see if that fixes the issue? If not, then we will need to apply the proposed fix on [2019-04-30|https://issues.jboss.org/browse/WFLY-12031?focusedCommentId=13...] on top of 1.1.4.Final. So either way, I think it's helpful to try out wildfly-transaction-client 1.1.4.Final
> 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, 6 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:
-----------------------------------
[~petrjoac] could you try running with the latest wildfly-transaction-client [1.1.4.Final|https://github.com/wildfly/wildfly-transaction-client/release...], and see if that fixes the issue? If not, then we will need to apply the proposed fix on [2019-04-30|https://issues.jboss.org/browse/WFLY-12031?focusedCommentId=13...] on top of 1.1.4.Final. So either way, I think it's helpful to try out wildfly-transaction-client 1.1.4.Final
> 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, 6 months
[JBoss JIRA] (DROOLS-3746) JavaScript run error when edit Guided Decision Tables on latest chrome
by Alberto Fanjul Alonso (Jira)
[ https://issues.jboss.org/browse/DROOLS-3746?page=com.atlassian.jira.plugi... ]
Alberto Fanjul Alonso edited comment on DROOLS-3746 at 6/26/19 9:36 AM:
------------------------------------------------------------------------
I tried this with chrome:
{code:javascript}
| Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://localhost:8080/business-central/verifier/dtableVerifier/DDFC3D4453...)
{code}
and firefox
{code:javascript}
| Uncaught exception: TypeError: b is undefined (http://localhost:8080/business-central/verifier/dtableVerifier/DDFC3D4453...) | Uncaught exception: TypeError: b is undefined (http://localhost:8080/business-central/verifier/dtableVerifier/DDFC3D4453...)
{code}
So seems not related with chrome.
Seing the stack trace from chrome:
{code:javascript}
Uncaught TypeError: Cannot read property 'createElement' of undefined
at Qb (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:13294)
at Rsb (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:23506)
at ssb (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:8218)
at rsb (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:3192)
at tsb.wsb [as tb] (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:38072)
at KT (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:12820)
at QT (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:11819)
at gc (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:10406)
at bc (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:12150)
at DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:6237
at self.onmessage (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:14754)
{code}
formatted code is:
{code:javascript}
function Qb(a) {
var b, c, d;
d = !a.c ? (Ob(),
window) : a.c;
b = (Ob(),
d.document);
c = b.createElement('script');
Pb(c, a.b);
(b.head || b.getElementsByTagName('head')[0]).appendChild(c);
a.a && (c.parentNode.removeChild(c),
undefined);
return c
}
{code}
this is generated code by gwt http://www.gwtproject.org/overview.html so the real code is under.
drools-wb-services/drools-wb-verifier/drools-wb-verifier-webworker/src/main/java/org/drools/workbench/services/verifier/plugin/backend/DecisionTableVerifierWebWorkerProvider.java
or
drools-wb-screens/drools-wb-guided-dtable-editor/drools-wb-guided-dtable-editor-client/src/main/java/org/drools/workbench/screens/guided/dtable/client/widget/analysis/DecisionTableAnalyzerBuilder.java
Not sure if in code itself or in gwt translation
Any idea on what to check, debug or test to fix this?
was (Author: afanjula):
I tried this with chrome:
```
| Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://localhost:8080/business-central/verifier/dtableVerifier/DDFC3D4453...)
```
and firefox
```
| Uncaught exception: TypeError: b is undefined (http://localhost:8080/business-central/verifier/dtableVerifier/DDFC3D4453...) | Uncaught exception: TypeError: b is undefined (http://localhost:8080/business-central/verifier/dtableVerifier/DDFC3D4453...)
```
So seems not related with chrome.
Seing the stack trace from chrome:
```
Uncaught TypeError: Cannot read property 'createElement' of undefined
at Qb (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:13294)
at Rsb (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:23506)
at ssb (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:8218)
at rsb (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:3192)
at tsb.wsb [as tb] (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:38072)
at KT (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:12820)
at QT (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:11819)
at gc (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:10406)
at bc (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:12150)
at DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:6237
at self.onmessage (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:14754)
```
formatted code is:
```
function Qb(a) {
var b, c, d;
d = !a.c ? (Ob(),
window) : a.c;
b = (Ob(),
d.document);
c = b.createElement('script');
Pb(c, a.b);
(b.head || b.getElementsByTagName('head')[0]).appendChild(c);
a.a && (c.parentNode.removeChild(c),
undefined);
return c
}
```
this is generated code by gwt http://www.gwtproject.org/overview.html so the real code is under.
drools-wb-services/drools-wb-verifier/drools-wb-verifier-webworker/src/main/java/org/drools/workbench/services/verifier/plugin/backend/DecisionTableVerifierWebWorkerProvider.java
or
drools-wb-screens/drools-wb-guided-dtable-editor/drools-wb-guided-dtable-editor-client/src/main/java/org/drools/workbench/screens/guided/dtable/client/widget/analysis/DecisionTableAnalyzerBuilder.java
Not sure if in code itself or in gwt translation
Any idea on what to check, debug or test to fix this?
> JavaScript run error when edit Guided Decision Tables on latest chrome
> ----------------------------------------------------------------------
>
> Key: DROOLS-3746
> URL: https://issues.jboss.org/browse/DROOLS-3746
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.18.0.Final
> Reporter: xiaodong zhang
> Assignee: Toni Rikkola
> Priority: Blocker
>
> When updated to the latest chrome (72.0.3626.121), When I do edit using Guided Decision Tables, an error will throw.
> The error detail is :
> | Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://127.0.0.1:8080/kie-drools-wb/verifier/dtableVerifier/C1C6DDEF649DA...)
> My version is 7.14.0.Final and I also tried the latest 7.18.0.Final but no lucky. It's happend on both windows and Mac client when using the latest chrome or safari.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months
[JBoss JIRA] (DROOLS-3746) JavaScript run error when edit Guided Decision Tables on latest chrome
by Alberto Fanjul Alonso (Jira)
[ https://issues.jboss.org/browse/DROOLS-3746?page=com.atlassian.jira.plugi... ]
Alberto Fanjul Alonso commented on DROOLS-3746:
-----------------------------------------------
I tried this with chrome:
```
| Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://localhost:8080/business-central/verifier/dtableVerifier/DDFC3D4453...)
```
and firefox
```
| Uncaught exception: TypeError: b is undefined (http://localhost:8080/business-central/verifier/dtableVerifier/DDFC3D4453...) | Uncaught exception: TypeError: b is undefined (http://localhost:8080/business-central/verifier/dtableVerifier/DDFC3D4453...)
```
So seems not related with chrome.
Seing the stack trace from chrome:
```
Uncaught TypeError: Cannot read property 'createElement' of undefined
at Qb (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:13294)
at Rsb (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:23506)
at ssb (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:8218)
at rsb (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:3192)
at tsb.wsb [as tb] (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:38072)
at KT (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:12820)
at QT (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:11819)
at gc (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:10406)
at bc (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:12150)
at DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:6237
at self.onmessage (DDFC3D4453CB85BB71197C4DE2FF626C.cache.js:formatted:14754)
```
formatted code is:
```
function Qb(a) {
var b, c, d;
d = !a.c ? (Ob(),
window) : a.c;
b = (Ob(),
d.document);
c = b.createElement('script');
Pb(c, a.b);
(b.head || b.getElementsByTagName('head')[0]).appendChild(c);
a.a && (c.parentNode.removeChild(c),
undefined);
return c
}
```
this is generated code by gwt http://www.gwtproject.org/overview.html so the real code is under.
drools-wb-services/drools-wb-verifier/drools-wb-verifier-webworker/src/main/java/org/drools/workbench/services/verifier/plugin/backend/DecisionTableVerifierWebWorkerProvider.java
or
drools-wb-screens/drools-wb-guided-dtable-editor/drools-wb-guided-dtable-editor-client/src/main/java/org/drools/workbench/screens/guided/dtable/client/widget/analysis/DecisionTableAnalyzerBuilder.java
Not sure if in code itself or in gwt translation
Any idea on what to check, debug or test to fix this?
> JavaScript run error when edit Guided Decision Tables on latest chrome
> ----------------------------------------------------------------------
>
> Key: DROOLS-3746
> URL: https://issues.jboss.org/browse/DROOLS-3746
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.18.0.Final
> Reporter: xiaodong zhang
> Assignee: Toni Rikkola
> Priority: Blocker
>
> When updated to the latest chrome (72.0.3626.121), When I do edit using Guided Decision Tables, an error will throw.
> The error detail is :
> | Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://127.0.0.1:8080/kie-drools-wb/verifier/dtableVerifier/C1C6DDEF649DA...)
> My version is 7.14.0.Final and I also tried the latest 7.18.0.Final but no lucky. It's happend on both windows and Mac client when using the latest chrome or safari.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months
[JBoss JIRA] (DROOLS-4168) [DMN Designer] Documentation - Add an image to documentation cover
by Guilherme Gomes (Jira)
[ https://issues.jboss.org/browse/DROOLS-4168?page=com.atlassian.jira.plugi... ]
Guilherme Gomes edited comment on DROOLS-4168 at 6/26/19 9:11 AM:
------------------------------------------------------------------
[~uxdlc] Done, I've put the DROOLS-4245 into the current sprint.
Also, I already viewed the DROOLS-4245. I think the description is complete enough :-)
was (Author: karreiro):
[~uxdlc] Done, I've put the DROOLS-4245 into the current sprint.
Also, I already viewed the DROOLS-4245. I think it's complete enough :-)
> [DMN Designer] Documentation - Add an image to documentation cover
> ------------------------------------------------------------------
>
> Key: DROOLS-4168
> URL: https://issues.jboss.org/browse/DROOLS-4168
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> Currently, we're not showing any image in the documentation cover (in the DMN Documentation).
> The expected result is to have a logo in the cover (following the template provided by the UX team).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months
[JBoss JIRA] (DROOLS-4168) [DMN Designer] Documentation - Add an image to documentation cover
by Guilherme Gomes (Jira)
[ https://issues.jboss.org/browse/DROOLS-4168?page=com.atlassian.jira.plugi... ]
Guilherme Gomes edited comment on DROOLS-4168 at 6/26/19 9:11 AM:
------------------------------------------------------------------
[~uxdlc] Done, I've put the DROOLS-4245 into the current sprint.
Also, I already viewed the DROOLS-4245. I think it's complete enough :-)
was (Author: karreiro):
[~uxdlc] Done, I've put the DROOLS-4245 into the current sprint.
I already viewed the https://issues.jboss.org/browse/DROOLS-4245. I think it's complete enough :-)
> [DMN Designer] Documentation - Add an image to documentation cover
> ------------------------------------------------------------------
>
> Key: DROOLS-4168
> URL: https://issues.jboss.org/browse/DROOLS-4168
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> Currently, we're not showing any image in the documentation cover (in the DMN Documentation).
> The expected result is to have a logo in the cover (following the template provided by the UX team).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months