StackOverflow in org.jboss.wildfly.naming.client during deployment

Solution Verified - Updated

Environment

  • JBoss Enterprise Application Platform (EAP) 7.1

Issue

  • When attempting to deploy our application, it fails due to a StackOverflow with lots of recursion in org.wildfly.naming.client:
Caused by: java.lang.StackOverflowError
	at java.net.URI$Parser.scanIPv4Address(URI.java:3292)
	at java.net.URI$Parser.parseIPv4Address(URI.java:3332)
	at java.net.URI$Parser.parseServer(URI.java:3234)
	at java.net.URI$Parser.parseAuthority(URI.java:3155)
	at java.net.URI$Parser.parseHierarchical(URI.java:3097)
	at java.net.URI$Parser.parse(URI.java:3053)
	at java.net.URI.(URI.java:673)
	at org.jboss.remoting3.EndpointImpl.doGetConnection(EndpointImpl.java:466)
	at org.jboss.remoting3.EndpointImpl.getConnectedIdentity(EndpointImpl.java:433)
	at org.wildfly.naming.client.remote.RemoteNamingProvider.getFuturePeerIdentityPrivileged(RemoteNamingProvider.java:151)
	at org.wildfly.naming.client.remote.RemoteNamingProvider.lambda$getFuturePeerIdentity$0(RemoteNamingProvider.java:138)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.wildfly.naming.client.remote.RemoteNamingProvider.getFuturePeerIdentity(RemoteNamingProvider.java:138)
	at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentity(RemoteNamingProvider.java:126)
	at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:106)
	at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:53)
	at org.wildfly.naming.client.NamingProvider.getPeerIdentityForNamingUsingRetry(NamingProvider.java:105)
	at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNamingUsingRetry(RemoteNamingProvider.java:91)
	at org.wildfly.naming.client.remote.RemoteContext.lambda$lookupNative$0(RemoteContext.java:189)
	at org.wildfly.naming.client.NamingProvider.performExceptionAction(NamingProvider.java:222)
	at org.wildfly.naming.client.remote.RemoteContext.performWithRetry(RemoteContext.java:100)
	at org.wildfly.naming.client.remote.RemoteContext.lookupNative(RemoteContext.java:188)
	at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
	at org.wildfly.naming.client.AbstractFederatingContext.list(AbstractFederatingContext.java:276)
	at org.wildfly.naming.client.store.RelativeFederatingContext.listNative(RelativeFederatingContext.java:78)
	at org.wildfly.naming.client.AbstractFederatingContext.list(AbstractFederatingContext.java:274)
	at org.wildfly.naming.client.AbstractFederatingContext.list(AbstractFederatingContext.java:42)
	at org.wildfly.naming.client.AbstractFederatingContext.list(AbstractFederatingContext.java:280)
	at org.wildfly.naming.client.store.RelativeFederatingContext.listNative(RelativeFederatingContext.java:78)
	at org.wildfly.naming.client.AbstractFederatingContext.list(AbstractFederatingContext.java:274)
	at org.wildfly.naming.client.AbstractFederatingContext.list(AbstractFederatingContext.java:42)
	at org.wildfly.naming.client.AbstractFederatingContext.list(AbstractFederatingContext.java:280)
	at org.wildfly.naming.client.store.RelativeFederatingContext.listNative(RelativeFederatingContext.java:78)

Resolution

  • Apply JBoss EAP 7.1 cumulative patch 4 or later

Root Cause

SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.