Java heap retention due huge numbers of org.jboss.ejb.client.EJBClientContext

Solution In Progress - Updated -

Issue

  • Poor GC performance.
  • GC full collections are not able to reclaim old generation space.
  • Heap analysis shows 1+ million org.jboss.ejb.client.EJBClientContext
  • log file showing this error:
javax.naming.NamingException: No provider URL configured for connection
  at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:196)
  at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:196)
  at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:171)
  at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:171)
  at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:146)
  at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:146)
  at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:122)
  at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:122)
  at org.jboss.as.naming.InitialContext.init(InitialContext.java:107)
  at org.jboss.as.naming.InitialContext.init(InitialContext.java:107)
  at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154)

Environment

  • JBoss Enterprise Application Platform (EAP) 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.