[JBoss JIRA] (WFLY-10813) OutOfMemory error when trying to display resource adapters in web console
by Helena Knyttlová (JIRA)
[ https://issues.jboss.org/browse/WFLY-10813?page=com.atlassian.jira.plugin... ]
Helena Knyttlová updated WFLY-10813:
------------------------------------
Description:
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=Log}
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}
was:
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}
> 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: 10.0.0.Final, 13.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=Log}
> 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] (WFLY-10817) Incorrect data check when clearing body of large compressed message after failover
by Erich Duda (JIRA)
Erich Duda created WFLY-10817:
---------------------------------
Summary: Incorrect data check when clearing body of large compressed message after failover
Key: WFLY-10817
URL: https://issues.jboss.org/browse/WFLY-10817
Project: WildFly
Issue Type: Bug
Components: JMS
Reporter: Erich Duda
Assignee: Jeff Mesnil
Priority: Critical
*Scenario*
* There are two WildFly (Artemis) servers in dedicated shared store HA topology
* Connection factory is configured to compress large messages
* Live server is killed
* Clients do failover to backup
After the clients do failover to backup, I can see following exceptions in the log when a receiver tries to clear body of large message. The test fails because of lost messages.
I can see this issue with Artemis 1.5.5.jbossorg-012.
I am not able to reproduce it locally but I hit it on Jenkins every time.
{code}
javax.jms.JMSException: AMQ119029: Error writing body of message
at org.apache.activemq.artemis.jms.client.ActiveMQBytesMessage.clearBody(ActiveMQBytesMessage.java:337)
at org.jboss.qa.hornetq.apps.clients.Client.cleanMessage(Client.java:144)
at org.jboss.qa.hornetq.apps.clients.Receiver11.receiveMessage(Receiver11.java:153)
at org.jboss.qa.hornetq.apps.clients.ReceiverTransAck.run(ReceiverTransAck.java:89)
Caused by: java.lang.RuntimeException: AMQ119029: Error writing body of message
at org.apache.activemq.artemis.core.client.impl.ClientLargeMessageImpl.getBodyBuffer(ClientLargeMessageImpl.java:93)
at org.apache.activemq.artemis.jms.client.ActiveMQBytesMessage.getBuffer(ActiveMQBytesMessage.java:363)
at org.apache.activemq.artemis.jms.client.ActiveMQBytesMessage.clearBody(ActiveMQBytesMessage.java:335)
... 3 more
Caused by: ActiveMQLargeMessageException[errorType=LARGE_MESSAGE_ERROR_BODY message=AMQ119029: Error writing body of message]
at org.apache.activemq.artemis.core.client.impl.LargeMessageControllerImpl.sendPacketToOutput(LargeMessageControllerImpl.java:1077)
at org.apache.activemq.artemis.core.client.impl.LargeMessageControllerImpl.setOutputStream(LargeMessageControllerImpl.java:258)
at org.apache.activemq.artemis.core.client.impl.CompressedLargeMessageControllerImpl.setOutputStream(CompressedLargeMessageControllerImpl.java:75)
at org.apache.activemq.artemis.core.client.impl.CompressedLargeMessageControllerImpl.saveBuffer(CompressedLargeMessageControllerImpl.java:80)
at org.apache.activemq.artemis.core.client.impl.ClientLargeMessageImpl.checkBuffer(ClientLargeMessageImpl.java:159)
at org.apache.activemq.artemis.core.client.impl.ClientLargeMessageImpl.getBodyBuffer(ClientLargeMessageImpl.java:91)
... 5 more
Caused by: java.io.IOException: incorrect data check
at org.apache.activemq.artemis.utils.InflaterWriter.close(InflaterWriter.java:81)
at org.apache.activemq.artemis.core.client.impl.LargeMessageControllerImpl.sendPacketToOutput(LargeMessageControllerImpl.java:1074)
... 10 more
Caused by: java.util.zip.DataFormatException: incorrect data check
at java.util.zip.Inflater.inflateBytes(Native Method)
at java.util.zip.Inflater.inflate(Inflater.java:259)
at java.util.zip.Inflater.inflate(Inflater.java:280)
at org.apache.activemq.artemis.utils.InflaterWriter.close(InflaterWriter.java:77)
... 11 more
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-95) [Artemis 2.x Upgrade] Client is not able to instantiate destinations by names
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFWIP-95?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil moved WFLY-10054 to WFWIP-95:
-----------------------------------------
Project: WildFly WIP (was: WildFly)
Key: WFWIP-95 (was: WFLY-10054)
Component/s: JMS
(was: JMS)
> [Artemis 2.x Upgrade] Client is not able to instantiate destinations by names
> -----------------------------------------------------------------------------
>
> Key: WFWIP-95
> URL: https://issues.jboss.org/browse/WFWIP-95
> Project: WildFly WIP
> Issue Type: Bug
> Components: JMS
> Reporter: Martin Styk
> Assignee: Martyn Taylor
> Priority: Blocker
> Labels: activemq
>
> Having queue defined as follows
> {code:xml}
> <jms-queue name="InQueue" entries="jms/queue/InQueue java:jboss/exported/jms/queue/InQueue" durable="true"/>
> {code}
> Client is instantiating it directly using its name.
> {code:title=Client}
> HashMap<String, Object> map = new HashMap<String, Object>();
> map.put("host", hostName);
> map.put(TransportConstants.HTTP_UPGRADE_ENABLED_PROP_NAME, true);
> map.put("port", httpPort);
> TransportConfiguration transportConfiguration = new TransportConfiguration(NettyConnectorFactory.class.getName(), map);
> try {
> ConnectionFactory cf = ActiveMQJMSClient.createConnectionFactoryWithoutHA(JMSFactoryType.CF, transportConfiguration);
> Queue orderQueue = ActiveMQJMSClient.createQueue("InQueue");
> connection = cf.createConnection();
> session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
> MessageProducer producer = session.createProducer(orderQueue);
> connection.start();
> ...
> {code}
> Client is not able to send messages to, because {{session.createProducer(orderQueue)}} throws following exception
> {code}
> javax.jms.InvalidDestinationException: Destination InQueue does not exist
> at org.apache.activemq.artemis.jms.client.ActiveMQSession.createProducer(ActiveMQSession.java:326)
> {code}
> This is regression against EAP 7.1.0
> Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10816) Use galleon feature packs in wildfly-testsuite-shared module
by Yeray Borges (JIRA)
Yeray Borges created WFLY-10816:
-----------------------------------
Summary: Use galleon feature packs in wildfly-testsuite-shared module
Key: WFLY-10816
URL: https://issues.jboss.org/browse/WFLY-10816
Project: WildFly
Issue Type: Task
Components: Test Suite
Reporter: Yeray Borges
Assignee: Yeray Borges
wildfly-testsuite-shared is still using legacy feature packs as dependencies. Although those legacy feature packs are only there to bring in the correct dependencies for the test suite, we should be using galleon packs instead.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2795) [DMN Designer] Data-types: Grid: DecisionTable
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2795?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2795:
-----------------------------------
Sprint: 2018 Week 33-35 (was: 2018 Week 36-38)
> [DMN Designer] Data-types: Grid: DecisionTable
> ----------------------------------------------
>
> Key: DROOLS-2795
> URL: https://issues.jboss.org/browse/DROOLS-2795
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> *_Decision Table_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
> - (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
> - (x) {{InputClause}} columns header should show Input Data Type
> - (x) {{InputClause}} columns should support changing the Input Data Type
> - (x) {{OutputClause}} columns header should show Output Data Type
> - (x) {{OutputClause}} columns should support changing the Output Data Type
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2796) [DMN Designer] Data-types: Grid: Context
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2796?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2796:
-----------------------------------
Sprint: 2018 Week 33-35 (was: 2018 Week 30-32)
> [DMN Designer] Data-types: Grid: Context
> ----------------------------------------
>
> Key: DROOLS-2796
> URL: https://issues.jboss.org/browse/DROOLS-2796
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> *_Context_*
> - (x) Grid header _could_ show Output Data Type (for Decision/BKM)
> - (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel
> - (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}})
> - (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}})
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months