[JBoss JIRA] (WFLY-10813) OutOfMemory error when trying to display resource adapters in web console
by Helena Knyttlová (JIRA)
Helena Knyttlová created WFLY-10813:
---------------------------------------
Summary: OutOfMemory error when trying to display resource adapters in web console
Key: WFLY-10813
URL: https://issues.jboss.org/browse/WFLY-10813
Project: WildFly
Issue Type: Bug
Components: Web Console
Affects Versions: 13.0.0.Final, 10.0.0.Final
Reporter: Helena Knyttlová
Assignee: Harald Pehl
Priority: Minor
We have about 25 resource adapters set through CLI. When I want to display them in web administration console it kills the whole wildfly server - server is not responding and after several minutes it ends up with OutOfMemory error and server must be restarted. We've seen this issue since wildfly 10 (it was the first version we used). With only a few resource adapters it is not happening.
Memory settings: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m
The error which appeared on WidlFly 13.0.0.Final:
{panel:title=My title}
ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("read-resource-description") failed - address: ([
("subsystem" => "resource-adapters"),
("resource-adapter" => "AppAdapter"),
("connection-definitions" => "cp-host")
]): java.lang.OutOfMemoryError: Java heap space
at java.util.HashMap.resize(HashMap.java:704)
at java.util.HashMap.putVal(HashMap.java:629)
at java.util.HashMap.put(HashMap.java:612)
at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:180)
at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:169)
at org.jboss.dmr.ModelNode.clone(ModelNode.java:1867)
at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:180)
at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:169)
at org.jboss.dmr.ModelNode.clone(ModelNode.java:1867)
at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:180)
at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:169)
at org.jboss.dmr.ModelNode.clone(ModelNode.java:1867)
at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:180)
at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:169)
at org.jboss.dmr.ModelNode.set(ModelNode.java:693)
at org.jboss.as.controller.operations.global.ReadResourceDescriptionHandler$ReadResourceDescriptionAssemblyHandler.execute(ReadResourceDescriptionHandler.java:618)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1404)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423)
at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243)
at org.jboss.as.controller.ModelControllerImpl$$Lambda$490/414756260.run(Unknown Source)
at org.wildfly.security.auth.server.SecurityIdentity$$Lambda$491/367363594.run(Unknown Source)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243)
at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:212)
at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72)
at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:93)
at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.lambda$handleRequest$0(ElytronIdentityHandler.java:62)
at org.jboss.as.domain.http.server.security.ElytronIdentityHandler$$Lambda$790/1228674018.run(Unknown Source)
{panel}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2792:
--------------------------------
Description:
*_Literal Expression_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
h3. Manual acceptance test
- Resizing (/)
- Ctrl+C, Ctrl+v (/)
- Default Data Type for literal expression (/)
- Selecting itemDefinition (/)
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Changing data type in graph node (/)
- Changing data type in properties panel (/)
- Building project (?)
-- Should the deployment fail if I have literal expression of type number but inside string constant like: "string constant"?
- Undo / Redo
was:
*_Literal Expression_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
h3. Manual acceptance test
- Resizing (/)
- Ctrl+C, Ctrl+v (/)
- Default Data Type for literal expression (/)
- Selecting itemDefinition (/)
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Changing data type in graph node (/)
- Changing data type in properties panel (/)
- Building project (?)
-- Should the deployment fail if I have literal expression of type number but inside string constant like: "string constant"?
> [DMN Designer] Data-types: Grid: LiteralExpression
> --------------------------------------------------
>
> Key: DROOLS-2792
> URL: https://issues.jboss.org/browse/DROOLS-2792
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Attachments: DROOLS-2792.odt, Screen Shot 2018-08-01 at 10.11.48 AM.png, Screen Shot 2018-08-01 at 10.20.35 AM.png, Screenshot from 2018-08-09 09-21-01.png
>
>
> *_Literal Expression_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
> - (x) Update header when Output Data Type is changed via Properties panel
> h3. Manual acceptance test
> - Resizing (/)
> - Ctrl+C, Ctrl+v (/)
> - Default Data Type for literal expression (/)
> - Selecting itemDefinition (/)
> - Long name of data type (?)
> -- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
> - Used in levels of context grid (?)
> -- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
> -- Should be the data type shown anytime or just if literal expression is top level context entry?
> - Changing data type in graph node (/)
> - Changing data type in properties panel (/)
> - Building project (?)
> -- Should the deployment fail if I have literal expression of type number but inside string constant like: "string constant"?
> - Undo / Redo
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2792:
--------------------------------
Description:
*_Literal Expression_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
h3. Manual acceptance test
- Resizing (/)
- Ctrl+C, Ctrl+v (/)
- Default Data Type for literal expression (/)
- Selecting itemDefinition (/)
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Changing data type in graph node (/)
- Changing data type in properties panel (/)
- Building project (?)
-- Should the deployment fail if I have literal expression of type number but inside string constant like: "string constant"?
was:
*_Literal Expression_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
h3. Manual acceptance test
- Resizing (/)
- Ctrl+C, Ctrl+v (/)
- Default Data Type for literal expression (/)
- Selecting itemDefinition (/)
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Changing data type in graph node (/)
- Changing data type in properties panel (/)
- Building project (/)
-- Should the deployment fail if I have literal expression of type number but inside string constant like: "string constant"?
> [DMN Designer] Data-types: Grid: LiteralExpression
> --------------------------------------------------
>
> Key: DROOLS-2792
> URL: https://issues.jboss.org/browse/DROOLS-2792
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Attachments: DROOLS-2792.odt, Screen Shot 2018-08-01 at 10.11.48 AM.png, Screen Shot 2018-08-01 at 10.20.35 AM.png, Screenshot from 2018-08-09 09-21-01.png
>
>
> *_Literal Expression_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
> - (x) Update header when Output Data Type is changed via Properties panel
> h3. Manual acceptance test
> - Resizing (/)
> - Ctrl+C, Ctrl+v (/)
> - Default Data Type for literal expression (/)
> - Selecting itemDefinition (/)
> - Long name of data type (?)
> -- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
> - Used in levels of context grid (?)
> -- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
> -- Should be the data type shown anytime or just if literal expression is top level context entry?
> - Changing data type in graph node (/)
> - Changing data type in properties panel (/)
> - Building project (?)
> -- Should the deployment fail if I have literal expression of type number but inside string constant like: "string constant"?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2792:
--------------------------------
Description:
*_Literal Expression_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
h3. Manual acceptance test
- Resizing (/)
- Ctrl+C, Ctrl+v (/)
- Default Data Type for literal expression (/)
- Selecting itemDefinition (/)
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Changing data type in graph node (/)
- Changing data type in properties panel (/)
- Building project (/)
-- Should the deployment fail if I have literal expresison of type number but inside string constant like: "string constant"?
was:
*_Literal Expression_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
h3. Manual acceptance test
- Resizing (/)
- Ctrl+C, Ctrl+v (/)
- Default Data Type for literal expression (/)
- Selecting itemDefinition (/)
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Changing data type in graph node (/)
- Changing data type in properties panel (/)
- Building project (/)
-- Should the deployment fail if I have literal expresison of type number and but inside string constant like: "string constant"?
> [DMN Designer] Data-types: Grid: LiteralExpression
> --------------------------------------------------
>
> Key: DROOLS-2792
> URL: https://issues.jboss.org/browse/DROOLS-2792
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Attachments: DROOLS-2792.odt, Screen Shot 2018-08-01 at 10.11.48 AM.png, Screen Shot 2018-08-01 at 10.20.35 AM.png, Screenshot from 2018-08-09 09-21-01.png
>
>
> *_Literal Expression_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
> - (x) Update header when Output Data Type is changed via Properties panel
> h3. Manual acceptance test
> - Resizing (/)
> - Ctrl+C, Ctrl+v (/)
> - Default Data Type for literal expression (/)
> - Selecting itemDefinition (/)
> - Long name of data type (?)
> -- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
> - Used in levels of context grid (?)
> -- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
> -- Should be the data type shown anytime or just if literal expression is top level context entry?
> - Changing data type in graph node (/)
> - Changing data type in properties panel (/)
> - Building project (/)
> -- Should the deployment fail if I have literal expresison of type number but inside string constant like: "string constant"?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2792:
--------------------------------
Description:
*_Literal Expression_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
h3. Manual acceptance test
- Resizing (/)
- Ctrl+C, Ctrl+v (/)
- Default Data Type for literal expression (/)
- Selecting itemDefinition (/)
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Changing data type in graph node (/)
- Changing data type in properties panel (/)
- Building project (/)
-- Should the deployment fail if I have literal expression of type number but inside string constant like: "string constant"?
was:
*_Literal Expression_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
h3. Manual acceptance test
- Resizing (/)
- Ctrl+C, Ctrl+v (/)
- Default Data Type for literal expression (/)
- Selecting itemDefinition (/)
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Changing data type in graph node (/)
- Changing data type in properties panel (/)
- Building project (/)
-- Should the deployment fail if I have literal expresison of type number but inside string constant like: "string constant"?
> [DMN Designer] Data-types: Grid: LiteralExpression
> --------------------------------------------------
>
> Key: DROOLS-2792
> URL: https://issues.jboss.org/browse/DROOLS-2792
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Attachments: DROOLS-2792.odt, Screen Shot 2018-08-01 at 10.11.48 AM.png, Screen Shot 2018-08-01 at 10.20.35 AM.png, Screenshot from 2018-08-09 09-21-01.png
>
>
> *_Literal Expression_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
> - (x) Update header when Output Data Type is changed via Properties panel
> h3. Manual acceptance test
> - Resizing (/)
> - Ctrl+C, Ctrl+v (/)
> - Default Data Type for literal expression (/)
> - Selecting itemDefinition (/)
> - Long name of data type (?)
> -- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
> - Used in levels of context grid (?)
> -- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
> -- Should be the data type shown anytime or just if literal expression is top level context entry?
> - Changing data type in graph node (/)
> - Changing data type in properties panel (/)
> - Building project (/)
> -- Should the deployment fail if I have literal expression of type number but inside string constant like: "string constant"?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2792:
--------------------------------
Description:
*_Literal Expression_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
h3. Manual acceptance test
- Resizing (/)
- Ctrl+C, Ctrl+v (/)
- Default Data Type for literal expression (/)
- Selecting itemDefinition (/)
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Changing data type in graph node (/)
- Changing data type in properties panel (/)
- Building project (/)
-- Should the deployment fail if I have literal expresison of type number and but inside string constant like: "string constant"?
was:
*_Literal Expression_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
h3. Manual acceptance test
- Resizing (/)
- Ctrl+C, Ctrl+v (/)
- Default Data Type for literal expression (/)
- Selecting itemDefinition (/)
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Changing data type in graph node (/)
- Changing data type in properties panel (/)
- Building project
> [DMN Designer] Data-types: Grid: LiteralExpression
> --------------------------------------------------
>
> Key: DROOLS-2792
> URL: https://issues.jboss.org/browse/DROOLS-2792
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Attachments: DROOLS-2792.odt, Screen Shot 2018-08-01 at 10.11.48 AM.png, Screen Shot 2018-08-01 at 10.20.35 AM.png, Screenshot from 2018-08-09 09-21-01.png
>
>
> *_Literal Expression_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
> - (x) Update header when Output Data Type is changed via Properties panel
> h3. Manual acceptance test
> - Resizing (/)
> - Ctrl+C, Ctrl+v (/)
> - Default Data Type for literal expression (/)
> - Selecting itemDefinition (/)
> - Long name of data type (?)
> -- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
> - Used in levels of context grid (?)
> -- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
> -- Should be the data type shown anytime or just if literal expression is top level context entry?
> - Changing data type in graph node (/)
> - Changing data type in properties panel (/)
> - Building project (/)
> -- Should the deployment fail if I have literal expresison of type number and but inside string constant like: "string constant"?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2871) Remove manners example from code and docs
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-2871:
-----------------------------------
Summary: Remove manners example from code and docs
Key: DROOLS-2871
URL: https://issues.jboss.org/browse/DROOLS-2871
Project: Drools
Issue Type: Task
Components: core engine
Reporter: Mario Fusco
Assignee: Mario Fusco
Manners hasn't worked in a while, as it requires depth based search, which we don't currently provide any more. We should remove the example and the docs for it.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2870) [DMN Designer] Can not build project with multiple models
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-2870:
-----------------------------------
Summary: [DMN Designer] Can not build project with multiple models
Key: DROOLS-2870
URL: https://issues.jboss.org/browse/DROOLS-2870
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.10.0.Final
Reporter: Jozef Marko
Assignee: Michael Anstis
Priority: Blocker
Attachments: Screenshot from 2018-08-09 10-20-16.png
If the project contains multiple dmn models, it can not be built.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months