[jboss-jira] [JBoss JIRA] (WFLY-10813) OutOfMemory error when trying to display resource adapters in web console
Helena Knyttlová (Jira)
issues at jboss.org
Tue Apr 30 09:10:00 EDT 2019
[ https://issues.jboss.org/browse/WFLY-10813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728256#comment-13728256 ]
Helena Knyttlová edited comment on WFLY-10813 at 4/30/19 9:09 AM:
------------------------------------------------------------------
Our resource adapter configuration looks like this:
{panel:title=Resource Adapter}
<subsystem xmlns="urn:jboss:domain:resource-adapters:5.0">
<resource-adapters>
<resource-adapter id="App">
<archive>
App-ear-1.11.ear#App-rar-1.11.rar
</archive>
<connection-definitions>
<connection-definition class-name="some.package.ManagedConnectionFactory" jndi-name="java:/eis/app" enabled="true" pool-name="app">
<pool>
<max-pool-size>100</max-pool-size>
</pool>
<timeout>
<idle-timeout-minutes>5</idle-timeout-minutes>
</timeout>
<validation>
<background-validation>false</background-validation>
</validation>
</connection-definition>
</connection-definitions>
</resource-adapter>
....
{panel}
If you cannot reproduce it, you can probably close this. It can be some problem only on our server.
was (Author: obludik):
Our resource adapter configuration looks like this:
{panel:title=My title}
<subsystem xmlns="urn:jboss:domain:resource-adapters:5.0">
<resource-adapters>
<resource-adapter id="App">
<archive>
App-ear-1.11.ear#App-rar-1.11.rar
</archive>
<connection-definitions>
<connection-definition class-name="some.package.ManagedConnectionFactory" jndi-name="java:/eis/app" enabled="true" pool-name="app">
<pool>
<max-pool-size>100</max-pool-size>
</pool>
<timeout>
<idle-timeout-minutes>5</idle-timeout-minutes>
</timeout>
<validation>
<background-validation>false</background-validation>
</validation>
</connection-definition>
</connection-definitions>
</resource-adapter>
....
{panel}
If you cannot reproduce it, you can probably close this. It can be some problem only on our server.
> 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: Management, Web Console
> Affects Versions: 10.0.0.Final, 13.0.0.Final
> Reporter: Helena Knyttlová
> Assignee: Harald Pehl
> Priority: Minor
> Attachments: standalone-full-ha.xml
>
>
> 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.12.1#712002)
More information about the jboss-jira
mailing list